If you run procurement for a multi-location dental group or DSO, you already know the quiet problem that never shows up cleanly on a P&L: every office orders a little differently. One location's office manager has a favorite rep at one distributor. Another buys the same gloves from a different vendor at a different price. A third still places orders by phone and keys the invoices in by hand. Nobody is doing anything wrong — and that's exactly why it's so hard to fix.
Multiply that across eight, fifteen, or forty locations and the cost isn't one big leak. It's a thousand small ones: price inconsistencies, duplicate vendor accounts, no visibility into what's actually being spent until the invoices land, and an approval process that lives in someone's inbox. This guide walks through why multi-location procurement breaks, what "standardizing" actually means in practice, and how to get there without forcing every office onto a rigid system they'll resent.
Why procurement breaks as you add locations
A single practice can run procurement on habit and trust. The office manager knows the reps, knows the prices, knows what to reorder. That informal system works — for one office.
The moment you have multiple locations, three things happen at once:
Pricing fragments. Each location negotiates (or inherits) its own pricing with each vendor. The same composite, the same burs, the same PPE can cost meaningfully different amounts depending on which office is buying and which account number is on the order. Without a single place to see it, you can't even tell it's happening.
Vendor relationships multiply. Every location accumulates its own set of vendor accounts. Now you have the same distributor represented by five account numbers across five offices, each with its own ship-to, its own contact, its own terms. Consolidating purchasing power becomes nearly impossible because you can't see the whole picture in one view.
Visibility disappears. At the group level, the people responsible for the budget find out what was spent after it's spent — when invoices arrive. By then, the decisions are made and the money is gone. There's no real-time line of sight into what each location is ordering, from whom, at what price.
None of this is a discipline problem. It's a structural one. The informal system that works beautifully for one office simply doesn't scale, and bolting more spreadsheets onto it doesn't help.
What "standardizing procurement" actually means
"Standardize" is a word that makes office managers nervous, because they hear "you're going to take away the autonomy that lets me do my job." Done well, standardizing procurement isn't about stripping locations of control. It's about putting a consistent layer over the chaos so the group gets visibility and leverage while each location keeps ordering what it actually needs.
In practice, standardizing across locations means four things:
One catalog, many locations. A shared, group-level catalog of approved items and vendors — so "a box of gloves" means the same product at the same negotiated price whether it's ordered in office one or office fifteen. Locations order from a common source of truth instead of each reinventing it.
Consistent ordering and approval. A single workflow for how orders get created, who approves them, and how they're sent — applied across every location, instead of each office having its own ad hoc process. The approval rules can still vary by location or dollar threshold; what's consistent is that there is a process and it's visible.
Vendor accounts mapped, not merged. You don't have to collapse every location into one account — locations often need their own ship-to addresses and their own account numbers with each distributor for legitimate billing and delivery reasons. What standardizing means is mapping those accounts into one system so the group can see them all at once and route each order to the right account automatically.
Spend visible in real time. The whole point: leadership sees what every location is ordering and spending as it happens, not three weeks later. That's what turns procurement from a cost you discover into a cost you manage.
The integration question: how orders actually reach your vendors
This is where multi-location procurement gets technical, and it's worth understanding because it's where a lot of "procurement software" quietly falls short.
To standardize ordering across locations, the system you use has to actually talk to your vendors — or at least make sending orders to them effortless. Vendors support a few different integration methods, and a good multi-location setup has to handle the mix, because you'll never have all your vendors on the same one:
- Punchout lets a buyer shop the vendor's own catalog — with live, account-specific pricing and real-time stock — from inside your procurement system, then bring the cart back as an order. It's the most widely supported method, especially among distributors, because it puts the live catalog where the buyer already is.
- Electronic documents (cXML / EDI) let the system send purchase orders and receive order confirmations, ship notices, and invoices automatically, vendor-to-system, with no manual rekeying.
- Email and manual ordering still matter for the long tail of smaller vendors that don't offer either of the above — so the system needs to handle those cleanly too, ideally sending a proper purchase order document rather than making someone retype it.
The reason this matters for multi-location groups specifically: each location's account numbers and ship-to addresses have to route correctly through whichever method a given vendor uses. An order from your Rogers office and an order from your St. Petersburg office need to land on the right account, ship to the right place, and bill correctly — automatically, every time, without the office manager thinking about it. That account-and-location mapping is the unglamorous heart of multi-location procurement, and it's exactly what most generic tools get wrong.
How to get there without a painful rollout
The fastest way to make a standardization project fail is to mandate a rigid system that ignores how each office actually works. A more durable approach:
Start by seeing what you have. Before changing anything, get every location's vendors, account numbers, and current pricing into one place. Most groups have never actually seen this in a single view, and the picture alone usually reveals obvious wins — duplicate accounts, price gaps between offices, vendors you're paying more than you should.
Standardize the catalog, not the people. Build the shared catalog of approved items and vendors first. Let locations keep ordering the items they need from it. You're standardizing the menu, not dictating every meal.
Layer in approval and visibility. Add a consistent approval workflow and real-time spend visibility at the group level. This is what gives leadership control without micromanaging each order.
Connect the vendors you can, cleanly. Wire up punchout and electronic ordering for the vendors that support it, and make email/manual ordering effortless for the rest. The goal is that every order — regardless of vendor or location — flows through one system and lands correctly.
The point of the sequence is that each step delivers value on its own. You get visibility before you've changed a single order. You get a shared catalog before you've touched approvals. Nobody has to swallow a giant change all at once.
Where SupplyLasso fits
SupplyLasso is built specifically for this — procurement for multi-location healthcare groups, including dental groups and DSOs, ambulatory surgery centers, oral and maxillofacial surgery practices, and clinics. It's vendor-neutral by design: you keep your own vendor accounts and your own negotiated pricing, and SupplyLasso unifies them into one catalog, one ordering workflow, and one real-time view of spend across every location.
That includes the account-and-location mapping that multi-location groups actually need — each location's vendor accounts and ship-to addresses routed correctly and automatically — plus punchout to shop vendor catalogs with live pricing, electronic order confirmations, ship notices, and invoice matching for vendors that support them, and clean purchase-order sending for the ones that don't.
If you're running procurement across more than one location and you've felt the chaos this guide describes, that's exactly the problem SupplyLasso was built to solve. schedule a demo and we'll show you what your group's procurement looks like when every location finally runs on the same system.