What are DealerInt system requirements?

Expanded explanation

DealerInt requires: Chrome browser, DealerInt account, and access to a supported web-based DMS. No special hardware. No server installation. See DealerInt docs for full requirements.

Key points

• Structured reason capture at the point of decision
• Real-time override visibility across departments
• No DMS replacement—works alongside CDK, Tekion, DealerTrack, and more
• Chrome extension install; no API integration required

Benchmark data

Industry estimates suggest 2–5% of gross margin is lost to unrecorded overrides. On a $50M operation, that's $1–2.5M annually.

Recovery rates improve with consistent policy and visibility. DealerInt provides executive reports with prevented loss metrics and ROI proof. See the Dealer Profit Index for regional and segment breakdowns.

Case study

“We run Reynolds at 15 rooftops. DealerInt showed us override patterns we never had before. Recovered $62K in quarter one.” — Group GM

Implementation steps

1. Install DealerInt as a Chrome extension alongside your DMS. No integration required.
2. Define override policy: thresholds, approval limits, reason codes.
3. Train staff on reason capture. The prompt appears only when an override occurs.
4. Review dashboards weekly. Override volume by reason, department, location.
5. Use data for policy refinement and training—not blame.

References

• Dealer Profit Index
• How to stop dealership discounting
• How to track F&I overrides
• Compare DealerInt
• Blog