Custom GS1 GLN integration development
A Global Location Number, or GLN, is the GS1 location code: a 13-digit number that uniquely identifies an organisation or location worldwide. A customer, a warehouse, a loading dock or an accounts department each get a single number, so name and address no longer need to be included in every message. Appfront builds the integration that manages GLNs in your own systems: recording them against the right party or location, validating them and using them in messages, labels and invoices.
What is a GS1 GLN integration?
A GS1 GLN integration ensures that every party and every location in your systems has the correct Global Location Number and that this number is used consistently everywhere. According to GS1 Netherlands, the GLN is a 13-digit number that identifies locations uniquely and unambiguously. It can refer to a legal entity, such as a company or branch; a function within an organisation, such as the accounts department; a physical location, such as a warehouse, loading dock, branch, shelf or plot; or a digital location, such as an IT system or network address. The last digit of a GS1 code is a check digit. Name, address and other details then only need to be passed on once and are subsequently looked up via the GLN.
You apply for GLNs through MijnGS1, where you also assign them to a company, a location or a loading dock. They are included in the global GLN registry. The GS1 Location Finder lists, per GLN, details such as trade names, name and address data, geocoordinates and linked locations, such as a distribution centre with its docks. Trading partners search it via MijnGS1 or Verified by GS1, and for larger volumes an API connection is available. When a relocation or new address requires a new GLN is set out in GS1's GLN Allocation Rules Standard. In barcodes, the GLN has its own identifiers, such as AI 410 for the delivery address, AI 411 for the invoicing party and AI 414 for a physical location.
We build this as a custom solution because, in practice, GLNs are scattered: in the customer file, in a table in the EDI translator, in the WMS and on a buyer's list. The integration brings them together in a single source, assigns each GLN to the right party or location, builds the hierarchy from organisation to branch, warehouse and dock, and checks the data against the Location Finder. It then supplies the right GLN wherever it is needed: in orders, dispatch messages and invoices, on logistics labels and in the integration with your ERP. A GLN that does not belong to a known party ends up on a list rather than in a message.
One source
All GLNs brought together.
Per site
From organisation to dock.
In every message
Right GLN included.
How we build your GS1 GLN integration
We start with your parties and locations: which GLNs you hold yourself, which trading partners work with GLNs, where those numbers are currently stored and in which messages, labels and invoices they end up. We then import the existing numbers, compare them and highlight where duplicate, missing or unknown GLNs are hiding. We build the central source with the location hierarchy first and let you review the result. Adding GLNs to messages and labels and checking against the Location Finder follow once that works well. After that, we maintain the integration as parties move, locations are added or GS1 changes its rules.
Parties, numbers, messages.
Duplicate, missing, unknown.
With the location hierarchy.
Go-live, monitoring, and management when new locations are added.
What a GS1 GLN integration actually does
The components below appear in almost every GLN integration. Which ones you need depends on the number of parties and locations and on the messages you exchange.
Location source
All GLNs in one place.
Hierarchy
Organisation, branch, dock.
Validation
Structure and check digit.
Lookup
Data from the Location Finder.
Messages
GLN in order and invoice.
Labels
AI 410 and 414 in barcodes.
Who we build a GS1 GLN integration for
The integration is intended for organisations that work with many trading partners and locations and currently maintain GLNs separately in several places. The more delivery addresses, branches and messages you have, the more it delivers.
Wholesalers
Customers and delivery addresses.
Retailers
Stores and distribution centres.
Logistics
Warehouses and loading docks.
Software builders
GLN management in your software.
Technology and integrations
This page is about the GLN: the number for parties and locations. For product codes and barcodes on items, see our page on the GS1 GTIN integration. We build the message exchange itself, in which the GLN is one of the fields, with EDIFACT integration software or a broader EDI integration. If it concerns locations within your own warehouse, also look at a custom WMS. You can read about our approach on building software.
Why choose Appfront for your GS1 GLN integration?
A delivery that arrives at the wrong distribution centre, an invoice that is rejected because the invoicee's GLN is wrong, or a delivery address spelt differently in three systems: all of these cost time for you and your trading partners. That is what we build around: one source for all GLNs, checks before a number ends up in a message and a log showing what has changed.
Unambiguous
One number per location.
Checked
Before the message goes out.
Traceable
Every change recorded.
Security and privacy in a GS1 GLN integration
The integration mainly processes business data: GLNs, names, addresses and the relationships between locations. For sole traders, growers or healthcare providers, this can be personal data, in which case the GDPR applies. The integration retrieves only the data you need from the Location Finder, records the source and the time of each lookup, and logs every change to a GLN with the time and user.
The integration runs in a European data centre, with encrypted connections and storage. Login credentials and API keys for MijnGS1 and the Location Finder are kept secure and are not visible to staff. We agree with you in advance who may add or link GLNs and who may approve a discrepancy.
Frequently asked questions about a GS1 GLN integration
Questions that wholesalers, retailers and logistics providers ask before getting started.
The Global Location Number, the GS1 location code: a 13-digit number that uniquely identifies an organisation or location worldwide. It can refer to a company or branch, a department, a physical place such as a warehouse or loading dock, or a digital location such as an IT system.
A GTIN identifies a product, a GLN a party or location. In an order, the GTIN appears with each item and the GLN with the buyer, the supplier and the delivery address. Both are GS1 codes, but each has its own purpose and its own integration.
You request GLNs through MijnGS1 from GS1 Netherlands. There you assign them to your company or to locations, such as a branch or loading dock, and they are added to the global GLN registry. The GLN Allocation Rules Standard sets out when you need a new GLN, for example after a relocation.
Via the GS1 Location Finder, in MijnGS1 or on Verified by GS1. You search by GLN or company name and can see trade names, address details, geocoordinates and linked locations, among other things. For larger volumes of lookups, GS1 offers an API connection.
Yes. A GLN can be converted into a GS1 barcode or an EPC/RFID tag. In GS1 barcodes, an application identifier indicates what the GLN means, for example AI 410 for the delivery address, AI 411 for the invoicing party and AI 414 for a physical location.
An EDIFACT integration handles the message traffic with your trading partners: orders, dispatch advices and invoices. A GLN integration makes sure the GLNs in those messages are correct and belong to the right party and location. They work together, and the GLN integration can be built into an existing EDI environment.
For organisations with many customers, delivery addresses, branches or warehouse locations, and for software vendors who want to support GLNs in their package. If you work with a handful of fixed partners, a table in your EDI package is often enough.
All your GLNs in one place and correct everywhere?
Tell us how many parties and locations you work with and where your GLNs are stored now. We'll show you how an integration brings them together and passes them on correctly.