Skip to main content

Trading Partner Onboarding - Sterling Jewelers

If you are looking to implement Sterling Jewelers as a new Trading Partner within your EDI network, this article will provide you with an understanding of the requirements, preliminary and next steps, as well as commonly used transaction types.

S
Written by Stacie McGee

Trading Partner: Sterling Jewelers


EDI IDs


Sterling Jewelers utilizes the following Electronic Data Interchange (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 Sterling Jewelers.​

X12 Qualifier

EDI ID

Primary ID?

ZZ

JEWELS

Yes

ZZ

JEWELSTEST

No

ZZ

JEWELTEST

No

Sterling Jewelers 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 Sterling Jewelers to determine the proper EDI ID to use.


Preliminary Steps


To initiate the EDI Setup process, Sterling Jewelers vendors will be required to email [email protected] and supply the following detail:


Direct Trading Partner Testing


Sterling Jewelers requires you to complete compliance testing before Go-Live. Please refer to the Next Steps section of this article for detailed instructions and expectations. If you prefer, TrueCommerce can conduct and complete compliance testing on your behalf.


Commonly used Transactions


The table, below, lists the most commonly used EDI transactions with Sterling Jewelers.


Next Steps


Once the purchase of the Sterling Jewelers 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/5/2026

Did this answer your question?