Salsify Logo Vertical-highres

Statement of Work

Foundation Services Package + GDSN

Introduction

This Statement of Work (“SOW”) is subject to the attached Order Form with the associated Terms of Service and attachments between Salsify and Customer. Capitalized terms not otherwise defined herein will have the meaning ascribed to them in the Terms of Service, as the case may be. 

SOW Term. The Services shall commence on the date set forth on the Order Form and shall continue until the earlier of: (i) completion of the Services as outlined in the Completion Criteria section or (ii) the termination date set forth on the Order Form.

Objective

The objectives of this document are the following:

  • To gain agreement between Customer and Salsify on the project scope and requirements for the work described in this SOW
  • To serve as the blueprint for what will be delivered

Project Overview

This service package is designed to provide a Salsify led onboarding focused on the set up and enablement of one of your operating units. The Salsify project team will perform hands-on configuration of the Salsify platform based on the services outlined in this SOW and Customer-defined objectives. At the end of this onboarding period, customers will have centralized product content including digital assets, a standard catalog configured to provide a visual review of content, data modeled to support GDSN requirements, syndication to trade partners through a GDSN data pool and training and enablement allowing your team to self-manage the Salsify platform. 

Scope of Work

Service Activities

Salsify will perform the following services as part of this SOW:

Data Model / Content Import Milestone

Data Model Discovery &  Advisory

Salsify will conduct a discovery session to review and consult with Customer on the following topics:

  • Perform analysis on customer provided data to validate that key data requirements are met and data is complete for GDSN GS1 standards.
  • Review and confirmation on product identifiers, data types, category hierarchy / taxonomy, property definitions, property groups, property permissions focused on Customer’s retailer syndication and filename conventions for digital assets.
  • Best practice around configuration of a data model within Salsify focused on source system data.

Data Model Configuration

Based on the information gathered during the discovery phase, Salsify will configure Customer’s data model within Salsify. The data model will account for properties required to support source systems and GDSN requirements. Salsify will also configure a readiness report for Customer which will allow the Customer team to evaluate content completeness and quality against both GDSN and Customer internal content standards. 

Initial Content Loads 

Once the data model is complete, Salsify will work with Customer to load content into Salsify from Customer’s source system(s),  including up to 3 different data feeds that are expected to contain copy and digital media. As part of the content loading process, Salsify is able to link digital assets to existing products based on a consistent file naming convention inclusive of the product ID. Salsify will link assets based on up to 25 variations of the file name. If additional naming conventions exist, additional effort may be required to include all variations. 

Ongoing Content Feeds

After the initial content load is complete, Salsify will work with Customer to set up a semi-automated data feed process where Customer can place new or updated product information in a flat file format (.xlsx or .csv) on a Salsify provided SFTP server. This process will consume files placed on the SFTP and add or update product information in Salsify. 

Data Model and Content Import Review

Salsify will also configure a digital catalog to provide an additional visual aide to support Customer with review of the configured data model and imported content. 

Once all configuration has been completed and approved, Salsify will provide one overview session and supporting documentation for Customer. The purpose of this session will be to review key decisions made during the content import milestone and the process designed to import content in an ongoing fashion. This thirty minute session is in addition to the standard training courses.

GDSN Syndication

As part of this package, Salsify will configure, map and support publishing to GDSN trade partners. 

Syndication Mapping and Configuration

Salsify will configure one or more Salsify channels for publishing to GDSN trading partners. For each GDSN channel, Salsify will work with Customer product experts to:

  • Configure Readiness Reports based on channel requirements provided by Customer
  • Map Global Classification Codes (GCC) or customer category hierarchies to GS1 GCC standards. 
  • Map of Customer product content to GDSN dependent, retailer-independent, and retailer-specific GDSN attribute requirements across product categories
  • Identify gaps in required GDSN attributes and advise the customer project team to adjust content loads, as well as configure workflows to remediate content gaps

GDSN Training & Documentation

Salsify will provide Customer with a live training session, documentation to outline the specific configurations that were completed as part of this GDSN onboarding and configuration of a daily report to share publish and error information with Customer. During this session, Salsify will ensure Customer is able to manage GDSN configuration post onboarding. 

Training

Customer’s project team will complete the Salsify Standard Platform Training curriculum, which provides foundational Salsify skills that ensure Customer can configure and administer Salsify on a go-forward basis. The Salsify Standard Platform Training curriculum includes training on modules within the Salsify platform, and is accessible via on-demand recordings (included with Customer’s Salsify subscription).

Timing

This project is estimated at 3-5 months from project kick-off to Go-live. This project timeline is an estimate based on the activities outlined above. The assigned Salsify Consultant will create a detailed project schedule upon project initiation based on actual assigned resource availability and project dependencies. While Salsify will try to adhere to the estimated project timeline, many factors such as delays in Customer providing deliverables or changes in scope can affect both the individual task dates and the projected go-live date.

Testing

A Salsify engineer/consultant will validate that the functionality delivered meets the completion criteria as defined in this SOW.  

Following successful Salsify testing, it is expected that a Customer resource will also test and validate that the delivered functionality meets the requirements as defined in this SOW or provided use cases. All feedback will be reported to Salsify so that resolution of defects can be tracked and resolved. 

Completion Criteria

The following completion criteria have been defined and agreed to by Customer and Salsify. Salsify will ensure the delivered functionality meets the criteria as defined below.  Customer will have five (5) business days of each milestone delivery to provide Salsify feedback identifying and describing in reasonable detail any defects within the delivered functionality. The functionality shall be considered complete upon the later of the five day feedback period and the update of the requested modification.

  • Data model configured to support customers source data and GDSN requirements
  • Data imported to configured data model, including copy and digital assets
  • GDSN data pool syndication channel(s) mapped and tested
  • Data model and imported content overview completed
  • GDSN training and documentation completed

Warranty for Services

Customer must report any deficiency in Services to Salsify in writing within thirty (30) days of completion of such an applicable portion of the Services (the “Warranty Period”).  Salsify will promptly remedy and support any deficiency in the Services reported to Salsify during the Warranty Period; Salsify will have no obligation to provide, remedy or support any requirements or functionality which are outside the scope of this Statement of Work.  

Following the expiration of the Warranty Period, Salsify will use commercially reasonable efforts to remediate any bugs or defects in the Services for so long as Customer is covered by an active paid subscription to Salsify’s proprietary Salsify Platform.

Customer Responsibilities

As part of this engagement, Customer is responsible for:

  • Availability of key personnel (“Project Team”) for the duration of the Services Period. This includes:
    • A primary point of contact that can align necessary resources as required in order to complete any tasks determined as part of the scope of services defined in this SOW.
    • Organization of a core Project Team, including at least one Salsify administrator to drive ongoing administration of Customer’s Salsify account, including additional configuration beyond the initial implementation configuration outlined in this package.
    • Completion of Salsify training.
    • Additional personnel with expertise in source systems to be integrated into Salsify, expertise in customer/account relationships, and expertise in Customer’s product content to work closely with Customer’s Salsify administrator and Salsify Project Team on integrating source systems, mapping product categories, mapping product attributes, and other implementation areas as appropriate.
  • Content Import Milestone: 
    • Providing product identifiers, data types, category hierarchy / taxonomy, and property definitions.
    • Translation of content for all localized data feeds.
    • Providing a consistent naming convention across assets that reference a consistent product identifier and property identifier. For example, an asset filename can include Customer’s product SKU and image type delimited by underscore: 1234_Front.jpg.
    • Providing content extracts in a CSV (comma-separated value) or single-sheet tabular XLSX file export. 
  • GDSN
    • Customer will be responsible for providing any necessary content to facilitate mapping to GDSN requirements, either via import or directly within customer's Salsify account
    • Customer will provide a list of all required GLNs for trading partners receiving Customer’s data 
    • If switching data pool providers, Customer must have an active license with existing provider until the cut over to Salsify’s data pool is complete. 
    • Customer maintains an active GDSN license for the data pool for publishing content to GDSN recipients.

Assumptions

Salsify will deliver the services described in this document subject to the assumptions listed in this section. Invalidation of these assumptions may alter the scope of services required for successful implementation/administration of the Salsify platform and may require a change order or an additional SOW, where the change process will be followed as described in the “Change Control Process” section of this document. 

  • If Customer does not have all content based on the retailer requirements, Salsify will not be able to publish until the content is complete. If the required content can not be added or updated within ten (10) days of the channel mapping being completed, the channel mapping will be considered complete.
  • After initial configuration of Customer-provided list of trading partners and delivery of Customer GDSN training, Customer will be responsible for adding trading partners to the GDSN publish process

Risks

In addition to those mentioned elsewhere in this SOW, the following risks have been identified that may impact the timing or success of this project (this is not necessarily a complete list):

  • Delay in receiving data
  • Customer does not have data fulfilling GDSN requirements
  • Customer does not have team to support implementation
  • Customer does not have Salsify administrator

Change Control Process

The below identifies the change control process that will be utilized when Customer requires a deliverable that is not currently in scope as part of this SOW and is required to be delivered as part of this initial project. If the new request can be delivered outside of this project, then a new SOW will be issued:

  • Stakeholders recognize the need for a possible change.
  • The need is communicated to the Project Team.
  • The Project Team captures and documents the change order in the form of an SOW, change order, or order form.
  • Salsify provides a cost estimate for the change.
  • The change order is reviewed by Salsify & Customer representative(s) and is either rejected, or mutually approved.
  • Project team communicates the status of the change order to stakeholders, documents action, and closes the request.
  • If the Change Order is approved, any appropriate updates to the project plan or project costs are made and communicated.

Out-of-scope

Services beyond the scope of this document will be considered out of scope and will require a change order or an SOW to be issued. All change orders will follow the change control process as defined in this document. The following items have been identified as out of scope (this is not necessarily a full list):

  • Product content and image creation, clean-up, curation, and refresh
  • Language translation of product content 
  • Ongoing Salsify platform administrative services, including additional hands on configuration of the Salsify platform, such as data modeling, imports, and end to end syndication configuration outside of what is defined in this SOW
  • Custom engineering services

Additional Terms

  • This Statement of Work is governed by the attached Order Form with the associated Terms of Service and attachments.
  • Unless otherwise agreed or specified, all services are performed remotely.
  • Unless executed, this SOW and services terms are valid for up to 30 days from the date presented to Customer. Salsify then reserves the right to make any necessary revisions to this SOW.
  • If travel is required, all travel costs will be approved by the customer prior to booking.