- Products & Services
- Retailer Services
- Become a Partner
- Request a Demo
- Try Salsify
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 meanings ascribed to them in the Terms of Service, as the case may be.
The objectives of this document are the following:
The goals for this project as identified by Customer and Salsify:
This SOW is designed to support the onboarding effort required when existing Salsify customers are looking to syndicate to GDSN through Salsify to the Salsify GDSN data pool.
Salsify will design the data model to support the GS1 standards for content requirements, data structure and appropriate trade item logistical hierarchies when syndicating to a GDSN data pool. During the data model configuration phase Salsify will work with the customer to analyze their current configuration, source data in order to update Salsify configuration, which may involve updating a product identifier property, creating new products to represent different hierarchy levels, or other architectural options.
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:
Salsify will work with Customer personnel to perform testing of GDSN channel mappings and syndication to the Salsify GDSN data pool. Salsify will also configure a daily report to share publish and error information with Customer users.
Provide one overview session and supporting documentation for appropriate Customer personnel in content validation. The purpose of this session will be to review key decisions made during the GDSN configuration and the process designed supporting the ongoing syndication to GDSN. This session typically lasts thirty minutes and is expected to be in addition to the standard training courses.
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 an 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.
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. Upon meeting the completion criteria Salsify will deem the functionality delivered and complete. The delivered functionality will then fall under the standard warranty as defined in this SOW.
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; provided that 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.
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 SOW, where the change process will be followed as described in this document.
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):
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:
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):