Dealer networks
What is a dealer management system? Two meanings
A dealer management system is software for running dealer sales and service. The phrase means two different things, and the difference decides what you buy.
The short answer
- A dealer management system (DMS) records a dealer's enquiries, sales, service and stock.
- One meaning is the dealership's own shop system: billing, workshop, parts counter, accounts.
- The other is the brand's network system: leads, follow-up and outcomes across every dealer.
- Most brands need both, and they should share records rather than compete for them.
- Before you choose, write down which questions head office cannot answer today.
A dealer management system is the software that records the sales, service and stock work of a dealer business. In practice the phrase means two different things: the system one dealership runs its own shop on, and the system a brand uses to work with its whole dealer network. This post explains both, and this blog is about the second.
What a dealer management system means in practice
Ask a dealer principal what their DMS is and they will name the software their accountant, service manager and parts counter use every day. Ask a brand's national sales head and they will describe something else: the system that tells them whether the enquiry their campaign paid for last Tuesday was ever called.
Both are fair uses of the words. They answer different questions for different people, and buying one when you needed the other is a common and expensive mistake.
The dealership's shop system
- Used by one dealer's own staff
- Billing, job cards, parts counter, accounts
- Answers "how is my shop doing?"
- Chosen by the dealer, often
- Records belong to one business
The brand's network system
- Used by head office, regions and every dealer
- Enquiries, routing, follow-up, outcomes
- Answers "what happened to every lead we sent?"
- Chosen by the brand, for all dealers
- One record shared by brand and dealer
The dealership's own shop system
For a single dealership, the DMS is the back office. A vehicle dealer uses it to raise invoices, open job cards in the workshop, sell parts over the counter, manage the yard and close the books. A paint or battery dealer may call the same thing billing software.
This system is local by nature. It knows the dealer's stock, the dealer's staff and the dealer's customers. It rarely knows where an enquiry came from, and it was never built to tell the brand anything. When a brand asks a dealer for a weekly report, someone usually exports from this system into a spreadsheet and emails it.
That is not a failing of the shop system. It is doing its own job.
The brand's dealer network system
The second meaning sits one level up. A brand with two hundred dealers needs one place where an enquiry from a national campaign, a store page or a call centre lands, goes to the right dealer, and comes back with an answer: called, test ride booked, quotation sent, lost to a competitor, bought.
The questions it answers belong to head office. Which dealers call within the day? Where do enquiries stop moving? Which region's follow-up has slipped this month? Who owns this lead right now, and since when?
- RoutingEvery enquiry reaches one named dealer and one named person.
- Follow-upEach lead carries a next action and a date.
- DispositionsEvery call ends with an agreed outcome, not a free-text note.
- VisibilityHead office and regions see the same records the dealer works.
- PermissionsEach dealer sees its own leads, and only its own.
- OnboardingNew dealers start on the same journeys and fields as the rest.
Each of these jobs has its own post on this blog: dealer lead management from enquiry to outcome, lead routing to dealers, dealer network visibility for head office, and a dealer onboarding checklist for bringing many dealers onto one system.
Which one this blog is about, and why it matters
This blog is about the brand's network system. Our readers run the network, not one shop in it.
The distinction matters most at the point of purchase. A brand that buys a shop system for every dealer gets two hundred separate back offices and still cannot see its leads. A brand that buys a network system and expects it to raise workshop invoices will be disappointed too. The two should be connected where a record really is shared, such as the customer and the sale, and left alone where it is not.
| Question you are asking | System that should answer it |
|---|---|
| Was this enquiry called, and by whom? | Network system |
| What is in this dealer's parts stock today? | Shop system |
| Which dealers book test rides from leads within two days? | Network system |
| What did this dealer bill this month? | Shop system |
| Did a lead from our campaign end in a sale? | Both, joined on the customer record |
How to tell which one you need
Start from the questions, not the software. Sit with your regional managers and write down every question they answer by phoning a dealer or chasing a spreadsheet. If most of the list is about enquiries, follow-up and outcomes across dealers, you need a network system. If it is about one shop's invoices and workshop, the dealer needs a shop system and may already have one.
- List the questionsCollect what head office and regions ask dealers for every week.
- Mark the ownerFor each question, note whether the brand or the dealer needs the answer.
- Find the recordName where the answer lives today: a system, a sheet, or someone's phone.
- Choose the systemBrand questions point to a network system; shop questions to a shop system.
- Decide the joinsAgree which records must pass between the two, and which never need to.
The last step is where most projects go wrong. Not every field needs to travel. The customer, the enquiry and the outcome usually do. The workshop's labour codes usually do not.
How Intellsys OS fits a dealer network
Intellsys OS is a network system, not a dealership's shop system. A business defines its own journeys, activities, forms, dispositions, roles and territories, and head office, regions and dealers work the same records in table, list, board and calendar views. Each dealer store has its own catalogue and staff.
Permissions go down to a single record, by role, by reporting hierarchy and by geography, so a dealer can be limited to its own leads. Work can be reassigned one at a time or in bulk, round-robin, with an audit log. In venture partner deployments Intellsys OS runs beside SAP and Salesforce. Field Sales gives the field team beat plans, location-stamped visits and orders captured on mobile, online or off. The customer side is described on our customers page.
Questions people ask
What is a dealer management system in simple terms?
It is software that records a dealer business's work. For one dealership that means billing, workshop, parts and accounts. For a brand, it means the system that sends enquiries to dealers and records what each dealer did with them.
Is a DMS the same as a CRM?
Not quite. A shop DMS runs a dealership's back office. A CRM records customers and sales conversations. A brand's dealer network system is closest to a CRM shared between a brand and its dealers, with routing, permissions by dealer and outcomes head office can see.
Do dealers have to give up their own software?
No. A dealer can keep its shop system for billing and workshop. The network system handles enquiries and outcomes the brand needs to see. The two should share only the records that are truly common, such as the customer and the sale.
Who should own the dealer network system?
The brand, usually the sales or dealer development head, with a named owner for the journeys, fields and dispositions. Dealers use it, but if each dealer can change the outcomes and stages, head office loses the ability to compare one dealer with another.