There's a specific moment in a dental group's growth when supply spend stops being a manageable line item and starts being a mystery. It usually arrives somewhere between the second and fifth location. Someone on the leadership team — an ops director, a partner, the person who signs off on the budget — asks what should be a simple question:
"What did we spend on supplies last month, across all our locations?"
And nobody can answer it. Not because the money was mismanaged, but because the information to answer it doesn't live in any one place. It's scattered across separate vendor portals, separate invoices, separate email inboxes, and separate office managers' heads. Getting a real number means a week of invoice archaeology — and by the time you have it, the month it describes is long gone.
This is the problem most multi-location dental groups actually have. Not overspending. Invisibility. And the standard prescription for it — "we'll centralize purchasing" — is exactly the wrong fix, for reasons worth understanding before you spend money trying to implement it.
The problem isn't spending, it's that nobody can see it
A single practice runs procurement on trust and memory. The office manager knows the reps, knows roughly what things cost, knows what to reorder and when. That informal system is efficient and it works — for one office.
Add locations and the informal system doesn't scale, it fragments. Each office keeps running on its own memory, but now there are three or eight or fifteen separate memories, none of which talk to each other. The group's leadership sits on top of all of it with no line of sight. They find out what was spent after it's spent, when the invoices arrive — by which point every decision has already been made and the money is already gone.
Notice what the problem is and isn't. It isn't that any office is doing something wrong. It's that the group has no way to see across the offices. That distinction matters, because it points to a completely different solution than the one most groups reach for first.
Why "we'll just centralize purchasing" fails
The instinct is understandable: if the problem is that ordering is scattered, pull it together. Route every order through a central purchasing function or a corporate approval queue. On a whiteboard, it's clean.
In practice, it breaks against how offices actually work:
The rep relationship you can't see on the org chart. The office manager at your busiest location has worked with the same distributor rep for eleven years. That rep knows the practice, handles problems with a phone call, and occasionally makes a backorder disappear. Route that ordering through corporate and you haven't just changed a process — you've severed a relationship that was quietly saving the office time every week. The office manager knows it, even if leadership doesn't.
The emergency that can't wait for corporate. A location runs out of something mid-morning with a full schedule. The office manager needs it now, not after a purchase request sits in an approval queue until someone at corporate gets to it. So they call the rep directly and order it the old way. The centralized process didn't survive contact with a busy Tuesday.
Approval-for-everything resentment. When staff who've responsibly ordered supplies for years suddenly need sign-off to buy a box of gloves, the message they hear is "we don't trust you." Sign-off on a $4,000 equipment order is reasonable. Sign-off on routine consumables feels like bureaucracy for its own sake, and people treat it accordingly.
Here's the part that makes over-centralization actively counterproductive: offices route around systems that slow them down. They keep a side vendor account. They order "off the books" and expense it later. They batch requests to avoid the approval friction. Every one of those workarounds is another place the money goes that your central system can't see. You set out to increase visibility and, by making the official path painful, you fragmented ordering into a dozen unofficial ones. Visibility gets worse.
What actually needs to be central (and what doesn't)
The fix isn't to centralize ordering. It's to centralize visibility and guardrails, and deliberately leave ordering where it already works.
Draw the line like this.
Centralize the things leadership is accountable for:
- Real-time spend by location. What every site is spending, as it happens — not a quarter later.
- Budgets with thresholds. Each location gets a monthly number appropriate to its size and patient volume, and someone can see it approaching in real time instead of discovering the overrun after the fact.
- Approval only above a dollar amount. A threshold, not a gate on everything. Routine orders flow; the large or unusual ones get a look.
- Price visibility across sites. The ability to see that the same item costs different amounts at different locations — which, as we'll see, it almost always does.
Leave local the things offices do well:
- Vendor choice. Let the office keep its distributors, its account numbers, its reps, its negotiated pricing.
- Everyday ordering. The routine reorder stays a two-minute task the office manager owns, not a request they submit and wait on.
- Receiving. The people who unpack the boxes and know what actually showed up stay in charge of confirming it.
The whole move is to put a thin layer of visibility and guardrails over how offices already operate, instead of replacing how they operate. Leadership gets control of the numbers. Offices keep control of the ordering. Nobody has to route around anything, because the fast path and the official path are the same path. This is the same balance our DSO procurement guide frames as centralization with local flexibility — and it's the heart of standardizing ordering across a group without a painful rollout.
The "same item, three prices" problem
Here's the thing centralized visibility surfaces almost immediately, and it's usually the first jolt: your locations are paying different prices for the identical item.
Not because anyone made a bad deal. It happens innocently. Each location opened at a different time, was set up by a different manager, and negotiated (or simply inherited) its own pricing with each vendor. Rates drift. A price increase lands quietly on one office's autopay invoice and not another's. One site bought from a backup vendor during a stockout two years ago and never switched back.
Consider a purely illustrative example — the specific numbers are made up to show the shape of the problem, not a claim about any real group. Say a nitrile exam glove costs one location $8.40 a box, a second $9.10, and a third $9.75, all for the same product. On a single box the gap looks like rounding error. But that item might move a few hundred boxes a year at each site, and it's one line in a catalog of hundreds of items, each with its own quiet spread. The per-item difference is invisible; the aggregate across a full catalog and a full year is the number leadership actually cares about — and it's precisely the number nobody can see, because each office only ever sees its own vendor's price and assumes it's normal.
You don't fix this by mandating the cheapest option everywhere — that ignores real reasons a location uses a particular vendor. You fix it by making the spread visible, so you can decide, deliberately, where to negotiate or consolidate and where the difference is worth it. The insight is the point. You can't manage a gap you can't see.
A phased path that offices will actually adopt
The reason standardization projects fail is almost always sequencing. Groups start with the hardest, most disruptive change and lose the room before they get to the easy wins. Reverse it.
Phase 1 — Visibility only. Nothing changes for office managers on day one.
Bring every location's orders and invoices into one place so spend rolls up automatically by location, category, and vendor. Critically, no office changes how it orders. Same vendors, same reps, same process. You're not asking anyone to do anything differently — you're just turning on the lights. This is what earns adoption, because there's nothing to resist. And the picture alone almost always reveals obvious wins: duplicate accounts, the price spreads above, a vendor one office is overpaying.
Phase 2 — Budgets and threshold approvals.
Once spend is visible, add per-location budgets and a single, sensible rule: approval required only above a dollar threshold. Everyday ordering still flows without friction. Leadership gets guardrails on the spend that matters without turning routine reorders into paperwork.
Phase 3 — A shared catalog for the top items.
Only now, with trust established and data in hand, standardize the menu for your highest-volume items — say the top 50 consumables — so "a box of gloves" means the same product at the same negotiated price group-wide. Locations still order what they need; they're just ordering from a common source of truth for the items where standardization actually pays.
The sequence is the strategy. Groups that start at Phase 3 fail — they lead with the most disruptive change, hit resistance, and stall. Groups that start at Phase 1 succeed, because each phase delivers value on its own and each one earns the credibility to attempt the next. You get visibility before you've changed a single order.
Questions to ask before you buy anything
If you're an ops director evaluating tools for this, most of the sales conversation will be about features. These three questions cut to whether a tool fits the visibility-first approach or quietly forces the centralize-everything approach that offices reject:
"Can each office keep its own vendor accounts and reps?" If the answer requires collapsing every location onto shared accounts or dropping vendors, you're buying the disruptive path. The right tool maps each location's existing accounts into one view rather than replacing them.
"Does this require retraining every office to place orders?" If turning it on means every office manager learns a new ordering workflow on day one, you've lost Phase 1 — there's nothing painless about it, and adoption will fight you. Visibility should be able to come on without changing how anyone orders.
"What rolls up automatically, and what depends on someone entering data?" Real-time visibility only works if spend flows in on its own. If the rollup depends on each office diligently keying orders into a second system, you've just recreated the spreadsheet problem with a nicer interface — it'll be current for about a week.
Two adjacent things worth checking while you're at it: whether the same visibility extends to inventory and, for any surgical sites in the group, whether it connects to case-level costs — the same discipline that makes preference cards accurate depends on that link.
Where SupplyLasso fits
SupplyLasso is built for exactly this pattern. Sites keep their own vendors, their own accounts, their own reps, and their own shelves — nothing about how an office orders has to change to get started. On top of that, approvals, budgets, and spend roll up to the group automatically and in real time, and you get per-item price comparison across locations, so the "same item, three prices" spread stops being invisible.
It's honest to say where we are: SupplyLasso is early, and its most proven ground today is live in an oral surgery practice, ordering electronically direct to Benco. But the design is deliberately the visibility-first, keep-ordering-local pattern this guide describes — because that's the version of "getting control of supply spend" that offices actually adopt instead of route around.
If you've hit the moment where nobody can answer what the group spent last month, schedule a demo and we'll show you what that number looks like when every location finally rolls up into one view.