Global Location Number(Gln)
What Is a Global Location Number (GLN)?
A Global Location Number (GLN) is a 13-digit GS1 identification key used to identify parties and locations in business transactions. In logistics, ecommerce, and supply chain management, it can identify a legal entity, an organizational function, a physical location, or a digital location. For example, a GLN may identify a company, its purchasing department, a distribution center, or an electronic destination used to exchange business information.
The purpose of a GLN is to give trading partners a consistent identifier for the party or location involved in a process. Rather than relying only on company names, written addresses, or internal warehouse codes, connected systems can use a GLN to reference the same entity or location. The associated details, such as a postal address or business role, are maintained separately as master data.
What a GLN Can Identify
Although its name emphasizes location, a GLN is not limited to buildings or geographic coordinates. GS1 distinguishes several identification uses. These refer to different business objects, so a company should establish what each GLN represents before sharing it with partners.
| Identification use | What it identifies | Illustrative supply chain example |
|---|---|---|
| Legal entity | An organization with legal standing | The company that purchases goods under a supply agreement |
| Function | An organizational subdivision or department associated with particular responsibilities | A retailer's accounts payable department |
| Physical location | A tangible place where activities occur or where something is located | A distribution center, store, or receiving area |
| Digital location | An electronic address used for communication between systems | An electronic endpoint used to exchange business information |
These uses explain why a company's identity and its delivery destination should not automatically be treated as the same thing. A retailer may have one purchasing organization but several warehouses. Conversely, a single warehouse address may contain operations belonging to different parties. GLN allocation should reflect the distinctions that trading partners need to recognize, following the applicable GS1 rules.
Structure and Associated Information
A GLN contains 13 numeric digits, with the final digit serving as a check digit. In the GS1 Company Prefix-based structure, the preceding digits consist of a GS1 Company Prefix and a location reference. The relative lengths of those components depend on the prefix allocation; they are not fixed-length fields that can always be separated in the same way.
The check digit helps detect certain data-entry errors. It does not establish that the identifier has been validly assigned, that the associated organization is trustworthy, or that the location information is current. A number passing a mathematical check still requires appropriate verification against its assigned identity and supporting records.
A GLN should be treated as an identifier rather than a compressed address. Users should not attempt to derive a street address, customs jurisdiction, delivery instruction, or warehouse capability from its digits. Such information belongs in the records associated with the GLN. In software, preserving the identifier as a 13-character numeric string helps avoid losing leading zeros during import, export, or spreadsheet processing.
How GLNs Are Used in Logistics and Ecommerce
Order and delivery coordination
In structured business messages, GLNs can identify parties such as the buyer and supplier, as well as locations such as the delivery destination. Their meaning depends on the field or business role in which they appear. A GLN entered as the buyer identifier does not automatically identify the warehouse where goods should be delivered.
This distinction matters when an ecommerce business purchases inventory centrally but distributes it across several fulfillment facilities. The order may identify the purchasing entity separately from the receiving location. Systems must preserve those roles when converting information between purchasing, warehouse, and transportation applications.
Warehouse operations and inventory records
A warehouse management system may associate a GLN with a facility or a more specific physical location where separate identification is required. Internal bin and aisle codes can still be used for local operations. A GLN does not mean that every shelf, rack, or storage position must receive its own globally shared identifier.
The practical question is whether a location needs to be identified distinctly in the relevant business process. A receiving area shared with trading partners may require a different identification approach from a temporary internal staging position. Organizations should apply GS1 allocation rules rather than creating extra GLNs solely because their software contains additional location fields.
Cross-border transactions and returns
In cross-border ecommerce, GLNs can help distinguish the entities and facilities participating in a supply chain. For example, a merchant's legal entity, an overseas fulfillment center, and a return-receiving facility may represent different identification needs. Shared identifiers can make those distinctions explicit in partner records and business messages.
A GLN does not replace an importer registration, tax identifier, customs declaration, postal address, or any other information required by a particular authority or transaction. Whether a specific document or electronic message accepts or requires a GLN depends on its governing requirements. Possessing a GLN alone does not establish customs compliance or permission to import goods.
Illustrative Order-to-Receipt Workflow
The following example describes a possible implementation, not a mandatory sequence for every business.
- Define the identities. A retailer distinguishes its purchasing entity from the warehouse that will receive an order. It determines which identities require GLNs under the relevant GS1 rules and partner requirements.
- Maintain master data. The retailer records what each GLN identifies and associates it with the appropriate name, address, role, and operational details.
- Share the records. The supplier receives the identifiers and their meanings through an agreed onboarding or data-exchange process. Both parties confirm that their systems interpret the roles consistently.
- Create the purchase order. The order identifies the buyer and delivery destination in the appropriate fields. Different GLNs may appear where those roles refer to different parties or locations.
- Prepare the logistics units. The supplier identifies the pallets or other logistics units separately. Their identifiers can be connected with the destination GLN in shipment records.
- Receive and reconcile. The receiving operation compares incoming goods and logistics-unit information with the expected order and destination. Any mismatch is investigated using the underlying records.
The GLN supplies a stable reference within this workflow, but it does not perform the physical routing or reconciliation itself. Those functions depend on correctly maintained data, compatible systems, and operating procedures.
GLN Compared with Related Identifiers
| Identifier or reference | Primary purpose | Difference from a GLN |
|---|---|---|
| Global Trade Item Number (GTIN) | Identifies a trade item, such as a product offered for ordering or sale | A GTIN identifies what the item is; a GLN identifies a party or location involved in the transaction. |
| Serial Shipping Container Code (SSCC) | Identifies an individual logistics unit, such as a pallet or parcel | An SSCC identifies the logistics unit being handled; a GLN can identify its destination or another relevant party or location. |
| Carrier tracking number | References a shipment or package within a carrier's tracking processes | A GLN is not a parcel-tracking reference and does not provide delivery-event updates. |
| Postal address | Describes a destination using address information | A GLN references an identified party or location; it does not eliminate the need for usable address data. |
| Internal warehouse code | Identifies a facility within an organization's own system | An internal code has meaning within its managed context, whereas a GLN belongs to the GS1 identification system. |
These identifiers are complementary rather than interchangeable. A transaction may reference a product by GTIN, a pallet by SSCC, and a receiving warehouse by GLN. Each answers a different question about the same movement of goods.
Allocation, Maintenance, and Implementation Checks
Organizations obtain and manage GLNs through the applicable GS1 arrangements. Before assigning identifiers, they should consult the relevant GS1 Member Organisation and the GS1 GLN Allocation Rules. Arbitrarily creating a 13-digit number, even one with a valid check digit, does not establish a properly allocated GLN.
Maintenance is as important as initial assignment. Changes to legal entities, functions, or locations need to be evaluated under the allocation rules to determine whether an existing GLN remains appropriate or a new one is required. A relocation, organizational change, or closure should not be handled solely by overwriting a database field without reviewing the identification implications.
Useful implementation checks include:
- Identity scope: Document exactly what each GLN identifies, including whether it represents a legal entity, function, physical location, or digital location.
- Data integrity: Preserve all 13 digits, validate the check digit, and prevent unintended numeric conversions.
- Role mapping: Confirm that buyer, supplier, invoice-related, and delivery-location fields refer to the intended identities.
- Partner agreement: Establish how identifiers and associated data will be exchanged and corrected.
- Change control: Assign responsibility for reviewing changes against GS1 rules and informing affected partners.
- Operational detail: Keep routing instructions, contact information, and receiving requirements in appropriate associated records rather than assuming the GLN contains them.
Common Misunderstandings
A GLN is not necessarily a warehouse number. A warehouse is one possible identification target, but legal entities, functions, and digital locations also fall within the GLN framework.
A GLN is not itself a barcode. It is an identification key. GS1 standards define how it can be represented in relevant data carriers and messages. Encoding and placement requirements depend on the application.
A GLN does not provide live location tracking. Identifying a facility or party is different from reporting where a vehicle or parcel is currently located. Tracking requires additional event information and systems.
A GLN does not remove the need for master-data management. Trading partners still need an accurate, shared understanding of the identity behind the number. Inconsistent or outdated associated records can undermine otherwise valid identification.
QA
How many digits are in a GLN?
A GLN contains 13 numeric digits, including a final check digit. Systems should preserve its complete format, including any leading zeros.
Does every warehouse need a separate GLN?
The answer depends on the identification requirements and applicable GS1 allocation rules. When warehouses must be distinguished as separate physical locations in business processes, their identification needs should be assessed individually.
Can a GLN be used to track a parcel?
Not by itself. A GLN identifies a party or location, while parcel tracking uses shipment or package references and associated tracking events.
Is a GLN required for every cross-border ecommerce shipment?
A GLN is not a universal requirement for every cross-border shipment. Its use depends on the relevant trading-partner, system, industry, or regulatory requirements, and it does not replace required customs or address information.
Sources
- GS1: Global Location Number (GLN) — Official definition, identification scope, and business uses.
- GS1: GLN Allocation Rules — Identification decisions, allocation principles, and management of changes.
- GS1 General Specifications — Technical framework for GS1 identification keys, data structures, and data-carrier applications.
- GS1: Global Trade Item Number (GTIN) — Trade-item identification and its distinction from party and location identification.
- GS1: Serial Shipping Container Code (SSCC) — Logistics-unit identification and its distinction from GLN use.
