Building a Monthly Marketplace Performance Scorecard
A monthly Marketplace performance scorecard turns posting volume into a meeting you can run: coverage, listing health, response, sold-unit hygiene, and segment notes without fake benchmarks.
The used-car meeting already has a pack report, an aging bucket, and a recon list. Marketplace, if it appears at all, shows up as "we posted a lot" or "leads were slow." That is not a scorecard. It is a vibe with a channel name attached. General managers who cannot see coverage, listing health, and response on one page will keep funding posting labor without knowing whether the labor did anything.
Building a monthly Marketplace performance scorecard is how you put Facebook Marketplace on the same operating rhythm as days-to-turn. The card is internal. It does not claim a published conversion rate, a guaranteed reach number, or a Meta benchmark. It answers five questions a GM can ask without opening ten tabs: Did we cover the lot? Were listings complete? Did we answer? Did sold units leave? Which segments wasted capacity?
This article is for general managers and internet directors. It complements the broader Marketplace posting KPIs with a monthly package you can actually run in a standing meeting.
What Belongs on a Monthly Marketplace Performance Scorecard
If the card has twenty lines, nobody will read it. If it has two lines, it will hide the failure. Aim for a page you can print.
Coverage, not raw post count
Post count is a vanity number. Coverage is operational:
- Units in inventory that should have been live this month.
- Units that were actually posted (status: posted) at some point in the month.
- Units that sat in draft, failed, or never entered a queue.
A store that posted eighty times on forty unique VINs did not cover eighty cars. It recycled. Count unique vehicles with a live listing, then count posts as a pacing and labor metric on a separate line.
Listing health, not "looks good"
Pick a few binary checks the desk can audit on a sample of live ads:
- Title, year, trim, and photos describe the same vehicle.
- Price in the field matches the description and the asking price on the jacket.
- Mileage is current enough that a buyer with a phone flashlight will not catch you.
- Description is unit-specific, not a cloned paragraph with the stock number swapped.
Score a sample (illustrative: twenty live listings mid-month), not the whole pack, unless the pack is small. Record the fail count. The scorecard is allowed to say "4 of 20 sampled listings had a price mismatch." It is not allowed to invent a quality index with no definition.
Response and sold-unit hygiene
Two operational failures look like "Marketplace is dead":
- Inquiries sitting unanswered while the unit is still live.
- Sold units still advertised, generating angry messages and junk data.
Put both on the card. Response belongs next to the leads inbox workflow. Sold-unit hygiene belongs next to the same-day removal habit in inventory hygiene.
The Monthly Marketplace Performance Scorecard Template
Use columns that a manager can fill from systems you already have: inventory statuses, a queue, a leads inbox, and a sold log. Do not wait for a perfect CRM export.
The core rows
| Row | Definition | Where it comes from |
|---|---|---|
| Unique units posted | Distinct vehicles that reached posted status this month | Inventory |
| Coverage gap | Retail-available units that never posted | Inventory vs. posted |
| Failed posts | Units that ended the month in failed, unresolved | Inventory / queue |
| Sample listing defects | Defects found in the mid-month sample | Manual audit |
| Inquiries logged | Messages captured in the period | Leads inbox or a shared log |
| Unanswered after same day | Inquiries with no first reply by close of the posting day | Leads inbox |
| Sold-still-live incidents | Sold units found still advertised | Spot check + sold list |
| Segment notes | One line per weak or strong body style | Manager judgment, labeled as such |
Keep inquiries as a count of conversations you recorded, not as a claimed "lead conversion." If you did not log it, it did not happen for the scorecard.
Optional rows that earn their space
Add these only if someone will act on them:
- Posts by source (CSV import vs. auction capture vs. manual).
- Posts by rep, for coaching, not for a public leaderboard that rewards dumping.
- Aged units still live with no price or photo change this month.
- Units posted to Marketplace plus profile or groups, if your workflow uses those surfaces.
If a row has no owner and no action, delete it next month.
What never goes on the card
- Invented percentages ("Marketplace closes at X%").
- Rankings of Meta distribution you cannot see.
- Customer quotes, testimonials, or "we tripled leads" stories.
- A single blended days-to-turn for the whole store pretending to be a Marketplace metric.
Days-to-turn is a retail metric. You may put segment-level aging next to posting coverage, but do not pretend Facebook published a turn rate.
How to Run the Meeting Without Theater
A scorecard that is not reviewed is a wallpaper file. Put it on a calendar.
Cadence and roles
- Owner: used-car manager or internet director, one name.
- Prep: numbers pulled the last business day of the month, sample audit done mid-month so defects can still be fixed.
- Meeting: fifteen to twenty minutes inside the existing used-car meeting, not a new standing call.
- Audience: GM, used-car manager, the manager who assigns queues. Floor reps see their own slice, not a public shaming table.
Questions the GM should actually ask
- What share of retail-available inventory never made it to Marketplace?
- Of the units that posted, how many failed and sat there?
- What did the listing sample fail on, and is that a person or a process?
- How many inquiries had no same-day reply?
- How many sold units were still live when we checked?
- Which segment should we stop feeding posting capacity, and which should we stock?
Write the answers in verbs: assign, rewrite, release, archive, stop buying. "Monitor" is not an action.
Common ways the card lies
- Counting posts instead of VINs. Burst reposts inflate labor and hide a coverage gap.
- Counting every Messenger ping as demand. Bots, "still available," and tire-kickers are not equal to a booked appointment.
- Ignoring failed status. A queue full of failed units looks like work in progress. It is work abandoned.
- Changing definitions mid-year. If "posted" meant something else in March, April is not comparable. Freeze definitions on the first card.
For a fair year-ago comparison later, freeze the definitions now and leave a note. That work belongs with comparing Marketplace results year over year.
Keep the Scorecard Honest as the Store Changes
Stores add lots, add associates, and change who is allowed to post. The card has to survive that.
Multi-lot and multi-login stores
If two rooftops share a scorecard, split coverage by location. A downtown store posting well can hide a second lot that never lists trucks. Assign inventory and queues by rooftop the same way you assign floor traffic.
If several reps post, show volume by rep only alongside quality and response. A rep who posts the most and answers the least is not winning.
When the month is ugly
Do not sand the numbers. An ugly month is the only month that teaches. If coverage collapsed because recon piled up, say that. If a restriction or a wave of removals hit, say that you paused, cleaned listings, and resumed on a conservative cadence. Do not invent a Meta threshold to explain it. Point people at current commerce policies and at your own listing audit.
The one-page checklist for month close
- Unique VINs posted vs. retail-available inventory.
- Failed and draft units still sitting.
- Mid-month sample defects, with the top defect named.
- Inquiry log complete enough to discuss, or an explicit "we did not log, so we cannot talk."
- Same-day reply misses.
- Sold-still-live incidents, with owners.
- One segment sentence: keep, test, or pull.
That is a monthly Marketplace performance scorecard. Everything else is decoration.
How PostToMarket Automates This
A monthly card dies when the underlying statuses live in chat threads. Building a monthly Marketplace performance scorecard requires one inventory, one queue, and a way to see who posted what without rebuilding the month from screenshots.
PostToMarket inventory statuses (draft, posting, posted, sold, failed) are the raw material for coverage and failure rows. Unlimited vehicles on every plan means the pack is not truncated to fit a spreadsheet tab. Bulk CSV and Excel import with import history and a row-level error log tell you whether the month started with clean data or with bad VINs. Team analytics by rep and source feed the optional coaching rows. The leads inbox gives managers a single place to see inquiries instead of hunting personal Messenger threads. The team queue view shows stuck claims so "unposted" is a releasable assignment, not a mystery. Managers assign units to associate queues; sales reps self-queue from shared inventory. Mark as sold and archive from inventory or the queue so sold-still-live incidents become a process miss, not a surprise. No tool can guarantee Facebook will distribute every listing; the scorecard measures your operation, not Meta's ranking.
Run Next Month's Meeting on a Real Card
If Marketplace only appears in the used-car meeting as an anecdote, you will keep paying for posting that you cannot inspect. Building a monthly Marketplace performance scorecard is cheaper than another month of "leads were slow."
PostToMarket puts inventory, import history, queues, team analytics, and a leads inbox in one dashboard, with AutoPost that sends one vehicle at a time under server-enforced daily limits. The Dealership plan is $299 per month for up to 13 team logins (including 2 managers). The Starter plan is $59 per month if you are a solo seller or independent lot with a single login.
Start your 10-day free trial through secure Stripe checkout. Connect the pack, post with a queue, and fill next month's card from statuses instead of memory. Cancel anytime.