Syndication · ScoutX → your partner
A feed for a partner we have never heard of
OEM programmes and regional aggregators ask for odd files. Rather than treating each one as a development project, Scout has a feed builder: you define the columns, the format and the delivery, and the file exists.
How it works
- Columns are defined by you — your names, your order, values drawn from a token list covering identifiers, specifications, pricing, photos and the unit’s own URL.
- CSV or XML, delivered either by SFTP on a schedule or served from a private URL the partner pulls. The URL form carries a long random access token, so it is not guessable and needs no login on their side.
- The price token resolves the same base-price projection the site shows, including installed accessories and rebates — which matters in powersports, where accessories and freight and setup often are the difference between the two numbers.
- The same scoping applies: location, condition, category, franchise or individual units.
- 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.
Other integrations
Lightspeed → ScoutX
Lightspeed DMS
Automatic unit sync from Lightspeed across every franchise you carry.
Motility → ScoutX
Motility
Unit sync from Motility, in either its XML or CSV export.
Your DMS → ScoutX
SFTP inventory feed
Any DMS that can drop a scheduled file — XML, CSV or pipe-delimited.
Questions
Custom feed questions
How long does a new feed take?+
It is configuration rather than a release, so it is a setup task. The partner confirming their own specification is usually the long pole.
Can the partner pull it instead of us pushing?+
Yes. Either delivery mode works; the pull URL carries a long random token rather than requiring credentials.
Can we use the partner’s column names?+
That is the point of it. Their names, in their order.