Archiving Old Records: What to Keep and What to Clear
Old inventory records clog queues and hide live work. A keep-or-clear framework for archiving sold, wholesale, duplicate, and training rows without losing the history you still need.
Open Inventory on a store that has been posting for six months and you can usually tell, in ten seconds, whether anyone archives. The list is a mix of live retail units, cars that sold in March, wholesale flips that never needed a Marketplace listing, duplicate VINs from a messy import, and three rows named "TEST." Reps scroll past the noise. Managers stop trusting counts. New associates queue the wrong car because the stock number they heard on the lot matches a sold record still sitting in the working list.
Archiving is not housekeeping for its own sake. It is how you keep the working inventory identical to the cars a buyer can actually see and buy. Archiving old records is the decision of what to keep in the active list, what to mark sold and archive, and what was never inventory in the first place.
This article gives used-car managers a keep-or-clear framework. It is operational, not a records-retention policy for accounting or compliance. Your DMS remains the system of record for deals. PostToMarket inventory is the system of record for what you intend to advertise. When those two drift, archiving is how you pull them back together.
Why Archiving Old Records Changes How the Floor Uses Inventory
People treat a long list as "complete." A short, current list as "maybe missing something." The opposite is true for posting tools. Completeness belongs in the archive of what happened. Currency belongs on the screen people queue from.
What stale records cost you this week
- A sales rep self-queues a unit that already sold, then spends twenty minutes building a listing for a car that is gone.
- A manager reads posted count and thinks coverage is fine, because sold-but-unarchived rows still look like activity.
- Duplicate VINs make the team queue view harder to read: two claims, one vehicle.
- Failed posts on cars that left last month keep appearing in exception lists, training the team to ignore failed as a status.
Separate "we sold it" from "delete it"
Marking a unit sold and archiving it is not the same as pretending it never existed. You still want a trail of what was imported, captured, and posted. You do not want that trail in the same view as this week's retail list. If your instinct is "we might need that row," archive it. Do not leave it in the working set as a souvenir.
Same-day sold-unit hygiene on Marketplace is covered in why sold units must leave Marketplace the same day. This article is the inventory-side companion: what to do with the record after the listing should no longer be live.
What to Keep in Working Inventory
Keep a record in the active inventory when a person on the floor might still need to post it, edit it, or answer a buyer about it as an available vehicle.
Keep: retail units you still own
Anything with a path to a retail buyer stays. Status can be draft, posting, posted, or failed. Failed stays until it is fixed or you decide the unit will not be advertised. Do not archive a failed live unit just to clean the screen; that hides a car you still need to sell.
Keep: legitimate holds
In recon, in transit, waiting on title, waiting on photos. These belong in draft (or whatever status you use for not-yet-posted) with an owner. They are old only if the hold has no date. Age alone is not a reason to archive a car that is still on your lot.
Keep: a posted unit with an active conversation
If a listing is live and a buyer is in thread, do not archive from under the rep. Mark sold only when the deal is actually done, then archive as part of that same motion.
Keep: the single surviving row after a duplicate cleanup
When two rows share a VIN, you keep one. That survivor stays in working inventory until the car sells. The extra row is what you clear.
What to Clear: A Keep-or-Clear Table
Use this table in a monthly archive pass, and use the sold column every day.
| Record type | Keep in working inventory? | Action |
|---|---|---|
| Sold retail, listing still up or row still active | No | Mark sold and archive the same day |
| Sold wholesale / flipped / returned to auction | No | Mark sold (or equivalent exit) and archive |
| Duplicate VIN of a live unit | No | Clear the extra row; keep the accurate one |
| Import test rows, dummy VINs, training cars | No | Archive or remove from working inventory after training |
| Failed post on a unit you still own | Yes | Fix and retry; do not archive the problem away |
| Draft, still owned, photos or price pending | Yes | Leave it; put it on the draft review |
| Aged posted unit, still in stock | Yes | Refresh the listing; archiving would hide a live car |
| Deal fell through, unit returned to stock | Yes | Do not leave it sold; return it to draft or posted as appropriate |
Sold retail
This is the default clear. The car is gone. The listing should not collect messages. The inventory row should not be queueable. Mark as sold and archive from inventory or from the queue, whichever screen the person is on when they hear the deal is done.
Wholesale and auction exits
Independent lots and BHPH stores move units off the line without a retail Marketplace posting. Those rows still clutter inventory if they were captured or imported "just in case." If you never intended to post them, archive them as soon as the exit is real. Do not keep a wholesale unit in draft for three weeks as a maybe.
Duplicates
Duplicates happen after a second import, a recapture from an auction page, or two reps creating the same VIN. Clear the extra. If both rows have different mileage or price, stop and decide which record matches the deal jacket before you archive either. Archiving the accurate row and keeping the stale one is worse than leaving both for a day.
Training and test data
The first week on a new account produces junk rows. Schedule a clear at the end of onboarding. A twelve-person floor that learned on fake VINs will queue those VINs during a busy Saturday if they are still in Inventory.
How to Run a Monthly Archive Pass Without Creating a Mess
Daily sold-unit hygiene handles the flow. A monthly pass handles the sediment: rows that missed the daily rule.
Before you start
- Export or glance at what you think you currently own (DMS, whiteboard, whatever the desk trusts). You are matching posting inventory to physical inventory, not inventing a third list.
- Tell the floor you are archiving so nobody is mid-post on a row you are about to clear.
- Do not archive during a bulk import. Finish the import, work the error log, then archive.
The pass, in order
- Sold, still active. Mark sold and archive. This is the biggest win and the least controversial.
- VIN duplicates. Keep one, clear extras.
- Wholesale and gone. Anything the desk confirms is not on the lot and not coming back.
- Test rows. Search for obvious dummy stock numbers and training names.
- Failed on units you no longer own. Archive those. Failed on units you still own stays.
What you are not doing
You are not rewriting history to make analytics look better. Posting analytics by rep and source should still reflect work that happened. Archiving removes rows from the working list; it is not a tool for hiding that a rep posted a car that later sold. You are also not using archive as a substitute for recon decisions. A 70-day unit that is still on the lot stays in inventory until it sells or you wholesale it.
Tie archive work to statuses, not vibes
If a row is posted, ask whether the listing should still be live. If it is sold, archive. If it is draft and the car is gone, you missed the sold step; do it now. If it is failed, ask whether the unit still exists. Statuses are the language of the pass. Guessing from stock photos is how you archive a live truck.
A daily version of this thinking belongs in an exception list. The monthly pass is for everything that escaped the day. If you want the daily companion, pair this with using statuses to build a daily exception list.
Pitfalls When Archiving Old Records
Archiving too early
A pending deal is not a sold unit. If you archive when the buyer "is coming Saturday with a cashier's check," you will recapture or re-import the VIN when the deal dies, and you may duplicate the listing. Wait until the desk calls it sold.
Archiving instead of fixing failed
Failed means the post did not complete. If the car is still yours, the job is to correct the listing and retry, not to make the red status disappear. Managers who archive failed to "clean the board" teach reps that failed is optional.
Shared logins hiding who archived what
If two people share a login, you will not know who cleared a row. One login per person is part of archive discipline. The Dealership plan exists so a twelve-person floor is not borrowing the manager's email.
Clearing posted units to "refresh" them
Do not archive a live listing because you want a new timestamp. That is a relist decision with its own risks, and it is not what archive is for. Archive is for cars that should no longer be in the working set.
How PostToMarket Automates This
Archiving old records fails when sold, duplicate, and working units share one undifferentiated list, and when marking sold is a separate chore from the queue. PostToMarket keeps a status on every vehicle and lets you mark sold and archive from inventory or the queue, so the person who hears "it sold" can clear the record without hunting.
Status first, archive second
- Inventory statuses: draft, posting, posted, sold, failed. Sold is a first-class state, not a note in a spreadsheet.
- Mark as sold and archive from inventory or the queue.
- Team queue view so a manager can see a sold unit still claimed by a rep and release or clear it.
Stop junk rows from becoming "old records"
- Bulk CSV and Excel import with import history and a row-level error log, so bad and duplicate rows are caught at upload.
- Capture from auction and wholesale sites into inventory as drafts you can archive later if the unit never retails.
- Unlimited vehicles in inventory, so you are never forced to delete history just to add this week's buys.
Keep the working list aligned with who posts
- Per-rep queues and manager assignment so archived units are not sitting in a junior associate's list as if they were still work.
- Personal posting queues that only contain what a rep should still post.
- Chrome extension posts one vehicle at a time from the queue you actually intend to work, not from a graveyard of last quarter's stock.
No tool should promise that Facebook will stop showing a listing the instant you archive. The operational win is that your team stops advertising, queueing, and counting cars that are gone.
Keep a Short List of Cars You Can Actually Sell
Working inventory should look like the lot, not like a museum of every VIN that ever passed through the store. Archive sold, wholesale, duplicate, and training rows on purpose. Keep the units you still own, including the failed ones you still need to fix. A short list makes every other posting habit easier: assignment, analytics, and Saturday coverage.
PostToMarket gives you the statuses, the mark-as-sold path, queues, and import tools to make that list trustworthy. Starter is $59 per month if you are a solo seller who needs sold units out of the way. Dealership is $299 per month for up to 13 team logins so managers can clear records without borrowing a rep's session.
Start your 10-day free trial via secure Stripe checkout. Load inventory, mark last week's sold units, archive the leftovers, and look at how much shorter the working list becomes. Cancel anytime. If a row should not have been cleared, contact info@posttomarket.com.