A procurement platform recommends Supplier A. The DSO operator looks at the cost comparison, sees Supplier A at the top of the list, and approves the order. The recommendation seemed neutral. The interface presented it as data.
What the operator didn't see is that Supplier A pays the platform a placement fee. Or a referral commission on every order routed through the system. Or a percentage of the transaction volume sent their way. The recommendation wasn't neutral. It never was.
Many dental procurement platforms make a meaningful share of their revenue from supplier arrangements, not from the customers who use the software. That changes what the platform is optimizing for, and it quietly shapes what users see, what gets prioritized, and which suppliers benefit from the platform's design. Most DSO buyers don't know to ask about this during evaluation. They see a software invoice and assume that invoice represents the full cost of the relationship.
Most buyers assume they're paying for the software. Many are also paying in ways they can't see.
The common revenue models in procurement software include:
A DSO can be on a relatively modest software contract while generating significant revenue for the platform on the supplier side. The buyer rarely thinks to ask about the second number, and the platform rarely volunteers it.
This isn't a fringe critique. Peer-reviewed economics research on commission-driven platforms shows a consistent pattern: when a platform earns from the choices users make, it has a structural incentive to rank higher-commission options ahead of options that would better serve the buyer. The bias is documented and measurable across industries. Procurement software is not exempt from it.
A platform that earns when you buy from Supplier A has a reason, even a subtle one, to make Supplier A more visible, more accessible, or more attractive than Supplier B.
That bias rarely shows up as an obvious thumb on the scale. It shows up in design decisions that look reasonable on the surface:
The DSO is making purchasing decisions based on data the platform curates. A dashboard that says one supplier consistently offers the lowest price might be technically accurate within a curated set of options that excluded the suppliers who chose not to pay for placement. The buyer never sees what was filtered out. That's the structural problem.
Recent research on AI-driven procurement systems has found the same pattern in vendor-scoring algorithms: they can encode bias toward suppliers with certain integration histories or commercial relationships with the platform itself. Suppliers who didn't pay for integration get scored lower on inputs that have nothing to do with whether they'd serve the buyer well.
A conflicted platform compromises every procurement function that depends on clean, complete data.
If suppliers pay for visibility, the platform's recommendations on lowest cost may quietly exclude options that would have won on price. The cost comparison engine looks neutral. In reality, it's running against a dataset pre-shaped by who paid to be in it.
A DSO benchmarking a Supplier A renewal against numbers generated by a platform that earns from Supplier A is negotiating from a compromised position. The supplier knows the numbers. The platform knows the numbers. The DSO sees a version shaped by both.
When the platform earns commission on certain products, the analytics surrounding "preferred" alternatives carry an embedded bias. Recommendations to switch to lower-cost alternatives may exist for some categories and not others, and the categories where they don't exist may correlate with where the platform's revenue is concentrated.
The dashboards a CFO uses to evaluate supplier performance reflect what the platform shows, not the full market. Reports on price creep, supplier reliability, and category spend all depend on the platform being a neutral observer. It cannot be a neutral observer when its revenue depends on specific outcomes.
The cost of getting this wrong is significant. APQC's healthcare supply chain benchmarks consistently document substantial gaps between top-quartile and bottom-quartile organizations on procurement cost and cycle time. Becker's Dental has reported on the savings DSOs capture when they move from fragmented supplier relationships to consolidated, data-driven procurement. Clean, complete data separates the operators capturing those savings from the ones leaving them on the table. A platform that profits from how you buy is structurally unsuited to surface those problems honestly.
The alternative is a procurement platform that earns its revenue from the value of the software, not from where customers buy.
That sounds like a marketing claim. It's a structural difference in how the business is built, and it shows up in how the product behaves:
A vendor-agnostic platform can support a deliberate two-to-three supplier strategy because it has nothing to gain from steering volume in any particular direction. It can surface honest comparisons between branded products and private-label equivalents because it doesn't earn more when you buy one over the other. It can recommend you negotiate harder with a current supplier because that recommendation doesn't cost the platform anything.
The DSO becomes the only customer the platform has financial reason to serve. That's the alignment that makes the data trustworthy.
Undisclosed supplier interests, kickbacks, and preferential treatment routinely appear in procurement fraud literature as the most common red flags. The questions below aren't a clever sourcing trick. They're standard due diligence.
A platform that answers these questions plainly is showing you something about how it operates. A platform that deflects, gives vague answers, or treats the questions as inappropriate is also showing you something. Both responses are useful.
Procurement software is supposed to give DSO leadership a clearer view of how their organization spends money and where it can spend less. A platform with a financial stake in the buying decision can't deliver that view honestly, no matter how clean the interface or how strong the feature set looks in a demo. The structure of the business model determines what the data is allowed to tell you.
When the platform earns from your suppliers, the platform serves your suppliers. When the platform earns from you, the platform serves you.
To see how Method's vendor-agnostic model changes the data you get and the decisions you can make from it, book a demo.