EDI Migration Strategy (GTIN and GLN Implementation)
EDI Migration Strategy should be defined by trading partners for using GTIN and GLN in transactions. EDI transaction standards support numerous types of identifiers for products and parties/locations, including both GS1 identifiers and Non-GS1 identifiers. Because GTIN and GLN are global identification standards that can be used by all trading partners, implementing GTIN and GLN in EDI transactions instead of proprietary identifiers provides the opportunity to simplify product and party/location identification.
There are two basic strategies for companies implementing the standards:
- Replace Non-GS1 identifiers with GLN and GTIN.
- Use GLN and GTIN alongside Non-GS1 identifiers.
Replacing Non-GS1 identifiers with GTINs and GLNs will require a more coordinated effort between trading partners in order to assure alignment and accuracy. Often, replacement reveals identifiers within both parties’ enterprise systems which may not have been previously exchanged. Even if the goal is replacement, accommodations should be made within the internal systems to support several identifiers (GS1 and Non-GS1) in order to support a smooth changeover. The fact that GTINs and GLNs can be implemented in transactions alongside Non-GS1 identifiers supports such a transition or migration to a single identifier.
To learn more about EDI and become a certified EDI Professional please visit our course schedule page.