What gets bundled in dental
The inventory
Only vendors this wiki has researched appear here; the list is representative, not exhaustive. Fuller PMS detail is in the PMS directory.
Legacy server products such as Dentrix, Eaglesoft, and Open Dental assemble similar capabilities through partners and software bridges. That creates a different integration burden and can make switching vendors more complicated.
The evaluation rubric
Ask what the software costs without payment processing. If the vendor cannot provide a separate price, some of the software cost may be built into processing margins that are harder to compare.
Where bundling can create problems in a DSO structure
Three single-practice assumptions can create problems for a dental support organization (DSO) running multiple professional entities: 1. Settlement destination. Route patient receipts to the account authorized for the enrolled billing or merchant entity under state law, payer and program terms, merchant and bank documents, and any approved transition mechanics. A platform that forces every location into one configured account can misroute funds and obscure entity ownership unless the structure is expressly authorized and maintains complete per-entity ledgers. See Why DSO banking is different. 2. Multiple employers. Which entity employs each person depends on state law, licensure rules, contracts, duties, and actual supervision. Many groups use professional entities for licensed clinicians and a DSO for administrative personnel, but that is not a national rule. A payroll product designed around one employer may place workers on the wrong entity’s books or require separate instances that were not apparent during the sales process. 3. Reporting per entity. A platform reporting only at the practice level cannot produce the per-entity financials a DSO needs. See Produce investor-grade reporting. Test all three during the demo using your actual entity structure and receipt flows.Platform-bundled vs bank-integrated
The two integration models attach financial services at different points:
For a single-location practice, a bundled platform can be a sensible tradeoff because it may post card payments to the patient ledger automatically. A multi-entity DSO needs to test more than that workflow. Bank integration does not answer the legal or accounting questions by itself. The product still needs to support authorized receipt destinations, the actual employer for each worker, appropriate permissions, and separate entity ledgers. Apply the same rubric to either model.
When bundling may fit
- Single-entity, single-location practices, where integration saves real time
- Very early stage, where speed matters more than optimized economics
- Small teams with no finance function to manage multiple vendors
- Products with useful native integrations, such as imaging inside the chart or payments that post to the ledger
When bundling may be a poor fit
- Multi-entity groups, when the product cannot represent the group’s entity structure
- Meaningful card volume, where blended pricing costs more than negotiated interchange-plus
- Groups planning a raise or sale, where per-entity financial clarity affects valuation
- Groups wanting their own analytics, where data portability may matter more than a bundled integration
Sources
- Curve Dental, DSO page and Fast facts (vendor pages).
- Archy, archy.com; Series A announcement, PR Newswire, 2024; Pearl AI integration, Dentistry Today.
- Planet DDS, Denticon; Planet DDS release via Yahoo Finance (vendor-sourced); DentalOS coverage, John Flucke, July 2026.
- Patterson Dental, Fuse.
- tab32, tab32.com (vendor page); roundup at SoftSmile.
- Oryx, comparison page (vendor page).