Global Location Number

A Global Location Number (GLN) is a 13-digit GS1 identification key that uniquely identifies a physical location, functional entity, or legal entity in the supply chain. It answers "who" and "where" in business transactions, serving as a standardized digital address for plants, warehouses, dock doors, departments, and EDI endpoints so ERP and trading-partner systems can exchange location data without ambiguity.

In practice, a plant first decides whether each physical point needs its own GLN. A receiving dock can carry one code so inbound ASN and EDI documents point to the exact dock or zone instead of the plant's general address. Warehouses can assign separate GLNs to line-side supermarkets, kitting areas, QA holds, and staging lanes; each movement then updates the right inventory node and preserves traceability across handoffs. Supplier and customer locations are also coded in ERP, so purchase orders, invoices, and delivery routing refer to the same standardized location as the trading partner's system. When raw materials move from supplier site to transfer point to storage, the GLN identifies the legal owner and the physical node at each event. This lets teams capture accurate stock visibility, reduce misrouted put-away, and keep master data synchronized across the network.

• ⚠️Overloaded Location Code: When a plant, dock, and warehouse share one GLN, receiving and inventory transactions collapse into a single node, masking shortages and misrouting put-away until traceability fails.
• ⚠️Mismatched Trading-Partner GLN: If supplier, ship-to, or bill-to GLNs are inconsistent across ERP and partner systems, orders and ASNs point to the wrong site, creating receiving delays, invoice mismatches, and manual corrections.
• ⚠️Stale Master Data After Relocation: When an expansion, dock move, or reorganization is not reflected in GLN allocation rules, downstream systems keep sending transactions to obsolete locations, causing stock visibility errors and confusion.