A Pre-Import Checklist for Your Vehicle CSV File

A used-car manager exports from the DMS at 4:50 p.m., drops the CSV on the Import page, and leaves. In the morning a rep is answering messages on a row that had no price, a VIN with a letter that cannot exist, and a description field that swallowed the next three columns because someone typed a comma inside an unquoted note. The upload "worked." The file was never ready. A pre-import checklist for your vehicle CSV file is the ten minutes that keep that Friday from becoming a week of cleanup.

This is not a mapping tutorial for a specific DMS. Exports differ. The discipline does not: every CSV that will become Marketplace copy has to survive a human pass while it is still a spreadsheet. PostToMarket accepts bulk CSV and Excel import with import history and a row-level error log. The log catches many bad rows. It cannot invent a trim you left blank or know that stock 4412 is already sold.

Use this checklist before every upload, including the weekly refresh. If your source file is Excel rather than CSV, run the same logic, then see How to Prepare an Excel Inventory Sheet for Bulk Import for workbook-specific traps.

Why a Vehicle CSV File Needs a Pre-Import Checklist

Import is fast. Wrong data on a live listing is slow. The checklist exists because speed without a gate is how aged, mispriced, and duplicate units reach buyers.

What "imported fine" conceals

A file can load and still be commercially wrong:

• Price in the mileage column after a shift.
• Trim that does not match the VIN.
• Units in recon listed as if they are on the front line.
• Duplicate VINs from a previous export plus a manual add.
• Blank photos planned "later," which means a listing with no usable lead image.

The row-level error log is for rows the system cannot accept. The checklist is for rows it can accept that you should not post.

Who owns the pass

On a one-person lot, you own it. On a team, the person who exports is not always the person who posts. Assign the checklist to whoever has authority to delay an upload. A sales associate should not be the last person to eyeball prices. A manager or admin should be able to say "this file does not go up today."

The Pre-Import Checklist for Your Vehicle CSV File

Print this. Run it in order. Do not skip to upload because the lot is busy.

1. File hygiene

• Save a copy with a dated name (lot-inventory-2026-10-30.csv) so import history can be matched to a file you still have.
• Confirm it is actually CSV (or convert deliberately). A file renamed from .xls without an export is not a CSV.
• Open it in a spreadsheet tool, not in Notepad, so you can see columns.
• Check encoding if you see garbled characters in model names. Fix in the spreadsheet, then re-export.
• Remove extra header rows, logos, and "report run by" lines. One header row. Data starts on row two.

2. Column completeness

You need, at minimum, the fields you will advertise and the fields you will operate from:

• VIN
• Year, make, model, trim
• Mileage
• Price (the cash price you will honor, not "call")
• Stock number if you use one internally
• A status or notes column you can use to keep recon and holds out of the posting queue

Optional but useful: exterior color, interior, drivetrain, transmission, engine, body style. Empty optional fields produce thinner AI titles and descriptions. Wrong optional fields produce copy you will have to rewrite.

3. VIN pass

• Every VIN is complete. No truncated last four.
• No letters that do not belong in a VIN.
• No two rows with the same VIN unless you know why (you should almost never).
• Spot-check a handful of VINs against the unit or the window sticker. If the decode in your head does not match the row's make and model, stop the file.

Duplicate VINs in a CSV become duplicate-listing risk on Marketplace. Clean them here. Duplicate listings on Facebook Marketplace covers the posting-side cost; the cheapest fix is still a deleted row.

4. Price and mileage pass

• No blank prices.
• No "Call," "OTO," or "See dealer."
• No extra zeros from a copy-paste (999500 instead of 9950).
• Mileage is a number, not "TMU," "exempt," or "99,999+".
• Mileage is plausible for the year. A 2024 with 280,000 miles might be real; it should not be unnoticed.
• Price and mileage are not swapped. Scan a sorted column for outliers.

5. Status pass

Before import, tag or remove rows that should not post:

• Sold pending delivery
• On hold / deposit
• In recon or at the body shop
• Wholesale units not for retail
• Auction purchases not yet on the lot

PostToMarket inventory can hold them as drafts after import. The checklist's job is to make sure you know which rows those are. If the CSV has no status column, add one. A manager cannot filter what the file does not mark.

6. Text fields that break CSV

Descriptions, option lists, and dealer notes are where CSVs go to die.

• Commas inside unquoted fields shift every later column.
• Line breaks inside a cell split one vehicle into two rows.
• All-caps DMS dumps will flow into AI input and then into listings unless you plan an edit pass.
• Internal codes (pack codes, recon RO numbers) do not belong in a public description. Keep them in a notes column you will not advertise, or strip them.

If a description field is routinely dirty, consider leaving it empty in the CSV and letting AI draft from specs, then editing. Garbage in the description column is worse than no description column.

7. Final scan

When the table is clean, upload. Then open import history and read the row-level error log even if the upload looks successful. The checklist and the log are two gates, not one.

After the Checklist: Import Without Trusting the First Pass

A clean CSV is necessary. It is not the end of the workflow.

Read the error log immediately

Fix rows in the source file, not by improvising in a posting session. Re-export. Keep the dated copy. Import history and row-level error logs is the companion article for what to do when the log is not empty.

Import into inventory, then decide what posts

Unlimited vehicles in inventory means the CSV can be the whole lot. The posting queue should be the ready subset. AI-generated titles and descriptions will draft from the specs you just imported; edit them before anything is queued. Capture from auction sites is a separate intake path — do not mix an unvetted capture and a dirty CSV in the same "just get it up" hour.

Make the checklist a recurring standard

The first import of the month is when people are careful. The Thursday refresh is when they are not. Same checklist every time. If a column keeps failing, fix the export, not the ritual. If a person keeps uploading without the pass, that is a role problem, not a software problem.

How PostToMarket Automates This

A pre-import checklist fails in shops that treat upload as the finish line. The product's import tools exist so the checklist has a second layer: a stored history of the file and a row-level view of what could not be accepted.

• Bulk CSV and Excel import from the file you just cleaned.
• Import history so you can see which upload created which units, and when.
• Row-level error log so a bad VIN or empty price is a specific row, not a vague failure.
• Unlimited inventory with statuses (draft, posting, posted, sold, failed) so flagged recon and hold units can sit without going to Marketplace.
• AI titles and descriptions generated from the specs in the file, editable before posting, which is why those specs have to be right in the CSV.
• Mark as sold and archive after import if a sold row still slipped through.

The checklist is still human. Automation catches the rows that break. It does not replace walking a unit that the spreadsheet says is a 2019 when the lot says 2016.

Upload Cleaner Files Starting With Your Next Trial

Every bad CSV row you catch in a spreadsheet is a Messenger apology you do not have to write. Run the pre-import checklist, then let import history and the error log confirm the file before a single vehicle is queued.

On Starter, $59 per month covers a solo seller or independent lot with one login and unlimited inventory, including bulk import. Dealership is $299 per month for up to 13 logins when a manager should own the checklist and associates should only post what they are assigned. Both plans start with a 10-day free trial.

Start your 10-day free trial and check out through secure Stripe checkout. Bring one real CSV, run this list, and see the error log on your own file. Cancel anytime. If an import question needs a person, write info@posttomarket.com.