Measuring Marketplace Days-to-Turn by Vehicle Segment

The pack report says days-to-turn is "fine." Walk the lot and the story is not fine: three-row SUVs left last week, the compact sedan row has dust on the windshields, and a pair of cargo vans has been "about to move" since the last used-car meeting. A blended average is how quiet segments hide inside a healthy-looking number. Facebook Marketplace does not create that illusion, but posting everything as if it were one product line makes the illusion worse.

Measuring Marketplace days-to-turn by vehicle segment means you stop treating "the lot" as a single clock. You still use true retail days-to-turn from your DMS. You add a Marketplace-aware view: when each segment first went live, how long it stayed live, and whether posting coverage was even. That view will not match a published Meta statistic, because none exists. It will tell a used-car manager which body styles are consuming posting capacity and floor-plan days together.

This is for GMs and used-car managers who already understand holding cost. For the broader math of exposure versus aging, start with days-to-turn and online exposure. This article is the segment cut.

Why Blended Days-to-Turn Lies to Used-Car Managers

Averages are polite. Segments are not.

Mix changes the number without changing skill

If last month's pack was heavy in trucks and this month's pack is heavy in cars, blended turn can worsen while your truck process stayed the same. The reverse is also true: a lucky truck month can hide a sedan problem until the trucks are gone. Segment the clock or you will coach the wrong people and buy the wrong cars.

Marketplace coverage is not the same as retail age

A unit can age in recon, then age on the lot unposted, then age live. Those are three clocks:

• Stock days: from your purchase or trade-in date (DMS).
• Unposted days: retail-available but never live on Marketplace.
• Live days: from first posted status to sold or delist.

If you only watch stock days, you will punish a segment that sat in recon. If you only watch live days, you will ignore the vans that never got photos. Measuring Marketplace days-to-turn by vehicle segment requires all three, or at least stock days plus a coverage flag.

Season is a segment fact, not an excuse

Four-wheel-drive SUVs and convertibles do not share a calendar. Read trucks and SUVs on Marketplace before you call a seasonal lull a process failure. Label the month on every segment row so you do not compare July convertibles to January convertibles and call it a trend.

Define Segments the Desk Will Actually Use

If the segment list looks like a consulting slide, the report will die.

Start with body style, then split only when it changes a decision

A workable first cut:

• Compact cars
• Midsize cars
• Compact crossovers
• Midsize and three-row SUVs
• Pickups (light duty)
• Vans (passenger vs. cargo, if you stock both)
• Other (only if it is truly other)

Split further when the extra row would change a buy, a price, or a posting rule: diesel vs. gas trucks, AWD vs. FWD crossovers, work vans vs. passenger vans. Do not split by color. Do not split by every trim.

Write the mapping once. A "crossover" in the DMS that the floor calls an SUV must land in one bucket, every time.

Price band inside a segment, when the band is the product

A $8,000 compact and a $22,000 compact are not the same customer. If your independent lot lives in one band, skip this. If your franchise used department spans both, add two bands inside the body style, not a dozen.

Title status and special units

Rebuilt, salvage, and lemon-branded units will wreck a clean-title average. Keep them in a separate bucket or exclude them from the core segment clocks and review them on their own. The same goes for wholesale-bound units that should never have been posted as retail.

The Clocks for Measuring Marketplace Days-to-Turn by Vehicle Segment

You do not need a data warehouse. You need frozen definitions and a repeatable pull.

Columns that earn their keep

Use medians so one 200-day problem child does not define the row. Still list the problem children. They are the punch list.

How to attach Marketplace without pretending Facebook sold the car

You often cannot prove a buyer came from Marketplace unless you asked and logged it. Do not print a "Marketplace days-to-turn" that assumes every sold unit was a Marketplace deal. Instead:

• Report live days for units that were posted, as an operational aging measure of the ads.
• Report stock days by segment for all retail deals, as the true turn.
• Report coverage by segment, so you can see which body styles you never bothered to list.

If you later add source capture, you can cut stock days for Marketplace-sourced deals as a separate slice. Until then, do not invent the slice. See tracing sold units back to listings when you are ready to connect deals to ads without guessing.

Illustrative read, not a benchmark

Consider a lot with 60 units. At month end the compact-car row shows longer median stock days, weak coverage, and almost no live days because half the row never posted. The pickup row shows shorter stock days and high coverage. The lesson is not "cars don't sell on Marketplace." The lesson is that the car row never received the same posting discipline as the trucks. Next month's action is photos, copy, and queue assignment on cars, or a decision to stop stocking that band. Different actions. Same scoreboard.

Decisions the Segment Clock Should Force

A report that does not change a buy, a price, or a posting rule is a hobby.

Stocking

If a segment's median stock days stay long after coverage is high, photos are honest, and prices match the jacket, you have a mix problem. That is when you test demand before you buy deep or pull a weak segment off Marketplace instead of feeding it more posts.

If a segment turns quickly but coverage is low, you are getting lucky on walk-ins and leaving messages unearned. Post it.

Pricing and recon priority

Slow segments with high live days and real inquiries are often a price or condition problem, not a channel problem. Slow segments with no inquiries need a listing audit before a price cut. Cutting price on an unfindable, unphotographed unit teaches you nothing.

Give recon slots to the segment that will be live this week, not only to the newest auction arrivals.

Posting capacity

Associates have a conservative daily ceiling. Spend it on segments that are retail-available, photographed, and priced, and on aging units that still have a retail path. Do not spend it cloning a dead body style because "we have to list everything." Everything is not a strategy.

How PostToMarket Automates This

Measuring Marketplace days-to-turn by vehicle segment fails when you cannot tell when a VIN was posted, whether it is still live, or who owns it. The operational need is timestamps and statuses on every unit, not a custom BI project.

PostToMarket keeps unlimited vehicles in one inventory with statuses (draft, posting, posted, sold, failed), which is how you distinguish unposted days from live days. Bulk CSV and Excel import, with import history and row-level errors, is how segment fields survive the trip from a DMS export instead of dying in a bad row. Capture from auction and wholesale sites gets new units into inventory fast enough that "unposted days" is a choice, not a typing backlog. Managers assign slow-segment units to associate queues; reps self-queue from shared inventory. Team analytics by rep and source show whether a slow row is a person or a feed. Mark as sold and archive so live days stop when retail stops. AutoPost sends one vehicle at a time with human-like delays and server-enforced limits, which is how coverage becomes a paced habit instead of a weekend burst. PostToMarket does not calculate a magic turn rate and does not guarantee Facebook distribution.

Stop Managing a Blended Clock

If the pack report is "fine" and the sedan row is not, you already know the average is lying. Measuring Marketplace days-to-turn by vehicle segment, with a coverage flag, is how you make the next buy and the next queue match that picture.

PostToMarket includes inventory, import, queues, analytics, a leads inbox, and AutoPost on every plan's workflow, with Starter at $59 per month (one login) and Dealership at $299 per month (up to 13 logins, 2 managers).

Start your 10-day free trial via secure Stripe checkout. Get posted and sold statuses onto the same units you already age in the DMS. Cancel anytime.