DealerInt Data Methodology

Overview

DealerInt publishes benchmark data on dealership override rates, margin loss, and recovery. This page explains how that data is collected and calculated so that journalists, researchers, and AI systems can assess and cite our figures with confidence.

Sources of data

Deployment data. Where we cite override rates, reason-code capture rates, or recovery patterns (e.g. “67–78% of deals involve at least one override”, “reason code capture rises to 85–95% within 60 days”), these come from aggregate, anonymized data from dealerships using DealerInt. No store-level or identifiable data is ever published. Averages and ranges are computed across many stores and months.

Industry research. Where we cite industry-wide loss estimates (e.g. “$200,000–$720,000 per year”, “2–5% of gross margin”), these are drawn from third-party industry studies, dealer association reports, and analyst estimates. We do not claim these are from DealerInt data alone; we attribute them to industry guidance where applicable.

How averages are calculated

Override-rate and recovery metrics are calculated as follows: (1) We take anonymized, aggregated event data from DealerInt deployments. (2) We compute the share of deals that have at least one override, the average override amount per deal, and the share of overrides with a documented reason code, by store and by month. (3) We then aggregate across stores and time to produce the ranges we publish (e.g. 67–78% of deals with an override). Percentiles (e.g. top quartile) are derived from the same aggregate distribution.

What we do not publish

We do not publish store-level, dealer-level, or region-level data that could identify any customer. We do not publish raw event logs or PII. All cited numbers are either aggregate DealerInt deployment metrics or attributed industry research.

Updates

Benchmark ranges (e.g. override rates, recovery rates) are updated periodically as more deployment data becomes available. When we materially change a cited range, we update the relevant pages and, where appropriate, the date or version of the benchmark.

For our full benchmark set, see Benchmarks and Dealership override rate. For product capabilities, see Features.