If a sold vehicle stays live on your website or third-party listings for more than 24 hours after the DMS marks it sold, that’s not a minor delay — it’s a feed problem actively generating inquiries your team then has to field and disappoint, wasting real BDC time on a vehicle that was never actually available.
The Three Recurring Failure Patterns
| Problem | What causes it | How to catch it |
|---|---|---|
| Stale listings | Status changes in the DMS don’t flow to the website/listing platforms fast enough | Mark a real vehicle sold and time how long it takes to disappear from every channel — should be under 24 hours |
| Price mismatches | DMS pricing and marketplace-listing pricing drift out of sync | Weekly spot-audit of 10 random vehicles across channels — any mismatch signals a feed issue, not a one-off fluke |
| Duplicate feeds | Both your DMS and a separate website provider push the same vehicle to the same destination (commonly Facebook or Google) | Audit which system is actually pushing to each channel — duplicates get penalized by the receiving platform, not just ignored |
Why This Costs More Than It Looks Like
Each of these failure modes has a compounding cost beyond the immediate symptom: a stale listing wastes a shopper’s time and your BDC’s time on a vehicle that isn’t real inventory; a price mismatch damages trust the moment a shopper notices the discrepancy between what they saw online and what’s quoted in person; and duplicate feeds don’t just look sloppy — platforms like Facebook and Google actively penalize accounts pushing duplicate content, which can suppress the account’s overall visibility, not just the duplicated listing.
Real-Time Feeds vs. the Old CSV-Upload Model
A modern Dealer Inventory API shares data near-instantly between systems rather than relying on scheduled CSV uploads — inventory providers now commonly update feeds automatically at least once daily, and often several times a day. This shift matters directly for the stale-listing problem specifically: a feed updating once daily has a much wider window for a sold vehicle to sit live than one syncing every few hours or in near-real-time.
What to Actually Do
- Designate one authoritative source per channel — if both your DMS and website provider can push to Facebook or Google, pick one and disable the other’s feed to that specific destination, rather than letting both run simultaneously.
- Run the 24-hour removal test regularly, not just once at setup — feed reliability can degrade silently over time as systems update or integrations change.
- Spot-check pricing weekly across a random sample rather than waiting for a customer complaint to surface a mismatch.
- Confirm your inventory provider’s actual sync frequency rather than assuming — “synced” can mean anything from real-time to once-daily depending on the specific integration.
This connects to the broader dealer website data picture in AutoScout24 Inventory Sync for WordPress Dealers. Want your dealership’s inventory feeds audited across channels? Get in touch.
Frequently Asked Questions
How quickly should a sold vehicle actually disappear from listings?
Under 24 hours is the benchmark worth testing against — anything slower means real shoppers are inquiring about vehicles that no longer exist, which wastes both their time and your team’s.
Is it really a problem if both my DMS and website vendor push the same listings?
Yes — platforms like Facebook and Google penalize duplicate listings from the same account, which can hurt visibility for the account broadly, not just create a harmless duplicate entry.
How often should I audit pricing accuracy across channels?
A weekly spot-check of a random sample (around 10 vehicles) is a reasonable cadence to catch drift before it becomes a customer-facing trust problem.
Featured image: original illustration.