Syndication · ScoutX → ICC
ScoutX and ICC
ICC normalises dealer inventory feeds and passes them on to third parties. Feeding ICC once means several downstream systems are fed correctly rather than each being wired separately.
How it works
- The file matches the certified-inventory column format exactly — 49 fields — so ICC does not have to remap anything on receipt.
- One file covers the whole group, with the dealer identifier resolved per row from a per-location map.
- Location names are matched case-insensitively and with surrounding whitespace ignored. That sounds pedantic; an exact-match lookup blanks out a whole store’s identifier when a location name has a trailing space, and that fails silently rather than loudly.
- A store with no identifier of its own can be pointed at a sibling rooftop’s while still carrying its own name on every row.
- This feed sends your sale price. Base-price display is supported through the condition-level override, which substitutes the price before the file is built; the more granular make-and-model pricing rules do not apply to this partner.
- 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.
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
ICC / JD Power questions
We have a store with no ICC rooftop of its own. Is it excluded?+
No. It can be mapped to a sibling rooftop’s identifier and still carries its own location name.
Do we need one feed per store?+
No — one file carries the group, with per-row dealer identifiers.