Skip to main content

Trading Partner Onboarding - Starbucks

Looking to implement Starbucks as a new Trading Partner within your EDI network? Read on to gain understanding of requirements, preliminary/next steps, and commonly used transaction types.

L
Written by Lorilei Nash

Trading Partner: Starbucks


EDI IDs


Starbucks utilizes the following Electronic Data Interface (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.

Below is a list of the most common EDI IDs typically used by Starbucks:

X12 Qualifier

EDI ID

Primary ID?

ZZ

SBUXCP

Yes

ZZ

SBUXCT

No

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


Preliminary Steps


Before TrueCommerce is able to begin onboarding Starbucks into Transaction Manager, you will need to perform the following action to kick off your Trading Partner Implementation Project:


Direct Trading Partner Testing


Starbucks requires you to complete compliance testing before Go-Live.

Please refer to the below Next Steps section for detailed instructions and expectations. If you prefer, TrueCommerce can conduct and complete compliance testing on your behalf.


Commonly-Used Transactions



Next Steps


Once the purchase of the Starbucks 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.


Important Information


Starbucks utilizes OpenText connections for EDI.

Starbucks needs to confirm and approve the relationship, on their side, with GXS prior to the start of the testing.


Related Documentation


rev. 6/17/2026

Did this answer your question?