ScoutX and Motility

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 powersports dealers have experienced at least once.
• Two readers exist — one for the XML export, one for the CSV — so you send whichever your installation produces rather than being asked to change it.
• Field names differ between installations. Mapping is configuration rather than code, so an unusual column name is handled by pointing the mapping at it instead of waiting for a release.
• Which of your status values mean sold, pending, on hold or on order is something you set. A value nobody has mapped yet is recorded for review rather than guessed at — guessing is how a unit that is merely on hold disappears from the site.
• 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.