Using Import History as an Audit Trail for Inventory Uploads

The general manager is on the lot with a printout. The Silverado on Marketplace says $21,995. The deal jacket and the whiteboard say $23,495. Nobody remembers whether the price moved in a Tuesday export, a Thursday "repair" file, or a rep typing in a hurry. Without an audit trail, that conversation is folklore. Using import history as an audit trail for inventory uploads is how a used-car manager answers "where did this number come from?" with a file name, a time, and a row — not a shrug.

PostToMarket stores bulk CSV and Excel imports in import history and records row-level errors. That history is not a legal archive of Meta activity, and it is not a substitute for your DMS. It is the operational record of what your team brought into posting inventory and when. This article shows how to read it like a deal jacket: reconstruction, exception review, and a weekly GM-ready summary.

This is operational guidance, not legal advice. If you need a retention policy for regulators, counsel, or a franchise audit, confirm that separately. Import history helps you run the store. It does not replace your books.

What an Import-History Audit Trail Can (and Cannot) Prove

Be precise about the artifact. Over-claiming it makes it useless in a meeting.

What it is good for

• Which upload created or attempted a set of rows, and when.
• Which rows failed and therefore never should have been queued from that file.
• Sequence: last week's full file vs. this week's repair file vs. a one-off arrival sheet.
• Pattern: the same VIN erroring every Wednesday, which is an export problem, not a posting problem.
• Accountability on a team: which login performed the import (admin or manager, if you have assigned ownership correctly).

What it is not

• Proof of what Facebook showed a buyer. Marketplace distribution is separate. PostToMarket is not affiliated with, endorsed by, or sponsored by Meta.
• A complete vehicle history report or title chain.
• A cost-accounting ledger. Do not import pack and invoice into a posting tool and expect it to become your accounting system.
• A guarantee that the data was true — only that it was the data in the file at upload time.

If a rep edited a price in inventory after import, history tells you the file's number, not every later click. Pair history with inventory status and, on Dealership teams, posting analytics by rep and source when you need the "who posted it" half of the story. Posting analytics by rep and source covers that coaching view.

Using Import History as an Audit Trail: A Reconstruction Procedure

When a VIN is in dispute, do not start in Messenger. Start in history.

Reconstruct a single vehicle

1. Identify the VIN and stock number.
2. Open import history. Find uploads that could have included that VIN (dated files, repair files, arrival files).
3. Open the matching source file from disk. If the file is gone, your trail is already broken; restore naming discipline before the next import.
4. Read the row-level error log for those uploads. Did this VIN fail, succeed, or never appear?
5. Open the inventory record. Compare status (draft, posting, posted, sold, failed) and current fields to the file.
6. Check queues: is it claimed, posted, or archived?

Write the reconstruction in four lines. Example of the form (illustrative): "VIN entered in Monday full file as $23,495. Not in Tuesday error log. Thursday repair file not applicable. Inventory now $21,995 — changed after import; not an upload event." That last sentence is the one that stops a false accusation of "the import tool changed our prices."

Reconstruct a week

For a weekly operating review:

• List every import event in the week (full, repair, arrivals).
• Note error counts. Rising counts mean the export is drifting.
• Note sold units that still appeared in a retail file (process failure upstream).
• Note duplicate VIN attempts.

This pairs with A Weekly Inventory Import Routine for Small Lots. The routine produces the events. History is how you inspect them.

Reconstruct a bad batch

When many listings look wrong in the same way (all mileages too low, all trims blank):

• History will show a single upload dominating that window.
• The error log may be empty if the values were legal but wrong. Blank logs do not mean the file was true. They mean rows were accepted.
• Pull the dated file. Look for a shifted column. That is an audit finding: "accepted rows, bad structure," which is different from "rejected rows."

Accepted-but-wrong is why a human checklist still sits in front of upload. History cannot see a column shift that still parses as numbers.

Operating Rules That Make the Trail Usable

An audit trail is only as good as the habits around it.

File naming and retention on your side

Import history will not store a human-readable copy of every spreadsheet in your filing cabinet. Keep dated upload files for a period that matches how long you argue about prices (many lots keep at least the current month). Name them so a GM can find retail-2026-10-28.xlsx without Slack archaeology.

One import owner

On Dealership, admin or manager imports. Sales reps self-queue; associates receive assignments. If four reps can upload, your trail still exists but the story becomes "why did four people think they owned the lot file?" Roles are explained in the team-roles article; the audit implication is simple: fewer uploaders, cleaner history.

Never use a second upload as a silent rewrite of history

Re-uploading a full lot to "fix one VIN" muddies the trail and risks duplicates. Prefer repair-only files. Record in the file name that it is a repair. Future you will thank present you.

Tie sold-unit events to the trail

If a car sold Tuesday and the Wednesday file still contains it, history plus the file is evidence of a DMS or export lag. Mark sold and archive in inventory regardless. The audit question is "why was it in the file," not "why did we keep advertising it after we knew."

A GM one-pager you can produce in ten minutes

No percentages. No awards. Just a table that survives a tense meeting.

Training the floor

Reps do not need to love Import. They need to know:

• Do not upload "a copy I cleaned" without telling the owner.
• Do not relist a VIN to fix a price; change the record or ask for a repair file.
• If a listing number looks impossible, say so before the customer arrives — and bring the stock number, not a vibe.

How PostToMarket Automates This

Using import history as an audit trail only works if uploads are stored as events and failures are stored as rows. That is the specific problem this workflow solves: inventory arguments that otherwise devolve into memory.

• Bulk CSV and Excel import as the events being audited.
• Import history as the timeline of those events.
• Row-level error log as the exception list.
• Inventory statuses (draft, posting, posted, sold, failed) as the current-state counterpart to the file.
• Mark as sold and archive so the trail of "still in the export" does not keep a sold unit in the posting queue.
• Team roles, queues, and team queue view so you can see who claimed a unit after it imported.
• Team analytics by rep and source when you need posting activity, not just upload activity.
• Unlimited inventory so old records remain inspectable instead of disappearing when a new file arrives.

There is no claim of a DMS integration writing this trail for you. You upload; history records the upload.

Put Inventory Arguments on a Paper Trail This Trial

Price fights, trim fights, and "who posted the $1 car" fights get shorter when import history is a habit, not a screen you open after something explodes. Use the 10-day free trial to import twice, keep both files, and practice reconstructing one VIN from history to the lot.

Starter at $59 per month gives a solo seller one login and the same import history a larger store uses. Dealership at $299 per month adds up to 13 logins so a manager can own uploads while the floor works from queues. Checkout is Stripe. Cancel anytime.

Start your 10-day free trial and run one week of dated files as if a GM will ask. When they do, you will have more than a guess. Support: info@posttomarket.com.