Import History and Row-Level Error Logs: Fix Bad Rows Before They Post

A used-car manager uploads a 140-row spreadsheet on Thursday night. By Friday noon, a customer messages about a "2019 Silverado" that is actually a 2016 with 40,000 more miles than the listing says. The price field was shifted one column to the right in rows 61 through 88. Nobody noticed, because the file "imported fine." That phrase is the problem. A file can import without complaint and still carry a hundred small lies into your public inventory.

Import history and row-level error logs exist to stop that failure at the only point where it is cheap to fix: before the data becomes a listing. This article explains what an import history and a row-level error log do for a dealership, how to read them, and how to build an upload routine in which bad rows get repaired in a spreadsheet and not in front of customers.

If your inventory arrives as a DMS export, a wholesaler's sheet or a lot manager's hand-built Excel file, the discipline below applies to you. It does not depend on any one DMS. It depends on treating every upload as a controlled event with a record.

Why Bad Rows Are Cheaper to Fix Before They Post

A bad row costs almost nothing in a spreadsheet and a lot on Facebook. Understanding the cost curve explains why a row-level error log is worth the extra five minutes per upload.

The cost curve of a data error

• In the file: edit one cell. Seconds.
• In the dashboard before posting: correct one record. A minute or two.
• After posting: edit the live listing, field wrong buyers, apologize on Messenger, and possibly correct a listing that has already been seen.
• After a sale conversation: you have a trust problem, not a data problem.

The errors that appear again and again

Dealership imports fail in familiar ways. Learn the pattern and you can predict where the log will point.

• VIN problems: truncated, wrong length, letters that cannot appear in a VIN, or a VIN that decodes to a different trim than the one in the row.
• Price problems: blank, text such as "Call," a stray currency symbol or comma format that does not parse, or a price that belongs to a previous unit.
• Mileage problems: blank, "TMU," or a number with a unit suffix.
• Status problems: units on hold, in recon or pending delivery that should not be posted yet.
• Shifted columns: one extra comma in a description field pushes every later column to the right.
• Duplicates: the same VIN twice, once from the DMS and once from a manual add.

Duplicates deserve special attention because repeated listings are a standing risk on Marketplace. Read Duplicate Listings on Facebook Marketplace: What Car Dealers Must Avoid for the posting-side consequences, then use the import log to prevent them at the source.

How Import History and Row-Level Errors Work in Practice

PostToMarket supports bulk CSV and Excel import. Each upload is kept in an import history, so the team has a record of what was brought in and when. When rows cannot be accepted, the row-level error log tells you which rows had a problem, instead of rejecting the whole file with a vague message.

Import history as an audit trail

Think of import history the way you think of a deal jacket: a record that answers "what happened here?" later. It lets a manager answer practical questions without guessing.

• Which file did these units come from?
• Was this vehicle imported once or twice?
• Did the Tuesday upload fix the rows that failed on Monday?
• How often is the store actually refreshing its inventory?

Without a history, every upload is a blank slate and every mistake is a mystery. With one, you can trace a bad listing back to the file that created it.

Row-level errors instead of all-or-nothing failures

A flat "import failed" message is useless on a 300-row file. A row-level log changes the work from detective work to a to-do list: row 47, row 112, row 113. You open the original sheet, repair those rows and run the correction. You do not hunt through the whole file for the one typo.

The log only tells you what the system could detect. It cannot tell you that a legal-looking price is simply the wrong price for that car, or that a plausible mileage belongs to a different unit. Treat the error log as a safety net under your own review, not a replacement for it.

A realistic example

Consider a lot with 60 units and a weekly Monday upload. In one week, the log flags five rows: two blank prices on units newly acquired from auction, one VIN with a missing character, one row with a mileage value of text, and one duplicate of a unit already in inventory. The manager fixes the four data problems in the sheet and deletes the duplicate row. Total time: about ten minutes. The same five issues found after posting would have cost five public listings, five corrections and a few confused messages.

An Upload Routine That Keeps Bad Rows Out of the Queue

A good routine is short enough that people actually follow it. Use this sequence every time.

Before the upload

1. Export fresh. Never reuse last week's file; stale prices are the most common silent error.
2. Remove units that should not be advertised. Take out recon, hold and sold-pending-delivery vehicles.
3. Sort by stock number or VIN so duplicates sit next to each other.
4. Scan the high-risk columns: VIN, price, mileage, year, make, model and trim.
5. Check for shifted columns by scrolling to the last column and confirming it still holds the value you expect.

During the upload

1. Run the import.
2. Read the result summary, then open the row-level error log.
3. Copy the failing row numbers into a note so you can work through them in order.

After the upload

1. Fix the failed rows in the spreadsheet, not by memory.
2. Re-run the corrected rows and confirm the log is clear.
3. Spot-check five imported vehicles against the physical car or the deal desk record.
4. Review the AI-generated title and description before anything is queued.
5. Only then add units to a queue.

For the broader preparation that sits upstream of this routine, How to Bulk Import Vehicle Inventory From CSV or Excel Without Errors walks through file preparation in detail.

A short pre-upload checklist

• File exported today.
• Held, recon and pending units removed.
• VINs 17 characters and unique.
• Every row has a price and mileage.
• No obviously shifted columns.
• Someone other than the person who exported has glanced at the top and bottom of the file.

Reading the Log Like a Manager, Not a Data Clerk

The log is useful to the person doing the upload, and it is more useful to the person responsible for the store's online presence.

Look for patterns, not just rows

If the same error shows up in every upload, the problem is upstream. Repeated blank prices on auction units point to a process gap in how new inventory is entered. Repeated VIN problems may mean a particular lot manager is typing them by hand. Fix the source once and the log gets shorter every week.

Assign accountability for the clean-up

Decide who owns the corrections. In a small lot, that is the person who runs the import. In a larger store, the internet director owns the log and the used-car manager owns the fix when the error is a pricing or condition issue. Unowned errors stay in the log forever and quietly turn into stale inventory.

Know when to stop and ask

Some problems are not row-level. If most rows fail, the likely cause is a structural issue with the file: the wrong sheet, a header row in the wrong place, or a format your DMS changed in a software update. Stop, inspect the file and re-export. If you still cannot find the cause, contact support at info@posttomarket.com.

How PostToMarket Automates This

Importing is the first step in a chain that ends with a listing on Facebook. PostToMarket automates the steps around the upload so a clean record stays clean all the way through.

From upload to a Marketplace-ready record

• Bulk CSV and Excel import with unlimited vehicles in inventory on every plan.
• Import history that records each upload.
• A row-level error log so you can fix exactly the rows that need fixing.
• Capture from auction and wholesale sites so some units never go through a spreadsheet at all.

From record to listing

• AI-generated titles and descriptions built from each vehicle's specs and editable before posting, which reduces the raw-DMS-dump look that weakens listings.
• Facebook photo picker to choose listing photos.
• Inventory statuses of draft, posting, posted, sold and failed, so everyone sees the real state of every unit.
• Posting through the Chrome extension, one vehicle at a time, with human-like delays and server-enforced daily limits.

PostToMarket is an independent tool and is not affiliated with, endorsed by or sponsored by Meta. It reduces the operational mistakes that commonly cause listing problems; it cannot guarantee that Facebook will distribute every listing or that a row you consider correct will perform.

Make Every Upload a Clean One: Try It Free for 10 Days

Every dealership has a story about the spreadsheet that went wrong. The point of an import history and a row-level error log is that the next one is a ten-minute fix, not a public correction.

Test it on your own inventory with the 10-day free trial, set up through secure Stripe checkout, and cancel anytime. The Starter plan is $59 per month for a solo seller or independent lot with 1 login, and the Dealership plan is $299 per month for a team with up to 13 logins. Both include unlimited vehicles, bulk import and the row-level error log.

Start your 10-day free trial, upload this week's export and see how many bad rows you catch before a single one reaches a customer. Fixing bad rows before they post is the cheapest quality control your store will ever buy.