Audience: Designer Brands Canada Inc suppliers

This page contains documents that are unique for suppliers connecting with Designer Brands Canada Inc on the platform. The documents on this page have been customized for Designer Brands Canada Inc suppliers and should be used during the onboarding process and when receiving live orders.

For questions related to the Designer Brands Canada Inc drop-ship program, please reach out to your brand's Designer Brands Canada Inc merchandising representative.

For onboarding support, please email the Onboarding team at dscopartnersetup@rithum.com.

For production support, check out Rithum’s supplier documentation or reach out to our Software Support team.

Onboarding with Rithum

To learn more about the onboarding process and your next steps, see: 

• Joining the Rithum network
• About Rithum Solutions

Required Fields by Workflow

Designer Brands Canada Inc requires certain fields for inventory, cancel, shipment, and invoice updates. You will need to ensure that you are sending all the required fields for this program. The document below outlines those required fields by workflow.

Designer Brands Canada Inc - Required Fields by Workflow

Excel Templates for Each Workflow

If you would like a description of the required fields listed in the document above, or if you plan on using Excel files for your feeds, the templates below are available for you to use.

Designer Brands Canada Inc - Inventory Upload Template 
Designer Brands Canada Inc - Cancel Upload Template 
Designer Brands Canada Inc - Shipment Upload Template 
Designer Brands Canada Inc - Invoice Upload Template

EDI Documentation

If you are going to exchange EDI documents with Rithum for Designer Brands Canada Inc, you will use the standard EDI specifications.

Note: In the EDI specifications, there are two versions for the 850 file: 4010 and 5010. For Designer Brands Canada Inc, we recommend you use the 5010 version for 850 files. All other files (846, 856, 870, 810) will use the 4010 version.

API Documentation

If you are going to exchange transactions via API, you will use the V3 API specifications. 

Resources