To translate GLN Global Location Numbers and GS1 location data accurately, a translator must separate the name of a company, department or place from the identifier that points to that party or location in supply-chain systems. Purchase orders, electronic invoices, warehouse records, healthcare transactions and master-data files can place organization names, addresses, departments and GLNs in the same record. The descriptive language may need translation; the Global Location Number normally must remain exact.
This guide explains how to translate business and logistics records without changing GLNs, GS1 location identifiers or the party-and-location relationships attached to them. It solves one distinct search intent: what does a GLN identify, how is a legal entity different from a physical or functional location, which fields may be localized, why a GLN is not a postal address or company registration number, and how can multilingual master data preserve the same party and place after translation?
The working rule is translate the human-readable name and address where appropriate, preserve the GS1 identifier, identify the entity or location role, and verify the relationship after export. GS1 defines the Global Location Number as a 13-digit identification key used to identify parties and locations, including legal entities, functions and physical or digital locations under GS1 rules. The number is designed for stable system-to-system reference, not for linguistic translation. This specialist branch connects to Master Art of Translation, the protected Vocabulary Learning Hub, and How English Works without creating a competing logistics or company-identity hub.
GLN is a GS1 identification key
The Global Location Number is a standardized GS1 key for identifying parties and locations. Treating it as an ordinary 13-digit quantity invites formatting errors. Preserve all digits exactly. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify a legal entity
A company or other legal organization can receive a GLN under GS1 allocation rules. The legal-entity GLN is not simply the translated company name. Keep identity and display name separate. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify a function
Departments or organizational functions can be identified separately where the rules permit. Calling every GLN a company number can erase internal location meaning. Preserve the role of the GLN. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify a physical location
Warehouses, stores, loading bays or other physical locations can be represented in GS1 systems. A postal address and GLN are related but not interchangeable. Translate address text while preserving GLN. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify digital locations
GS1 also supports identification of certain digital locations under its standards. A URL or system endpoint is not automatically the GLN itself. Keep digital address and GS1 key separate. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN is 13 digits
The identifier has a fixed 13-digit representation including a check digit. Dropping a leading zero or adding separators breaks the key. Store GLN as text. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Check digit supports validation
The final digit is calculated under GS1 check-digit rules. A valid check digit can detect some transcription errors. Validate but still verify the entity relationship. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
A valid GLN can still belong to the wrong party
Copying another supplier’s valid GLN will pass syntax checks. Character validation alone cannot catch row swaps. Check name, role and address too. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GS1 Company Prefix can participate in key construction
Organizations licensed through GS1 can use company-prefix capacity to create identifiers under allocation rules. The prefix should not be translated or treated as a country name. Preserve the complete key. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GS1 prefix is not country of origin
GS1 prefix allocation does not by itself tell where a product or company was manufactured. Translating it as origin information creates false trade data. Use explicit origin fields instead. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN is not a company registration number
Legal entities can have corporate registration numbers and GLNs simultaneously. One belongs to corporate registry identity and the other to GS1 identification. Keep namespaces separate. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN is not an EORI
Customs operators can have EORI and GLN values in the same supply-chain record. EORI serves customs identity while GLN serves GS1 party/location identity. Do not substitute one for the other. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN is not a VAT number
Tax identifiers can appear beside GLNs on invoices. Using GLN as a tax number changes the legal meaning of the field. Keep tax and GS1 identity separate. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN is not a GTIN
GTIN identifies trade items while GLN identifies parties or locations. Both are GS1 keys and can be 13 digits in some representations, making confusion easy. Label the key type explicitly. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN is not an SSCC
SSCC identifies logistics units such as pallets or parcels. A warehouse GLN and pallet SSCC can appear in the same shipment. Keep place and logistics-unit identity separate. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify ship-to location
Electronic orders can use GLN for the destination receiving location. Translating the ship-to name does not change the GLN. Preserve the destination key. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify bill-to party
Invoices can identify a billing entity or function separately from delivery location. Using the ship-to GLN for bill-to can route transactions incorrectly. Keep business roles distinct. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify supplier or seller party
Procurement messages can use GLN to identify trading partners. A translated supplier name should still resolve to the same GLN. Verify party mapping. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify buyer party
Buyer and seller may each have one or more GLNs. A row shift can reverse trading partners. Use role-aware QA. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can identify healthcare locations
Healthcare supply chains can use GLNs for organizations and locations. A hospital, pharmacy or department name can change language while the key remains stable. Preserve location identity. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Address lines are translatable data
Street types, regions and country names can require localized display. The GLN should not be reconstructed from the translated address. Keep address and key separate. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Postal code is another identifier layer
Postal codes route mail and identify geographic delivery areas under national systems. They do not replace GLN. Preserve both fields. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Latitude and longitude are not GLN
Coordinates can describe a physical location but do not identify the business party under GS1. A site can move or use different coordinate precision. Keep spatial data separate. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Location name can change
A warehouse can be renamed without necessarily changing its physical identity under applicable allocation rules. Updating the name should not trigger an invented GLN change. Use GS1 allocation rules for identity decisions. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Location can move
A physical relocation may have implications for GLN allocation depending on the identity change. Translators should not decide whether a new GLN is required. Preserve authorized source data. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Department reorganizations can affect functional identity
Business functions can be renamed, merged or split. A language change alone is not the same as organizational restructuring. Keep translation and master-data governance separate. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Master-data records need version context
Names and addresses can be updated while historical transactions retain old display data. Silently modernizing an invoice changes the source record. Preserve source-period fields. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Electronic Data Interchange uses identifiers as keys
EDI messages can carry GLNs in structured segments. Translating the raw EDI value or segment code breaks processing. Localize documentation, not machine syntax. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
XML and JSON keys are machine contracts
APIs can expose GLN fields in structured payloads. Translating property names in production payloads can break integrations. Translate interface labels separately. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GS1 Digital Link is another layer
GS1 standards can connect identifiers to web-resolvable information. A Digital Link URI is not the same field as a bare GLN. Keep identifier and resolver syntax distinct. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Barcode carriers can encode GLN
GS1 barcodes can carry location identifiers using defined application identifiers. Recreating the barcode from translated text can change encoded data. Preserve and scan-test the carrier. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Application Identifier syntax is not prose
GS1 Application Identifiers can precede encoded values. Parentheses or numeric prefixes can look like ordinary punctuation. Protect machine syntax. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Human-readable interpretation should match encoded data
Printed digits can appear near a GS1 barcode. A mismatch between text and barcode creates operational risk. Decode and compare after localization. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
GLN can appear without a barcode
Many electronic transactions carry GLNs only as data fields. Absence of a barcode does not make the number translatable. Preserve the key. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Leading zeros matter
A 13-digit GLN can begin with zero. Spreadsheet numeric conversion can remove it. Store as text. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Thousands separators must never be added
Locale formatting can turn a GLN into grouped digits. That display no longer matches the identifier. Disable numeric formatting. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Localized numeral glyphs can break lookup
Some languages use non-ASCII numeral forms in prose. GS1 keys should remain in their standardized digit representation. Translate labels, not digits. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Right-to-left layouts need directionality testing
RTL text can visually reorder long digit strings and parentheses. The underlying key can be correct while display becomes hard to copy. Test final UI and PDF. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
OCR can misread GLNs
Scanned invoices can confuse digits, especially in small fonts. A one-digit error can produce another syntactically valid key. Validate check digit and entity mapping. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Spreadsheets can convert GLN to scientific notation
Long numbers are vulnerable to numeric formatting. The displayed value can lose precision or leading zeros. Import as string. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
CSV needs explicit schema
CSV does not retain field types or namespace metadata. A bare 13-digit value could be GLN or another identifier. Define the key type. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Machine translation should lock GLNs
MT systems can insert spaces or localize digits. A readable target can become unusable for EDI. Protect GLN fields. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Translation memory can carry another trading partner’s GLN
Invoices and orders are repetitive. A high TM match can reuse a prior customer’s key. Populate identifiers from current source data. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Search-and-replace can damage many keys
Bulk punctuation or digit formatting rules can touch every identifier in a corpus. One editorial rule can break thousands of records. Restrict changes to translatable fields. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Duplicate names do not imply duplicate GLNs
Different branches can share a trading name while having distinct location identities. Name matching alone can merge locations. Use address and GLN together. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
One entity can have multiple GLNs
A company can identify legal entity, functions and locations separately. Seeing several GLNs for one brand is not necessarily an error. Check entity type. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
One GLN should not identify unrelated roles by guesswork
Master-data governance determines allocation and reuse under GS1 rules. Translators should not consolidate identifiers to simplify a table. Preserve authorized records. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Acquisitions and mergers need governance
Company ownership changes can affect names and master data. A translator cannot infer whether a GLN should change. Use the source and GS1 governance decisions. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Worked example: seller and warehouse
A fictional supplier has one legal-entity GLN and a separate warehouse GLN. The target translates company and warehouse names while preserving both keys. Keep seller and ship-from roles distinct. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Worked example: bill-to and ship-to
A fictional purchase order uses different GLNs for billing and delivery. A translated address block must not swap them. Verify business role and location. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Worked example: GLN and GTIN
A fictional order line contains supplier GLN and product GTIN. Both are GS1 identifiers but identify different objects. Keep party/location and trade-item layers separate. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Error clinic
Common failures include leading-zero loss, GLN/GTIN swaps, EORI substitution, localized digits, barcode mismatch and row shifts. These errors can survive fluent business prose. Run dedicated GS1-location QA. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Release checklist
GLN, entity type, party role, address, source date and encoded carrier all need verification. Checking only names and addresses is insufficient. Validate both token and relationship. Treat the human-readable party or location description as translatable, the GLN as protected, and the role relationship as something to verify after export. This prevents a correct key from being attached to the wrong buyer, seller, warehouse or department.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Frequently asked questions
GLNs should not be translated. Users often ask whether GLN is a company number or address. Explain that it is a GS1 key for parties and locations. The practical test is master-data traceability. A reviewer using only the target should be able to resolve the same party or location and understand what role the GLN performs in the transaction.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Connection to eduKateSG architecture
This specialist owner protects GS1 party and location identity. A broad logistics hub would overlap existing owners. Use this page for GLN and other pages for product, shipment or customs identity. For structured files, store the GLN as text with an explicit key-type field and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change names and addresses around a stable GS1 key.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Authoritative sources
GS1 General Specifications and GLN allocation guidance govern the identifier. Local GS1 Member Organizations support implementation. Verify keys and allocation decisions against GS1 resources. A strong reviewer checks both directions: start from the target name/address and confirm the GLN, then start from the GLN and confirm the same entity type, business role and location.
Before release, ask what the GLN identifies in this record: legal entity, function, physical location or another permitted location type. The target should state that role clearly rather than treating every GLN as a generic company number.
Reference verification route
For production work, use GS1’s Global Location Number resources, the current GS1 General Specifications and applicable GLN allocation rules. Local GS1 Member Organizations can provide implementation guidance. The translation workflow should preserve the assigned key and localize only the human-readable party, address and role information around it.