Syndication · ScoutX → DealerVision
ScoutX and DealerVision
Scout builds the inventory file DealerVision specifies and delivers it on a schedule.
How it works
- The file carries identifiers, specifications, features, condition and pricing in the layout DealerVision asks for.
- Multi-rooftop groups send one file, with the dealer identifier resolved per row from a per-location map.
- This feed sends your sale price. Base-price display is supported through the condition-level override, which substitutes the price before the file is built; the more granular make-and-model pricing rules do not apply to this partner.
- An automated check flags any enabled feed whose last successful push is more than 48 hours old, or that has been switched on for 48 hours and has never pushed at all. Alerts are raised once per dealer and name every affected feed, rather than firing on every run.
- Every file that goes out is archived, so when a partner says a listing is wrong there is a copy of exactly what was sent rather than a reconstruction of what should have been.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Read more
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Read more
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Read more
Questions
DealerVision questions
Each store has its own DealerVision ID. Does that work?+
Yes. Identifiers are mapped per location and applied row by row within a single file.
Can we exclude a location or a condition?+
Yes — scope by location, condition, category or individual unit.