What software do car dealerships use?

Core systems

The DMS typically holds accounting, deals, parts and repair-order records. The CRM manages leads, customers, appointments and follow-up. Website, inventory and digital-retailing tools support shopping and transaction workflows.

Revenue and customer systems

Advertising, SEO, CDP, email, chat, call, reputation, equity-mining and AI tools acquire, identify and communicate with shoppers and owners. Their value depends on clean source data and usable outcome write-back.

Operational systems

Service scheduling, MPI, lane, shop, parts, payments, HR, cybersecurity and business-intelligence tools support dealership operations. Each should have a named system of record, owner and failure procedure.

Why the stack differs from store to store

A franchised new-car store carries manufacturer reporting, program and certification obligations that an independent used-car lot does not, and a dealer group adds consolidation and reporting layers on top. Store count, brand mix, whether the store runs its own service and body shop, and how much selling happens online all change which of the categories above are essential, optional or absent. Treat any list of what dealerships use as a starting inventory to check against your own operation, not a target to copy.

How to build your own stack map

List every system a person logs into, then record for each: who owns it, what data it holds, which other systems it exchanges data with, what it costs per month, and when it renews. Draw the exchanges as arrows and mark the ones that rely on someone re-keying data. The map usually surfaces overlapping tools, systems nobody owns and integrations that exist only as a logo on a vendor page, which are the items worth attention before any new purchase.

Common mistakes when listing dealership software

The first is counting products instead of workflows, which hides gaps: a tool can be installed and still leave a workflow manual. The second is forgetting the small systems, such as key control, loaner tracking and document scanning, that fail without anyone noticing.

The third is treating the DMS vendor's related modules as automatically integrated. Ask where each module's data actually lives before assuming a single system of record.

Where to look for gaps

After building the map, mark workflows that have no system, such as trade appraisal notes kept in email or service reminders sent from a spreadsheet. Gaps and manual workarounds are where staff time is lost, and they are usually easier to close than replacing a working platform.