Aging Buckets: Sorting Used Inventory by Days on Lot

Most used-car meetings start with a pack sorted by stock number, make, or the manager's favorite salesperson. The 11-day hatchback and the 87-day truck sit on the same page. Everyone "reviews inventory." Nobody reviews time. By the end of the hour the truck is still "a good car" and the hatchback has eaten the conversation because it is easier to talk about a unit that is still in the honeymoon window.

Aging buckets exist to stop that. Sorting used inventory by days on lot is not a reporting flourish. It is a way to make time the first column so the desk spends Monday on the cars that are about to cost real money, not the cars that arrived last week.

This article is for used-car managers and general managers who already live in days-to-turn but still run meetings off a DMS printout that was built for accounting. It explains how to define buckets, what each bucket is for, how to keep the sort honest when recon and "sold pending" distort the clock, and how to connect the list to posting ownership. Illustrative examples are labeled as such; use your own days-on-lot definitions and lender clocks.

Why Aging Buckets Beat a Single Days-on-Lot Column

A single aging number is a fact. A bucket is a decision queue. Humans do not process 80 VINs as 80 unique ages. They process groups: fresh, working, and late. If you do not name the groups, every car becomes a special case and every special case gets another week.

What "days on lot" should mean in the sort

Agree on the start date before you argue about the buckets. Common choices:

• Date funded if you are managing floor plan and holding cost.
• Date in stock if cash deals and trades mix on the same lot.
• Date front-line ready if you want a retail-performance clock separate from recon.

You can keep more than one clock. You cannot mix them in one meeting without lying to yourself. A truck that has been in body for 20 days is not a 20-day retail problem. It is a recon problem that will become a retail aging problem the day it hits the line. Put recon units in their own working list, or tag them so they do not inflate the "we cannot sell anything" story.

A simple three-bucket model most desks can run

There is no magic set of day counts. A conservative operating model many independent lots can start with:

Franchise stores with slower luxury segments sometimes stretch the middle bucket. BHPH lots with different funding realities may tighten it. The point is not the integers. The point is that every VIN falls into a named group with a default next action.

If you also track floor plan curtailments, overlay the lender date on the 61+ list. A unit can be 45 days old and still be the most urgent car on the lot if a paydown is next week.

How to Sort the Pack So Aging Buckets Drive the Meeting

The physical or digital pack should open on late units, not on A-to-Z. If the first page is still "what we just bought," you will run out of time before you reach the cars that need a decision.

Build the weekly sort in this order

1. 61+ first. Read every unit. Each gets an owner and a next action dated this week.
2. 31–60 second. Scan for silent units: live but no conversations, or not live at all.
3. 0–30 last. Only confirm exposure and data quality unless a unit is already a problem (wrong price, missing photos, title delay).
4. Recon and hold separately. Do not let a body-shop car masquerade as a retail aged unit, and do not let a sold-pending car linger in the late bucket.

Print or export with days on lot as the leftmost data column after stock number. Color is optional. Sequence is not.

Keep the buckets honest with status hygiene

Aging reports rot when statuses are wrong:

• A sold unit that is still "posted" looks like a 70-day failure. It is a hygiene failure. Mark it sold and archive it the same day.
• A unit in draft that has never been listed is not a market problem. It is an exposure gap.
• A failed post that nobody retried is invisible inventory with a running clock.
• Two rows for one VIN, one aged and one fresh, means your import or clone process is lying. Deduplicate before you manage.

Inventory statuses of draft, posting, posted, sold, and failed are enough to run this honestly if someone actually uses them. The sort is only as good as the last status change.

What Each Aging Bucket Is For (and What It Is Not)

Buckets fail when they become labels without jobs. "It's in the 60-day bucket" is not a plan.

0–30: earn the right to age

Fresh units should be front-line ready, uniquely described, and live on the channels you actually use. The bucket's job is to catch intake mistakes while they are cheap:

• VIN, mileage, and price match the listing and the windshield.
• Photos are daylight, current, and not a wholesale lane shot if the car has been detailed.
• A person owns the unit in a queue, not "the floor."
• The ask is defensible against local comps, not a cost-plus fantasy.

If a 12-day unit is not posted, do not discuss its gross. Discuss why it is not posted.

31–60: choose an action, not a feeling

This is the bucket where stores either stay in control or start the slide into 90-day wreckage. Default actions:

• Refresh the lead photo and the first lines of the description if the car has been detailed or the original shots were weak.
• Recheck comps and, if you are off the market, use a planned price change rather than a hallway cut.
• Confirm the listing is findable: right location, current price, no stale "pending" language.
• If conversations exist and deals are dying in F&I or appraisal, that is a process problem, not an aging problem.

Do not use this bucket to relist the same car under a new account "for a fresh timestamp." Duplicate and near-duplicate listings are an operational risk; change the content or the price, then keep one live record. For aged units that still have a retail path, refreshing photos before cutting price is often the cheaper test.

61+: exit or justify, in writing

Late units need a sentence a GM can live with: "Retail at $X with a markdown on this date" or "Wholesale on this date." Open-ended "it's a nice car" is how lots fill with monuments.

Pair this bucket with action rules at 30, 60, and 90 days so the meeting is executing a policy, not inventing one under pressure.

Pitfalls When Sorting Used Inventory by Days on Lot

Aging buckets only work if the sort matches how the store actually operates.

Mixing segments in one bucket conversation

A 40-day compact and a 40-day diesel dually are not the same problem. You can still use the same day counts as a trigger to talk. You should not use the same markdown amount or the same wholesale deadline. Split the late list by segment if the meeting keeps comparing unlike cars.

Letting one rep's pets skip the sort

If a closer "has a deal working" for three weeks with no deposit, the unit is not in a special bucket. It is in the same 61+ list with a note. Either there is a real hold with store rules behind it, or the car goes back to available and stays in the sort.

Starting the clock on the wrong day

If you start days on lot at first photo, you will understate holding cost and overstate retail performance. If you start it at purchase and never tag recon, you will overstate retail aging and yell at the wrong department. Write the rule. Print it on the pack.

Reviewing aging without reviewing exposure

A 55-day unit that was live for 50 of those days is a different animal from a 55-day unit that was live for 8. Always put "first listed date" next to days on lot, or you will markdown cars that the market has barely seen.

How PostToMarket Automates This

Aging buckets collapse when the desk cannot see days on lot, listing status, and owner in one workflow. The problem this article names is not "we need a prettier report." It is that used inventory is still sorted the way the DMS likes to print, while time and posting ownership live in someone's head.

Keep every unit in a status the whole store can see

• Unlimited vehicles in inventory with draft, posting, posted, sold, and failed statuses, so the 0–30 bucket is not padded with cars that never went live and the 61+ bucket is not padded with sold ghosts.
• Bulk CSV and Excel import with a row-level error log, so a missing price or bad VIN does not enter the pack as a fake fresh unit.
• Mark as sold and archive from inventory or the queue so the next aging sort is true.

Put bucket work into queues, not hallway assignments

• Managers assign late and mid-bucket units to associate queues; sales reps self-queue from shared inventory.
• Team queue view lets a manager see and release any claim that is sitting while the clock runs.
• Mobile dashboard on a phone's home screen so a used-car manager can reorder today's work between customers, starting with 61+ rather than with whoever walked up.

Make the listing match the bucket action

• AI-generated titles and descriptions from each vehicle's specs, editable before posting, so a 31–60 refresh is unit-specific instead of a cloned paragraph.
• Facebook photo picker for a real lead-image choice when the action is "reshoot or recrop before we cut."
• Team analytics by rep and source and a leads inbox so you can tell whether a late unit is quiet because nobody posted it, or because buyers saw it and passed.

PostToMarket does not calculate your official days-to-turn for the manufacturer or the bank. It keeps the operational list — what is live, who owns it, what failed — close enough to the truth that aging buckets become a meeting tool instead of a PDF nobody trusts.

Run the Lot in Aging Buckets, Not in Alphabetical Order

Aging buckets are how a used-car desk sorts inventory by days on lot so time, not stock number, sets the agenda. Fresh units get exposure. Mid-age units get an action. Late units get an exit. If your pack still opens on last week's purchases, you are managing arrivals and ignoring the cars that are already expensive.

PostToMarket keeps inventory, queues, and listing status in one place so the sort you run on Monday matches what buyers can actually see. Starter runs $59 a month for a solo seller or small independent lot with a single login. Dealership runs $299 a month when you need up to 13 logins and two managers on the same pack.

Start your 10-day free trial with secure Stripe checkout. Import the inventory, put 61+ in queues first, and hold the next used-car meeting against live status instead of a stale printout. Cancel anytime.