Most conversations about GS1 standards in healthcare stop at the barcode on the box — the Global Trade Item Number, or GTIN, that identifies a specific catheter, dressing, or reagent kit. That’s only half the picture. The other GS1 identifier, the Global Location Number (GLN), rarely gets mentioned outside of supply-chain and EDI documentation, yet it’s the piece that determines whether a purchase order actually lands at the right loading dock, gets billed to the right department, and reconciles cleanly against an invoice. For a practice trying to reduce ordering errors and speed up inventory visibility, understanding the difference — and why both matter together — is more useful than another primer on what a barcode is.
Two Different Questions: What vs. Where
GS1’s identifier system is built around a simple split. A GTIN answers "what is this item?" It’s the number encoded in the UPC or EAN-style barcode on a case of gloves, a surgical tray, or an implant, and it’s what most practices already associate with GS1 because it shows up on packaging. A GLN answers a different question entirely: "who or where is this transaction happening?" It’s a 13-digit code that functions as a digital address, uniquely identifying a legal entity, a physical location, or a functional department — the hospital system, a specific clinic, a purchasing office, a loading dock, or even a supply cabinet on a particular unit.
Both are GS1 standards maintained by GS1, the global not-for-profit organization responsible for the identifier and barcode standards used across retail and healthcare supply chains. But they solve different problems, and a practice that has only adopted GTIN-level product scanning is still missing the identifier that makes ordering and invoicing actually match up.
What a GTIN Actually Tells You
A GTIN is product-specific. Scan it and you get the manufacturer, the item, the packaging level (each, case, pallet), and often a lot number or expiration date if it’s paired with GS1’s serialization layer. This is the identifier that drives point-of-use inventory counts, expiration tracking, and recall lookups — if a lot is recalled, the GTIN plus lot number tells you exactly which units in your storeroom are affected. It’s the layer most clinical and materials-management staff interact with directly, because it’s printed on the thing they’re holding.
What a GTIN does not tell you is where that item needs to go, who’s authorized to order it, or which cost center should be billed. That’s where the gap shows up in day-to-day ordering: a practice can have perfect product-level barcoding and still see purchase orders misrouted, invoices posted to the wrong location, or shipments arriving at the wrong dock — because nothing in the transaction identified the locations involved.
What a GLN Actually Tells You
A GLN closes that gap. It identifies the buyer, the supplier, the ship-to location, and the bill-to entity as distinct, unambiguous parties in a transaction — each with its own number, the same way a bank routing number identifies an institution rather than an account holder. For a multi-site practice or a hospital system with several receiving docks, that distinction matters: the purchasing department, the central warehouse, and an individual clinic can each carry a separate GLN, so a supplier’s system knows precisely which physical location an order or shipment is tied to, without relying on address text fields that vary from one order to the next.
GS1 publishes implementation guidance specifically for healthcare GLN use, because the identifier has to be applied consistently across departments, sites, and even individual storage areas (crash carts and pharmacy stock rooms are common examples) to deliver its full value. A GLN assigned once and applied inconsistently across a practice’s ordering systems provides little more benefit than not having one.
Where GLNs Do the Real Work: EDI and Purchase Orders
The practical payoff of a GLN shows up in electronic data interchange, not in a scanner. When a practice or health system exchanges standard EDI transaction sets with a distributor — purchase orders, invoices, and shipping notices — GLNs are what make those documents route and reconcile automatically instead of requiring manual matching:
- Purchase orders: the buyer’s and supplier’s GLNs are embedded in the order transaction, so the order is routed to the correct supplier location and attributed to the correct purchasing entity without a human re-typing an address.
- Invoices: the issuer’s and receiver’s GLNs let accounting systems auto-post invoices against the right cost center, rather than a staff member manually matching a paper invoice to a department.
- Shipping and receiving: a GLN on the shipping notice tells the receiving dock, cross-dock, or warehouse exactly where a shipment belongs, which is what makes automated receiving workflows possible in the first place.
None of this requires a practice to touch a barcode scanner differently. It’s a back-office data setup — assigning and registering the right GLNs with trading partners — that determines whether EDI transactions clear cleanly or generate the kind of manual exception-handling that ties up a billing or purchasing team.
GLN and GTIN, Side by Side
| Question it answers | GTIN | GLN |
|---|---|---|
| What it identifies | A specific product or trade item | A legal entity, physical location, or department |
| Where you see it | Printed as a barcode on packaging | Embedded in EDI transactions, not on physical goods |
| Typical use | Inventory counts, expiration tracking, recalls | Order routing, invoice posting, shipment receiving |
| Who touches it day to day | Clinical and materials-management staff | Purchasing, accounting, and EDI/ERP systems |
| Governing body | GS1 | GS1 |
Getting Both Identifiers Right
A practice that has adopted GTIN scanning for point-of-use inventory has done real work — but it’s only solved the "what" half of the ordering equation. The "where" half depends on whether GLNs have been assigned to every relevant location and entity, and whether those numbers are actually configured inside the purchasing, EDI, and ERP systems a practice uses to place orders and receive invoices. That configuration step is usually where practices get stuck: it isn’t a clinical workflow change, it’s a data and systems-integration task that touches a distributor’s EDI setup, a practice management system, and sometimes a group purchasing organization’s records all at once.
For an Arizona practice trying to reduce order errors, speed up receiving, and get accurate inventory visibility across multiple sites, the fastest path is usually connecting with a vendor who already handles GS1/GLN onboarding and EDI configuration as part of supply-chain or practice-management services — rather than trying to reverse-engineer the setup internally. That’s the kind of match a neutral, statewide health-IT resource is built to make: pointing a practice toward a qualified vendor for the specific piece — GLN registration, EDI trading-partner setup, GDSN data alignment — that its current systems are missing.
Conclusion
The GTIN on a product barcode and the GLN behind a purchase order are solving two different problems, and healthcare supply chains need both working correctly to function. A practice that has only implemented one half of the GS1 GLN vs GTIN pair will keep seeing the same symptoms — misrouted orders, invoices that won’t auto-post, shipments to the wrong dock — no matter how well its product-level barcoding is running. Closing that gap is a systems and data question, not a clinical one, which is exactly why it’s worth routing to a vendor who specializes in it rather than treating it as a side project for existing staff.