Wien37% >90 d
- Margin
- Below plan
- Explanation
- Old stock
Dealer groups
Stop asking six sites why their numbers disagree.
When every site writes to one record, the group figure and site figure are the same figure. Permissions preserve autonomy; shared definitions remove reconciliation.
Dealer groups
Sample data
Group stock · six-site view
Sample data · 3 entities · CZK & EUR
SiteAgeing
Praha12% >90 d
- Margin
- On plan
- Explanation
- Healthy mix
Plzeň18% >90 d
- Margin
- On plan
- Explanation
- 27 transfers
A sample slice of the six-site group from R-SOL-03, showing three sites: Wien, Praha and Plzeň. Values are sample interface data; no close-time, rollout or customer uplift is claimed.
- Best fit
- Multi-brand, multi-rooftop and multi-entity dealer groups.
- Operational job
- Keep each site's own P&L, stock and permissions while every site uses one definition of the vehicle, customer and margin.
- What you get
- Comparable site figures with shared definitions and access scoped by role.
The reconciliation tax
Six sites, six versions, one week gone
None of this is about anyone doing their job badly. It is what happens when six databases each hold part of the truth and a definition drifts between them.
Monthly close
Six exports, three definitions of ‘days in stock’, a week of email
Moving a car between rooftops
An internal sale invented so both systems balance, distorting both P&Ls
A customer known at one site
Unknown at the other five, so the group looks smaller than it is
Comparing pricing discipline
Impossible. Each site prices by its own instinct and reports its own way
Opening the seventh site
A new installation, a new chart of accounts, three months of setup
A manager moves site
Learns a differently configured system, and their old reports stop making sense
Group stock as one pool
Six lists nobody can search at once, so cars age locally while another site has the buyer
System relationship
A connected workflow for dealer groups
One month in a group
Five things a group does that a single site never has to
Each one is where a group's data model either helps or gets in the way. Select one.
A transfer, not an invented sale
Plzeň has a Passat that has sat for ninety-six days. Praha has a customer asking for one. In six separate systems the only way to move it is to sell it internally, which puts a fake margin in one P&L and a fake cost in the other.
Here it is a stock movement between sites. The landed cost, the inspection and the ninety-six days travel with the car, so whoever sells it knows exactly what it owes.
- In
- Passat at Plzeň, 96 days, landed 488 200
- Omnetic
- Moves the vehicle to Praha with its full cost and condition history, no re-invoicing
- Out
- Twenty-seven transfers this month, and both P&Ls still honest
Comparing sites on the same definitions
A group comparison is only useful if ‘margin per unit’ means the same thing in Wien as in Ostrava. Because both figures are built from the same events, a difference is a difference in behaviour rather than in bookkeeping.
And the site can open the same screen, which changes the review from a defence into a conversation about the stock.
- In
- Six sites, 192 units sold, two currencies
- Omnetic
- One definition per metric, converted at the entity's rate, drillable to a deal
- Out
- Wien's gap explained by 37% over ninety days, not by argument
Closing across three entities
Each legal entity closes in its own currency with its own statutory output. The group view sits over all three, and every posting still carries the vehicle and the order it came from.
Which means a controller can question a number and get to the document without asking a site to prepare anything.
- In
- Three entities, CZK and EUR, six sites' worth of documents
- Omnetic
- Statutory statements per entity, one management view across them
- Out
- A close that starts on the fourth · certified accounting markets pending
Scope is a property of the role
A Brno advisor sees Brno. A used-car manager sees group stock but not group payroll. A controller sees every entity and cannot edit a work order. Permissions live on the data, so a report cannot leak what a role may not read.
Every read and write is logged with the user, the time and the previous value, which is what makes an audit trail worth having in a group of this size.
RoleOwn siteGroup stockGroup P&L
AdvisorWrite——
Site managerFullReadOwn site
Used-car managerFullFull—
Group controllerReadReadFull
The seventh site inherits the sixth
Acquiring a dealership normally means a new installation, a mapped chart of accounts and months before its numbers can be compared with anyone else's. Here it is a configured site on an existing model.
Its stock, customers and open items migrate; its history stays searchable. From the first month it appears in the same comparison as the other six.
- In
- An acquired dealership with its own DMS and its own habits
- Omnetic
- Adds a site to the existing configuration, migrates open items, scopes permissions
- Out
- Comparable from month one · durations pending delivery sign-off
How a group rolls out
One pilot, then the rest inherit it
No group switches over at once, and nobody should ask you to. The pilot exists to settle the configuration, entities, roles, chart of accounts and what a vehicle means here, on real stock rather than in a workshop. Every site after it is faster, because the argument has already been had once.
Pilot site
phase 1The configuration decisions that everything else inherits, settled on one site's real stock. Pricing and ageing pay for the phase on their own.
DMS CorePrice ReportStock Report
Roll out, site by site
phase 2Your own super-users from the pilot train the next site. Transfers between live sites start working the moment the second one is on.
Used & New Car SalesWorkshopCRM
Operate as a group
phase 3Multi-entity close, group reporting, permission governance, and the group warehouse or BI tool fed from the event stream if you keep your own.
AccountingReportingSecurity & TrustOpen Platform
Outcome & proof
A group decision needs all four to say yes
Group CEO or owner
Compares sites on identical definitions, and can see whether a weak month is behaviour or stock structure.
Group CFO or controller
Closes three entities in two currencies without asking sites to reconcile their own version first.
Site manager
Keeps their own P&L and their own stock, and stops being asked to justify a number they did not calculate.
Group IT or transformation lead
Governs one permission model instead of six, and has no integrations between sites to maintain.
What a group asks before a pilot
Evidence
Scale we can evidence, outcomes we cannot yet
2,200+ dealers across 8 European markets
Platform scope with each figure's own definition, the relevant reassurance for a group evaluating whether multi-market is real.
Median 58 days in stock · 14% over 90 days
Published with method and sample. The number your worst site should be read against before anyone concludes it is badly run.
A dealer-group customer story
Deliberately empty. A group willing to publish stock and margin figures across rooftops is the most valuable story this site could carry, and none is on file.
What we do not claim
No days-to-close improvement, no reconciliation hours saved and no rollout duration. All three are measurable and none is measured.
Worth reading first
Study
Stock Ageing Benchmark 2026
Ageing by market and price band, the context for comparing your own sites.
Read the studyPlatform
Security & Trust
Residency, roles, audit trail and recovery objectives, for the procurement conversation.
Open the trust pageTool
ROI calculator
Model it on your own site count and stock. Results are estimates and say so.
Open the calculatorPilot the site whose numbers you trust least
Use real stock to settle entities, roles, accounting definitions and vehicle meaning once; later sites inherit the proven configuration.
Discuss a pilotOne definition
Margin, ageing and performance are built from the same events at every site.
A transfer, not a sale
Vehicles move between rooftops with cost and condition intact, without invented margin.
Scope on the role
Each site and group role reads only the records its permissions allow.