Marketplace · ScoutRV → Autotrader

ScoutRV and Autotrader

Autotrader’s single-dealer file specification is precise about layout, and getting it wrong means a rejected file rather than a warning. Scout builds it to spec.

How it works

  • New and used are separate files with different column layouts, because that is what the specification requires — 26 fields for new, 24 for used.
  • The specification’s formatting rules are applied rather than approximated: every field quoted, no header row, no currency symbols or decimals in price fields, image URLs listed within the field, and file names carrying the dealer identifier and the date.
  • Pricing is rule-aware: condition-based overrides, make and model overrides, and base-price display are all resolved before the file is built, so the number that ships is the one you configured rather than whatever sits in the raw price column.
  • On new units both the manufacturer price and your price travel, in the fields the specification assigns to each.
  • 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.
  • Every file that goes out is archived, so when a partner says a listing is wrong there is a copy of exactly what was sent rather than a reconstruction of what should have been.

Questions

Autotrader questions

Why are there two files?+

The specification defines different column layouts for new and used. Sending one combined file is a rejection.

We have several rooftops with separate Autotrader dealer IDs. How does that work?+

Where the partner wants separate files per rooftop, each store gets its own feed configuration scoped to that location. Where a partner wants one file for the group, the dealer identifier is resolved per row instead.

Ask us about your stack.

Request a Demo