Insights

Choosing a DMS (Dealer Management System) is not an IT purchase. It is a management decision that directly affects business transparency, operational control and, ultimately, profitability.

A wrong choice can be expensive: from employee resistance and inefficient processes to poor data quality and the need to replace the system again a few years later.

Below is a practical step-by-step approach to selecting a DMS for a dealership, automotive service business or multi-site automotive operation.

1. Start with the question: Why do you need a new DMS?

One of the most common mistakes is to start with software.

The right starting point is the business problem you want to solve.

Typical objectives may include:

• improving KPI transparency;

• increasing workshop productivity and capacity      utilization;

• improving parts inventory management;

• reducing operational losses and errors;

• improving gross profit and profitability control;

• improving customer experience;

• automating routine processes;

• integrating Service, Parts, Finance and CRM;

• creating reliable management reporting;

• supporting business growth or network expansion.

If the business objective is not clearly defined, it is almost impossible to choose the right system.

The question should not be:

“Which DMS is the best?”

It should be:

“Which DMS is best for our business model, processes and management objectives?”

2. Define the project team: Who must be involved?

Selecting a DMS is a cross-functional business project.

Delegating the decision entirely to IT is a mistake. But allowing only the Service Manager or General Manager to choose the system is equally risky.

The DMS will connect multiple areas of the business, so all major stakeholders must be involved from the beginning.

Management

CEO / General Manager / Owner

Responsible for:

• strategic objectives;

• investment level;

• business priorities;

• final decision.

After-Sales Operations

Service Manager / After-Sales Manager

Responsible for:

• workshop processes;

• customer flow;

• repair orders;

• technician productivity;

• capacity planning;

• service KPIs.

Parts Manager

Responsible for:

• parts ordering;

• inventory;

• pricing;

• stock availability;

• purchasing;

• obsolescence;

• parts profitability.

Finance

CFO / Finance Manager / Accounting

Responsible for:

• financial integration;

• accounting requirements;

• revenue and cost allocation;

• profitability;

• financial reporting;

• compliance.

IT / Digital

Responsible for:

• infrastructure;

• cybersecurity;

• integrations;

• data migration;

• user access;

• technical support.

Key Users

This group is often underestimated.

It should include people who will use the DMS every day:

• Service Advisors;

• Workshop Foremen;

• Technicians, where applicable;

• Parts Advisors;

• Warehouse Staff;

• Warranty Staff;

• Managers.

A system that looks perfect to management but is difficult to use for frontline employees will eventually fail.

3. Decide who will implement and administer the system

Selecting the DMS is only half of the project.

The next question is:

Who will make sure that the system actually works?

There are usually three implementation models.

1. Implementation by the DMS vendor

Advantages:

• deep product knowledge;

• experience with standard implementation;

• direct access to technical expertise.

Potential limitations:

• the vendor may focus on configuring the software rather      than redesigning your business processes;

• customization may be limited.

2. Implementation by an independent integrator or consultant

Advantages:

• stronger focus on business processes;

• independent assessment;

• support in requirements definition;

• integration of multiple systems.

Potential limitations:

• additional cost;

• requires coordination with the software vendor.

3. Internal project management

The company appoints an internal project manager who coordinates management, users, IT, vendor and integrator.

Best practice

In many cases, the strongest model is a combination of all three:

Business Owner + Internal Project Manager + DMS Vendor + Implementation / Consulting Support

The internal project manager is particularly important because someone inside the company must remain accountable for the result.

4. Understand the main types of DMS

There is no single “best” DMS for every automotive company.

The market can be broadly divided into several categories.

1. Traditional Dealer Management Systems

Typically designed for franchised dealerships and often closely aligned with OEM processes.

Typical characteristics:

• strong dealership functionality;

• OEM integration;

• warranty processes;

• standardized workflows;

• extensive reporting.

Best suited for: official dealers and dealer groups.

2. Independent Automotive DMS

Designed primarily for independent workshops, service centers and automotive groups.

Typical characteristics:

• flexibility;

• simpler implementation;

• lower entry cost;

• workshop-oriented functionality;

• often cloud-based.

Best suited for: independent workshops and growing automotive service businesses.

3. ERP + Automotive Modules

Large ERP platforms can be adapted for automotive operations through dedicated modules and customization.

Typical characteristics:

• high flexibility;

• extensive financial functionality;

• strong enterprise integration;

• significant customization potential.

Best suited for: large groups and complex organizations.

The disadvantage is usually higher implementation complexity and cost.

4. Cloud / SaaS DMS

Cloud-based systems have become increasingly popular.

Typical characteristics:

• rapid deployment;

• lower infrastructure requirements;

• subscription-based model;

• automatic updates;

• easier access from multiple locations.

However, the company must carefully evaluate:

• data ownership;

• cybersecurity;

• integration capabilities;

• availability;

• backup procedures;

• customization limitations;

• long-term subscription costs.

5. Define your requirements before talking to vendors

Do not start the selection process by inviting vendors to demonstrate their products.

First create your own DMS Requirements Matrix.

The requirements should cover at least the following areas.

Service Operations

• repair order management;

• appointment scheduling;

• workshop planning;

• technician allocation;

• labor time recording;

• job status management;

• quality control;

• warranty processes;

• customer communication.

Parts Management

• stock management;

• purchasing;

• replenishment;

• parts identification;

• alternative parts;

• pricing;

• inventory analysis;

• obsolescence management;

• wholesale sales.

Finance

• revenue tracking;

• cost allocation;

• gross profit;

• margins;

• integration with accounting;

• financial reporting.

CRM and Customer Experience

• customer history;

• vehicle history;

• reminders;

• follow-up activities;

• customer communication;

• online booking;

• customer retention.

Management & Analytics

• KPI dashboards;

• real-time reporting;

• technician productivity;

• workshop utilization;

• parts turnover;

• gross profit;

• customer retention;

• management reporting.

Integrations

Evaluate integration capabilities with:

• OEM systems;

• accounting / ERP;

• parts catalogues;

• CRM;

• telephony;

• online booking;

• payment systems;

• websites;

• BI platforms.

6. Establish clear DMS selection criteria

Once the requirements are defined, evaluate every candidate using the same scoring methodology.

1. Business fit

Does the system support your actual business model and processes?

The system should support the business — not force the business to work around the software.

2. User experience

How easy is it for employees to use?

Consider:

• number of steps;

• number of clicks;

• screen logic;

• speed;

• mobile access where relevant;

• ease of training.

3. Functionality

Does the system cover the required processes without excessive customization?

4. Analytics

Can management easily see what is happening?

A modern DMS should provide actionable information, not simply store transactions.

5. Integration capability

Can the system communicate with other critical platforms?

6. Total Cost of Ownership — TCO

Do not compare only license prices.

Calculate:

TCO = Software + Implementation + Integration + Migration + Training + Support + Updates + Internal Resources

A system with a low license price can become the most expensive option after implementation.

7. Scalability

Can the system support:

• additional users;

• new locations;

• additional brands;

• new business models;

• increasing transaction volumes?

8. Vendor stability and support

Evaluate:

• implementation experience;

• customer references;

• local support;

• response times;

• development roadmap;

• financial and operational stability.

7. Conduct the demo differently

A traditional DMS demonstration is usually a sales presentation.

That is not enough.

Instead of asking the vendor:

“Show us what your system can do.”

give them your real business scenarios.

For example:

Scenario 1 — Service

A customer calls → appointment is created → vehicle arrives → repair order is opened → parts are allocated → technician performs the work → additional work is approved → vehicle is completed → invoice is issued → customer receives follow-up communication.

Scenario 2 — Parts

Demand appears → stock is checked → alternative part is identified → order is created → goods arrive → warehouse receives them → part is allocated to repair order → margin is calculated.

Scenario 3 — Management

The Service Manager wants to know:

• workshop utilization;

• technician productivity;

• labor sales;

• parts sales;

• gross profit;

• open repair orders;

• customer retention.

Ask the vendor to demonstrate the complete process — not individual features.

8. Run a pilot before full implementation

A pilot is one of the best ways to reduce implementation risk.

Instead of immediately migrating the entire business:

• select one department;

• one location;

• one process;

• or a limited group of users.

Then evaluate:

• usability;

• data quality;

• process accuracy;

• integration;

• employee acceptance;

• reporting;

• system performance.

The pilot should answer one key question:

Can our people successfully run our real business through this system?

If the answer is no, it is better to discover this before full implementation.

9. Prepare the organization

Technology is only one part of a DMS implementation.

The other part is people and processes.

Before launch, define:

• processes;

• responsibilities;

• user roles;

• access rights;

• operating procedures;

• data standards;

• training requirements;

• KPI definitions.

Employees should understand not only how to use the system, but why the new process is being introduced.

This is particularly important when replacing an old DMS.

People tend to compare the new system with the familiar one — even when the old process was inefficient.

10. Define who will administer the DMS after implementation

A DMS requires ongoing ownership.

Someone must be responsible for:

• user management;

• master data;

• system configuration;

• reports;

• workflows;

• permissions;

• data quality;

• updates;

• coordination with the vendor.

This can be:

Internal DMS Administrator + IT + Business Process Owners + External Vendor Support

The critical point is clear accountability.

If nobody owns the DMS, the DMS will gradually stop supporting the business.

11. Control the system after go-live

The implementation does not end when the system goes live.

The first months are critical.

Management should monitor:

• system adoption;

• data quality;

• process compliance;

• user errors;

• reporting accuracy;

• KPI performance;

• unresolved technical issues.

The DMS should gradually become the single source of operational truth for the business.

The most common mistakes when choosing a DMS

❌Choosing based primarily on price

The cheapest DMS is not necessarily the cheapest solution.

❌Letting IT make the decision alone

IT evaluates technology. The business must evaluate business value.

❌Ignoring frontline users

The people who use the system every day often identify problems that management will never see during a demo.

❌Starting with software instead of processes

A DMS cannot compensate for poorly designed processes.

❌Underestimating implementation

The software is only one component of the project.

❌No internal owner

Without an accountable person, decisions are delayed and system quality deteriorates.

❌No pilot

A full-scale implementation should not be the first real test of the system.

A practical DMS selection sequence

A structured selection process can be summarized in 10 steps:

01 — Define business objectives
↓
02 — Map current processes
↓
03 — Form the project team
↓
04 — Define requirements
↓
05 — Shortlist DMS providers
↓
06 — Conduct scenario-based demos
↓
07 — Score and compare solutions
↓
08 — Calculate TCO and business case
↓
09 — Run a pilot
↓
10 — Implement, train and control

Final thought

Choosing a DMS is not an IT project.

It is a business transformation project.

The right DMS should provide management with better visibility, employees with better tools, customers with a better experience and the business with better financial control.

The most important question is therefore not:

“Which DMS should we buy?”

but:

“What kind of business do we want our DMS to help us manage?”

A properly selected and implemented DMS can become the operational backbone of an automotive business. A poorly selected one can become an expensive obstacle to growth.

do2be3 — Enabling Operational Excellence

Consulting • Training • Business Performance

Extra: Symptoms of existing Management Accounting Problems

• Lack of organised primary documentation for core processes. It's impossible to identify those responsible for transactions, shipments, movements, picking, assembly, etc.

• A significant amount of time is spent on document processing: creation, registration, and issuance – resulting in long waits for customers.

• It's impossible to quickly obtain high-quality primary information on sales, inventory, and inventory movement to make immediate tactical decisions.

• It's impossible to quickly manage the company's pricing policy across product lines (markup, profitability, discounts, etc.).

• It's impossible to objectively evaluate the performance of individual company divisions, product groups and goods, employees, etc. It's unclear who earns what, how much, and from what sources.

• Lack of understanding the actual cost of services, goods, and semi-finished products at any given time.

• Discrepancies between accounting system data and data provided by responsible persons, as well as actual data.

• Complex control over prices, discounts, and the fulfillment of plans and standards.

• Lack of automated control over purchase prices and acquisition costs.

• And much more…