Trading Partner: Metro
EDI IDs
Metro 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 Metro:
X12 Qualifier | EDI ID | Primary ID? |
ZZ | MRIPTC09 | Yes |
ZZ | METRO | No |
ZZ | EUMRTEST | No |
ZZ | METROTEST | No |
Metro 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 Metro to determine the proper EDI ID to use.
Preliminary Steps
Metro vendors should contact [email protected] to initiate the EDI setup. Metro has an EDI form that must be completed, below is the EDI-related information required for the form:
AS2 Name: TrueCommerceSHA2
Test Exempt Relationship
Metro does not require compliance testing. When the EDI relationship is setup, Metro will issue a live purchase order from their production environment.
Commonly Used Transactions
The table, below, lists the most commonly used EDI transactions with Metro:
EDI Transaction |
Next Steps
Once the purchase of the Metro plug-in is complete, your Implementation Specialist will reach out to schedule time to complete and/or coordinate a plan for go-live and/or Enterprise Resource Planning (ERP) system integration setup.
Related Documentation