GLNs In eCommerce Transactions
GLNs are used in many types of electronic commerce transactions and are most commonly used in conjunction with Global Trade Item Numbers® (GTIN®) and Serial Shipping Container Codes (SSCC) for purchasing, shipping, invoicing and stock status transactions.
They provide the globally unique identification needed to securely exchange business information as well as unambiguously identify all legal entities, physical/operational locations described in business documents. GLNs ensure lean and efficient communication and processing since names, addresses and other information about particular locations do not need to be communicated with every transaction.
The necessary information is shared only once, stored in the relevant system (e.g., Enterprise Resource Planning system or Data Management Entity/Interactive Response Technology (IRT), systems used for communication of information during a clinical trial) and subsequently retrieved by referring to a globally unique GLN. GLNs can identify suppliers, sponsors, purchasers, clinical trial sites, contract manufacturers, transport providers, depots, ship to and bill to locations.
GLNs are increasingly important in healthcare transactions to ensure correct pricing is applied to specific customers and that ordering, stock status reporting and delivery processes can become increasingly efficient, requiring minimal intervention from clinical staff. Note: In EDI transactions, IT systems facilitating message communications, e.g., eCommerce software or clinical trials Data Management Entities (IRTs), do not need GLNs allocated. GLNs play a key role in computer-to-computer communication to support transactions, traceability and business processes. People will continue to use short-form textual codes and descriptions to identify locations in their day to day communications. These codes and descriptions should be recorded internally as attributes of the relevant GLN.
To learn more about EDI and become a certified EDI Professional please visit our course schedule page.