Stop Typing VINs Twice: Connecting Your DMS to Your Recon Board
Connect your DMS to your recon board with a daily inventory file: your DMS provider schedules an export to an SFTP address, and the recon software imports it. The VIN is the only required field. Ask your provider five questions before you start, and check the sync log weekly so a feed that stops doesn't go unnoticed.
A truck comes off the trailer at 7:30. Your buyer enters it in the DMS: VIN, mileage, trim, what you paid. An hour later your recon manager enters the same truck again, on a whiteboard or a spreadsheet or a recon board. Two people, one vehicle, the same fourteen fields typed twice.
Most independent dealers run this way, and it costs more than the ten minutes it looks like it costs.
What double entry actually breaks
A mistyped VIN does not announce itself. It fails quietly, at the moment you need it most:
- Recall checks return nothing. The NHTSA lookup needs all seventeen characters. One transposed digit and the vehicle comes back clean when it is not.
- Pricing tools return the wrong car. A bad VIN pulls comps for a different trim, and you price against the wrong market.
- The clock starts late. Your recon board thinks the truck arrived when somebody typed it in, not when it hit the lot. Every cycle-time number you report is short by that gap.
- Two lists disagree. The DMS says 61 units, the board says 58, and now your manager spends Friday afternoon reconciling instead of moving cars.
The fix is not a better data-entry habit. Your DMS already holds everything your recon board needs. The work is getting it to hand that over on a schedule.
How does DMS inventory get into a recon board?
One of three ways: your DMS pushes a file to an SFTP address, you upload a file yourself, or the software reads your DMS's API.
Your DMS pushes a file. This covers almost every DMS on the market, including the ones with no API at all. You get an SFTP address, a username and a password. Your DMS provider schedules a daily inventory export to that address. Frazer and Autosoft both do this today, and any DMS that can export a report to a folder can do it.
You upload a file yourself. A CSV export, dragged in once a day. Worth doing on week one while the automated feed gets scheduled, and worth keeping as a fallback.
Your DMS offers an API. Fewer providers do, and the ones that do vary. Dominion runs on SecureVUE 2 with OAuth and paginated XML, for example. When an API exists it is the cleanest option, because sold and status changes come through without waiting for tomorrow's file.
For most independent dealers the pushed file wins. It needs no developer on either side and your DMS provider has done it a hundred times.
Five questions for your DMS provider
Email these five and the answers tell you whether this takes a day or a month:
- Can you schedule a daily inventory export over SFTP? Routine request. Say daily, and name the hour you want it.
- What format, and can it be CSV? Comma, tab or pipe delimited all work fine. XML is where tools differ, so ask before you assume.
- Does the export include photo URLs, and are they publicly reachable? Links behind a dealer login or links that expire after an hour are the single most common reason photos never show up.
- When a unit sells, does it drop off the file or come back with a status flag? This decides whether your board can retire sold cars on its own.
- Who has to authorize this? Sometimes you. Sometimes a regional rep. Find out on day one.
What does the inventory file have to contain?
Less than dealers expect: only the VIN is required.
VIN is the only hard requirement. Rows without one get skipped, because there is nothing to match them against.
Column headers do not need to match anything. Good recon software reads your DMS's own names. "VehStockNo", "Stock #" and "stock_number" all land in the same place. If your DMS calls mileage "Odometer" and yours calls it "Miles", that is a mapping problem the software solves once and remembers.
Dated filenames are fine. "VehInvDetail_20260912.csv" works as well as "inventory.csv". The newest file in the folder wins.
A header row worth asking for, if your provider lets you choose: vin, year, make, model, trim, mileage, price, exterior_color, images. Photo links go in one cell, separated by a pipe, best photo first.
Why do DMS inventory feeds break?
Most breaks come from four things: photo links that need a login, an export format that changed, sold units left in the file, and a feed that quietly stops arriving.
Photos that need a login. The feed imports, the vehicles appear, and every card is blank. Ask for public URLs before you go live, not after.
A format that changed and nobody said so. Your DMS updates its export, a column moves, and yesterday's mapping reads garbage. Software that regenerates its own column mapping when a file stops parsing handles this without a phone call. Software that does not will hand you a board full of "Unknown / Unknown".
Sold units that never leave. If your DMS keeps sold vehicles in the export with no status flag, your board fills up with cars that left the lot in July. Question four above is the one that catches this.
Silence. A feed that stops arriving looks exactly like a week with no acquisitions. Whatever you connect, find out where the sync log lives and glance at it on Mondays.
What it looks like when it works
Your buyer enters a truck in the DMS at 8am. Overnight, the export runs. By the time your recon manager opens the board with coffee, the truck is there with its recall status checked and its market price attached, sitting in the first step of your process with the clock already running.
Nobody typed it twice. Nobody reconciled two lists. Your cycle-time numbers start from when the vehicle actually arrived, which means they finally describe your shop instead of your paperwork.
That is the whole point of connecting the two systems. Not the ten minutes of typing you save, though you save that too. It is that every number downstream starts telling you the truth.
Recon imports from any DMS that can export inventory, plus AutoTrader and CarGurus feeds, and reads your DMS's own column names rather than making you rename them. If you want to know whether your specific DMS will play nicely, book a walkthrough and bring a sample export. Fifteen minutes with a real file answers more than any feature list.