DMS · IDS → ScoutRV

ScoutRV and IDS

IDS is the DMS most RV dealers run, and Scout reads from it directly. Your DMS workflow does not change.

How it works

  • Inventory flows from your DMS into Scout automatically on a schedule — no exports, no spreadsheets, no re-keying.
  • Units arrive with pricing, status, photos and specifications, and changes made in the DMS appear on the site without anyone touching the website.
  • Feed health is monitored. If your DMS stops sending, an automated check catches it within hours rather than when a customer calls about a unit you sold last week — a failure mode most RV dealers have experienced at least once.
  • The IDS reader understands the shape of an IDS/AHIN export rather than treating it as a flat file: plain elements, the spec block, and the option list are each mapped separately, so a value that lives in the spec block still lands on the right field.
  • IDS records frequently arrive thin on the fields shoppers actually filter on — sleeps counts, lengths, dry weights. Scout enriches those against its own RV spec library so units stay findable rather than being technically listed and practically invisible.
  • Staleness is judged on the date of the feed file itself, not on whether the nightly sync ran. A provider that keeps re-serving the same file makes the sync look healthy while your inventory quietly freezes; that is the case the check is built to catch, and anything over 48 hours raises an alert.

Questions

IDS DMS questions

Our IDS data is inconsistent. Is that a problem?+

It is the normal case, and it is why the spec library exists. Units are matched to floorplan data by year, make, model and floorplan so missing fields get filled without anyone cleaning records by hand.

Does Scout write anything back to IDS?+

No. The sync is read-only into Scout.

How are sold units handled?+

Status carries through from IDS and sold units come off the site promptly.

Ask us about your stack.

Request a Demo