Statement of Work

Base Activation - Single Digital Shelf


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.


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


  • Centralize content into a single platform
  • Activate and Enrich content on key retailer

Scope of Work


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, the ability to distribute to a key digital shelf, and system training and enablement allowing your team to self-manage the Salsify platform. 

Onboarding Services

Data Model / Content Import Milestone

Data Model Discovery &  Advisory

Following delivery by Customer of a representative data set that consists of all properties required for developing a data model, 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 onboarding.
  • Review and confirmation on product identifiers, data types, category hierarchy, property definitions, property groups, property permissions focused on Customer’s endpoint requirements and filename conventions for digital assets.
  • Review and confirmation of Customer’s downstream objectives and requirements for product content and assets.
  • Best practice around configuration of a data model within Salsify focused on source 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 data requirements. As part of this milestone, Salsify will configure the following:

  • Product Hierarchy
    • One (1) product inheritance hierarchy to be used across all product categories, up to four (4) levels in depth.
  • Localization
    • Up to five (5) locales in Customer's Salsify instance. A locale is defined as a language-country combination such as 'English - Canada', and 'French - Canada', or as a language without a country designation such as 'English'.
    • Up to fifty (50) localized properties, inclusive of localized digital asset properties.
  • Digital Assets
    • Up to twelve (12) assets per product, across up to twelve (12) digital asset properties; 360 spins are considered a single asset.
  • Security
    • Up to five (5) security policy groups. Security policy groups are defined as groups of users (by role) that are able to see various entities such as groups of products, digital assets, and channels  in Salsify.
    • Up to ten (10) user groups defined by the level of access that the user should have. User groups are defined as groups of users (by role) that have varying levels of permissions (create, read, updated, delete) throughout Salsify. 

Initial Content Loads 

Once the data model is complete, Salsify will work with Customer to load content into Salsify from Customer’s sources, including up to three (3) different content sources with up to five (5) files per source such as copy, logistics data, and other data relevant to ecommerce. 

In addition to these three (3) content sources, Salsify will perform one (1) manual upload of Customer-provided digital assets and associated metadata from a single source, as needed. As part of the initial digital asset loading process, Salsify will link digital assets to existing products based on a consistent file naming convention inclusive of the product ID, subject to Assumptions defined below. Salsify will link assets based on up to twenty-five (25) variations of the file name. 

Ongoing Content Feeds

Salsify will configure an automated / semi-automated feed of product content from an upstream system as long as Customer is able to schedule an export of Salsify-importable data from that upstream system, per the relevant Assumptions and Customer Responsibilities defined below.

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 single-tab format (.xlsx or .csv) on a Customer or Salsify 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 configure a digital catalog to provide an additional visual aide to support Customer with review of the configured data model and imported content and digital assets. 

Once all configuration has been completed and approved, Salsify will provide one thirty-minute 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 session is in addition to the standard training courses.

Syndication Milestone

The configuration and testing of one (1) retail digital shelf for one locale and up to three (3) retailer-defined product categories is included as part of this implementation. For each of the configured channels, Salsify will publish via the best available method; this could be an available connection, or by flat file and use of an SFTP server. As part of this milestone, Salsify will closely involve core Customer project team members on how to manage and add additional digital shelves. 

Salsify will complete the following work for each of the in scope retail digital shelf: 

Requirements Gathering

For the identified retail digital shelf, Salsify will review the retailer template and requirement information provided by Customer.  Remote calls will be conducted with Customer’s project team to understand the requirements and mappings for each of the selected channels.  

Readiness Report Setup

A new Readiness Report will be configured based on each of the retail digital shelf requirements provided by Customer to provide users visibility into the completeness of their data and how ready they are to publish to each of the digital shelves.

Mapping / Configuration 

Salsify will perform the following activities as part of the mapping / configuration of the retail digital shelf: 

  • Map Customer’s category hierarchies to meet the retail digital shelf requirements.
  • Configure mappings of product content to channel-specific attribute requirements across product categories.
  • Conduct a review session of the mapped channel(s) with Customer's personnel and update mappings as necessary.
  • Identify and communicate gaps in required attributes to Customer's personnel.
  • Work with Customer to identify the process or steps necessary for Customer to fill required content gaps for products and the timing related to filling those gaps in order to be ready for syndication.


Salsify will perform the following activities in support of publishing content to identified digital shelves:

  • Support Customer with one publish to the retailer portal for the selected digital shelf, inclusive of any products that have all required content available and are approved to be published at completion of mapping; publishing will use the method available between Salsify and the retailer.
  • Provide feedback to Customer on the status of the publish and troubleshoot any errors.

Customer will provide Salsify up to thirty (30) products across the retailer-defined categories for testing and verification

Syndication, Content Validation Training & Syndication Process Review

Salsify will provide one overview session and supporting documentation for appropriate Customer personnel. 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 thirty minute session is in addition to the standard training courses.

Following the publication by Salsify and the review, Customer may update the channel to include a broader set of products and attributes, if needed.


** See ‘Appendix A’ for more details about Salsify and Customer responsibilities for setting up initial and subsequent digital shelves.

Insights Milestone

Insights Configuration

Salsify will gather the necessary requirements to complete the configuration and enablement of all available Insights reports. Once all available Insights reports have been configured, Salsify will provide an overview of each report to Customer. 

Salsify Rollout Support

In addition to Milestones outlined above, Salsify has also included rollout support time with an implementation consultant. Salsify will schedule two (2) remote calls weekly for four (4) consecutive 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:

  • Content management guidance (i.e. advising on data modeling, loading content & digital assets into Salsify, and automation of content feeds)
  • Syndication guidance (i.e. advising on setting up channels, channel mapping, and publishing)
  • People, Process and Organizational Setup (i.e. advising on configuring lists, users, groups, permissions, and establishing workflows to foster internal collaboration)
  • Sales enablement (i.e. advising on setting up digital catalogs, lightboxes, and sell sheets)
  • Technical guidance (i.e. advising on writing formulas, and computed properties.


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).

Project Management and Communication

Project Management

Salsify will assign a Project management resource that works as the primary project coordinator and point of contact for activities related to this project. The project manager will be responsible for:

  • Project planning and timeline management
  • Project team communication and status reporting
  • Salsify resource management 
  • Deliverable tracking

Project Communication Methodology

Throughout the project, Salsify will communicate with Customer on a regular basis.  These touchpoints ensure visibility and awareness of project deliverables and timelines.  The following are details around the type of communication, frequency, details on what will be covered and duration of the communications.










  • Introduction to Salsify
  • Identify Key Dates/Dependencies
  • Customer Deliverables & Scope Review
  • Next Steps
  • Salsify Project Manager
  • Salsify Implementation Consultant
  • Customer Project Team

60 Mins

Weekly Technical/ Status Call



Project Status

  • Highlight Risks & Deliverables 
  • Review Project Plan and Timeline 


  • Requirements Gathering
  • Address Technical Questions
  • Configuration Reviews
  • Customer Feedback
  • Milestone Functionality Demos
  • Consult on best practices 
  • Salsify Project Manager
  • Salsify Implementation Consultant
  • Customer Project Team

90 Mins

Project Tracking



  • Status Recap notes
  • Deliverable Tracking
  • Project Plan Updates
  • Decision Tracking
  • RAID Log
  • Follow up Communication
  • Resource Coordination
  • Salsify Project Manager
  • Customer Project Manager


Project Wrap Up & Post Onboarding Introduction


One Time

  • Final Project Review
  • Introduction to Post-Onboarding Support Team 
  • Salsify Post-Onboarding Support Team
  • Salsify Project Manager
  • Salsify Implementation Consultant
  • Customer Project Team

30 Mins

Project Sponsor Meetings



  • High Level Project Status & Timing
  • Key Risks & Mitigation Strategy
  • All Key Stakeholders 

30 Mins



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.


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 Customer’s source data and retail digital shelf requirements
    • Initial data imported from content sources
    • Ongoing feeds of content configured, if applicable
    • Initial asset upload and linking complete, if applicable
    • Security groups and user groups configured, if applicable
  • Data model and imported content overview completed
  • Fully configured, mapped and tested channel(s) supporting one (1) key retail digital shelf

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 your 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 content extracts in a CSV or single-sheet tabular XLSX file export for up to three (3) content sources that are representative of Customer’s content and properties; this will be used to define and configure Customer’s data model, and populate the content in Salsify.
    • Identifying a unique product ID or set of potential unique product IDs that exist within each upstream system or file provided as a data source per each relevant level of the product hierarchy (i.e. Material Number for parents, UPCs for SKUs, etc.)
    • Defining product identifiers, data types, category hierarchy and taxonomy, and properties.
    • A consistent naming convention across assets that reference a consistent product identifier and property identifier. 
    • Providing digital assets as files (i.e. .tiff, .png, .jpeg, .mp4), file archives (i.e. .zip), or as publicly accessible URLs in a CSV or single-sheet tabular XLSX format.
    • Additional configuration of localized properties beyond the initial fifty (50).
    • Manual asset loads following the three (3) initial loads.
    • If Customer requires ongoing feed(s) for this project, Customer must have one of the  following capabilities; if these are not feasible, Customer will be responsible for either manually importing updated data on an ongoing basis, or building an automated process to import from an upstream system:
      • Ability to schedule an export of Salsify-importable data from the upstream system, delivered to Salsify's SFTP server. 
      • If Customer is unable to deliver source data to Salsify's SFTP server, but is able to deliver a Salsify-importable file to a Customer owned SFTP server, Customer will ensure that:
        • The file is named consistently and without any date/timestamp or other variation.
        • Credentials to access relevant directory on Customer’s SFTP server are provided.
        • The file will be delivered on a regular cadence (daily, weekly, etc.).
        • The delivery cadence will be shared with Salsify for configuration purposes
  • Syndication Milestone:
    • Engagement with any internal or 3rd party resources as needed in support of Syndication efforts. 
    • Providing retailer templates and requirements for the in-scope digital shelf and categories.
    • Providing credentials for any retailer portals needed to publish content and assets.
    • Resource availability to address all content gaps for required attributes in the retailer channel in a timely fashion for a minimum of five products. 
    • Availability and engagement of Customer resources who are familiar with the retailer's processes, limitations, and vendor support model.
    • Ensuring the required data for any product variation / family syndication to this retailer exists in Customer's Salsify instance. 
    • Definition of any required product and brand-specific retailer-specific identifiers, and ensuring those identifiers already exist in Customer's Salsify instance.
    • Filling content gaps after Salsify identifies and communicates gaps. 
    • Ensuring content in Salsify is ready for publication to the identified retailer.


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. 

  • Each data source file will consist of up to two hundred (200) columns, and will have up to three hundred (300) unique data points across all three (3) content sources.
  • Customer will provide Digital Assets with a consistent file naming convention across assets that adhere to the best practices defined below:
    • A product identifier that is available in Salsify and unique across all products -- for instance, Customer’s internal product SKU number or UPC/EAN.
    • A consistent delimiter to support programmatic linking of assets to products, such as an underscore
    • Specification of the property / shot type to which the asset should be assigned (i.e. ‘Front’, ‘Back’, ‘Nutrition’, ‘Ingredients’, etc.)
    • If Customer plans to have more than one image per property / shot type, the name should include an index (i.e. 012345_FRONT_01.jpg)
  • 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
  • Customer has an existing relationship with the retailer identified for this service.
  • The retailer digital shelf and selected categories are supported within Salsify by one of the three following methods:
    • Salsify direct connection
    • Salsify receives category templates with regular updates directly from the retailer
    • Retailer template provided by Customer, products are exported in bulk, and template format is compatible with Salsify's Readiness Report and export capabilities


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:

  • Delay in receiving data
  • Delay with receiving retailer templates
  • Customer does not have team to support implementation
  • Customer does not have Salsify administrator
  • Incomplete content preventing syndication
  • Salsify does not control content from the retailer portal to the retailer website, therefore syndication can only be validated to the retailer portal

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.


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:

  • Automated feeds of product content or digital assets that do not comply with relevant Assumptions defined above.
  • Linking of digital assets with filenames that do not comply with relevant best practices in the Assumptions defined above
  • Product content and image creation, clean-up, curation, and refresh
  • Language translation of product content 
  • Salsify’s configuration does not include seasonal products
  • 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
  • Syndication to non-retailer end points
  • Mapping of multiple digital shelves based on locales 

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. 


Appendix A: Salsify Channel Responsibilities

During the Services Period covered by this services package, responsibilities for setting up Salsify channels will be: 




Collect new/updated channel schema/requirements



Build/update Salsify target schema and channel Readiness Report



Map Customer taxonomy and attributes to channel requirements



Fill in all content gaps for channels required attributes to be ready for syndication



Execute the first publish to channels in the best available method 



Address channels feedback of the initial publish 



Manage publishing and feedback from the channels after the first successful publish



Document the full syndication process for the Salsify Project team



Responsibilities for setting up additional Salsify channels will be:




Collect new/updated channel schema/requirements



Build/update Salsify target schema and channel Readiness Report



Map Customer taxonomy and attributes to channel requirements



Fill in all content gaps for channel required attributes to be ready for syndication



Publish to channel in the best available method 



Address channel feedback of published products 



Document the full syndication process for the Salsify Project team




  •   Responsible – The responsible party owns all activities necessary to complete the corresponding task.
  •   Consult– The consult party provides expertise and information to support the responsible party in completing the corresponding task.