CRM · ScoutRV → VinSolutions
ScoutRV and VinSolutions
VinSolutions takes ADF, which is the format Scout produces for every lead. You supply the lead address for each store and the leads arrive in the shape VinSolutions parses.
How it works
- Delivery is ADF 1.0 XML to the lead address VinSolutions issues you. There is nothing to install and nothing inside VinSolutions to reconfigure.
- Routing is per location and per department, so a group sends each store’s enquiries to that store’s VinSolutions address.
- Leads are stored on the Scout side before delivery is attempted, so they remain visible and re-sendable in the Scout admin regardless of what happens downstream.
- The ADF carries the unit of interest and, where the form collected one, the trade-in as a second vehicle block.
- One quirk worth knowing: some CRMs on this lineage ignore the price element in an inbound ADF. Where that matters, the unit price is also written into the comment body so it is visible on the lead your team actually opens.
- A delivery failure raises an alert instead of being logged and forgotten.
Other integrations
Lightspeed → ScoutRV
Lightspeed DMS
Automatic inventory sync from Lightspeed, including multi-store feeds.
IDS → ScoutRV
IDS DMS
Automatic inventory sync from IDS, the most common DMS in RV retail.
Motility → ScoutRV
Motility
Inventory sync from Motility, in either its XML or CSV export.
Questions
VinSolutions questions
Do we need an API key or a special connector?+
No. Delivery is ADF/XML to the lead address VinSolutions gives you, which is the route it is designed to receive.
Can each rooftop go to its own VinSolutions instance?+
Yes — the destination is set per location, and per department within a location.
What if a lead does not appear in VinSolutions?+
The lead is in the Scout admin either way, a delivery failure raises an alert, and it can be re-sent.