The group’s monthly meeting opens with a table: margin and days of inventory for each store, side by side. The brand A store shows a lower margin and slower inventory than the brand B store. Someone asks whether the comparison is fair, and nobody can say. Each number came from the standard report of a different dealer management system, and each system has its own idea of what margin and a day of inventory mean.

Comparing stores requires the math to be the same everywhere. That sounds obvious, but in practice it means deciding the rule outside the systems, translating each system’s data into that rule and proving the result ties out to the books.

First, a written definition

Before any dashboard, the controller’s office needs to put in writing what each metric means. Three metrics account for most of the disagreements.

Vehicle gross margin. Define the base (revenue net of sales taxes, not list price), what goes into cost (vehicle, freight, prep, installed accessories) and what stays out. The points that vary most between systems are:

  • manufacturer bonuses and incentives, which some systems deduct from the cost of the vehicle sold and others post separately, sometimes months later;
  • finance and insurance income, which may be added to the vehicle margin or shown on its own line;
  • margin on revenue versus margin on cost: 10% of revenue and 10% of cost are different numbers, and some reports call both “margin.”

Days of inventory. Two legitimate measures live here, and they answer different questions:

  • vehicle age, counted from the day the vehicle came in until today (or until it sold), which helps find units that are sitting;
  • days of supply, which divides average inventory at cost by daily cost of sales and tells you how many days of sales the average inventory covers.

For vehicle age, decide which date counts as the start: the manufacturer’s invoice to the store, physical arrival or entry into the system. Also decide whether a transfer between stores resets the clock. For days of supply, decide how average inventory is calculated: the average of the opening and closing balances, or the average of daily balances. When stock swings a lot, the two give different answers.

Turnover. This is cost of sales for the period divided by average inventory at cost for the same period. Always state the period: monthly and annual turnover are not comparable. Keep new vehicles, used vehicles and parts apart, because each moves at its own pace and an average of the three describes none of them.

The output of this step is a metrics dictionary: name, formula, grain, the source of each field and who owns the rule.

Map each system’s codes

Every dealer management system (DMS) has its own codes for store, department, sale type, vehicle status and model. A fleet sale may have a dedicated code in one system and be a free-text note in another. A demo vehicle may sit in new inventory for one brand and in a separate inventory for another.

The fix is a mapping table for each system that translates the source code into the group standard. A few rules help:

  • the table is owned by the controller’s office, not just by IT;
  • each row has a start and end date, because codes change when the manufacturer updates its system;
  • a code with no match does not drop out of the result: it goes to an exceptions list that someone reviews before month-end close;
  • the classification used in the math (new, used, demo, fleet) is the group’s, not each system’s.

Calendar and month-end close

Two stores can both be right and still disagree because they are looking at different periods. Check:

  • which date defines a sale: order, invoice or delivery;
  • whether any store closes the month on a day other than the last calendar day;
  • how cancellations and returns posted after the close are handled;
  • whether the dashboard shows a frozen closed month or data that keeps changing.

A simple practice is to save a snapshot of the month on closing day. Later adjustments go into the following month or into a logged reprocessing run, and the number shown at the meeting does not quietly change afterward.

Reconcile with finance

A dashboard metric earns trust only when it ties out to accounting. For each store and closed month, compare:

  • vehicle revenue and cost in the dashboard against the matching accounts in the income statement;
  • inventory at cost in the dashboard against the inventory balance on the books;
  • the number of vehicles sold against the invoices issued.

Set a tolerance for each comparison and explain every difference above it. The usual causes are manual journal entries, bonuses recognized in a different month and canceled invoices the operational system has not yet picked up. An unexplained difference is a reason to hold the number back, not to adjust it by hand.

An example with made-up numbers

The figures below are an invented example meant to show the effect of the definitions. They do not come from any company. A 30-day month, figures in thousands of Brazilian reais, new vehicles only.

Store A Store B
Net sales revenue 2,640 3,000
Cost of vehicles sold 2,400 2,760
Manufacturer bonus for the month 0 60
Inventory at cost, start of month 4,200 4,800
Inventory at cost, end of month 3,800 5,000

Store A’s system report calculates margin on revenue, without the bonus: (2,640 − 2,400) ÷ 2,640 = 9.1%. Store B’s system calculates it on cost and deducts the bonus: (3,000 − 2,760 + 60) ÷ 2,760 = 10.9%. In the meeting table, B looks better.

Under the group rule (margin on net revenue, bonus shown on its own line), store B comes to (3,000 − 2,760) ÷ 3,000 = 8.0%. The ranking flips.

Inventory follows the same path. At store A, average inventory is (4,200 + 3,800) ÷ 2 = 4,000; monthly turnover is 2,400 ÷ 4,000 = 0.60; days of supply are 30 ÷ 0.60 = 50 days. At store B, average inventory is 4,900; turnover is 2,760 ÷ 4,900 ≈ 0.56; days of supply come to about 53 days. If store B’s report showed the average age of the units in stock, counted from arrival and reset on transfers, the number could be much lower, and the comparison would still be wrong, because it measures something else.

Anyone can redo this math from the table above. That is the test a metrics dictionary has to pass.

Common pitfalls

  • Average inventory from opening and closing balances only at stores that receive large batches on irregular dates. A daily average is more faithful.
  • Annualized turnover by multiplying one month by twelve in a strongly seasonal business.
  • Transfers between stores counted as a sale at the origin and a purchase at the destination, inflating the group’s turnover and revenue.
  • Trade-ins with no rule for the value at which they enter inventory, which shifts both the used-vehicle and the new-vehicle margin.
  • Averaging percentages: the group margin is total gross profit divided by total revenue, not the average of the store margins.
  • Rule changes without history: when a definition changes, restate prior months or flag the break in the series.

Once the definitions are stable, a question like “which stores saw margin drop in the last closed month?” has a single answer. That foundation is also a prerequisite for any automated querying of the metrics, covered in how to tell whether your company’s data is ready for AI.

Want to compare your stores on the same basis?

If each brand in your group counts margin and inventory its own way, an assessment maps the systems, the rules in use and the gaps against finance. Learn about our BI for car dealerships service or request an assessment.