Add-on Digital Catalog Configuration Services
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:
This service package includes the configuration of one (1) digital catalog by a Salsify consultant.
Salsify will perform a discovery session with Customer’s project team to determine the required information and set up for a single digital catalog, which may include product data, clickable banners, and digital asset downloads.
Salsify will configure a single digital catalog for Customer containing up to fifty (50) properties, supporting one (1) level of the Salsify product hierarchy, and for one (1) locale, based on the information gathered during the discovery.
Salsify will provide one overview session with the appropriate Customer personnel. The purpose of this session will be to review key decisions made during the digital catalog milestone. This thirty minute session is in addition to the standard training courses.
This project is estimated at 1-2 months from project kick-off to Go-live. This project timeline is an estimate based on the activities outlined above. 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. 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.
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.
As part of this engagement, Customer is responsible for:
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.
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):