Prep rejections are process failures, not bad luck. The five errors that cause most of them, and how to move prep requirements out of someone's memory and into the warehouse management system.
Marketplace prep is the least glamorous part of e-commerce fulfillment and one of the most expensive to get wrong. A rejected or mislabeled inbound shipment does not just cost the prep labor twice. It strands inventory in a receiving queue during the exact weeks you planned to sell it, and it usually surfaces as a stockout before it surfaces as a compliance notice.
The failure is rarely one dramatic mistake. It is a prep process that lives in someone's head, works fine at 200 units a week, and falls apart the first time volume triples or the person who knew the rules is out.
Prep is the set of physical steps that turn supplier-packed goods into units a marketplace warehouse will accept and store without damage.
In practice that means unit identification, protective packaging, set and multi-pack handling, expiration and lot marking where the category requires it, carton preparation, and inbound documentation. Each of those has a rule, and the rules differ by category, by program, and by marketplace. A supplement, a fragile glass item, and an apparel poly bag are three different processes that share a bench.
The operational point is that these are deterministic requirements, not judgment calls. Anything deterministic can be written down, and anything written down can be verified by someone other than the person who wrote it.
Unreadable or duplicated identification. A unit carrying both a supplier barcode and a new marketplace label will scan as whichever the receiver reads first. Cover or remove the original identifier rather than layering a new one beside it.
Missing suffocation or protective packaging. Poly-bagged goods above a size threshold need the correct warning text, and the bag must be sealed rather than folded over. This is one of the most common and most avoidable rejections.
Sets not marked as sets. A multi-pack that is not identified as a single sellable unit gets separated at receiving and counted as loose units. Recovering from that costs far more than the tape and label it would have taken to prevent.
Overweight or overloaded cartons. Weight limits exist for handling safety and they are enforced. A carton that arrives over limit can be refused outright, and cartons packed to the exact limit arrive crushed.
Documentation that does not match the physical shipment. Carton counts, unit counts, and box content declarations that disagree with what is inside create receiving variances that take weeks to reconcile, and the missing units are your loss until proven otherwise.
The difference between a prep operation that survives Q4 and one that does not is whether the requirements exist outside of memory.
Write a prep spec per SKU. One short record naming the required packaging, label placement, unit or set treatment, and any category-specific marking. Store it against the SKU in your warehouse management system, not in a shared document that goes stale.
Verify at the bench, not at the truck. A scan-verified prep step, where the operator scans the unit and the system confirms the correct prep spec was applied, catches errors while they cost one unit of labor rather than an entire shipment.
Photograph the first unit of every new SKU. A reference image resolves nine out of ten future arguments about how something should be prepped, and it onboards seasonal staff faster than any written instruction.
Separate prep from packing physically. Prep needs bench space, supplies, and inspection light. Doing it at a pack station starves outbound during peak and produces inconsistent results.
Track prep minutes per unit by SKU. This is what tells you whether a product is actually profitable to sell through a marketplace program at all. Some SKUs cost more to prep than they earn in margin, and that only becomes visible when the labor is measured rather than absorbed.
The prep bench is the last point at which you control what a customer receives. It is also the only place where supplier quality problems can be caught before they become returns.
A short inspection step, checking for damage in transit, verifying the item matches the SKU, confirming count on inner packs, catches issues that would otherwise arrive as negative reviews weeks later. Where a supplier is new or has a history of variance, sample more heavily on the first few receipts and taper once performance is proven.
Record what you find. Supplier defect rates are negotiating leverage at reorder, and they are impossible to reconstruct after the fact.
Prep is a reasonable candidate for a 3PL when volume is uneven, when packaging supplies are consuming space you would rather use for stock, or when the requirements change often enough that keeping internal staff current is a job in itself.
The questions worth asking a prospective partner are operational, not commercial. Do they hold a documented prep spec per SKU, or do they rely on instructions in an email thread? Is prep scan-verified? What is their turnaround from receipt to marketplace-ready, measured in hours rather than described as fast? Who absorbs the cost when a shipment is rejected for a prep error, and how is that determined?
A partner who can answer those in specifics is running a process. A partner who answers in reassurances is running on memory, and memory does not scale into Q4.
Marketplace prep rewards boring consistency. The requirements are published, stable, and mostly unambiguous, which means every rejection is a process failure rather than bad luck. Put the spec in the system, verify it at the bench, measure the minutes, and photograph the reference unit. The operations that do those four things stop thinking about prep entirely, which is exactly the point.