CRM · ScoutRV → Lightspeed CRM
ScoutRV and Lightspeed CRM
Where you run Lightspeed CRM, leads go in over its lead import API rather than by email — a direct post, with the vehicle and trade-in attached.
How it works
- Leads post as the prospect record Lightspeed expects, carrying the customer, the unit of interest, and the trade-in where the form collected one.
- Credentials are per store, so a group configures each rooftop against its own Lightspeed dealership rather than pooling everything into one.
- A lead that fails to post can be retried from the admin, and the retry re-sends only the leg that failed — it does not duplicate the lead into the other places it already arrived.
- This runs independently of the Lightspeed inventory sync. You can have one without the other.
- Where Lightspeed cannot mark a value as approximate — a location derived from the visitor’s connection rather than typed by them — the notes say so, rather than presenting a guess as a fact your salesperson will act on.
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
Lightspeed CRM questions
Is this the same integration as the inventory sync?+
No. Inventory sync reads from Lightspeed DMS; this posts leads into Lightspeed CRM. They are configured separately and either can run alone.
What happens if a post fails?+
The lead is already stored on our side and visible in the Scout admin. The failed post can be retried, and the retry only re-sends the Lightspeed leg.
Can each store post to its own Lightspeed dealership?+
Yes. Credentials are held per store.