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 service package is designed to provide a Salsify lead onboarding focused on the set up and enablement of one of your operating units that distributes Enhanced Content to available retailers. The Salsify project team will perform hands on configuration of the Salsify platform based on the services outlined in this SOW and objectives defined in the planning phase. At the end of this onboarding period, customers should have centralized product content including digital asses, data model that supports the creation and distribution of Enhanced Content templates and system training and enablement allowing your team to self-manage the Salsify platform.
Salsify will conduct a discovery session to review and consult with Customer on the following topics:
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 system, product hierarchies and Enhanced Content requirements. Salsify will also configure a readiness report for Customer which will allow the Customer team to evaluate content completeness and quality against Customer internal content standards.
Once the data model is complete, Salsify will work with Customer to identify and load content into the Salsify system from Customer’s source system including up to 3 different data feeds that are expected to include 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.
Salsify will also 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.
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 content import milestone and the process designed to import content in an ongoing fashion. This session typically lasts thirty minutes and is expected to be in addition to the standard training courses.
Salsify will configure up to three (3) Enhanced Content templates as well as train the core project team on how to manage and add additional templates.
Provide one overview session and supporting documentation for appropriate Customer personnel in content validation and the Enhanced Content process. The purpose of this session will be to review key decisions made during the Enhanced Content milestone and how to publish Enhanced Content to the available retailers. This session typically lasts thirty minutes and is expected to be in addition to the standard training courses.
In addition to Milestones outlined above, Salsify has also included rollout support time where an implementation consultant will schedule two (2) remote calls weekly for four (4) weeks following the completion of the services. These calls can be used to cover best practice recommendations on using Salsify and sharing ecommerce expertise. Examples of these topics include:
This project is estimated at 2 - 4 months from project kick-off to Go-live. This project timeline is an estimate based on the activities outlined above above. The assigned Salsify Consultant will create a detailed project schedule during the Planning Phase of the project 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.
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):