Manage Exceptions, Not Averages
Dashboards built from operational events rather than a monthly data-gathering exercise. If a vehicle is late, a deal is stuck or a delivery is blocked, that is a record in the system — not something someone has to notice.
Why dealership reports disagree with each other
Usually because the same term is defined differently in each department. Days in stock counted from invoice date, shipment date or yard receiving produces three different numbers. Fixing the definition centrally, and calculating it from a recorded operational event rather than a manually entered date, removes most of the disagreement.
This is the practical case for reporting from a DMS rather than from a business intelligence layer sitting on top of several systems. A dashboard can only be as consistent as the operational data feeding it. When receiving, allocation, approval and delivery are all recorded as events at the moment they happen, the metric has a defensible source.
Fixed definitions
Each KPI has one definition applied across every company, brand and branch, so a comparison between branches is a comparison rather than an argument.
Event-based calculation
Metrics derive from recorded events — receiving, allocation, approval, policy issuance, handover — not from a date someone typed into a spreadsheet later.
Drill to the record
A number on a dashboard resolves to the specific vehicles, deals or leads behind it, so the response is action rather than a request for a supporting report.
The dashboards
Eight standard dashboards covering the whole journey. Figures shown are illustrative sample data used to demonstrate layout and metric definitions.
Target vs achievement by branch
Deliveries — 12 weeks
Exception dashboard
| Exception | Count | Stage | Owner |
|---|---|---|---|
| Vessel delayed beyond ETA | 96 | Ocean transit | Logistics |
| Customs clearance over 5 days | 18 | Destination port | Logistics |
| Stock aged over 120 days | 19 | Yard / branch | Inventory |
| Delivery blocked — registration | 11 | Pre-delivery | Sales admin |
| Deal awaiting approval over 48h | 6 | Deal desk | Management |
| Finance approval expiring in 7 days | 9 | F&I | F&I |
| Leads unworked over 24h | 14 | CRM | Sales |
Dashboard shown for illustration. Figures are sample data, not customer results or benchmarks.
Executive
Group stock, sales, delivery and exceptions across every company and branch.
Sales & CRM
Pipeline by stage, conversion, lead response time, lead source and salesperson performance.
Inventory
Stock by status, model, trim, colour, branch and location, with aging and turnover.
Logistics
Units in transit, vessel ETA, port arrivals, customs pending and logistics delays.
Factory orders
Orders placed, units in production, production completed, forecast versus actual.
Delivery
Deliveries today, upcoming, blocked, delayed and average delivery days.
Stock aging
Aging buckets, slow-moving stock, days in stock and oldest units by branch.
Exceptions
Every record that is late, blocked, stalled or awaiting a decision, with an owner.
KPI definitions
The most useful dealership KPIs fall into four groups: inventory health, sales effectiveness, delivery performance and supply chain. Each should have a fixed definition so branches report the same thing rather than three versions of it.
Inventory health
| KPI | Definition | Why it matters |
|---|---|---|
| Days in stock | Calendar days from vehicle receiving at the first dealer location to today, or to delivery | The base measure for holding cost and pricing decisions |
| Aging buckets | Unit counts in 0–30, 31–60, 61–90, 91–120 and 120+ day bands | Shows the shape of the problem, not just the average |
| Slow-moving stock | Units exceeding a configured age threshold for their model and branch | Identifies specific vehicles requiring a decision |
| Stock turnover | Units sold in a period relative to average stock held | Whether stocking levels match actual demand |
| Demand vs stock | Enquiry and booking volume by specification against units held | Where the group is over- or under-stocked by variant |
Sales effectiveness
| KPI | Definition | Why it matters |
|---|---|---|
| Lead response time | Lead creation to first logged contact attempt | One of the few sales inputs directly controllable by a manager |
| Lead aging | Days a lead has been open without stage progression | Where the pipeline is silting up |
| Quotation-to-booking | Share of quotations converting to a confirmed booking | Whether pricing or availability is the constraint |
| Booking cancellations | Bookings cancelled as a share of bookings created | Early warning on delivery timing or deal quality |
| Deal margin | Operational margin on the approved deal, after discount, trade-in and accessories | Where margin is actually being given away |
| Allocation conflicts | Blocked attempts to allocate an already-committed VIN | Indicates process pressure on stock discipline |
Delivery and supply chain
| KPI | Definition | Why it matters |
|---|---|---|
| Booking-to-delivery | Days from confirmed booking to actual customer handover | Whether the back office keeps pace with sales |
| Order-to-delivery | Days from factory order confirmation to handover | End-to-end chain performance for a distributor |
| Delivery readiness rate | Share of scheduled deliveries where every dependency cleared on time | Predicts customer experience before it happens |
| Blocking reason | The dependency that most often prevents a scheduled delivery | Turns a general frustration into a specific fix |
| Units in transit | Vehicles despatched but not yet received at a dealer location | Forward supply visibility for sales planning |
| Logistics delays | Units whose actual milestone dates exceed plan | Early warning to customers rather than late apology |
| Customs pending | Units at destination port awaiting clearance, with elapsed days | Storage and demurrage exposure |
AutoFixia does not publish benchmark values for these KPIs. Any figure shown on this site is sample data. Comparative benchmarks would require consented, anonymised, methodologically explained data, which AutoFixia will publish only if and when it genuinely holds it.
Which numbers matter to whom
Consolidated stock and aging across branches, target versus achievement by branch and model, average order-to-delivery and booking-to-delivery time, deal margin with approval visibility, and an exception list covering delayed shipments, aging stock, blocked deliveries and deals awaiting approval. The exception list is usually the most actionable.
| Role | Primary metrics | Decision it supports |
|---|---|---|
| Dealer Principal | Group stock, aging, target vs achievement, order-to-delivery, deal margin, exceptions | Where to intervene this week |
| Sales Manager | Pipeline by stage, lead response time, quotation-to-booking, deals awaiting approval | Which salesperson and which deal needs attention today |
| Inventory Manager | Stock by status and location, days in stock, aging buckets, slow-moving units, transfers | Which specific vehicles need a pricing or transfer decision |
| Logistics Manager | Units in transit, vessel ETA, port arrivals, customs pending, logistics delays, damage reports | Which shipment to chase and which customers to forewarn |
| F&I Manager | Finance applications by status, approvals expiring, insurance issuance, disbursement status | Which files will block a delivery next week |
| Delivery Coordinator | Deliveries today and upcoming, readiness state, blocking dependency per deal | What to resolve before each scheduled handover |
| IT / Digital Lead | User activity, audit logs, data completeness, integration status | Whether the system is being used as designed |
Analytics FAQs
Yes, and the filtering respects the same data permissions as the operational screens.
A branch manager sees their branch. A brand director sees their brand across branches. Group management sees the consolidated position. Nobody sees data they are not permitted to see simply because it appears in a report.
Yes. Data export and API access support feeding an external business intelligence platform.
Groups that already have a BI standard usually want operational data flowing into it rather than a second reporting tool. The DMS dashboards remain useful for day-to-day operational management, where the value is drilling from a number straight to the record behind it.
Yes. Branch, salesperson and model targets can be set and measured against actual achievement.
Targets are configured rather than fixed, so a group can measure whatever it manages by — units, deliveries, or a combination. Target versus achievement then appears on the executive and sales dashboards without a separate tracking spreadsheet.
Dashboards reflect the operational records as they stand, because they read from the same data the operational screens use.
The practical limit is not the reporting layer but the operational discipline behind it: a vehicle received yesterday and recorded today will show in the stock position from the moment it is recorded. This is one reason receiving, allocation and delivery are designed as quick, structured actions rather than lengthy data-entry forms.
See the dashboards against your own operation
Bring the questions your management meeting actually asks, and we will show where each answer comes from.