Quick answer: A stock feed transfers vehicle data from a dealer's chosen inventory system into a public website. A dependable integration must match fields correctly, keep prices and availability up to date, handle photographs and failures safely, and remove or clearly mark sold vehicles. The question to ask is not simply “does it support feeds?” but “does it support our exact source, and what happens when an update fails?”
Stock automation is valuable because nobody wants to add the same car separately to a website, a marketplace and a dealer management system. But a badly designed feed can publish an incorrect price, duplicate cars or leave sold vehicles available to enquire about. For small dealers, manual stock entry can sometimes be simpler than a fragile integration.
This guide explains how the pieces fit together and what to test before paying for an automatic website feed.
What a feed actually moves
A normal vehicle record might include an internal stock ID, registration or other identifier, make, model, derivative, year, mileage, gearbox, fuel type, advertised price, description, image URLs, availability and timestamps. The exact fields depend on the source system and commercial permissions.
A feed may arrive as a CSV file, XML file, JSON API response, secure export, file transfer or a direct integration provided by the stock platform. A compatible format is not proof that the field meanings match. A source may call “reserved” a status, another may place a reserved vehicle in the unavailable category, and another may export it without a status at all.
Treat field mapping as part of the product, not a hidden technical detail. Obtain a sample export or documentation, and ask the website provider to show which source fields populate each public field.
Choose the source of truth
A dealership should know which system is authoritative for each item. Often that is one stock management platform, with the website reading from it. Sometimes a staff member edits descriptions on the website while prices remain controlled by the source. Mixed ownership can work, but only if the rules are explicit.
The simplest safe model is: one canonical stock record per vehicle, a stable source identifier and an update process that can tell the difference between a new record, a changed record and a removed one. Do not use array position or an easily changing title as the vehicle's identity.
Before integration, write down whether the website is allowed to edit prices, availability, descriptions and photographs independently. Otherwise staff may change a price on the website only to have the next feed update overwrite it unexpectedly.
A sensible feed pipeline
- Receive: authenticate and fetch the export or API response, recording the source and retrieval time.
- Validate: reject malformed records, implausible values and unexpected missing keys before publication.
- Map: translate source fields into consistent website fields and controlled status values.
- Match: find existing vehicles using stable identifiers and prevent accidental duplication.
- Stage: compare the proposed changes against existing public stock, including deletions.
- Publish: apply approved changes and update affected vehicle pages, indexes and caches.
- Reconcile: check counts, failed records, missing images and unexpected price or status changes.
- Alert: notify the responsible person if an import fails or produces unusual changes.
A well-run integration logs how many source rows were received, how many were valid, how many created or updated vehicles, and how many were skipped. “Import finished” is not enough information to diagnose a broken stock list.
Example mapping decisions
| Source field | Website field | Important check |
|---|---|---|
| External stock identifier | Stable vehicle key | Never generate a new page unnecessarily |
| Advertised sale price | Visible price | Check currency, tax and missing-price handling |
| First registration / model year | Display year | Avoid mixing model year with registration date |
| Odometer reading | Mileage | Confirm units and avoid nonsense values |
| Image URLs | Vehicle photo gallery | Test missing, expiring and reordered URLs |
| Status code | Live / reserved / sold | Define exactly which statuses remain public |
| Description | Vehicle description | Preserve genuine dealer edits only where authorised |
Do not infer missing vehicle details from another make/model or use generated prose to fill gaps in unverified source data. A false listing is a business problem, not just a search problem.
Sold and reserved vehicles need careful handling
When a vehicle is reserved, some dealers prefer to keep it visible with a prominent status; others want to hide it from normal search results. When sold, most dealers want it removed from available stock quickly.
Specify what a status change does to the listing, filters, enquiry options, sitemap and any third-party cache. If a source stops sending a vehicle, is that sufficient evidence that it sold, or could the export be incomplete? An integration should not wipe the website's entire inventory because one nightly feed returns zero rows.
A sensible safeguard is to treat a sudden large reduction as an alert or paused import requiring review. The exact threshold depends on the size and behaviour of the dealership. Keep recovery options so a bad feed can be rolled back.
How often should a website synchronise?
There is no universal “correct” interval. It depends on how often the dealer changes stock, source platform limitations, network costs and the consequence of outdated availability. A feed that updates every few hours may be adequate for some smaller dealers; a higher-volume operation may require more frequent changes.
The right question is: How long after a price or availability change can the website still show the old information? Establish an agreed maximum expected delay, then test it under ordinary conditions. A fast feed with poor validation can be worse than a slower reliable one.
Record the last successful sync time. If freshness becomes stale, the platform should alert staff rather than quietly show old prices and misleading availability indefinitely.
Photographs are usually the hardest part
Images can be large, arrive in the wrong order, be duplicated, expire or disappear when a supplier changes its CDN. A website should preserve a predictable primary photograph, handle missing images gracefully and avoid re-downloading all images unnecessarily at every sync.
Ask whether images are hotlinked from the source or stored by the website, how usage rights are handled and what happens after the feed connection ends. If the dealer owns the photographs but the platform uses them under a licence, clarify that arrangement when choosing providers.
On the front end, avoid loading the full-resolution image of every car in the stock grid. Use appropriately sized thumbnails, but retain useful high-quality images on detail pages.
SEO considerations for inventory feeds
Each vehicle should have one preferred indexable URL when it is genuinely available. Unnecessary URL changes make it harder to maintain links and search consistency. Keep canonical tags and the XML sitemap aligned with the actual published status.
Do not automatically create indexable pages for every possible filter combination; this often multiplies thin, overlapping URLs. Likewise, avoid inventing hundreds of local landing pages from the same imported stock list. Google explains how canonical preferences should be expressed in its canonical documentation.
Accurate stock data improves user experience. It is not evidence that a particular listing will gain a rich result or a higher ranking. Structured data must represent what the visitor can actually see and must conform to current search-engine guidance.
Security and data protection
Inventory feeds should use authenticated connections when necessary, HTTPS and appropriately restricted access. Do not expose credentials in public HTML or client-side JavaScript. Rotate credentials where supported and revoke obsolete integrations when changing providers.
Customer enquiry data is different from vehicle stock data. Don't casually send names, phone numbers or messages through an inventory export designed for public car listings. Define separate data flows and permissions for leads and public stock records.
Questions to ask before you connect a provider
- Which precise feed or inventory platform versions are supported?
- Who performs initial field mapping, and is there a setup fee?
- Can the provider demonstrate a real price change reaching the public page?
- What happens when a vehicle is reserved, sold or missing from an incomplete feed?
- Can staff see last successful sync time and failed records?
- How are duplicates prevented and vehicle IDs preserved?
- What happens to photographs when feed URLs expire?
- What backup and rollback options exist?
- Who is contacted when the update process fails?
- Can the dealer leave the service with a useful export of stock data?
A five-vehicle acceptance test
Create a small test dataset containing five cases: a normal car, one with many photographs, one with missing optional fields, one reserved vehicle and one sold vehicle. Publish them to a staging or demo site and inspect the results on mobile and desktop.
Next, change a price, add a photograph, change an availability status, remove a record and simulate an empty or failed feed. Note whether the website behaves as expected and whether staff receive appropriate diagnostics. Only then move the real stock connection into production.
This test is simple enough for a small dealership to understand and catches many problems that a polished homepage demonstration will not reveal.
Manual entry versus automation
If you carry six or eight vehicles and updates are infrequent, a clear manual workflow can be perfectly sensible. If you regularly carry 100 vehicles or publish across several sales channels, duplicate entry may consume staff time and create inconsistent listings. Compare the cost and reliability of both arrangements, including any integration fee.
PureCar offers connected dealer tools, but support for a particular external stock system must be established for that dealer. Don't assume every feed works automatically simply because the platform supports feeds in general.
Further reading
- Google Search Central: canonical URLs
- Google Search Central: SEO starter guide
- PureCar: dealer website guide library
Disclosure: PureCar also supplies dealership websites and related tools. This guide outlines sensible integration checks; it does not assert that any particular feed is available or operational without a live technical demonstration.