Multi-Brand, Multi-Branch: Why Dealer Groups Never Get One Version of the Truth

Ask the owner of a multi-brand dealer group a simple question: what did we sell last month, at what margin, and how much of the profit came from aftersales? In most groups the honest answer is "we'll come back to you." The team is not slow. The answer lives in six or seven places, and none of them were built to agree with each other.

Every brand has its own manufacturer-mandated DMS. Every branch has its own habits, spreadsheets and workarounds. Finance sits on an ERP that only knows what someone remembered to post into it. By the time the group's numbers are stitched together by hand, they describe a month that is already over. The decisions they should have informed, such as stock transfers, technician hiring, peak-season staffing and discounting, have already been made on instinct.

This article looks at why multi-brand dealer groups, especially those with sites in several countries, so rarely get one version of the truth, what the fragmentation costs on the ground, and what a sensible fix looks like. That fix does not begin by throwing away systems you have already paid for. It begins with a RevOps view of the whole revenue flow, from enquiry to invoice to aftersales, and ends with one operating picture that leadership can trust.

The Stack Behind Every Badge

A multi-brand group rarely runs one system. It runs many, and most were chosen for good reasons at the time.

Multiple DMS instances. One brand mandates its own dealer management system, the premium brand mandates another, and the newest franchise arrives with a third. Each handles vehicle stock, sales orders, workshop job cards, parts and warranty claims in its own data model. Part numbers, customer IDs and even the definition of a "completed" job differ from one to the next. Some are hosted by the manufacturer, so the group can pull reports but cannot touch the underlying data. Others are older instances sitting in a branch, a version behind the one down the road.

ERP. Group finance typically runs SAP, Oracle or Microsoft Dynamics 365 for the ledger, payables, receivables, fixed assets and consolidation. It is the financial system of record, but it meets the operational world only in summaries: journal uploads, end-of-day batches, or a file someone exports and re-keys.

BI tools. Power BI, Tableau, Qlik or something similar sits on top, promising the single dashboard. It is only as trustworthy as the feeds underneath.

Around all of this sit a CRM, a website with lead forms, a call centre and, increasingly, WhatsApp and other messaging channels. Messaging is often where the customer relationship really lives, frequently on individual advisors' phones rather than in any system at all.

A Month-End in the Group Finance Office

Consider a hypothetical dealer group with five brands and sites in three countries.

On the third working day, the group financial controller asks each branch for trial balances and sales and workshop reports. Each DMS exports in a different format. An analyst spends days mapping them to the ERP's chart of accounts. One brand's "gross profit" includes delivery and pre-delivery inspection charges, and another's does not. A vehicle transferred from a branch in one country to a branch in another shows as sold in one system and still in stock in the other. Parts transfers between branches have the same problem. Each of these needs a phone call, and each call needs someone who remembers what happened.

Tax adds another layer. Each country runs its own VAT or sales-tax regime, and where regional e-invoicing mandates apply, such as Peppol-based schemes, invoices raised in the DMS must also be correctly reported to the authority or network. If the invoice in the DMS, the submission to the e-invoicing network and the posting in the ERP do not reconcile, finance discovers it at filing time. A credit note raised in the workshop after a customer dispute but never mirrored in the ERP leaves a tax position that is slightly wrong. Finding that discrepancy can take two people a full day.

By the time consolidated numbers reach the board, they are weeks old and carry a footnote: subject to adjustments. Leadership is steering by the rear-view mirror, with no central command center view of what is happening across brands and locations right now.

Where the Service Lane Leaks

Aftersales is where fragmentation hurts most, because it is the highest-volume, most manual part of a dealer group, and the part customers feel every few months.

Picture a typical customer, Mr Reyes. He messages a branch on WhatsApp, in his preferred language, to book a service for his SUV. The advisor reads it between walk-ins and types the booking into the DMS by hand. Meanwhile, the CRM that sends service reminders holds an older mobile number, because he updated his details at a sister branch of the same group. He also owns a family car bought from a different brand in the group. To the systems he is two unrelated customers, so nobody sees that this household is worth far more than either record suggests.

In the workshop, the job card needs a part. The branch's DMS shows zero. A sister branch ten kilometres away has three on the shelf, but in a different DMS that nobody at the first branch can see. The part is ordered from the distributor, the car sits for four days, and the customer starts asking whether a nearby independent garage would be quicker.

A few weeks later, a warranty claim is rejected because the job card was closed without the correct labour code. The cost lands in the ERP as an unrecovered expense. No one connects it back to the workshop, so the same mistake repeats.

Now add a peak season. Working hours shift, demand spikes and message enquiries surge. Appointments taken by phone, walk-in and message compete for the same bays because there is no shared calendar. Advisors answer in several languages from their personal phones, and when one goes on leave, their conversations go with them.

Why the Dashboard Doesn't Fix It

The usual reaction is to buy a better BI tool. It is a reasonable instinct, but it rarely solves the problem, for three reasons:

• Definitions differ. If each DMS calculates margin, "units sold" or "workshop efficiency" differently, a dashboard displays three answers side by side, and the argument moves from the spreadsheet to the meeting room.
• Data arrives late. Many feeds are nightly exports or manual uploads. A dashboard fed monthly is a monthly report with better colours.
• Identities don't match. Customer, vehicle and part records are not linked across systems. Without a shared key, the BI layer cannot tell that two records are the same person or the same part.

Often the manual work is simply moved. Someone still reconciles spreadsheets before the data reaches the dashboard, and the group has paid for a licence to display the result. BI is valuable, but it is the last layer of the solution, not the first.

What Fragmentation Actually Costs

The damage shows up in five ways that every GM and COO will recognise:

• Delay. Consolidation takes weeks, so slow-moving stock, margin erosion and workshop under-utilisation are spotted after the damage is done.
• Exhausted teams. Skilled finance and operations people spend their days copying, matching and chasing instead of analysing. Month-end becomes a recurring crunch, and the people who understand the workarounds become single points of failure.
• Mistakes. Every re-keyed figure is a chance for error: wrong tax treatment, duplicated invoices, mismatched part numbers, unposted credit notes. Customer data copied between systems and personal phones also raises questions under data protection laws such as GDPR.
• Frustrated customers. Customers repeat their details, miss reminders, wait for parts that exist elsewhere in the group, and get different answers from different branches. Multilingual customers who switch between languages, and between messaging and phone, feel it most.
• Leaked money. Unclaimed warranty, missed service reminders, unbilled work, stock sitting in the wrong branch and discounts nobody can compare across sites all drain margin quietly.

None of these is dramatic on its own. Together they are a steady tax on every branch, and they are invisible because the numbers that would expose them are the ones that arrive late.

Why Rip-and-Replace Isn't the Answer

When groups see this picture, the temptation is to standardise on one platform. In practice that is usually impossible or unwise. Manufacturers mandate their DMS, so the group cannot choose to drop it. Years of customer, vehicle and service history live in these systems. Retraining hundreds of advisors, technicians and accountants during a peak season carries real risk to revenue. A multi-year replacement programme can leave the group more fragmented while it runs than before it started.

The better question is not "which system should replace the others?" but "how do the systems we already own behave like one?" That is an integration and operations problem, not a software-purchasing problem.

How The Ninjaz Group Approaches It

The Ninjaz Group is a managed-services partner. We design the change, wire your existing systems into one operating backbone, and stay on to run it. We sell the outcome, not software. The work moves through three phases, and you can stop after any one.

Blueprint. We map the operation end to end, from enquiry to invoice to aftersales follow-up, and find every gap where work is done twice, data goes stale or money leaks. You keep the map either way. For many groups, seeing the real flow between DMS instances, ERP, CRM and messaging channels is the first time anyone has had the whole picture in one place.

Build & Link. We build what is missing and connect what already exists into one backbone. There is no rip-and-replace, and software you have already paid for stays. The aim is for DMS, CRM, finance, service, website and messaging to behave like one system, with shared definitions, timely data and linked customer, vehicle and part records. That gives your ERP and BI tools something dependable to consume, and it gives RevOps a consistent view of pipeline, service revenue and retention across every brand and branch. Where it makes sense, the same backbone feeds a central command center, so leadership can see stock, workshop load, margin and open issues across all locations in one place.

Operate. Once it is live, we stay: support, monitoring and continuous improvement. Think of it as your operations and IT team without the headcount.

These phases map to our three service layers, and you can take any one of them. Managed Transformation Services covers strategy, design and development, which is the change itself. Managed Link is the operating layer between your systems, built, owned and maintained by us. Managed Business Operations covers managed and remote IT support for the day-to-day running after go-live.

On delivery, strategy and account leadership stay close to your business, while engineering, AI development and support come from a dedicated delivery team working across your business hours and time zones. We would not promise that any of this is effortless. Integrating brand-controlled systems takes careful design, and some manufacturer platforms limit what can be changed or accessed. Where they do, we work through supported interfaces, exports and the layers around the platform, and we say so early. If you want to see what your own operation looks like end to end, book a consultation.