Dealer management systems are bought rarely, kept for a decade, and evaluated — too often — on a demo of the sales screen. The sales screen is the easy part. A DMS earns or loses its decade in the unglamorous seams: whether the claim reconciles, whether the VIN survives a branch transfer, whether the workshop's Tuesday actually fits in Tuesday. This guide is the seam-checklist.
The twelve questions
1. Does one customer record survive the whole journey?
Lead → test drive → finance → quote → order → delivery → every service visit. If any step lives in another module with a batch interface, you have bought two systems wearing a coat.
2. Where does the test drive's odometer reading go?
A real answer names a field on a record. A vague answer means demo-fleet custody is on trust.
3. Can a quote refuse to forget the mandatory charges?
Ask to see a quote with the registration line deleted. The right answer is: you can't — mandatory components are enforced by the product model, not by training.
4. Is the VIN an inventory identity or a text column?
Allocation, branch transfer, invoice, warranty — the same serialised unit through all four, with in-transit stock valued. Ask what happens to the VIN's history when it moves branches.
5. What creates the service contract?
If the answer is "the service advisor sets it up", warranties will be missing the week the advisor is on leave. The invoice should create it.
6. Who generates the service due-list?
A person exporting a report is the wrong answer. Contracts and maintenance schedules should generate leads automatically, with reminder offsets.
7. How does a job line know its payer?
Warranty, package, customer, internal — decided per line before work, from the contract. If the cashier decides at billing, disputes are a designed-in feature.
8. Show me a claim rejected on one line of three.
Whole-claim status tracking means a side-spreadsheet within a month. Line-level approve, reject and reclaim — with automatic settlement to credit notes — is the bar.
9. Is the bay schedulable, or just the technician?
Bays, lifts and demo vehicles are capacity. If only people are scheduled, the whiteboard is still running the workshop.
10. What posts to the ledger without a human?
Every operational document, with GST on the line — or your accounts team is the integration.
11. Can the incentive computation be inspected?
Payout slabs, targets, actuals — from the same records as the books. "We export to Excel for incentives" means the argument is scheduled monthly.
12. What happens offline?
The technician in the basement, the driver at the stockyard gate. Offline-first with a durable outbox, or a paper process wearing an app icon.
The weighting that keeps you honest
Score the seams double and the screens single. Screens get rebuilt; seams are architecture, and architecture is what you keep for ten years. And insist every claim in the vendor's deck is shown live on their system with your scenario — a DMS demo script is a work of fiction until proven otherwise.
Where xMatix stands on each seam: the Auto DMS page walks the whole span in one pass, the automotive solution and its deep dives go seam by seam, or Tekion alternative for a head-to-head against the incumbent, or DMS vs SFA vs CRM if you're still deciding which category you're buying.