Last Updated: April 12, 2024
- General.For the specific Launch Services package included in the OF, Provider will provide the integration and setup services described in more detail below, to assist Customer with setting up certain elements of Customer’s account with Provider (“Launch Services”). During the Services Term applicable to the Launch Services, as indicated on the OF, Customer will be assigned to a Provider launch team (“Launch Team”) and will be able to contact its Launch Team via email. Each capitalized term not defined below has the meaning given to it in the Terms or in the relevant OF, as applicable.
- What’s Required from Customer.
- Prerequisites. In order for Provider to provide the Launch Services, in addition to the requirements set forth in the applicable OF, Customer must:
- Set up applicable shipping tables, tax calculations, and checkout processes.
- Complete necessary revisions to its inventory data (quality and accuracy of Customer’s inventory data can affect success of listings).
- Have stock available, be ready to ship orders, and have a clear and established order fulfillment plan.
- Have one SKU/inventory number per item relationship. SKU format and limits are based on each Channel’s requirements. Customer must provide inventory data and attributes required by a Channel (e.g., variation data, catalog data, GTIN data such as UPCs, EANs, ISBNs and other attributes required by such Channels as applicable).
- Be familiar with software tools to manage Customer’s catalog data and uploads to Provider (e.g., Excel or similar spreadsheet applications, PIM, ERP, OMS, etc.).
- Be an established Channel seller in at least one locale.
- Provide a URL for hosted images in proper format (https://example.jpeg) or via other collaborative sharing tools acceptable to Provider and the applicable Channel (i.e., FTP transfer, shared drivers, etc.) and provide Channel with images that comply with the requirements for their category and product, including but not limited to, size and quality (e.g., some Channel categories require images with white backgrounds, some categories prohibit the use of mannequins in images).
- Provide SKU parent/child variation relationships as required by Provider for SKU attributes and other items that apply.
- Provide data ready to import and in a standard data format acceptable to Provider (e.g., CSV, headers, and full data feeds).
- Provide at least one point of contact who can make decisions on behalf of Customer and who is able to communicate to Provider in English.
- Resources. The Launch Services offered by Provider is only a supplement to the documentation available on Provider’s knowledge center (knowledge.rithum.com/kc) (“Knowledge Center”) and Customer is responsible for familiarizing its personnel with this resource. All Provider documentation and technical support is provided via Provider’s Developer Network Google Group/Forum (developer.rithum.com).
- Posting Account. The Launch Services are limited to one account used within the Provider platform to post information on Channels.
- Prerequisites. In order for Provider to provide the Launch Services, in addition to the requirements set forth in the applicable OF, Customer must:
- Launch Services Packages.
| Launch Complete (full Provider platform integration with Channel launch) | ||
| Deliverables | Provider will provide (via email) Customer with a project plan and weekly status updates that outline due dates and task ownership. During the Services Term applicable to the Launch Services, Provider will:
Upon project completion, the Launch Team will transition Customer to Provider’s customer support team, who will then handle technical and other support case inquiries. | |
| Launch Team Lead | Launch Manager | |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Internal kickoff call | Provider |
| Project kickoff with Customer | Provider, Customer | |
| Setup Channel account, including setting up shipping and returns (including applicable shipping tables); Customer reviews Knowledge Center articles for Channel | Customer | |
| Set up applicable legal and tax prerequisites (e.g., setting up VAT/applicable tax) | Customer | |
| Input Channel credentials into Commerce Solutions for Brands | Customer | |
| Review incoming Customer data from Channel | Provider | |
| Update Customer data set for Channel | Customer | |
| Confirm Channel approval and perform Channel health check | Provider | |
| Mapping for incoming data (e.g., design, price, quantity, content), orders and fulfillments design, and order adjustments design | Provider, Customer | |
| 2 – Provider Platform Integration | Map incoming data templates for Channel(s) | Provider |
| Finalize pricing and quantity update process | Customer | |
| Finalize content update process | Customer | |
| Test order processes with test SKU set | Provider, Customer | |
| Test fulfillment processes with test SKU set | Provider, Customer | |
| Test order adjustment process with test SKU set | Provider, Customer | |
| 3 – Channel Integration | Where applicable, establish migration path for Amazon, eBay, Zalando, and Shopify Channels | Provider, Customer |
| Develop pricing plan | Customer | |
| Create pricing plan logic (and other business rules) | Provider | |
| Map to Channel template in Commerce Solutions for Brands | Provider | |
| 4 – Channel Go-Live | Activate Channel feed with test SKU set | Provider, Customer |
| Troubleshooting and error resolution (Customer consults Knowledge Center as needed) | Provider, Customer | |
| Re-testing as needed | Provider, Customer | |
| 5 – Data Optimization | 4 weeks of post-launch training, which includes:
| Provider, Customer |
| Launch remaining Channels (see Steps 3 and 4) | Provider, Customer | |
| Call to introduce Customer to Provider support | Provider, Customer | |
| 6 – Q&A; Delivery | 30-day period for Customer inquiries. Launch Services delivered. | Provider |
| Launch Channel Expansion (third-party Channel launch only) | ||
| Deliverables | Provider will provide Customer (via email) with a Project Plan and regular status updates at a cadence agreed to by the parties not more frequently than weekly, which outline due dates and task ownership. During the Services Term applicable to the Launch Services, Provider will:
Upon project completion, the Launch Team will transition Customer to the Provider’s customer support team, who will then handle technical and other support case inquiries. | |
| Launch Team Lead | Launch Manager | |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Project kickoff with Customer | Provider, Customer |
| Setup Channel account, including setting up shipping and returns (including applicable shipping tables); Customer reviews Knowledge Center articles for Channel | Customer | |
| Set up applicable legal and tax prerequisites (e.g., setting up VAT/applicable tax) | Customer | |
| Input Channel credentials into Commerce Solutions for Brands | Customer | |
| Review incoming Customer data from Channel | Provider | |
| Update Customer data set for Channel | Customer | |
| Confirm Channel approval and perform Channel health check | Provider | |
| 2 – Provider Platform Integration | Test order processes with test SKU set | Provider, Customer |
| Test fulfillment processes with test SKU set | Provider, Customer | |
| Test order adjustment process with test SKU set | Provider, Customer | |
| 3 – Channel Integration | Where applicable, establish migration path for Amazon, eBay, Zalando, and Shopify Channels | Provider, Customer |
| Develop pricing plan | Customer | |
| Create pricing plan logic (and other business rules) | Provider | |
| Map to Channel template in Commerce Solutions for Brands | Provider | |
| 4 – Channel Go-Live | Activate Channel feed with test SKU set | Provider, Customer |
| Troubleshooting and error resolution (Customer consults Knowledge Center as needed) | Provider, Customer | |
| Re-testing as needed | Provider, Customer | |
| 5 – Data Optimization | 4 weeks of post-launch training, which includes:
| Provider, Customer |
| Launch remaining Channels (see Steps 3 and 4) | Provider, Customer | |
| Call to introduce Customer to Provider customer support | Provider, Customer | |
| 6 – Q&A; Delivery | 30-day period for Customer inquiries; Launch Services delivered | Provider |
| Launch Support (add-on hours only) | |
| Scope and Responsibilities | During Services Term applicable to the Launch Services, Provider will provide up to 8 hours of personnel hours over 4 calendar weeks, which may comprise hands-on consulting services within Customer’s Commerce Solutions for Brands account, email support, and/or phone calls. Phone calls are limited to 1 hour per calendar week. |
| Launch Team Lead | Launch Manager |
| First Party Launch | ||
| Deliverables | Provider will provide Customer (via email) with a project plan and weekly status updates that outline due dates and task ownership. During the Services Term applicable to the Launch Services, Provider will:
Upon project completion, the Launch Team will transition Customer to Provider’s customer support team, who will then handle technical and other support case inquiries. | |
| Launch Team Lead | Launch Manager | |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Add Channel to Customer’s Platform Account | Provider |
| Project kickoff with Customer (as needed) | Provider, Customer | |
| Customer provides Provider with end-to-end testing plan | Customer | |
| Customer reviews Knowledge Center articles for Channel | Customer | |
| 2 – Provider Platform Pre-Testing | Assign product items to applicable label in Provider’s platform | Provider |
| Train Customer on template mappings | Provider | |
| 3 – Establish Channel Connection and Pre-Testing | Shares applicable Channel credentials | Provider |
| Enable activity logging in Provider Platform | Provider | |
| Channel confirms credentials and EDI Certificate to Provider | Channel | |
| Channel provides applicable vendor IDs to Provider if Customer cannot provide such IDs | Channel, Customer | |
| Provider and Channel each load applicable certificate to establish connection | Provider | |
| Channel sends test ping/Purchase Order (“PO”) to Provider Platform | Channel | |
| Provider receives and processes ping/PO | Provider | |
| 4 – Validation Testing | PO is accepted by Provider Platform. Provider sends acknowledgement to Channel | Provider |
| Packing slip and shipping labels validated with applicable Channel | Provider | |
| 5 – Go Live | Customer sends confirmation email to Provider that all testing is successful and Channel is ready to activate | Customer |
| Final confirmation on Provider Platform settings | Provider, Customer | |
| Update Channel connection to live production | Channel, Provider | |
| 6 – Q&A; Delivery | Provider confirms data transmissions to Channel are occurring | Provider, Customer |
| Troubleshooting and error resolution for 2 business days | Provider, Customer | |
| Handoff email to introduce Customer to Provider support | Provider, Customer | |
| Fulfillment Solutions Launch | ||
| Deliverables | Provider will provide Customer (via email) with a project plan and weekly status updates that outline due dates and task ownership. During the Services Term applicable to the Launch Services, Provider will:
Upon project completion, the Launch Team will transition Customer to Provider’s customer support team, who will then handle technical and other support case inquiries. | |
| Launch Team Lead | Launch Manager | |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Customer provides credentials for applicable Channel | Customer |
| Provider configures Channel within Provider Platform and upload credentials | Provider | |
| Customer provides quantity file to Provider; Provider uses quantity file to verify credentials with applicable Channel | Provider, Customer | |
| 2 – Establish Channel Connection | Provider adds applicable Channels within Provider Platform | Provider |
| Provider creates Channel Provider Platform label, which will be used to assign to products | Provider | |
| Provider works with Customer to configure applicable settings in Provider’s platform, including shipping mappings | Provider, Customer | |
| 3 – Channel Connection Testing | Provider works with Customer to apply Channel labels to Customer products to be fulfilled by such Channel. Test quantity updates and troubleshoot label errors (e.g., brand and MPN are not matching Channel details) | Provider, Customer |
| Provider works with Customer to create routing rules (e.g., for product costs and shipping cost) and shipping rules in Provider’s platform | Provider, Customer | |
| Provider works with Customer to create minimum cost business rules for bulk edits and set up automated tasks for populating product information | Provider, Customer | |
| Provider works with Customer to test orders from Provider’s platform to applicable Channel | Provider, Customer | |
| Provider confirms successful shipping update; re-testing and troubleshooting as needed | Provider, Customer | |
| 4 – Go Live | Customer adds Channel to its distribution center priority page in the Provider’s platform, which authorizes usage with Provider’s marketplace functionality | Customer |
| Provider and Customer review orders and confirm accurate updates are transmitted to Provider | Provider, Customer | |
| Handoff email to introduce Customer to Provider support | Provider, Customer | |