Automotive Inventory Syndication Software

The feed is the product. Everything downstream inherits its mistakes, and most stores have never seen theirs.

Syndication is a simple idea with a lot of failure surface. You have vehicle records in one place. Several destinations want them, each in a different shape, on a different schedule, with different required fields. Software sits in the middle, translates, and pushes.

The failures are almost never in the pushing. They are in the data. A unit with no photos publishes with a placeholder that kills the click. A unit missing trim publishes as a base model and prices badly against its competition. A unit that sold this morning stays live for six hours and generates three calls your team has to apologize through. A price change made in one system does not reach the destination until the next scheduled run, and a shopper arrives quoting yesterday's number.

Then there are the duplicates. Two feeds carrying the same VIN, or a unit that moved between rooftops and now exists twice, competing with itself and splitting its own performance data.

Every one of those is a data problem, not a distribution problem. Which is why the first question about any syndication tool is not how many destinations it reaches. It is what it does when the record is wrong. Feed management covers the mechanics in more depth.

Not all fields are equal. A handful carry most of the commercial weight, and stores routinely let them go stale.

Photos. Count and quality, in that order. A unit with four photos performs differently from the same unit with thirty, and the first photo does most of the work. Units publishing with a stock image or a placeholder are effectively invisible.

Price. Present, current, and consistent across destinations. A unit priced differently in two places is a conversation your salesperson loses before it starts.

Trim and options. The difference between a shopper filtering you in and filtering you out. Trim is also what makes your price look reasonable or absurd against the unit next to it.

Mileage and condition. Obvious, frequently wrong, especially on units that sat.

Description. The field most stores leave to an automated template. A real description written for the actual vehicle is one of the few remaining places a store can differentiate at zero marginal cost. See listing optimization for how to write them at volume.

Fix these once at the source and every destination improves at the same time. Fix them destination by destination and you will be doing it forever.

Naming the actual pieces rather than describing capability in the abstract.

Feed ingest and storage. It takes the dealer's live feed, with VIN, trim, mileage, price and photos, and holds it as a working dataset rather than a pass through.

A data manager. Where the ingested records are reviewed and worked on, so the store can see what actually arrived rather than trusting that it did.

A build and publish pipeline. Publishing is a defined step that produces output, which means it can be rerun, and a bad publish can be traced to the run that produced it.

Per salesperson inventory sites from a template. Every one of your people gets a site carrying your actual live inventory, which is a very different thing from a business card page. Pair it with the salesperson website and each rep has somewhere to send a shopper that belongs to them.

A public inventory API with key provisioning. Outside consumers can be issued a key and pull structured inventory data. That is syndication in the engineering sense: one authoritative source, many consumers, no file emailed at 2am.

Worth repeating: an inventory feed is not required to use the platform. Brokers and individual salespeople run on it without one. If you have a feed, Inventory Link ingests it and advertises your actual vehicles.

We would rather you learn this here than in a demo.

My Inventory Link is not a marketplace distribution hub. We do not maintain push connectors into every third party automotive marketplace, and we are not going to claim a destination count. If your requirement is a single console that pushes to a long list of external shopping sites and reconciles their individual rejection reports, that is a specific product category and you should evaluate vendors who sell exactly that.

We also do not sell a dealer management system. There is no general ledger, no deal posting to accounting, no vehicle or floorplan accounting, no title and registration work, and no parts or service module. Inventory Link handles vehicle data for merchandising and advertising, not the accounting behind the vehicle.

And we do not do pricing analytics. Market based pricing recommendations, days supply modeling and valuation tooling are separate products with their own data sources. See market based pricing for what that category involves.

Being specific about the boundary is not a weakness. A vendor who claims every adjacent category is a vendor you will be arguing with in month four.

Most dealer inventory still moves as a file on a schedule, and that design causes a specific set of problems that an API does not have.

A scheduled file is stale by definition. Between runs, your published data is a prediction rather than a fact, and the gap is exactly where sold units keep generating calls. A file also has no error channel worth the name. Something rejects a row, a report lands in an inbox nobody reads, and forty units quietly stop appearing somewhere.

A public API with issued keys changes the shape of the problem. Consumers pull current data when they need it rather than receiving a snapshot. Access is per key, so you can see who is consuming what and revoke a key when a relationship ends, which is a genuine control most stores have never had over their own inventory data.

This matters more than it sounds when you change vendors. If your inventory reaches a destination because your website provider pushes it, then changing website providers breaks that destination. If it reaches the destination because the destination pulls from an API you control, the relationship survives your vendor change. Ownership of the distribution point is worth more than the convenience of letting someone else own it.

Three operational details that decide whether syndication helps or embarrasses you.

Cadence. Ask what the maximum delay is between a change in your source and a change at the destination, stated in minutes. Then test it. Change a price on a unit and time how long it takes to appear. Vendors quote the schedule they intend, not the one they run.

Duplicates. Decide what your unique key is, usually VIN plus rooftop, and hold every process to it. Duplicates are worst in groups, where the same unit legitimately moves between locations, and where two rooftops both claim it for a week.

Sold units. The single most common complaint from shoppers. Decide on the removal trigger and make sure the whole chain honors it. Then check it, because the chain is only as fast as its slowest link, and one destination that runs nightly makes the whole system look nightly.

Build a habit of spot checking. Pick five units a week at random, look at them the way a shopper would on a phone, and note what is wrong. Fifteen minutes a week catches problems that reports do not.

Syndication is upstream work. It creates visibility. Visibility creates inquiries. Inquiries are worth nothing until somebody works them, and that is where most of the value in this whole chain is won or lost.

An inquiry generated by a well merchandised unit at 9pm on a Tuesday needs to be answered quickly, by a person, on the channel the shopper used. In practice that means the record has to land in a CRM with the vehicle attached, the source attached, and a follow up cadence already assigned.

In the platform that means the lead inbox, custom source feeds, SMS and MMS with RCS and SMS fallback, a click to call dialer, automations and follow up processes so the second and third touch happen without anyone remembering. Vehicle detail sits on the customer profile across multiple slots, so the unit they asked about, the unit they end up buying and the unit they are trading are one conversation.

Then desking, with loan and lease, a fifty state tax matrix and customer facing deal pages with electronic signature, so the numbers reach the shopper's phone rather than living on a four square on a desk. Dynamic inventory advertising covers the paid side of the same loop.

Ask these and you will know more than most stores learn in a quarter.

Show me the data manager with a real feed loaded, including the rows that failed. What is the maximum delay from source change to published change, in minutes, and can I watch you prove it? What is the unique key, and what happens when the same VIN arrives twice? What is the removal trigger for a sold unit, and how long does removal take at the slowest destination?

Then the ownership questions, which matter most. Who owns the photos? If I leave, do I get the images or just the records? Can I be issued an API key to my own data, and can I revoke keys issued to others? What is the contract length and the notice period?

Finally, ask what happens when it breaks at 7pm on a Friday of a holiday weekend. Not whether it breaks, because everything does. What the path is, who answers, and how fast.

None of this requires a technical background. It requires refusing to move on until the answer is specific. Our pricing is on the pricing page, month to month with no long term contract, and you can contact us if you want to ask whether we fit before sitting through anything.

Does My Inventory Link push my inventory to third party marketplaces?

No. It is not a marketplace distribution hub and we do not claim a destination count. It ingests your feed, stores it, publishes to salesperson inventory sites, and exposes a public inventory API with key provisioning for outside consumers.

Do we need an inventory feed to use LeadLocate?

No. An inventory feed and a DMS integration are both optional, which is why brokers and individual salespeople run on the platform. If you do have a feed, Inventory Link ingests it and advertises your actual vehicles.

How quickly does a sold unit come down?

It depends on your source and the destination, which is exactly why you should ask any vendor for the number in minutes and then test it yourself with a real unit rather than accepting the scheduled interval as the real one.

What is the API useful for?

Any consumer that needs current inventory: a site you build, a partner, an agency, a tool of your own. Keys are issued per consumer and can be revoked, so you keep control of your own data rather than depending on a vendor to push it.

Does LeadLocate price vehicles or calculate days supply?

No. Market based pricing recommendations, valuation and days supply modeling are a separate product category with their own data sources. Inventory Link handles vehicle data for merchandising and advertising.

Can each salesperson have their own inventory page?

Yes. Per salesperson inventory sites are built from a template and carry your live inventory, so a rep has a real destination to send a shopper to instead of a link that belongs to the store.

We will ingest a sample of your inventory, show you what arrived, and show you where the inquiries land afterward. Month to month, no long term contract.