DMS Integration Best Practices for Automotive Dealerships

Start with the DMS Platform, Not the Tool

Any integration evaluation should begin by confirming that the tool in question has a verified, active integration with your specific DMS. A well-regarded tool with no real DMS integration, or one that relies on a workaround data export rather than a true API connection, will create reconciliation problems, data lag, and manual work that undermine the reason for deploying it. The right first call is not to the vendor; it is to your DMS account team to confirm what is actually certified. Industry resources such as the NADA Dealer Academy also publish guidance on technology evaluation that complements the DMS-specific confirmation step.

Distinguish Read-Only from Read/Write Integrations

Tools that only read DMS data, such as those pulling customer records, VIN data, or appointment history, are lower risk but also lower impact. The highest-value integrations, including appointment booking, RO creation, and deal submission, require the tool to write data back to the DMS. These are worth more scrutiny during evaluation. An AI voice agent like Viova (see our Voice AI guide), for example, only delivers its full value when it writes appointments directly to the DMS in real time; without that, the tool is a more organized voicemail system. Ask the vendor specifically: what data fields does your tool write to the DMS, and what happens if the write fails?

Understand the Integration Fee Structure

Most major DMS platforms charge integration fees to third-party vendors, and those costs are typically passed through to the dealer in some form, either as a monthly line item or built into the tool's pricing. CDK-based integrations through the Fortellis marketplace carry per-transaction or per-dealership fees that can add up at scale. Ask any vendor to disclose the full cost of integration, including any fees charged by the DMS provider on top of the tool's subscription. Vendors that decline to disclose those fees are usually hiding them in the contract.

Prioritize Tools That Do Not Require New Interfaces for Front-Line Staff

The most effective integrations work transparently within the workflows your team already uses. A service scheduling tool like Xtime that books appointments directly into the DMS means the advisor opens the same screen they always do and sees appointments that arrived automatically. The same principle applies to reputation platforms like Podium and inventory tools like vAuto: they earn their keep when data flows back into the DMS without a second login. A tool that requires advisors to check a second system, reconcile two lists, or manually transfer data negates much of its value and creates adoption friction that degrades data quality over time. Front-line adoption is usually the deciding factor in whether an integration delivers what the demo promised.

Build for Fixed Ops and Variable Ops Separately

Fixed ops and variable ops have different workflows, different data requirements, and different success metrics. A CRM built for sales lead management, such as VinSolutions, is not the right tool for service retention, and a service scheduling tool that handles inbound phone calls for the shop is not designed to manage sales appointment callbacks. Map each integration to the specific department and workflow it serves rather than looking for a single tool that claims to do everything.

Treat Integration as Ongoing, Not a One-Time Event

DMS platforms issue updates that can break third-party integrations. A tool that worked correctly six months ago may need an updated connector after a DMS platform update. Assign ownership of integration monitoring to someone on your IT or operations team, and confirm with vendors what their process is for maintaining integrations across DMS version updates. The dealerships that get the most out of their integrations are the ones that treat the stack as a living thing rather than a set-and-forget purchase.

For category-specific guidance, see the Integration Categories hub. For platform posture, see the DMS Compatibility Guide.