How to verify dealership software integrations
An integration is only verified when both products, versions, markets, data objects, direction, frequency, provider, fees, monitoring and support ownership are documented for the dealer's configuration.
An integration is only verified when both products, versions, markets, data objects, direction, frequency, provider, fees, monitoring and support ownership are documented for the dealer's configuration.
Reject the logo-wall shortcut
A marketplace badge or partner logo is a discovery lead. It does not establish read versus write access, field scope, timing, OEM availability or who fixes failures.
Ask both sides
Require matching written confirmation from each vendor and name any certified data intermediary. Resolve discrepancies before contracting.
Test and monitor
Use representative records, failures and reconciliation reports in acceptance testing. Contract alerting, escalation, remediation and historical data recovery.
Write the integration down as a record, not a claim
"They integrate" is not a fact you can act on. A usable integration record names both products and versions, the direction of each object, the exact fields, the trigger and frequency, who operates the connection, who pays for it, what its current status is, when that was last confirmed and by whom. Anything not established should say so explicitly, because a silent gap reads as a confirmed capability.
- Both product names and the editions actually licensed
- Each data object and whether it reads, writes or both
- Trigger and frequency: real time, batch, or on demand
- The operating party, the fee owner and the support owner
- The date the scope was last confirmed with both vendors
Ask what breaks, not what works
Demonstrations show the happy path. The questions that matter are about the exceptions: a duplicate record, a customer who opts out in one system, a deal that is restructured after it syncs, a vehicle that changes status mid-transfer, a field that exceeds a length limit. Ask each vendor to describe what the other system sees in each case, and compare the two answers.
Establish who answers when both vendors blame each other
The most expensive integration failure is not a technical one; it is a support ticket that sits open for weeks because each side maintains the other is at fault. Before contracting, name the party that owns diagnosis, the escalation path when a case crosses the boundary, the response commitment and what happens if the two vendors' commitments differ.
Re-verify at the events that change it
An integration record is accurate on the date it was checked and not afterwards. Product releases, ownership changes, certification program changes and OEM program changes all move the scope without notifying the dealer. Attach a confirmation date to each record and treat these events as triggers to check it again.
- A major release on either side
- A change of ownership or corporate parent for either vendor
- A change to the DMS data-access program or its fees
- Renewal planning for either contract
Compare the relevant provider categories
Data integration & middleware
APIs, normalized feeds, warehouses, identity and vendor-to-vendor data movement.
Open category →Dealer management systems (DMS)
Accounting, sales, parts, service and OEM-connected system-of-record platforms.
Open category →CRM & sales enablement
Lead, showroom, follow-up, appointment and customer lifecycle workflow.
Open category →How to verify dealership software integrations FAQ
What is a bidirectional integration?
It reads from and writes to another system, but the phrase is incomplete until the exact objects, fields and triggers are named.
Who pays dealership integration fees?
Fees may be charged by either vendor, a data intermediary, the DMS or an OEM program. Put every setup, recurring and usage charge on one cost schedule.
How often should integrations be reviewed?
Review them at implementation, after material releases, when ownership or providers change, and during renewal planning.
Does a partner badge mean two products are integrated?
No. A directory listing or partner logo establishes a commercial relationship and nothing about data scope, direction, availability in your market or who fixes a failure. Treat it as a lead to verify, not as evidence.
What should a dealer ask about integration fees?
Who charges them, to whom, on what basis, and whether they change with volume or at renewal. Fees can originate from either vendor, from a certified data intermediary or from the DMS access program, and quotes routinely omit the ones the other party charges.
What does 'certified' mean in a DMS integration program?
It means the vendor has met that program's requirements for access, which is a real signal about data access and nothing about product quality or the depth of the specific connection you need. Ask which fields the certification actually covers.
How should an integration be accepted at go-live?
With representative records including exceptions, a reconciliation report proving what moved, and a named owner for failures. Acceptance on a successful demonstration alone leaves the failure modes untested.