Trading Partner: QVC
If you are looking to implement QVC as a new 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
QVC 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 EDI transaction that is sent or received.
The table, below, lists the most common EDI IDs used by QVC.
X12 Qualifier | EDI ID | Primary ID? |
12 | 4847011000CH | Yes |
12 | 4847011000CHQT | No |
QVC 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 QVC to determine the proper EDI ID to use.
Preliminary Steps
To begin the EDI setup process, contact CommerceHub (also known as Rithum) directly at [email protected]. CommerceHub will require EDI forms to be completed to start the testing process.
Portal Testing
QVC 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 CommerceHub portal
Username for the CommerceHub portal
Password for the CommerceHub portal
Commonly used Transactions
The table, below, lists the most commonly used EDI Transactions by QVC.
EDI Transaction |
Next Steps
Once the purchase of the QVC 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.
The EDI documents listed here are provided for reference only and may not be comprehensive. For the most up‑to‑date and complete list of required EDI documents, refer to the CommerceHub Test Portal.
Related Documentation
rev. 8/3/2026