Ask a medical-supply vendor whether they are "GS1 compliant" and you will often get a confident yes without a clear answer to the follow-up question: compliant with which identifier? GS1 Standards in Healthcare Supply Chains cover more than one number, and the two that matter most for ordering and inventory visibility — the Global Trade Item Number (GTIN) and the Global Location Number (GLN) — solve completely different problems. Understanding the difference, and what each one actually costs to obtain, is the fastest way for a practice administrator to tell a genuinely GS1-ready vendor from one repeating a buzzword.
Two Numbers, Two Completely Different Jobs
A GTIN answers the question "what is this product?" It is the number beneath the barcode on a box of exam gloves, a case of syringes, or a package of wound dressings, and it encodes the manufacturer, the specific item, and the unit of measure — down to the size or variant. Every distinct product configuration a supplier sells needs its own GTIN, which is why a manufacturer with a large catalog ends up licensing many of them.
A GLN answers a different question entirely: "who or where is this?" It identifies a legal entity or a physical location in the supply chain — a practice, a specific clinic location, a receiving dock, or a billing department — and is used in electronic transactions rather than printed on a product. For a practice with a single location this can feel abstract, but for a multi-site group it is what lets an ordering system tell a supplier "ship this to Clinic B, bill Clinic A" without a phone call. GLNs also show up in Drug Supply Chain Security Act (DSCSA) transaction records, since federal traceability requirements need a standardized way to identify trading partners, not just products.
In short: GTIN is about the item moving through the supply chain; GLN is about the entities and locations that item moves between. A vendor genuinely built for GS1-standard ordering needs to speak both.
What Each One Actually Costs
The cost structure is where a lot of practices get surprised, because it depends entirely on how many identifiers you need — and most practices need far fewer than a supplier does.
| Path | What it is | Cost | Best fit |
|---|---|---|---|
| Individually licensed GTIN or GLN | A single, one-off number for one specific product or one specific location | One-time fee, no annual renewal | A practice that just needs to register its own location, or a single custom kit |
| GS1 Company Prefix | A block of numbers your organization owns, used to generate many GTINs and GLNs as needed | Initial license scaled to how many numbers the block allows, plus a smaller annual renewal fee | Manufacturers and distributors with growing catalogs, or any regulated healthcare entity required to prove ownership of its identifiers |
The Company Prefix path is the one that matters for vendors, not for most clinical practices ordering supplies day to day. It gives an organization a documented, database-verifiable claim to its identifiers — useful when a distributor or hospital system wants proof that a GTIN on a shipment actually belongs to the company that says it does. A practice evaluating a supplier can ask, directly, whether the vendor holds its own Company Prefix or is reselling under someone else's numbers; the answer says a lot about how seriously that vendor treats data accuracy on the products it ships.
When a Small Practice Can Skip the Company Prefix
Most single-location and small multi-location practices never need to generate their own product identifiers, because they are not manufacturing anything — they are purchasing. What they typically need instead is:
- A GLN for the practice itself (or one per location), so ordering and remittance systems can address them unambiguously
- Confidence that the supplies they buy already carry manufacturer-issued GTINs that scan correctly at receiving and match what shows up on the invoice
- An EHR or inventory system that can actually read those GTINs, rather than requiring manual SKU re-entry
For that scope, licensing a handful of individual GLNs is usually enough, and it avoids paying for a Company Prefix sized for a catalog the practice will never build.
When the Prefix Becomes Necessary
The calculation changes for entities that create their own trade items rather than just buying them: a compounding pharmacy packaging its own kits, a group that private-labels supplies, or a health system consolidating purchasing across many sites and issuing its own internal item numbers. Regulated healthcare contexts in particular — anywhere DSCSA traceability or a hospital system's vendor-onboarding process requires a verifiable Company Prefix — push an organization past the individual-license threshold, because a one-off number does not carry the same ownership proof in the GS1 Company Database that a registered prefix does.
Vetting a Vendor Before You Sign
None of this is compliance advice, and a practice should not need to become a GS1 expert to order supplies correctly. But three concrete questions separate vendors who have actually built GS1 identifiers into their ordering and inventory workflow from vendors using the standard as marketing language: Does every SKU carry a real, scannable GTIN that matches the invoice line item? Can the vendor exchange a GLN with your practice so multi-site orders and billing route correctly without manual intervention? And if traceability matters for what you are ordering, does the vendor hold its own Company Prefix rather than operating under a reseller's numbers? A vendor that answers all three cleanly has done the underlying work; one that answers only the first has done the minimum.
Matching Arizona practices to vendors who can actually answer those questions — rather than just claim the acronym — is the kind of neutral, evidence-based vetting a statewide health-IT convener is built for, distinct from taking a side in the sale itself.