Your DMS export, turned into a feed for every channel
Every DMS and inventory tool can export a file. None of them export it the way Google, Meta and the marketplaces want it. MiFeed sits between the two: it reads the file you already have and publishes the files each channel needs.
If your DMS or inventory management tool can publish an inventory file to a URL, MiFeed can read it. Several files per rooftop — new and used from different systems, for example — are merged into one inventory. Files are fetched on the server, so hosts that block browsers still work.
From accounting columns to advertising fields
Map columns from dropdowns with sample values beside each one. Translate codes with value maps built from the values actually in your file. Build titles, clean descriptions and pick photos with a formula language that has vehicle helpers like VIN check-digit validation and model-year decoding.
Output in the format each channel reads
Every feed can be served as CSV, TSV, JSON or XML from the same setup, at its own URL protected by its own token.
How it works
Live in an afternoon.
STEP 01
Connect your export
Paste the URL of the inventory file your DMS or inventory tool already publishes. MiFeed reads it server-side and re-reads it every night.
STEP 02
Start from a template
Pick the channel template, map any columns it could not match, and preview the output on your real vehicles.
STEP 03
Publish one URL
Give the channel your feed URL. It always serves today’s lot, health-checked, with every delivery logged.
FAQ
Common questions
Any that can publish an inventory export as CSV, TSV or pipe-delimited text at a URL. That covers the major dealer management systems and most inventory tools. If yours only emails a file, tell us — Managed customers get help setting up a published export.
Inventory files up to 60 MB are read by default, which is far more than a typical rooftop’s export.
No. MiFeed only reads the export file’s URL. It never connects to your DMS directly.