Inventory feedTier 2

OneSource Integration

OneSource and Dashboard inventory reaches Matador over FTP. Vehicle data comes through, but treat VDP links and images as unreliable on this source.

Book a Demo All Integrations

Inventory feedCategory

Tier 2Source tier

VIN, trim, priceVehicle data

What Connects

Exactly What OneSource Syncs

What's live on the integration today, so you can plan your process around it.

Included

Live today on the OneSource integration.

Inventory ingestion over FTP

Why It Matters

What Changes With OneSource Connected

This is the weakest of the inventory routes and worth saying so plainly. The FTP feed delivers enough vehicle data for the AI to answer what is in stock, but the VDP URLs and photo references are not dependable, so replies should not lean on sending a link or an image. If your website provider offers a Tier 1 feed, that is a materially better connection and we would rather use it.

Point the feed

We connect your OneSource feed and map its vehicle fields.

Stay current

New units appear and sold units drop out on their own: nobody maintains a second list.

Answer with real stock

The AI quotes trim, price and availability from your feed, and links to the VDP where the feed carries it.

Straight Answers

Questions Worth Asking

Why are VDP links and photos unreliable here?

The OneSource and Dashboard route is an FTP feed rather than a live API, and the URL and image references it carries are not consistently correct. Vehicle data itself is usable; we simply do not build replies around linking or sending photos on this source.

Should I use this or something else?

If your website provider has a Tier 1 feed, use that: it gives reliable VDP links and photos. OneSource is the right choice when no better feed is available for your setup.

How long does it take to connect?

Most stores connect their stack in under an hour and are live within days. Our team handles the configuration: you need a kickoff call and credentials for the systems you want connected.