- General. For the specific Launch Services package included in the SOW, Rithum will provide the Services described in more detail below to assist Customer with setting up certain elements of Customer’s Rithum Platform account (“Launch Services”). During the Launch Services Period indicated on the SOW, Customer will be assigned and have access (via email) to a Rithum launch team (“Launch Team”). Each capitalized term not defined herein has the meaning given to it in the Terms or in the SOW for Commerce Solution for Brands (previously referred to as “Commerce Core”), as applicable.
- What’s Required from Customer.
- In order for Rithum to provide the Launch Services, Customer is responsible for the following:
- Set up shipping tables and tax calculations where applicable. Checkout occurs on the Network Site.
- Complete any necessary revisions to its inventory data (quality and accuracy of Customer’s inventory data can affect success of listings).
- Be able to accept orders with cleared payments.
- 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 in place. SKU value character is limited based on each Network Site requirements. Customer must provide inventory data and attributes required by a Network Site (for example: variation data, catalog data and Global Trade Identification Number data such as UPCs, EANs, ISBNs and other attributes required by such Network Sites as applicable).
- Be familiar with software tools to manage Customer’s catalog data and uploads to Rithum (i.e., Excel or similar spreadsheet applications, PIM, ERP, OMS, etc.).
- Be approved on Network Sites for which the Launch Services apply and understand Network Site requirements.
- Be an established Network Site 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 the applicable Network Site (i.e., FTP transfer, shared drivers, etc.) and provide Network Site with images that comply with the requirements for their category and product, including but not limited to, size and quality (i.e., some Network Site categories require images with white backgrounds, some categories prohibit the use of mannequins in images).
- Provide parent/child variation relationships as reasonably required by Rithum for SKU attributes and other items that apply.
- Provide data ready to import and in a standard data format (CSV, headers, and full data feeds).
- Perform all work necessary to appropriately integrate with Rithum’s API. All documentation and technical support is provided via Rithum’s Developer Network Google Group/Forum (https://developer.channeladvisor.com).
- Provide at least one single point of contact who can make decisions on behalf of Customer who is able to communicate to Rithum in English.
- Customer acknowledges that the training and launch service offered by Rithum is only a supplement to the documentation available on the Rithum Knowledge Center (https://knowledge.channeladvisor.com/kc) (“Knowledge Center”) and Customer is responsible for familiarizing its personnel with this knowledge base resource.
- The Launch Services are limited to one Posting Account per Network Site. A “Posting Account” means an account used within the Rithum platform to post information on Network Sites.
- Rithum has relied on the requirements above being met by Customer and they form the basis for the project scope, timelines, and Fees for the Launch Services. Customer’s failure to meet these requirements may cause changes to the timeline, Fees, deliverables, and level of effort required, or otherwise impact Rithum’s performance of the Launch Services and Rithum is not responsible for delays, costs, or other obligations resulting from Customer’s failure to meet the requirements above.
- In order for Rithum to provide the Launch Services, Customer is responsible for the following:
- Launch Services Packages.
| Launch Complete (full Rithum Platform integration with Network Site launch) | ||
| Deliverables | Rithum will provide (via email) Customer with a project plan and weekly status updates that outline due dates and task ownership. During the Launch Services Period, Rithum will:
Upon project completion, the Launch Team will transition Customer to Rithum’s customer support team, who will handle technical and other support case inquiries during the relationship. | |
| Launch Team |
| |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Internal kickoff call | Rithum |
| Project kickoff with Customer | Rithum, Customer | |
| Setup Network Site account, including setting up shipping and returns (including applicable shipping tables). Customer reviews Network Site materials provided by Rithum | Customer | |
| Set up applicable legal and tax prerequisites (i.e., setting up VAT/applicable tax) | Customer | |
| Input Network Site credentials into Commerce Solution for Brands | Customer | |
| Review incoming Customer data from Network Site | Rithum | |
| Update Customer data set for Network Site | Customer | |
| Confirm Network Site approval and perform Network Site health check | Rithum | |
| Mapping for incoming data design (price, quantity, content), orders and fulfillments design, and order adjustments design | Rithum, Customer | |
| 2 – Rithum Platform Integration | Map incoming data templates for Network Site(s) | Rithum |
| Finalize pricing and quantity update process | Customer | |
| Finalize content update process | Customer | |
| Test order processes with test SKU set | Rithum, Customer | |
| Test fulfillment processes with test SKU set | Rithum, Customer | |
| Test order adjustment process with test SKU set | Rithum, Customer | |
| 3 – Network Site Integration | Where applicable, establish migration path for Amazon, eBay, Zalando, and Shopify Network Sites | Rithum, Customer |
| Develop pricing plan | Customer | |
| Create pricing plan logic (and other business rules) | Rithum | |
| Map to Network Site template in Commerce Solutions for Brands | Rithum | |
| 4 – Network Site Go-Live | Activate Network Site feed with test SKU set | Rithum, Customer |
| Troubleshooting and error resolution (Customer consult Rithum materials as needed) | Rithum, Customer | |
| Re-testing as needed | Rithum, Customer | |
| 5 – Data Optimization | 4 weeks of post-launch training, which includes:
| Rithum, Customer |
| Launch remaining Network Sites (see Steps 3 and 4) | Rithum, Customer | |
| Handoff call to introduce Customer to Rithum support | Rithum, Customer | |
| 6 – Q&A; Delivery | 30-day period for Customer inquiries. Launch Services delivered. | Rithum |
| Launch Channel Expansion (third-party Network Site launch only) | ||
| Deliverables | Rithum 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 Launch Services Period, Rithum will:
Upon project completion, the Launch Team will transition Customer to the Rithum’s customer support team, who will handle technical and other support case inquiries during the relationship. | |
| Launch Team |
| |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Project kickoff with Customer | Rithum, Customer |
| Setup Network Site account, including setting up shipping and returns (including applicable shipping tables; Customer reviews Network Site materials provided by Rithum | Customer | |
| Set up applicable legal and tax prerequisites (i.e., setting up VAT/applicable tax) | Customer | |
| Input Network Site credentials into Commerce Solutions for Brands | Customer | |
| Review incoming Customer data from Network Site | Rithum | |
| Update Customer data set for Network Site | Customer | |
| Confirm Network Site approval and perform Network Site health check | Rithum | |
| 2 – Rithum Platform Integration | Test order processes with test SKU set | Rithum, Customer |
| Test fulfillment processes with test SKU set | Rithum, Customer | |
| Test order adjustment process with test SKU set | Rithum, Customer | |
| 3 – Network Site Integration | Where applicable, establish migration path for Amazon, eBay, Zalando, and Shopify Network Sites | Rithum, Customer |
| Develop pricing plan | Customer | |
| Create pricing plan logic (and other business rules) | Rithum | |
| Map to Network Site template in Commerce Solutions for Brands | Rithum | |
| 4 – Network Site Go-Live | Activate Network Site feed with test SKU set | Rithum, Customer |
| Troubleshooting and error resolution (Customer consult Rithum materials as needed) | Rithum, Customer | |
| Re-testing as needed | Rithum, Customer | |
| 5 – Data Optimization | 4 weeks of post-launch training, which includes:
| Rithum, Customer |
| Launch remaining Network Sites (see Steps 3 and 4) | Rithum, Customer | |
| Handoff call to introduce Customer to Rithum customer support | Rithum, Customer | |
| 6 – Q&A; Delivery | 30-day period for Customer inquiries; Launch Services delivered | Rithum |
Launch Support (add-on hours only) | |
| Scope and Responsibilities | During the Launch Services Period, Rithum will provide up to 8 hours of personnel hours over 4 calendar weeks, which may comprise of hands-on consulting services within Customer’s Commerce Solutions for Brands account, email support, or phone calls. Phone calls are limited to 1 hour per calendar week. |
| Launch Team | Launch Manager |
| First Party Launch | ||
| Deliverables | Rithum will provide Customer (via email) with a project plan and weekly status updates that outline due dates and task ownership. During the Launch Services Period, Rithum will:
Upon project completion, the Launch Team will transition Customer to Rithum’s customer support team, who will handle technical and other support case inquiries during the relationship. | |
| Launch Team |
| |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Add Network Site to Customer’s Platform Account | Rithum |
| Project kickoff with Customer (as needed) | Rithum, Customer | |
| Customer provides Rithum with end-to-end testing plan | Customer | |
| Customer reviews Network Site materials provided by Rithum | Customer | |
| 2 – Rithum Platform Pre-Testing | Assign product items to applicable label in Rithum Platform | Rithum |
| Train Customer on template mapping | Rithum | |
| 3 – Establish Network Site Connection and Pre-Testing | Shares applicable Network Site credentials | Rithum |
| Enable activity logging in Rithum Platform | Rithum | |
| Network Site confirms credentials and EDI Certificate to Rithum | Network Site | |
| Network Site provides applicable vendor IDs to Rithum if Customer can not provide such IDs | Network Site, Customer | |
| Rithum and Network Site each load applicable certificate to establish connection | Rithum | |
| Network Site sends test ping/Purchase Order (“PO”) to Rithum Platform | Network Site | |
| Rithum receives and processes ping/PO | Rithum | |
| 4 – Validation Testing | PO is accepted by Rithum Platform. Rithum sends acknowledgement to Network Site | Rithum |
| Packing slip and shipping labels validated with applicable Network Site | Rithum | |
| 5 – Go Live | Customer sends confirmation email to Rithum that all testing is successful and Network Site is ready to activate | Customer |
| Final confirmation on Rithum Platform settings | Rithum, Customer | |
| Update Network Site connection to live production | Network Site, Rithum | |
| 6 – Q&A; Delivery | Rithum confirms data transmissions to Network Site are occurring | Rithum, Customer |
| Troubleshooting and error resolution for 2 business days | Rithum, Customer | |
| Handoff email to introduce Customer to Rithum support | Rithum, Customer | |
| Delivery Solutions Launch | ||
| Deliverables | Rithum will provide Customer (via email) with a project plan and weekly status updates that outline due dates and task ownership. During the Launch Services Period, Rithum will:
Upon project completion, the Launch Team will transition Customer to Rithum’s customer support team, who will handle technical and other support case inquiries during the relationship. | |
| Launch Team |
| |
| Steps and Responsibilities | ||
| Step | Task | Responsible Party |
| 1 – Initial Setup | Customer provides credentials for applicable Fulfillment Endpoint | Customer |
| Rithum configures Fulfillment Endpoint within Rithum Platform and upload credentials | Rithum | |
| Customer provides quantity file to Rithum; Rithum uses quantity file to verify credentials with applicable Fulfillment Endpoint | Rithum, Customer | |
| 2 – Establish Fulfillment Endpoint Connection | Rithum adds applicable Fulfillment Endpoints within Rithum Platform | Rithum |
| Rithum creates Fulfillment Endpoint Rithum Platform label, which will be used to assign to products | Rithum | |
| Rithum works with Customer to configure applicable settings in Rithum Platform, including shipping mappings | Rithum, Customer | |
| 3 – Fulfillment Endpoint Connection Testing | Rithum works with Customer to apply Fulfillment Endpoint labels to Customer products to be fulfilled by such Fulfillment Endpoint. Test quantity updates and troubleshoot label errors (ex: brand and MPN are not matching Fulfillment Endpoint details) | Rithum, Customer |
| Rithum works with Customer to create routing rules (ex: for product costs and shipping cost) and shipping rules in Rithum Platform | Rithum, Customer | |
| Rithum works with Customer to create minimum cost business rules for bulk edits and set up automated tasks for populating product information | Rithum, Customer | |
| Rithum works with Customer to test orders from Rithum Platform to applicable Fulfillment Endpoint | Rithum, Customer | |
| Rithum confirms successful shipping update; re-testing and troubleshooting as needed | Rithum, Customer | |
| 4 – Go Live | Customer adds Fulfillment Endpoint to its Distribution Center priority page in the Rithum Platform, which authorizes usage with Rithum Platform marketplace functionality | Customer |
| Rithum and Customer review orders and confirm accurate updates are flowing through Rithum Platform | Rithum, Customer | |
| Handoff email to introduce Customer to Rithum support | Rithum, Customer | |