Choose a dealer management system by making vendors demonstrate the work your dealership must complete. Define the records, integrations, controls and recovery requirements first, then compare written commitments and full costs. A polished demonstration becomes useful when your staff can trace a transaction through the system and retrieve its evidence afterward.
Write a short operational brief
Describe your dealership: locations, franchises, departments, user roles and transaction volumes. Identify which records must be authoritative in the DMS and which remain in a customer relationship management system, accounting service, manufacturer portal or another application. Assign an owner to each requirement so conflicting departmental preferences are resolved deliberately.
Select three representative workflows. For example: receive a used vehicle and record reconditioning; open a repair order, approve additional work and allocate parts; complete a sale and reconcile the accounting entries. Include an exception such as a returned part or corrected invoice. Use fictional customer data in demonstrations.
Make each vendor perform the same demonstration
On a narrow screen, scroll the table horizontally. Keyboard users can focus its region and use the arrow keys.
| Task | What staff should see | Record to keep |
|---|---|---|
| Enter once, use across departments | Where data is reused and where someone must retype it | Fields, responsible role and any manual step. |
| Approve a change | Permission checks, approval trail and reversal process | Who approved what, when, and how the record can be retrieved. |
| Exchange data with another system | Actual supported connection and behavior when it fails | Integration owner, certification scope and error-handling procedure. |
| Close and reconcile | Totals that agree across the transaction and accounting view | Sample export, reconciliation result and unresolved differences. |
| Find an older record | Search, attachments, access restrictions and export | A usable record containing the context your business needs. |
Record whether a function was demonstrated in the offered product, shown as a mock-up, promised for a later release or dependent on another supplier. Treat those states differently. Ask frontline staff to repeat a key task, since a vendor’s practiced demonstration can conceal training effort and awkward exceptions.
Define the integration as a service commitment
For each connection, name the external system, supported version, data fields, direction of flow, update frequency and error owner. Ask who pays connection and API fees and who investigates when a transaction reaches one system but not the other. “Integrated” is a claim to unpack, not a complete requirement.
Clarify manufacturer requirements with the relevant franchise and the exact proposed configuration. Obtain written confirmation for essential connections. Document how duplicate records, corrected transactions and unavailable services are handled. Test a failed or delayed exchange during the pilot and reconcile the records afterward.
Assess access, recovery and provider oversight
Have your security lead define role-based access, authentication, audit records, encryption, incident contacts and recovery evidence. Ask the vendor to demonstrate account removal, permission changes and retrieval of an audit event. Establish who can export sensitive records and how that activity is recorded.
For U.S. dealerships subject to the FTC Safeguards Rule, the FTC’s automobile-dealer FAQ explains service-provider oversight: select capable providers, require appropriate safeguards by contract and assess them periodically according to risk. Applicability depends on the information and service relationship. Have the dealership’s compliance and legal advisers connect those requirements to its actual arrangements.
For continuity, specify the maximum acceptable interruption and data loss for each critical workflow. Ask for evidence of a restoration exercise, backup coverage, access during an outage and reconciliation after recovery. A promise that data is backed up leaves the time and usability of recovery unanswered.
Compare the same term and assumptions
Use your own written quotes and one common period, currency, user count and location count. Include implementation, data conversion, staff time, parallel operation, support tiers, annual increases, add-on modules and termination assistance. Keep recurring and one-time items separate so a seemingly low subscription price does not hide the cost of operating the complete system.
Agree on migration and acceptance before signing
Request a sample export containing related records and attachments, with a data dictionary and identifiers that preserve their relationships. Have the receiving team demonstrate that it can open and reconcile the sample. Define what remains accessible after termination, for how long, in which format and at what price. Let counsel establish retention and deletion requirements for your jurisdiction and records.
Run a bounded pilot with acceptance criteria: required workflows completed, opening balances reconciled, integrations tested, staff trained and recovery responsibilities understood. Record each defect, its owner and the evidence needed to close it. Sign-off should describe an operable business process and an agreed support arrangement, not simply successful software installation.
Save a working record
Download the Dealer Management Systems working record (plain text). Open it in a text editor, save a private copy and fill in the relevant prompts. Record unknowns explicitly and attach the evidence that supports each conclusion. The file includes instructions, source links and this article’s address.