CRM · ScoutX → VinSolutions
ScoutX and VinSolutions
VinSolutions takes ADF, which is the format Scout produces for every lead. You supply the lead address for each store and leads arrive in the shape VinSolutions parses.
How it works
- Delivery is ADF 1.0 XML to the lead address VinSolutions issues you. Nothing to install, nothing inside VinSolutions to reconfigure.
- Routing is per location and per department, so each store’s enquiries reach that store’s VinSolutions address.
- Leads are stored on the Scout side before delivery is attempted, so they stay visible and re-sendable regardless of what happens downstream.
- The ADF carries the unit of interest and, where collected, 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 opens.
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
VinSolutions questions
Do we need an API key or a 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 instance?+
Yes — set per location, and per department within a location.
What if a lead does not appear?+
It is in the Scout admin either way, a delivery failure raises an alert, and it can be re-sent.