Edit or Re-Import? A Decision Guide for Wrong Vehicle Records

The weekly DMS export lands, someone uploads it, and by mid-morning three people are arguing about the same Silverado. The trim is wrong. Mileage looks like a copy-paste from last month. Two rows share a VIN. A rep has already queued the bad record. The internet director's instinct is "just fix it in the dashboard." The office manager's instinct is "throw the file at it again." Both instincts are right in some cases and expensive in others.

Edit or re-import is a decision guide for wrong vehicle records, not a preference about clicking. One bad field on one unit is an edit. A systematically wrong file is a re-import. A unit that is already live is neither — it is a live-listing correction plus an inventory correction. Mixing those three paths is how you get duplicate drafts, posted listings that disagree with the dashboard, and a floor that stops trusting the grid.

This article is for the person who owns Import, usually an admin or manager, and for used-car managers who get pulled into the argument. It stays on workflow: CSV and Excel import, import history, row-level errors, statuses, and when to leave a live listing alone until the record is honest.

Edit or Re-Import: Separate One Wrong Record From a Wrong File

Start by naming the failure. If you cannot name it, you will pick the slower path by default.

Failure types that should drive the choice

• Single-field error on one VIN. Wrong price, stale mileage, misspelled trim, missing stock number.
• Identity error on one VIN. The photos or description belong to a different car, or the VIN itself is wrong.
• Row-level import errors on a known upload. The error log already told you which rows failed and why.
• Systematic file error. Every row has last week's prices, every 4WD is labeled FWD, or the mileage column shifted during the Excel export.
• Duplicate identity. Two inventory rows for one VIN, or one row that merged two stock numbers.

Edits scale linearly with people. Re-imports scale with file quality. If fixing the mistake requires touching more than a handful of units, you are in file territory even if each individual error looks small.

Status changes the decision

A draft is the cheapest place to be wrong. Edit or replace it before anyone queues it.

A unit in posting is in motion. Do not start a re-import war while the extension is submitting that VIN. Wait for posted or failed.

A posted unit is live. Changing the inventory record does not, by itself, rewrite what buyers already see. Treat the live listing as a separate correction after the record is right.

A sold unit should not be re-imported as if it were fresh supply. Mark sold and archive. If the file keeps resurrecting sold cars, the export is the problem.

A failed unit needs a cause. If the cause is bad data, fix the record (edit or re-import) before you retry. Retrying a wrong VIN just fails it again.

When to Edit the Record in Place

Edit when the identity is correct and the blast radius is small.

Edit these without touching the file

• One price the desk marked down after the export was built.
• Mileage on a long-stocked unit that has been driven since the last file.
• A trim spelling that does not match the window sticker.
• A description you are tightening for one car after reviewing AI copy.
• A photo set you are replacing because the lead image is weak.

These are unit-level facts. Re-uploading a 200-row spreadsheet to change one Camry's price is how you reintroduce last week's mistakes on units you already cleaned.

Do not "edit" an identity problem by overwriting fields

If the VIN on the row is not the car in the photos, you do not have a typo. You have a wrong record. Creating a correct draft (or capturing the right unit) and retiring the wrong one is cleaner than morphing a Silverado row into a Tahoe row field by field. People will keep trusting the old stock number.

Guardrails for editors

• Name who is allowed to edit live operational fields. Random floor edits on price without the desk's number recreate the original mess.
• After an edit, run a last look before the unit is posted. Specs, price, photos, copy, availability.
• If the unit is already in a queue, tell the owner of that queue. Silent edits on a queued record produce "I posted what I saw at 9 a.m." conversations at 2 p.m.

When to Re-Import Instead of Editing

Re-import when the source file is the system of record and the dashboard is a mirror that went stale or warped.

Re-import these

• A column shift that put mileage in the price field across the sheet.
• A full-lot price file that is a day behind a desk-wide markdown.
• An export that used internal trim codes nobody should advertise.
• A large set of row-level errors that are faster to fix in Excel than in one-off dashboard clicks.
• A store that never should have been editing in two places: the DMS and the dashboard both claimed to be source of truth.

Re-import is not "upload and hope." Prepare the sheet, then treat the new upload as a controlled event. Use the pre-import checklist for your vehicle CSV file and how to prepare an Excel inventory sheet for bulk import before you send the file through again.

After the upload, read import history like an audit log

Bulk CSV and Excel import in PostToMarket keeps import history and a row-level error log. That log is the decision record:

1. Open import history for the upload you just ran.
2. Read error rows. Fix those rows in the file or skip them with a written reason.
3. Confirm new drafts match the VINs you intended to add or refresh.
4. Confirm you did not create a second draft for a VIN that was already posted.

If the error log is long, you are not done because the file "went through." See fixing row-level import errors and re-uploading a corrected inventory file.

Re-import does not replace queue discipline

A corrected file can drop a pile of drafts on the floor. Someone still has to queue the units that are actually available, in a sensible order, without re-posting cars that are already live. Unlimited inventory is not a reason to treat every new row as a new Marketplace listing.

An Edit or Re-Import Decision Guide You Can Tape Next to the Desk

Use this when two people disagree in the hallway.

A five-question test

Ask these in order. Stop at the first "re-import."

1. Is only one VIN affected?
2. Is the VIN itself correct?
3. Can a trained person fix it in under two minutes?
4. Will the next scheduled export overwrite this fix anyway?
5. Is the unit still a draft?

If (1)–(3) are yes, (4) is no, and (5) is yes, edit. If (4) is yes — the DMS will blow away dashboard edits tonight — fix the source and re-import on the next clean file instead of fighting the export.

If you cannot answer (4), you do not have an import SOP. Get one before you do either path at volume.

How PostToMarket Automates This

Wrong vehicle records become a floor fight when nobody can see how the data arrived or what state the unit is in. This decision guide depends on those two facts being visible.

• Bulk CSV and Excel import with import history and a row-level error log, so "the file is the problem" is evidence, not a hunch.
• Capture from auction and wholesale sites for units that should never have been forced through a bad weekly export.
• Inventory statuses (draft, posting, posted, sold, failed) so you do not edit, re-import, and retry as if those states were the same.
• Mark as sold and archive when the right move is to stop advertising, not to massage the row.
• AI titles and descriptions generated from specs, which you re-check after an identity or trim edit, because copy follows the record.
• Queues that still need a human owner after a re-import, so corrected drafts do not sit unposted and duplicate posted units do not get queued again.

The product does not choose edit vs. re-import for you. It makes the cheap path obvious.

Pick a Path on Paper, Then Run It on the Trial File

Edit or re-import is a decision guide for wrong vehicle records that only works if the store picks one path per failure type and writes it down. Use edits for small, identity-correct drafts. Use a corrected upload when the sheet is the system of record. Keep sold cars out of both paths.

PostToMarket holds unlimited vehicles, logs every import, and keeps statuses honest while you clean the data. Starter at $59 per month is enough for a one-person lot that still needs that discipline. Dealership at $299 per month covers up to 13 logins so a manager can own Import while reps stay out of the file.

Start your 10-day free trial with secure Stripe checkout. Import one real export, read the error log, and practice this decision table on the actual mess in that file. Cancel anytime.