CRM · ScoutX → Lightspeed CRM
ScoutX and Lightspeed CRM
Where you run Lightspeed CRM, leads go in over its lead import API rather than by email — a direct post carrying the unit and the trade-in.
How it works
- Leads post as the prospect record Lightspeed expects, with 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.
- A failed 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 places it already arrived.
- This is independent of the Lightspeed inventory sync; either can run without the other.
- Where a value is approximate — a location derived from the visitor’s connection rather than typed by them — the notes say so, rather than handing a salesperson a guess dressed as a fact.
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
Lightspeed CRM questions
Is this the same as the inventory sync?+
No. That reads units out of Lightspeed DMS; this posts leads into Lightspeed CRM. They are configured separately.
What happens if a post fails?+
The lead is already stored and visible in the Scout admin, and the failed post can be retried on its own.