Authorized integration
Preferred: a dealer-approved vAuto, HomeNet, Dealer.com, or comparable provider export or API.
How inventory enters the gateway
Scheduled export
CSV, SFTP, object storage, or HTTPS provides a controlled path without broad system access.
Website evidence
Structured data and vehicle pages can bootstrap a pilot or fill public merchandising gaps.
Reconcile
Every field keeps its source and timestamp. Conflicts are reviewed instead of silently overwritten.
New inventory: vehicles and incentives stay separate
Base inventory can come from a provider or dealer export. Incentives should come from a licensed program source, dealer-approved merchandising feed, or dealer-maintained campaign file. When the only evidence is a public page, the gateway keeps the offer conditional and records its eligibility language, expiration, geography, source URL, and observation time.
No universal-rebate guessing. A public incentive is not applied to every shopper unless its authoritative rules say every shopper qualifies.
Used inventory: vAuto, HomeNet, or an authorized website adapter
Used-vehicle records can include mileage, stocked date, first public listing date, price, photos, condition, certification, warranty, and public reconditioning facts. CARFAX, AutoCheck, or another history source is connected only under the dealer’s provider rights, with discrepancies preserved.
When we crawl
A consented crawler is the practical fallback when no usable feed is available. It respects site policy and rate limits, prefers structured fields, captures evidence, detects template changes, and stops publishing stale or ambiguous data. It cannot make a website snapshot authoritative for current availability.
Start with a free AI Answer Audit → Read the open architecture