Intake is the control point
Every downstream problem — mispriced items, missing seller terms, payout disputes — is cheapest to prevent at intake. The rule: an item does not enter stock until its owner, split, condition, and target price are recorded together.
Batch intake works better than ad hoc. Set drop-off windows or appointments, and process each batch to done: photographed, priced, and either accepted with terms or returned. Half-processed items are where backlog starts.
- Record the owner and split before the item touches the floor.
- Photograph at intake, not at listing time. The photo queue is the usual bottleneck.
- Decline decisively. A polite no at intake costs less than an unsold item occupying a rail for a season.
One status everyone reads
Most staff interruptions are status questions in disguise: where is this item, has it sold, can I mark it down. The fix is a single status field per item that everyone trusts — in review, listed, sold, returned, or paid out — updated as part of doing the work, not as extra admin.
If status lives in a spreadsheet that one person updates on Sundays, it is already wrong by Tuesday. Status should change at the moment the thing happens: the sale, the return, the payout.
Listing readiness as a queue
Treat 'ready to list' as an explicit queue rather than a vibe. An item is ready when it has photos, a price, condition notes, and a channel decision. Anything missing means it sits in a named waiting state — waiting on photos, waiting on approval — so the bottleneck is visible.
Weekly rhythm beats heroics
Stores that run smoothly tend to share a weekly rhythm: intake batches on fixed days, a markdown review once a week, payout runs on a fixed schedule, and a short look at what is aging on the rail. The alternative is the quarterly panic tidy-up, which sellers notice.
- Fixed intake days keep the photo and pricing queues predictable.
- A weekly markdown pass keeps stock moving before it goes stale.
- A fixed payout day turns seller questions into a known answer.
