# GLN — Global Location Number

> The GLN registry row: thirteen digits naming a party or a location, one mod-10 rail, and the three-layer join — EDI N1 loops, EPCIS party lists, Peppol endpoints.

- page: https://barcoding.dev/schemes/gln/
- machine row: https://barcoding.dev/schemes/gln.json
- scheme (dotted registry name): gs1.gln

## Reference
- grammar: 13 digits — GS1 company prefix, location reference, check digit. One number space, two grains: a legal party or a physical/functional location; which grain a given GLN names is data, not grammar.
- check: GS1 mod-10, the same right-anchored rail as GTIN-13.
- canonical: The 13-digit form; party grain in EPCIS terms is the PGLN.
- barcode types: GS1-128 (AI 410–417 family) where marked at all; GLNs mostly travel in documents, not symbols
- enrichment: party: licensee name and issuing MO from GS1 prefix ranges; address grain where licensed
- join: The three-layer join: EDI N1 loops (N104 qualifier UL) ↔ EPCIS sourceList/destinationList (owning_party, location) ↔ the Peppol endpoint id — one key across all three layers.

## Registry rows (engine artifacts, digest-stated)
### gs1.gln
- grammar: `^\d{13}$`
- check: mod10 → "mod10 pass" (GS1 GenSpecs 26.0 §7.9)
- canonical: 13 digits
- segments: company prefix · location reference · check
- generate: gs1-128, gs1datamatrix
- hand-off: read here · resolved by id.org.ai
- digest: sha256:8a2ae77f331fc5984d966405852fad3fb9ea079e4415298be928e3ef195216d6

## Resolution stance
barcoding.dev detects, parses, verifies, enriches and generates — the codec and the data layer. Resolution — an identifier answered with identity and its linkset of live doors — is ONE capability family-wide, served by the family's identity layer, id.org.ai; vertical estates project the same one capability (vehicles: auto.dev). This registry row is the data that resolution consumes.

## Posts
- https://barcoding.dev/blog/gln-the-three-layer-join/
- https://barcoding.dev/blog/the-asn-knows-everything-except-who/