This page contains documents that are unique for suppliers connecting with Kohl's on the platform. The documents below have been customized for Kohl's suppliers and should be used during both the onboarding process and when receiving live orders.
For onboarding support, please email the Onboarding team at dscopartnersetup@rithum.com.
For production support, check out Rithum’s supplier documentation or email our Software Support team.
Onboarding with Rithum
To learn more about the onboarding process and your next steps, see:
EDI documentation
If you're going to exchange EDI files with the platform, you must use one of the two specifications listed below. The platform also has a standard EDI specification that includes separate 856 and 810 documents. However, when working with Kohl's, only the two specifications listed below are valid.
- If you are new to the Kohl's drop-ship program, you will need to use Rithum’s standard EDI specifications. This is the preferred method. For this spec, Kohl's asks that you ship and invoice on the 810.
- If you have migrated from Kohl's previous drop-ship platform and are using the same (Kohl’s) EDI spec, this spec will have you shipping and invoicing all on the 856. Please reach out to the Onboarding team at dscopartnersetup@rithum.com to have the specification sent to you.
Cancel code mapping
The Cancel Codes that are required by Kohl’s are available by selecting Settings > Mapping Settings > Cancel Code Mapping. The highlighted rows identify the cancel codes that are required by Kohl’s on all supplier-initiated cancel transactions.
Packing slip guide
Packing slips can be downloaded in the platform. If you prefer to create your own packing slips and map fields on the order files from the platform, this document provides instructions for replicating packing slips for Kohl's.
Please note that your packing slip must be approved by the Kohl's Direct Ship team before you can start receiving live orders.
Required Fields
Kohl's and Rithum require certain fields for inventory, cancel, shipment, and invoice updates. The fields in each section are required in order for updates to be accepted in the platform. The document below outlines those fields by workflow.
Partner SKU
A requirement of working with Kohl's is that each item in the platform must include a partner SKU. A partner SKU (also referred to as a merchant SKU or retailer SKU) is the identifier used by Kohl's when creating orders for a supplier's items. The partner SKU is not the same thing as a vendor SKU. The vendor SKU is the supplier's own unique identifier for the item. The partner_sku field in the platform should be used to include the Kohl's retailer SKU.
The table below shows the difference between a vendor SKU and retailer SKU and how each of those SKUs should be used in the platform.
| Rithum Field | Item Identifier |
|---|---|
| sku | Vendor SKU |
| partner_sku | Retailer SKU |
Warehouse Manager
All Kohl's suppliers need to be familiar with the Warehouse Manager and be ready to provide inventory by warehouse location. For more information, go to Warehouse Management.
Inventory Requirements:
- All suppliers must have at least one warehouse configured in their warehouse manager.
- All newly created items must be tied to a warehouse code that matches the exact code configured in their warehouse manager.
- Inventory feeds to the platform must include warehouse codes that match a warehouse created on your account. Inventory feeds with unrecognized warehouse codes will cause an inventory update to be rejected.
- All items must have both a total quantity and a warehouse quantity assigned to them using the configured warehouse codes.
XLS templates
If you would like a description of the required fields listed in the Required Fields by Workflow document above, or if you plan on using Excel files for your feeds, the templates below are available for you to use.
Kohl's - Inventory Template
Kohl's - Order Cancel Template
Kohl's - Invoice Template
API connection guide
If you are going to exchange transactions via API, you will use the V3 API specifications.
Comments
took me to where i needed to go.
Please sign in to leave a comment.