Why do dental supply prices differ between locations?

Because each location built its pricing separately and it drifted from there. Sites open at different times with different reps and different negotiated rates, price increases land silently on autopay invoices at one office and not another, and a stockout once sends an office to a pricier backup vendor it never switches back from. None of it is a mistake anyone made on purpose — the prices diverge quietly, and because each office only ever sees its own vendor's price, the divergence is invisible from inside any single office.

How do I compare supply costs across my offices?

Pick your highest-volume items, pull one recent invoice from each location, and build a grid: item, site, vendor, price per unit — normalized so a box at one site is comparable to a case at another. Even ten items across four sites will usually surface spreads you didn't know existed. Doing it by hand once is genuinely useful; the catch is that it's a snapshot that goes stale the next time pricing drifts, which is why groups eventually want the comparison to update on its own from every site's live orders and invoices.

What the Same Supplies Cost at Each of Your Dental Locations

Here's a question. What does a box of nitrile exam gloves cost at each of your locations?

Not roughly. Not "about eight or nine dollars." The actual per-box price, this month, at each site. If you run a multi-location dental group, sit with that question for a second, because for almost everyone it's genuinely unanswerable without real work — a week of pulling invoices from separate portals, squinting at line items, and normalizing pack sizes by hand. A box here, a case there, one invoice buried in an office manager's inbox.

The reason you can't answer it isn't that the number doesn't exist. It's that the number lives in a dozen disconnected places, and no one ever puts them side by side. So here's what's almost certainly true, and almost certainly invisible: you pay different prices for identical items at different locations, and nobody in your group can see it.

How the spread happens (all of it innocent)

Nobody negotiated a bad deal. The price divergence between your sites is the accumulated residue of ordinary history:

Different sites, different starts. Each location opened at a different time, was set up by a different office manager, and negotiated — or simply inherited — its own pricing with each vendor. Two offices buying the identical glove from the identical distributor can sit on rates set two years apart under two different reps. There was never a moment where anyone lined them up.

Rates drift. Negotiated pricing isn't permanent. Contract terms lapse, promotional pricing expires, tiers reset. What was a sharp price at one office three years ago has quietly softened while nobody was watching.

The silent autopay increase. This is the big one. A vendor nudges a price up, the increase lands on an invoice, the invoice is on autopay, and it gets paid without anyone reading the line item. It happens at one office and not another, so two sites that started even slowly separate — and the separation never triggers a single alarm, because paying the invoice is automatic.

The stockout that never got undone. An office runs out of something, the usual vendor can't ship in time, so the office manager grabs it from a backup vendor at a higher price to keep the schedule moving. Correct call in the moment. But the reorder point now quietly points at the pricier vendor, and six months later the office is still buying there, paying more, for a reason nobody remembers.

Every one of these is reasonable. That's exactly why the spread is so persistent — there's no villain to catch and no obvious mistake to fix. It's just drift, and drift doesn't announce itself.

Why the invoices don't save you

You might think the invoices would surface this. You're paying them; the prices are right there. But invoices are structurally incapable of showing you the spread, for a simple reason: nobody reads line items across sites.

The person paying at each office sees only their own vendor's invoice, with their own vendor's price, and has no reference point to judge it against. To that person, $9.75 a box isn't high — it's just the price. It looks normal because it's the only number they see. There's no column next to it showing that the sister location two towns over pays $8.40 for the same box from the same distributor.

The comparison that would reveal the problem is precisely the one no single invoice contains. Each invoice is a self-consistent little world. The spread only exists in the space between invoices — across separate vendor accounts, separate bills, separate inboxes — and that space is exactly where nobody is looking. You'd have to gather one invoice from every site, for the same item, in the same month, and lay them side by side. Which no one does, because it's tedious and nothing forces it.

What the spread actually costs

Let's put rough numbers on it — and to be clear, these are illustrative figures chosen to show the shape of the problem, not a claim about any real group's savings.

Picture a four-location group and one everyday item: an exam glove that runs $8.40 a box at the cheapest site and $9.75 at the priciest, with the other two in between. Call it a modest $0.60 average per-box gap against the best price the group is already getting somewhere. On one box, that's nothing. But say each site moves a few hundred boxes a year — a few thousand boxes across the group — and the gap on this one commodity item quietly adds up to a few thousand dollars a year that exists purely because the sites aren't priced alike.

Now remember that gloves are one line. Your catalog has hundreds of consumable items, and most of them carry their own quiet spread for all the same reasons. You don't have to believe any specific figure to see where this goes: a small, invisible per-item gap, multiplied across a full catalog and a full year, is the number that actually matters — and it's the exact number the structure of separate invoices is designed to hide.

The point of the math isn't the total. It's that the total is unknowable from inside the current setup, and unknowable is a choice you can change.

What visibility actually looks like

Fixing this doesn't start with switching vendors. It starts with seeing.

Visibility means the same item mapped across every site and every vendor, with price-per-unit normalized so the comparison is honest — a box at one location lined up against a case at another, converted to the same unit, so you're comparing like to like instead of being fooled by pack sizes. And it means the spreads flagged for you, so the outliers surface instead of hiding in a spreadsheet you'd have to build.

Notice what the goal is not. The insight isn't "switch everything to the cheapest source." Sometimes a location pays more for a legitimate reason — delivery reliability, a rep who actually solves problems, a bundle that nets out fine. The goal is simply to know the spread exists so you can act on it deliberately: negotiate the outlier up to the group's best rate, consolidate where it clearly pays, or consciously decide a gap is worth it. You can't make any of those calls on a number you can't see. Visibility is what turns "we probably overpay somewhere" into "here is exactly where, and by how much."

This is the same principle that runs through getting control of multi-location supply spend generally: you manage what you can see, and step one is always seeing.

What to do this quarter, without buying anything

You don't need software to start. You need one afternoon and a willingness to do a tedious thing once.

Pick your top 10 items. The high-volume consumables you buy constantly — gloves, masks, common composites and burs, whatever moves. That short list is where most of the spend and most of the spread live.
Pull one recent invoice per site. For each of those items, find the price each location most recently paid. One invoice per office is enough for a first pass.
Build the grid by hand. Item down the side, location across the top. In each cell: the vendor and the price per unit — and do the pack-size math so a box compares to a box. Ten items across four sites is a forty-cell grid you can build in an afternoon.

Then look at the rows. Where one site is 15% over another for the identical item, you've found a conversation to have — with the vendor, or about consolidating. You'll likely find two or three of these on the first pass, and paying for the exercise right there.

Here's the honest catch, and it's the whole reason groups eventually stop doing this by hand: the grid is a snapshot, and it goes stale immediately. The next silent autopay increase, the next stockout detour, and your afternoon's work is out of date. Doing it once is genuinely useful. Doing it every month, by hand, across a growing catalog and a growing number of sites, is exactly the kind of task that doesn't scale — which is the case, if there is one, for letting the comparison keep itself current. (For the broader picture of how vendor accounts and pricing fragment as a group grows, our DSO procurement guide covers the structural side.)

Where SupplyLasso fits

SupplyLasso shows per-item price comparison across your locations automatically — because every site's orders and invoices live in one system, the same-item spread that's invisible across separate inboxes becomes a column you can actually read, and it stays current instead of going stale the day after you build it.

To be straight about where the product is today: SupplyLasso is early, and its most proven ground is live in an oral surgery practice, ordering electronically direct to Benco. The price-comparison-across-sites capability is built for exactly the problem this post describes — the box of gloves that costs three different amounts and never should have.

If you couldn't answer the glove question at the top of this post, that's the point. Schedule a demo and we'll show you what the answer looks like when it's a screen instead of a week of invoice archaeology.