Your vehicles don't go from your lot to your website. They go from your lot to a DMS or an inventory tool, to a feed provider, to a file delivered on a schedule, to your website — and separately out to every marketplace you syndicate to. That chain is why a car you sold this morning is still on your site tonight, why the trim is wrong on three vehicles, and why nobody can tell you which system is at fault. Understanding the five links takes ten minutes and makes you much harder to fob off.
I build inventory platforms, so I've had to wire into this chain rather than describe it from outside. Here's the map, the four places it breaks, and the questions that get you a straight answer.
The five links
1. Capture. Someone photographs and describes the vehicle. This is where the data is born and where most errors originate. Vendors in this space have built whole businesses on it — Dealer Specialties, for example, states it has been collecting and distributing vehicle information for 30 years, covers over 4,000 dealers and a million vehicles, and delivers fully decoded vehicles with optional equipment identified plus actual photos of the vehicle. That "fully decoded, optional equipment identified" part is the real work: a VIN decode gives you the base car, not the $3,000 of options on the one in your lot.
2. Your system of record. A DMS, or an inventory management tool, or in plenty of smaller independents a spreadsheet. This holds the truth about what you own and what it costs.
3. A feed provider. This is the link most dealers don't know exists. Providers such as HomeNet, vAuto, Dealer Specialties and dozens of others take data from the system of record and distribute it. On the DealerRefresh dealer forums, practitioners describe the pattern as HomeNet pulling data from the DMS and handing it to vAuto — I'd treat forum accounts as informed sentiment rather than documented architecture, but the shape is right: data often passes through more than one intermediary before it reaches your site.
4. Delivery to your website. The customer data platform Fullpath defines an inventory feed as a list of all a dealership's vehicles usable as a data source for inventory, and describes it as "replacing a website scrape" — which tells you something important about the alternative. Their documentation says the data is automatically updated by the dealership's inventory provider at least once daily and up to several times a day, delivered via FTP or SFTP on a regular basis. Their supported-feeds list runs to 67 named providers, including website platforms themselves like DealerOn, Dealer.com, Dealer Inspire and Dealer eProcess alongside pure feed vendors.
Two things to take from that. First, "at least once daily, up to several times a day" is what the industry means by real-time, and it isn't. Second, if your integration isn't reading a feed, something may be scraping your own website to get the data — which means your site has become the source of truth for systems downstream of it.
5. Syndication. The same data goes out to marketplaces, your ad platforms and third-party listing sites, each with its own schedule and its own idea of what fields it wants.
Terminology, because two acronyms get mixed up constantly
ADF is not an inventory format. Auto-Lead Data Format is an XML specification whose stated purpose is providing a simple, flexible format for representing automotive customer leads. It's how an enquiry gets from a marketplace or your website into your CRM. It has nothing to do with getting vehicles onto your site, and I've watched that confusion waste an hour of a meeting more than once.
Inventory feeds are usually CSV or XML files delivered on a schedule to an FTP endpoint, or occasionally an API. Neither is inherently better; what matters is the schedule and what happens when a file is malformed.
The four places it breaks
Latency. Every link adds delay. If your feed provider exports nightly and your website ingests that export in the morning, your site can be up to a day behind your lot no matter how good your website is. Vendors in the space do assert that this should be immediate — DealerFire's guidance is that each time a vehicle is purchased or added, your website should reflect it immediately, and Dealer Specialties markets "fresh inventory live on your VDPs the same day, every day" — but a dealer should ask what the actual configured interval is rather than accepting the aspiration.
Silent failures. A feed that arrives empty or malformed is worse than one that doesn't arrive, because a well-behaved import rejects it and a badly-behaved one wipes your inventory or leaves it frozen. Ask what happens when a file fails validation, and whether anyone is alerted.
Field mapping and stale enrichment. Every link in the chain interprets the data. Trim levels get flattened, options get dropped, descriptions get overwritten by generated ones. A related problem is what the automotive marketing firm Demand Local calls schema drift — structured data that goes stale as inventory changes, which they identify as the most common real-world implementation issue with automotive markup. Your vehicle markup is generated from the same feed, so feed problems become search problems.
Sold vehicles. The hardest one, and the one with real consequences.
What happens when a car sells
Three things are true at once and they pull against each other.
It has to come off fast, and not only for customer experience. Advertising unavailable or nonexistent vehicles appears by name on the FTC's list of illegal pricing practices in the warning letters it sent to 97 auto groups in March 2026, which makes your sync interval a compliance parameter and not just a convenience. That's covered in more depth in the price display article.
It has to come off everywhere. As one inventory platform describes the ideal, sold or removed vehicles are automatically pulled from every connected marketplace, and a break at any stage produces the visible symptoms. That's a vendor's description of their own product rather than an independent finding, but the dependency is real: a car removed from your site and still live on three marketplaces is still generating calls.
And deleting the page has a cost. A discussion among practitioners on the DealerRefresh forums frames it bluntly: when you remove vehicles you delete URLs, lose indexed pages, and lose whatever authority those pages had built. That's forum sentiment, not measured data, but it points at a real design decision. The alternative to deletion is keeping the URL with a clear sold state and strong links to similar vehicles, which captures the buyer who arrived three days late instead of handing them a 404.
There's no single right answer here — it depends on your volume and how much organic traffic your VDPs actually earn. What's wrong is having no policy at all, which is the default state on most sites.
A well-built pipeline for a small independent looks like this. The vehicle data originates in one system of record and reaches the website as a scheduled file or API pull at a stated interval. Before anything on the site changes, the import is validated: an empty file, a file whose vehicle count suddenly collapses, and records missing a VIN, price or photo are all rejected. A rejected file leaves the previous inventory in place and sends an alert, so nobody discovers the problem from a customer.
When a vehicle is marked sold, the next import flips its page to a sold state instead of deleting it, and the sitemap is regenerated without it once its sold window ends. That means the time from "marked sold" to "gone from the site" is exactly one ingest interval, which is why the interval is the number to ask your vendor about. What the sold page should then do is covered in the sold vehicle pages article.
The one thing that makes this expensive
Worth knowing because it explains why the chain has so many links. Access to DMS data has been a long-running commercial fight. A vendor buyer's guide reports that CDK and Reynolds collectively paid over $730 million to settle antitrust lawsuits alleging they charged excessive data access fees to third-party vendors, and a separate procurement guide cites Reynolds certification charges of $10,000 to $100,000 annually including a proposed $100,000 data-access charge. I haven't verified either figure against primary court or contract documents, so treat them as reported rather than established — but they explain the structure. Intermediaries exist partly because direct DMS access is expensive and gated.
For an independent dealer the practical read is simpler: the fewer links between your lot and your website, the fewer places it can break, and the cheaper it is to fix when it does.
What this means for your dealership
Ask five questions and write down the answers. Who is my feed provider, and is there more than one in the chain? Is my website reading a feed, or is something scraping my site? What is the actual ingest interval, in hours? What happens when a feed file fails, and who gets told? And what does my site do with a vehicle's URL after it sells?
Then run one test that costs nothing. Note the time you mark a vehicle sold, then check your website, Google Business Profile and every marketplace you syndicate to. The longest gap in that set is your real exposure, and it's usually not the number in anyone's marketing.
Where I'd tell you not to hire me
If you're a franchise dealer with CDK or Reynolds and a stack of OEM-mandated integrations, a platform that already holds those certifications will get your inventory flowing faster and cheaper than I will, and the certification costs alone make a bespoke direct integration hard to justify. That's a genuine platform advantage and it belongs in the custom versus platform decision honestly.
Where a custom build wins is the smaller independent whose data lives in a spreadsheet or a lightweight tool, where the whole chain can be two links instead of five.
Sources
- Fullpath, Supported Inventory Feeds — definition of an inventory feed, "replacing a website scrape", update frequency of at least daily up to several times a day, FTP/SFTP delivery, 67-provider list.
- Dealer Specialties — 30 years of data collection, 4,000+ dealers, one million vehicles, decoded vehicles with optional equipment, actual photos, delivery options; "fresh inventory live on your VDPs the same day." Vendor's own claims.
- ADF specification (adfxml.info) — Auto-Lead Data Format as an XML format for representing automotive customer leads.
- FTC, Template Auto Warning Letter (sent 13 March 2026) — advertising unavailable or nonexistent vehicles listed as an illegal practice.
- Demand Local, Automotive Schema Markup — schema drift as the most common implementation issue.
- DealerRefresh forum threads on inventory providers and SEO guidance — cited as practitioner sentiment, not documented architecture.
- DealerFire and Spyne — vendor guidance on update immediacy and marketplace delisting. Vendor claims.
- VendorMotive and Monetizely — reported DMS data-access settlement and certification figures, not verified against primary documents.
Want to know how far behind your lot your website actually is? Tell me when you next mark a car sold and I'll time it.