Dealer problems often start at the importer
How importer integration, governance and dealer-performance systems can remove problems that otherwise keep reappearing at retail level.
The dealer network was under pressure, but a surprising amount of the problem was not being created inside the dealerships.
Importer, market and retail processes had grown separately. Local routines were inconsistent or incomplete, systems did not connect cleanly and management reports contained data that could not always be trusted enough to drive action.
That made operational and digital problems look like dealer-performance problems. Another round of retailer optimisation would have treated the symptom while leaving the upstream system unchanged.
The importer layer is often described as administration between OEM and dealer. In practice it determines much of what a dealer can execute consistently: target logic, stock visibility, pricing support, process standards, data definitions, escalation, DMS follow-up and the routines through which performance is managed.
When those pieces are fragmented, dealer variation increases because every outlet has to compensate locally. The network then looks inconsistent even when the original inconsistency sits upstream.
A dealer can only execute the operating system it is given. If the importer logic is fragmented, local heroics become part of the process.
Agree which problems were genuinely retail issues and which required importer-level ownership before changing tools or targets.
Standardise the customer, vehicle and data flows that crossed sales operations, importer functions and the retail network.
Create a KPI structure that used common definitions and made dealer performance comparable rather than producing several versions of the same number.
Connect regional and customer systems with dealer workflows so that information could move into the point of work instead of remaining in separate reporting layers.
Build recurring management and escalation routines around the redesigned system so that exceptions produced decisions rather than another report.
The technology was not the starting point. A DMS, CRM or regional platform can move information, but it cannot resolve a process whose owner is unclear or a KPI whose definition changes between functions.
The integration work therefore followed the process and decision logic. Data flows were connected after the business had agreed what the event meant, who owned it and what action should follow.
That reduced the common pattern where a new dashboard exposes more inconsistency without giving management a cleaner way to act on it.
- An approved transformation roadmap connected importer redesign with dealer-performance improvement.
- Core process flows were standardised across the relevant functions and retail interfaces.
- Dealer and importer teams worked from a shared performance logic rather than parallel measures.
- System and data connections were redesigned around operating workflows instead of isolated technical integration.
- The rollout could be phased, which reduced the need for a single large-bang implementation across every market and outlet.
at.Pointe engagement. The case is anonymised and focuses on the operating mechanisms rather than client identity.
Dealer performance is still local at the point of customer delivery, selling and service. That does not mean the causes of weak performance are local.
Before asking a dealer network to improve, management should be able to show that the importer has provided one process logic, one usable set of measures, clear decision rights and systems that support the workflow. If those pieces are missing, local variation is partly a rational response to an incomplete operating model.
This is why importer transformation and dealer performance should often be managed as one system rather than two programmes.
Written from operating experience, not market commentary.