What does 'source of truth' mean in a dealership technology stack?

Designate per object, not per system

Truth is object-specific. The DMS may own the deal and the repair order while the CRM owns the opportunity and the CDP owns consent. Write down which system owns which object.

Direction follows ownership

Once ownership is set, integration direction follows: non-owners read, the owner writes. Bidirectional connections without a designated owner are how conflicting records are created.

Reconciliation is the proof

Pick a small number of figures, units, gross, repair orders, and reconcile them across systems monthly. Persistent variance means the ownership rule is not being honoured.

Say it in the RFP

Ask every candidate which objects it expects to own and what it does when it is not the owner. Products that assume ownership of an object you have assigned elsewhere will fight your architecture.

A simple ownership table

Make a table with one row per object, such as customer, vehicle, deal, repair order, opportunity, consent and inventory, and columns for the owning system, the systems that read it, the direction of updates and the person responsible. Keep it to a page. The table settles most arguments about which record is correct and gives project teams a reference when adding tools.

Handling conflicts

When two systems disagree, the owner's value wins, and a process should exist to correct the other. Decide who investigates a mismatch and how it is fixed, for example a weekly exception report reviewed by a named person. Without this step, differences accumulate quietly and reports become unreliable.

Common mistakes with truth ownership

Naming a system as the source of truth for everything, allowing two-way updates on the same field without rules, not telling vendors about the ownership decision and never testing it are typical problems. Review the table when a new system is added or an existing one is replaced, since each change can shift ownership without anyone deciding it.

Questions to answer with your vendors

Which objects will you own in our stack? Which will you read and which will you update?

How do you handle a conflict when another system changes the same field? How do you tell us of a mismatch?

Write the answers into the ownership table and check them in a test with sample records.