How to Track Pricing Overrides at Your Car Dealership

Why track pricing overrides

If you don’t track why prices change, you can’t see patterns, enforce policy, or recover margin. Tracking overrides means: (1) capturing every override, (2) assigning a structured reason, (3) aggregating and reporting. Most DMS systems don’t do step 2 in a way that aggregates. So you need a layer that does.

What to capture

For each override: who (salesperson/manager), when, reason (from a fixed list), margin impact (baseline vs final). Reason codes might be: competitive match, manager approval, loyalty, aging inventory, F&I exception, other (with note). Keep the list short so staff use it.

How to categorise reasons

Align with your written policy. If you allow “competitive match,” require proof or a cap. If “other” is allowed, require a short mandatory note. Category badges in reports (pricing vs F&I vs recon) help. DealerInt lets you configure reason codes and categories per store.

Using the data

• By reason — Where is most margin going? Competitive match? Manager approval?
• By person — Who is above or below store average? Coaching, not blame.
• By location — Multi-store: which store has the highest override rate?
• By time — End-of-month spikes? Use data to tighten policy or training.

Implementation without disruption

Capture at the point of override. A dropdown with 5–6 reasons takes seconds. The prompt appears only when an override occurs. No long forms. Chrome extensions (e.g. DealerInt) run alongside your DMS—no API, no IT project. Install in 4 minutes.