Trading Partner: Kohl's DSCO
If you are looking to implement Kohls DSCO as a Trading Partner within your Electronic Data Interchange (EDI) network, this article will provide you with an understanding of the requirements, preliminary and next steps, as well as commonly used transaction types.
EDI IDs
Kohl's DSCO utilizes the following EDI IDs for identification purposes. These EDI IDs are made up of a Qualifier and an ID which will be sent within their Interchange Control Header, ISA segment, on your inbound transactions. This allows Transaction Manager to be able to identify the Sender and Receiver of any sent/received EDI transaction.
The table, below, lists the most common EDI IDs used by Kohl's DSCO.
X12 Qualifier | EDI ID | Primary ID? |
ZZ | KOHLSDSCO | Yes |
ZZ | KOHLS_DSCO | No |
Kohls DSCO will expect a specific EDI ID based on your business relationship with them. Selecting the wrong EDI ID will result in EDI Transactions not being sent or received.
You will need to work with Kohls DSCO to determine the proper EDI ID to use.
Preliminary Steps
In order to begin the EDI setup process, contact the DSCO team directly at [email protected]. DSCO will then begin the process to provide your team access to their testing portal.
Portal Testing
Kohl's DSCO requires you to complete compliance testing before Go-Live. Refer to the Next Steps section in this article for detailed instructions and expectations. If you prefer, TrueCommerce can conduct and complete compliance testing on your behalf, in which case you will need to provide the following details:
URL for the DSCO portal
Username for the DSCO portal
Password for the DSCO portal
Commonly used Transactions
The table, below, lists the most commonly used EDI transactions with Kohl's DSCO.
EDI Transaction |
Next Steps
Once the purchase of the Kohl's DSCO plug-in is complete, your Implementation Specialist will reach out to schedule time to complete and/or coordinate a plan for compliance testing and/or Enterprise Resource Planning (ERP) system integration testing.
Related Documentation
rev. 8/11/2026