Ask a practice manager which number their distributor needs for electronic ordering, and most will reach for the ten-digit code they already have memorized: the practice’s National Provider Identifier. It feels like the obvious answer — it’s the number CMS assigned, the number on every claim, the number every payer already recognizes. It is also, in most electronic ordering setups, the wrong number. The identifier that actually moves a purchase order through a distributor’s system is a GS1 Global Location Number, a different code built for a different job. Practices that don’t know the distinction end up with orders that misroute, invoices that mismatch, or a distributor rep manually re-keying an address every single time. This is a matching problem, not a legal or compliance question — and it’s the kind of operational gap a neutral vendor-matching directory exists to help a practice close.
Two Numbers, Two Completely Different Jobs
The confusion is understandable because both identifiers are short, standardized, and issued by an authority the practice never has to think about twice. But they were built to answer different questions.
The National Provider Identifier is a 10-digit number issued by the Centers for Medicare & Medicaid Services. It answers the question who is rendering care — it identifies the provider or organization for claims, referrals, and other clinical-administrative transactions. It was never designed to describe a physical location, a loading dock, or a shipping address.
The GS1 Global Location Number is a 13-digit code that answers a different question entirely: where does this shipment go, and who is the legal entity receiving it. A GLN can identify an entire practice, a single department inside it (purchasing versus accounts payable, for example), or a specific physical point like a supply-room shelf. Distributors and group purchasing organizations use GLNs to route shipments, match invoices, and confirm delivery — the exact mechanics an NPI was never built to handle.
GLN vs. NPI at a Glance
| Identifier | Issued By | Answers | Used For |
|---|---|---|---|
| NPI | Centers for Medicare & Medicaid Services (CMS) | Who is the provider? | Claims, referrals, clinical/administrative transactions |
| GLN | GS1 US | Where does this go? | Purchase orders, shipping, invoicing, supply-chain routing |
If a practice already works with a pharmaceutical wholesaler or a group purchasing organization, a GLN may already be assigned without anyone at the practice realizing it. If not, one is licensed directly through GS1 US, often alongside a GS1 Company Prefix if the practice needs to distinguish multiple locations or departments.
The EDI Layer That Actually Moves the Order
A GLN identifies the location, but it doesn’t move a purchase order on its own. That work is done by Electronic Data Interchange under the ANSI X12 standard, maintained by the Accredited Standards Committee X12. EDI replaces the fax-and-email cycle most small practices still run on with a standardized document exchange, and it’s built around a specific set of transaction types:
- EDI 850 – Purchase Order: the practice’s electronic order, sent to the distributor.
- EDI 855 – Purchase Order Acknowledgment: the distributor’s confirmation of pricing, availability, and receipt.
- EDI 856 – Advance Ship Notice: shipment detail, including quantities and expected delivery timing.
- EDI 810 – Invoice: the automated billing document that closes the loop.
- EDI 846 / 832 – Inventory and Product Data: catalog updates and replenishment data that keep par levels accurate.
The GLN is what tells this chain of documents where the order originates and where it should land. Without it correctly assigned and shared with a distributor, automated par-level reordering — the process of a system quietly reordering supplies once stock crosses a set threshold — has nothing reliable to route against, and a practice ends up back on manual phone-and-fax ordering even after paying for inventory software that was supposed to eliminate it.
The Other Half of GS1: GTIN and GDSN
A GLN identifies where an order goes. A separate GS1 identifier, the Global Trade Item Number, identifies what’s in the order — the specific product, manufacturer, and unit of measure, typically represented as the barcode on the box itself. Together, GLN and GTIN give a purchase order both halves of the address it needs: destination and contents.
Keeping that product data accurate across every distributor a practice orders from is the job of the Global Data Synchronization Network, a subscription-based system that lets suppliers and buyers share certified, consistent GTIN and GLN data instead of each side maintaining its own catalog by hand. For a practice juggling several vendors for consumables, durable equipment, and specialty supplies, GDSN participation (usually handled on the distributor side, not the practice side) is what keeps par-level counts from drifting out of sync with what a barcode scan actually says is on the shelf.
What This Means the Next Time a Vendor Asks for Your GLN
When an inventory-management vendor, a GPO, or a distributor’s onboarding form asks for a GLN, the answer isn’t “we don’t have one” and it isn’t the NPI copied into the wrong field. It’s a specific, license-able identifier that most practices either already have through an existing GPO relationship or can request directly from GS1 US in a matter of days. Getting it right the first time is the difference between an inventory system that reorders itself correctly and one that quietly fails every time a shipment goes to the wrong department.
The practical takeaway for a small practice evaluating supply-ordering or par-level software: ask any vendor directly whether their system speaks EDI ANSI X12 (850/855/856/810) and whether it can ingest or assign a GLN per location. A platform that can’t answer both questions clearly isn’t ready for automated reordering, no matter how polished its dashboard looks.
Conclusion
The GLN vs. NPI mix-up is a small, specific error, but it’s exactly the kind of gap that keeps a practice stuck on manual ordering long after they’ve bought software meant to fix it. Understanding that an NPI identifies a provider while a GLN identifies a location — and that EDI ANSI X12 transaction sets are what actually carry a purchase order between the two — is the first step toward a supply chain that runs on standards instead of phone calls.