What Is an Inventory Feed?

One record per vehicle, sent on a schedule, to every place your cars appear.

An inventory feed is a structured file or data connection that carries a dealership's current vehicles out to the places those vehicles are advertised. One record per unit, the same fields in the same order every time, refreshed on a schedule. It is the difference between a store's inventory existing in one system and that inventory appearing on its own website, on listing sites, in its marketing tools and inside its CRM without anyone retyping a single vehicle.

Feeds come in three common shapes. A delimited file, usually comma or tab separated, dropped on a server for each receiver to collect. An XML or JSON document published at a web address that receivers read on a timer. Or an interface, an API, where a receiver asks for exactly the units it wants when it wants them. The file is the oldest and still the most common; the interface is the most useful, because it can answer a question rather than hand over the whole list.

The sender is normally the store's dealer management system or the inventory tool the store uses to manage vehicles. The receivers are everyone downstream: the website provider, the marketplaces, the marketing platforms, the window label printer, the vehicle detail pages a shopper actually reads. Cadence ranges from nightly to every few minutes, and the right answer depends on how fast the store's prices and stock move.

Every feed carries the identity fields: VIN, stock number, condition, year, make, model, trim, body style, exterior and interior color, mileage, engine, transmission and drivetrain. Those are the fields a shopper filters on, so an empty trim or a blank mileage field does not just look sloppy, it removes the vehicle from searches that would have found it.

Then the fields that decide whether a listing earns a click. Photo URLs, and the count matters more than any other single field on the record. The vehicle description, which is the only free text in the whole file and the only place a store can say why this unit is worth more than the identical one two towns over. Price, and any second price field the receiver uses to show a reduction. Certification status, factory option codes and package names, days in stock, and the date the unit was added.

Last are the operational fields that nobody notices until they are wrong: status, which tells a receiver whether the unit is available, sold or pending, and the dealership identifiers that route the record to the right rooftop when a group sends one file for six stores.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

Say a store carries 180 units and publishes a file every night at two in the morning. Illustrative figures only. A vehicle sells at four on Tuesday afternoon. Unless something removes it sooner, it is still advertised for ten more hours, and the calls it generates on Wednesday morning are calls about a car nobody can sell. Move to an hourly refresh and the same unit disappears within the hour.

Now look at the other side of the same file. Twelve of those 180 units have fewer than four photos, because they arrived over the weekend and the photographer comes on Thursdays. Those twelve are in every search result a shopper runs, sitting beside fully photographed cars, and losing the click every time. Nothing is broken, the file is valid, the vehicles are real, and the store is quietly paying to advertise twelve vehicles that will not be looked at. That is what people mean when they say the feed is the product.

The first failure is staleness, and it has two halves: sold units still advertised, and price changes that reach one receiver hours before another. Both are corrosive because the customer sees the inconsistency and assumes it was deliberate.

The second is mapping. A receiver expects trim in one field and the sender puts it in another, so every vehicle arrives with a blank where the trim should be. Mapping problems are invisible from the sending side because the file looks perfect leaving the building. The only way to catch them is to look at what the receiver published, not at what was sent.

The third is silent change. Somebody at the sending end renames a column or changes a date format, and every receiver either drops the field or drops the record. The fourth is not knowing who consumes the feed at all. Stores routinely discover a receiver nobody remembers authorizing, still publishing inventory to a site the store stopped paying for a year ago. Keep the list of consumers, review it, and be able to switch one off the same day.

Inventory Link ingests the store's feed, stores it as one clean record per unit and publishes it outward. There is a feed editor for correcting what arrives, a request a change form when the fix belongs at the source, and stock number overrides so a human correction survives the next refresh. From that single record it builds the store's inventory site, an embeddable widget for any page the store already owns, per salesperson inventory sites and brand offer pages, and it exposes a public inventory API with key provisioning so the store can hand a consumer a key and take it back when the relationship ends.

If the store has no feed, that is not a blocker. Inventory Link imports inventory directly from the store's own website, recognizing dozens of website platforms, and an inventory feed and dealer management system access are not required to use the platform at all. The same vehicles then appear in the Inventory menu of LeadLocate CRM and behind the vehicle button in every text and email composer. The category page on dealer inventory feed management goes deeper, and inventory feeds covers the setup itself.

Who sends a dealership's inventory feed?

Usually the store's dealer management system or the inventory tool it uses to manage vehicles. A dealer group often sends one file covering several rooftops, with a dealership identifier on each record so receivers can route it to the right store.

How often should an inventory feed refresh?

Often enough that a sold car stops being advertised and a price change reaches shoppers the same day. Nightly is the old standard and is still common. Hourly or near live is better, and it matters most for stores that reprice weekly and sell quickly.

What is the difference between a feed and syndication?

The feed is the data and the format. Syndication is the act of publishing that data to many destinations on a schedule with rules for each one. You need a feed before you can syndicate anything, and most syndication problems are really feed problems.

Do I need an inventory feed to advertise my vehicles?

No. Inventory can be imported directly from the store's own website when there is no feed, and an inventory feed and dealer management system access are not required to use the platform. Brokers and single salespeople work this way every day.

A specialist loads your inventory live, shows what arrived, what is missing and where it publishes, in about fifteen minutes.

Prefer to talk right now? Call or text 844-376-2274.