How Many Units Belong in One Rep Queue?

A manager looks at a sales rep's queue on Thursday afternoon and sees forty-seven vehicles. The rep is proud of it. "I've got my whole week loaded." Two of those vehicles posted on Monday. One sold on Tuesday and is still in the list. The rest are a parking lot that nobody else can claim. How many units belong in one rep queue is not a trivia question. It is how you stop a personal queue from becoming a private inventory freeze.

There is no published Meta number for how many cars a person should queue, and PostToMarket does not publish a magic queue size either. What you can do is set a conservative operating standard based on what a human can inspect and post in a day, under server-enforced daily post limits and delays. This article gives managers and reps a way to size a queue without pretending there is an official cap.

For pacing context, see PostToMarket daily post limits and delays explained. For how to order the units once the count is sane, see how sales reps should build and order a personal queue.

Why Too Many Units in One Rep Queue Is Worse Than a Short List

A long queue feels like productivity. It behaves like a lock.

Blocked inventory

Every unit in a rep's queue is claimed. Other reps cannot honestly work it. Associates will not be assigned it if the claim is sitting there. A forty-unit claim list means forty units whose online fate depends on one person's interruptions, lunches, and days off.

Inspection quality collapses

AI-generated titles and descriptions still need a human pass. Photos still need a picker decision. Nobody does that well on the thirty-first car of a list they loaded at dawn. Thin copy and wrong lead photos are how listings underperform even when they go live.

Burst pressure at the end of the day

Oversized queues create a story in the rep's head: "I have to get through these." That story produces late-day bursts. Human-like delays and daily limits exist to stop that burst. The rep then feels the software is "slow." The software is protecting the account. PostToMarket is not affiliated with, endorsed by, or sponsored by Meta, and no queue size guarantees distribution. A panicked dump is still a bad idea.

Analytics lie

Posting analytics by rep look busy when the queue is huge and the posted count is small. You will coach the wrong problem unless you separate "claimed" from "completed."

A Conservative Operating Standard for Queue Size

Do not hunt for a platform threshold. Build from the day you actually run.

Inputs that set the number

• Posting windows the rep really has. A full-desk Saturday is not a posting day with a long list.
• Server-enforced daily limits. The queue should not be many times larger than what those limits will allow in the next day or two.
• Inspection time. Copy, photos, price, and a walk to the car. If you skip this, you are not posting; you are spraying.
• Interruptions. Customers, managers, and recon delays are normal. Size for them.

Illustrative ranges (not targets, not Meta rules)

Consider a lot with 60 units and three posting people:

• Associate, assigned queue: a short batch they can finish in one shift. Better to assign again tomorrow than to park a week of work on a junior login.
• Sales rep, personal queue: about a day's work plus a small leftover buffer for tomorrow morning — not the rest of the month.
• Manager's own queue: even smaller. Managers who load themselves like floor reps stop releasing other people's claims.

If those ranges feel "too small," that is the point. Small queues cycle. Large queues stagnate.

A simple cap conversation

Ask each rep: "If you posted nothing after lunch, would this list still be honest?" If the answer is no, it is too long. Cut it until the answer is yes.

How Many Units Belong in One Rep Queue Across Several Days?

Some stores want a multi-day queue so Monday's import does not have to be re-picked every morning. That can work if you follow rules.

Multi-day queues that stay healthy

• The list is still ordered: aged and new-to-online first.
• Each morning starts with a status pass (draft, posting, posted, sold, failed) and removal of anything that sold or went on hold.
• Units that did not move after a day or two go to the top or get released.
• The rep is not using the multi-day list as a way to hide inventory from colleagues.

Multi-day queues that rot

• Friday's leftovers sit untouched until the following Thursday.
• New units are always inserted at the top, so old claims never surface.
• The rep is out sick and the claims remain.

Managers should use the team queue view on a schedule and release what is stuck. A queue is a work order with an expiration, even if the product does not auto-expire it. The expiration is social: your store's standard.

Fit to a weekly posting rhythm

If your store already thinks in weekly posting windows, keep queue size inside that rhythm rather than loading the whole week on Monday. A practical calendar lives in the posting schedule for a dealership Facebook Marketplace workflow. Queue size is how that calendar survives contact with a real floor.

Manager Controls When a Queue Is Too Big

Reps will overfill. Plan for it.

What to look at

• Claim count vs. posted count over the last few days.
• Age of the oldest unit still sitting in a personal queue.
• Failed units accumulating because the rep keeps adding instead of fixing.
• Associates idle while a rep sits on a pile they will not reach.

What to do

1. Talk to the rep with the list open. Do not argue in the abstract.
2. Have them keep only what they will work next.
3. Release the rest from the team queue view and either return units to shared inventory or assign some to an associate.
4. Repeat until overfill stops being a personality trait.

Do not solve overfill by giving the same person a second unofficial list in a notebook. That is how duplicates return.

Associate queues are sized by the assigner

How many units belong in one associate queue is the manager's decision, not the associate's appetite. Assign a finishable batch. If they are fast and clean, assign more the same day. Do not "trust them" with twenty cars on day three.

How PostToMarket Automates This

The product will not stop a rep from claiming too many vehicles. It will make the cost visible and keep them from blasting the pile.

• Personal posting queues and manager-assigned associate queues so ownership is explicit.
• Team queue view to see oversized claims and release them.
• Inventory statuses so sold and failed units do not hide inside a long list.
• Server-enforced daily post limits and delays and one-vehicle-at-a-time extension posting with human-like delays.
• Mobile dashboard to keep a short list in the right order when the day breaks.
• Analytics by rep so "big queue" does not get confused with "productive poster."
• Mark as sold and archive to drain units that should not occupy a slot.

Size is a store standard you enforce with those tools. It is not a number to scrape from a help article and treat as a platform law.

Stop Treating a Queue Like a Private Lot

If one rep is sitting on dozens of VINs, you do not have a posting plan. You have a bottleneck with a name. Decide how many units belong in one rep queue using the day they actually have, then release the rest.

PostToMarket keeps inventory unlimited so you never need to park cars in a login to "save capacity." You need seats, queues, and pacing. Starter is $59 per month for a solo seller, one login. Dealership is $299 per month for up to 13 team logins and managers who can see and release claims.

Start your 10-day free trial through secure Stripe checkout. Load a short real queue, watch it finish, and cancel anytime if your floor still prefers a forty-unit trophy list.