- The Digital Shelf
- 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 meaning ascribed to them in the Terms of Service, as the case may be.
The objectives of this document are the following:
This package is designed to enable and help Customers with setting up a readiness report and the mapping for a digital shelf.
The configuration and testing of a single digital shelf is included as part of this SOW. Multiple channels may be required to support the full syndication requirements of each digital shelf. For each of the configured channels, Salsify will published via the best available method which could be an available connection or by flat file and use of an FTP server.
Salsify will complete the following work for the in scope channel:
For the digital shelf Salsify will review the retailer template and requirement information provided by Customer during the planning phase of this project.. Conduct remote calls with your project team to understand the requirements and mappings for the channel selected.
Configure a new Readiness Report based on the digital shelf requirements provided by the Customer which will provide users visibility into the completeness of their data and how ready they are to publish to each of the digital shelves.
Provide one overview session and supporting documentation for appropriate Customer personnel in content validation and the defined syndication process. The purpose of this session will be to review key decisions made during the syndication milestone and how to publish to key digital shelves.. This session typically lasts thirty minutes and is expected to be in addition to the standard training courses.
** See ‘Appendix A’ for more details about Salsify and customer responsibilities for setting up this initial digital shelve and subsequent ones beyond the scope of this SOW.
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.
The following completion criteria have been defined and agreed to by the 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):