Is purchase order software robust enough for DSOs? A 7-point test

Within a single location practice, purchase order software has a simple job and it’s to make ordering easier than juggling supplier portal passwords or keeping a shared spreadsheet updated. 

But what works for one office can break down quickly across dozens of locations.

A DSO needs more than a better checkout process. It needs dental procurement software that can control purchasing across the organization without making everyday ordering harder for individual practices.

This guide covers the seven things DSO leaders should evaluate before choosing purchase order software, including the questions that can reveal the difference between a true procurement platform and a marketplace with a procurement label.

What breaks when a DSO buys purchase order software built for a single office

If you're still weighing whether procurement software is worth it at all, that's a separate case to make with its own numbers. This piece assumes you're past that decision and need to know which platforms can actually hold up once you're managing real locations, not a pilot.

Affiliation with DSOs has more than doubled since 2015, reaching 16.1% of the U.S. dentist workforce, and that growth is happening at exactly the size tier where single-office tools stop working. 

A platform built for one location was optimized for a narrow set of decisions: one budget, one set of supplier relationships, one office manager who knows every price by memory. None of that holds at 20 or 50 locations, which is why dental procurement software purpose-built for DSO procurement looks completely different from what a solo practice needs.

The biggest problem with general procurement software

A common problem is software that looks like a procurement platform but functions more like a supplier marketplace with basic purchasing tools layered on top. A team member orders from an Amazon-style catalog, the request routes through a rubber-stamp approval, and a receipt gets emailed. What's missing is the purchase order itself. Sure, a receipt confirms a transaction happened. 

It doesn't commit a vendor to a price, and it gives an AP team nothing to match against when the invoice arrives with a different number on it. That gap is exactly why a cart confirmation isn't the same as completing the purchase order process, which is what actually binds a vendor to a price in the first place.

That gap is exactly why the seven criteria below matter more than a features list. Robust purchase order software has to do all seven of them at once, and most tools built for a single office were only ever asked to do two or three.

The 7-point test for purchase order software at DSO scale

Each of the seven criteria below maps to a specific failure mode. A platform that skips one of them isn't missing a feature but leaving a hole a CFO or an auditor eventually finds. Here's what purchase order management software has to get right, roughly in the order a buyer discovers the gaps.

1. It issues a real purchase order, not a cart confirmation

The purchase order is the single document that turns a quoted or negotiated price into the price of record. Once it's issued, the vendor is bound to it, and accounts payable has something concrete to check an invoice against.

• A cart confirmation or emailed receipt has no such standing. It documents that an order happened, not what price the practice is entitled to.
• Purchase order tracking software should show the full lifecycle on one record: request, approval, PO issuance, receipt, and invoice.
• Without a PO, a price dispute comes down to a screenshot and a phone call instead of a document both sides already agreed to.

If the platform stops at placing an order instead of issuing a purchase order, every step that follows becomes harder to manage.

2. It routes approval workflows without slowing down the person placing the order

A formulary and an approval chain only work if the person scanning a reorder tag at 7 a.m. can still submit a request in under a minute. Multi-location purchase order approval software has to serve two audiences at once: the assistant who just needs supplies and the controller who needs a paper trail.

• Location-level roles should route routine, in-budget requests through automatically instead of queuing every order for manual sign-off.
• Purchase order automation should flag only what's out of formulary, over budget, or from a new supplier, not every line item.
• Approval rules need to hold at 5 locations and 50 without a rebuild each time the DSO adds a practice.

When either job gets ignored, the controls disappear or the assistants stop using the system and go back to a supplier's own website, which is the same principle behind sound purchasing controls more broadly.

3. It enforces a formulary at the point of request, not after the fact

A DSO's negotiated pricing and preferred products only translate into real savings if the formulary shows up before someone orders, not in a report after the month closes.

• The requester should see the approved product and its negotiated price first, with off-formulary items requiring a reason or an extra approval.
• Consolidation decisions made at headquarters need to show up in what locations are actually ordering within days, not the following quarter.
• A formulary that lives in a spreadsheet or a memo gets followed inconsistently across locations, which is where savings from group purchasing power quietly disappear.

This is the criterion that turns purchasing volume into a bottom-line result instead of a slide in a board deck.

4. It captures off-catalog and custom-supplier purchases in the same audit trail

Dental practices deal with specialty items, local lab relationships, and one-off vendors that never show up in a standard catalog. A platform that can't handle those pushes that spend onto a personal or practice credit card, outside any oversight.

• Custom suppliers and custom products should be addable inside the platform, with negotiated terms preserved, rather than routed around it.
• Off-catalog purchases still need a purchase order and a receiving record, or they simply don't exist in the audit trail.
• A platform that only tracks its own marketplace inventory will always leak spend to the purchases it can't see.

The DSOs with the cleanest books are usually the ones where buying locally never meant buying invisibly.

5. It runs a three-way match before an invoice gets paid

A three-way match compares the purchase order, the receipt of goods, and the supplier invoice before a payment goes out, which is the backbone of getting invoice matching right in a dental practice. It's the control most likely to catch a price discrepancy before it costs money instead of after.

• The system should flag a mismatch automatically instead of relying on someone in AP to remember what was quoted six weeks ago.
• Best-in-class accounts payable teams process an invoice in about 3.1 days, compared with 17.4 days for teams still reconciling by hand.
• Purchase order tracking software that stops at "order placed" can't support this match. The three-way match needs the PO's committed price, not a supplier's list price that day.

This is also where price creep gets caught. A supplier who raises a price 2% at a time counts on nobody checking the invoice against the quote, which is exactly how price creep survives audits for years.

6. It stays vendor-agnostic in how it makes money

If a platform earns a cut of what gets purchased through it, its own spend analytics have a built-in reason to point buying toward whichever vendor pays it the most, not whichever vendor quoted the best price.

• Ask directly how the platform is compensated: flat subscription, transaction fee, or a percentage of spend routed through it.
• A vendor-agnostic platform should make it just as easy to add an outside supplier as one already in its marketplace, the same reason a sound multi-supplier approach depends on a platform that doesn't play favorites.
• Procure to pay software that profits from routing volume to specific vendors can't also be the system a CFO trusts to report where spend should be cut.

This is easy to miss during a demo. The problem often becomes clear later, when the platform’s recommendations and reporting consistently favor the same suppliers.

7. It reports at the enterprise level on clean, normalized catalog data

Dashboards are only as trustworthy as the product data underneath them. If the same box of gloves shows up as five different SKUs across five locations, a spend report will undercount that category and miss the consolidation opportunity entirely.

• Enterprise reporting needs a normalized catalog, not a rollup of whatever each location happened to type into a free-text field.
• A DSO's procurement team should see spend by category, location, and supplier without exporting five spreadsheets and reconciling them by hand.
• Reporting that only covers marketplace purchases misses everything captured in point four, which quietly understates total spend.

A dashboard built on messy data will always look confident. It just won't be right.

What to ask any purchase order software vendor

The seven criteria above translate into a short list of questions worth asking any purchase order approval software vendor before the conversation moves to the parts of the demo designed to impress rather than inform.

• Does this system issue a real purchase order, or a cart confirmation?
  A strong answer: Every request converts to a PO with a locked price before it goes to the supplier.
  Red flag: The order is simply emailed or placed directly, without a formal PO.
• How does formulary enforcement work at the point of order?
  A strong answer: The requester sees the approved product and negotiated price before submitting the order.
  Red flag: Compliance is measured after the purchase has already been made.
• Can I add my own suppliers and custom products?
  A strong answer: Yes, with the same negotiated pricing, controls, and audit trail as catalog items.
  Red flag: Those purchases have to be managed outside the platform.
• How does three-way matching work, and who resolves an exception?
  A strong answer: The system automatically flags mismatches between the purchase order, receipt, and invoice.
  Red flag: Accounts payable has to find and resolve discrepancies manually.
• How is the platform compensated?
  A strong answer: A transparent subscription model that does not change based on which suppliers or products you purchase.
  Red flag: The vendor cannot clearly explain how it makes money.
• Can I see spend by location and category without exporting data?
  A strong answer: Yes. Spend data is available live by location, category, supplier, and other relevant dimensions.
  Red flag: You need to export the data and build your own reports in a spreadsheet.

If your current process would fail more than one of these questions, it's worth seeing what changes. Schedule a demo and bring your own formulary and approval rules to the call.

The purchase order test most DSOs skip

Purchase order software is often evaluated on how quickly someone can place an order because that is the part every vendor demos well. But the real test starts after the order is placed.

Does the negotiated price hold? Can a CFO trust the numbers they see across every location?

A DSO that skips those questions may not discover the problems until two years and twenty locations later, when the numbers stop adding up.

Method issues a real purchase order on every request, matching it against a formulary and a location's budget before it ever reaches a supplier. Method Pay runs the three-way match automatically and flags a mismatch before payment goes out, and formulary management keeps negotiated pricing enforced at the point of order instead of in a report after the fact. Schedule a demo to see how your own procurement process holds up against the test.