Connecting dealer stock feeds to an automotive marketplace

There are two distinct projects. Define the direction first: it determines who grants access, which requirements apply and what the integration needs to deliver.

Before building the connection, establish which dealers will participate and what their systems can supply.

Confirm permission to use the vehicle information, photographs and dealer details. Agree whether the marketplace hosts full listings or sends buyers to the original vehicle page, and where enquiries should go.

The available route might be an API or a structured file export. Its suitability depends on the provider and the permissions attached to the data.

Starting with one confirmed source and a small set of participating dealers gives the project real records to work against. Additional sources can then be assessed against the same listing requirements.

A marketplace feed is an ongoing connection.

Define how new vehicles appear, how changes update existing listings and how sold or removed vehicles leave available-stock results. Sources may supply a complete inventory snapshot or only changed records; those require different removal rules.

A failed or incomplete import should not be mistaken for a complete inventory showing no stock. The process needs checks before it applies changes.

Agree freshness expectations with participating dealers too. Buyers need a marketplace that represents the available stock, and dealers need to understand how their own update workflow affects what appears.

The same vehicle may arrive through more than one route. A dealer might use multiple distribution services, or a listing might be present in both a direct feed and an intermediary export.

Decide which source owns the listing and how possible duplicates are reviewed. A reliable vehicle identifier can help where it is available and permitted, but the process still needs rules for missing or conflicting records.

Dealer attribution should remain clear throughout the browsing and enquiry journey. Buyers should know who is offering the vehicle, where it is located and who will respond.

An aggregator that sends visitors to dealer websites needs reliable destination links.

A marketplace that hosts full vehicle pages needs suitable imagery, specifications, dealer information and an enquiry route. A platform offering reservations or payments has a wider scope again.

Choose the model before deciding the import requirements. A feed that supplies enough information for a linked search result may not support a complete hosted vehicle page.

Registration or VIN data can be considered separately where it improves the experience. Access, coverage and permitted use need their own review; lookup data should not be assumed to exist in every inventory source.