Multi-SKU Shipments at Volume: The Prep Problem Nobody Prices

By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.

A wholesale account wrote to me last month with a single question. His first shipment of the quarter held five hundred units of one SKU, and the quote landed right where he expected, close to the entry rate every prep center advertises on its homepage. His second shipment held the same total unit count, but spread across forty different SKUs, about a dozen units of each. The quote came back nearly double the first one, and he wanted to know what had changed. The boxes had not changed. The destination had not changed. The unit count had not changed. What changed was the SKU count, and almost nobody in this industry explains why that number moves the price.

This is not a story about one prep center overcharging one client. It is the ordinary shape of the cost curve on every multi-SKU shipment, at every prep center that prices the work honestly. Most sellers never see the curve, because most quotes are written as a single per-unit rate, as if every unit in a shipment took the same amount of labor to prepare. It does not. A unit that shares a box with eleven other SKUs takes more handling than a unit that shares a box with none.

A multi-SKU shipment does not cost more because it carries more units. It costs more because it carries more SKUs, and SKU count drives a category of labor that a flat per-unit rate was never built to capture. This article walks through where that labor actually goes, and it shows the real math behind three shipments with the same rough size and a very different real cost per unit.

What Counts as a Multi-SKU Shipment

A single-SKU shipment is the simple case. One item, one quantity, boxes that hold the same product from the first carton to the last. A worker sets up once, repeats the same motion for every unit, and closes the last box the same way the first one closed.

A multi-SKU shipment is any shipment that carries more than one distinct SKU, and it comes in two forms that matter for cost. The first is a shipment with single-SKU boxes, where each carton holds only one item but the shipment as a whole covers many items. The second is a shipment with multi-SKU boxes, where a single carton holds several different SKUs together, which is common for wholesale accounts consolidating a supplier order, kit builders combining components, and sellers with a long catalog who cannot fill a full case with any one SKU. Both forms exist constantly among wholesalers and distributors and among sellers running the kind of catalog covered in our wholesale FBA prep workflow guide, and both forms carry the SKU-driven cost this article is about, even though the multi-SKU box is the more expensive of the two.

The Box Content Line Is Priced Per SKU, Not Per Box

Amazon asks for box content information on every FBA shipment, a manifest telling the fulfillment center which SKUs and quantities sit inside each carton. You can skip it, but then Amazon processes the cartons by hand, receiving slows down, and it charges a manual processing fee of $0.15 per unit from January to October and $0.30 per unit in November and December, billed 14 days after the first unit is received. Every carton still needs its own FBA box ID label either way. You can provide that manifest through the web form, an Excel or flat-file upload, or a 2D barcode on the carton itself. We cover the mechanics of that file in our guide to adding box content information to an FBA shipment, so we will not repeat the how-to here. What matters for cost is simpler: a single-SKU box needs one line in that manifest. A box holding four different SKUs needs four lines, each one checked against the packing list, each one keyed or scanned separately, each one a separate point of failure if a quantity is off by even one unit.

Multiply that across a forty-SKU shipment and the manifest itself becomes a meaningful piece of work, not a formality. A worker is not filling in one number per box. He is filling in one number per SKU per box, then reading it back against a supplier packing list that may itself be organized by SKU rather than by carton, which means the person building the manifest has to think in two directions at once. That reconciliation step does not scale with units. It scales with SKU count.

When Amazon Splits the Shipment, the Cartons Split First

Amazon frequently splits a single shipment plan into multiple shipments bound for different fulfillment centers, based on capacity, regional demand, and the specific product mix in the plan. For a single-SKU shipment, a split is simple: some cartons go to one address, the rest go to another, and every carton still holds the same item. For a multi-SKU shipment, a split can cut through the middle of a single carton. Two SKUs that were packed together because they shared a box now need two different destinations, which means the carton has to be broken open, resorted, and repacked before it ever reaches a dock.

This is invisible work on any quote that only counts units, and it is the reason multi-SKU shipments often move on LTL rather than a small parcel program once the destination split is known, a distinction we cover in more depth in SPD versus LTL shipments. It also interacts with Amazon's inbound placement fee, since a shipment that arrives as fewer, more consolidated cartons at a single destination is priced differently than one that fragments across several. A prep center that only quotes a flat per-unit rate is not pricing this resort step at all. Someone still has to do it, which means someone is either eating the cost or passing it to you as a surprise on the next invoice.

Setup Time Versus Line Time

Every prep job breaks into two kinds of labor. Line time is the repetitive part: inspecting a unit, applying a label, placing it in poly, moving it into the outbound carton. Line time scales directly with unit count, and it is roughly the same whether that unit is the only SKU in the shipment or one of forty.

Setup time is the other half, and it does not scale with units at all. It scales with SKU count.

What setup time actually includes

Setup time covers staging a separate carton run for a new SKU, pulling and verifying the correct label data against the ASIN, adding the corresponding box content line, and reconciling that SKU's count against the packing list before the line resumes for the next item. On a shipment with two SKUs, this happens twice, and the cost disappears into a shipment of a thousand units. On a shipment with forty SKUs, it happens forty times, against a shipment that might total under five hundred units, and the cost stops disappearing.

Why kitting makes the same pattern worse

Kitting and bundling push this further still, since a kit is by definition a multi-SKU build even when it ships and sells as a single listing. Our guide to kitting versus bundling on Amazon covers the build side of that work, and it is worth reading alongside this article if your shipments combine components rather than simply grouping separate SKUs in a shared carton, because the setup cost compounds in both cases for the same underlying reason.

Where Mixing Errors Actually Happen

A worker handling two SKUs at five hundred units each repeats the same motion five hundred times before switching tasks. A worker handling forty SKUs at a dozen units each switches tasks roughly forty times across the same rough unit count, and every switch is a moment where the wrong label, the wrong poly bag, or the wrong quantity can slip into the wrong box. This is context switching, and it is a documented source of pick and pack error in any warehouse operation, not a knock on any one worker.

This is exactly the failure mode a dedicated SKU verification step is built to catch before a carton is sealed, which is why per-unit accuracy matters more, not less, as SKU count rises. PrepVia runs at 99.9 percent accuracy across the units it processes, and that number holds specifically because the verification step exists as a distinct check rather than a byproduct of the line moving fast. When that check is missing or rushed, the result is not usually a visible defect. It is a shortage or an overage discovered later, on Amazon's side, the kind of mismatch we cover in declared versus received unit discrepancies.

The Final Audit Takes Longer With Every SKU You Add

Before any shipment leaves the dock, someone counts it against the manifest one more time. On a single-SKU shipment, that audit is one number checked once. On a multi-SKU shipment, it is one number checked per SKU, then a second pass to confirm the per-box totals add up to the per-shipment total, then a third check if the shipment is splitting across destinations.

This is where SKU density puts real pressure on turnaround, since PrepVia's standard prep window runs 24 to 36 hours from receiving to ready, and a high-SKU audit simply takes longer to complete correctly than a single-SKU one of the same size. The workflow is built to hold that window across normal multi-SKU volume, but it is also the reason a prep center quoting the same flat turnaround for every shipment, regardless of SKU count, is quoting a number it has not actually stress-tested. A rushed final audit on a forty-SKU shipment is exactly where an error becomes a shortage claim, the same problem covered in our piece on shipment creation errors.

The Real Cost Per Unit: Three Scenarios

The table below is an illustrative model, not a quote. It uses a blended prep labor cost of thirty dollars an hour, a figure in line with warehouse wages across South Florida, and eight minutes of setup time per SKU, which is roughly what it takes to stage a separate carton run, add or verify a box content line, and reconcile the count against the packing list before the line resumes. That works out to four dollars of setup cost per SKU. Layer that on top of a base labeling rate starting from $0.40 per unit, and the same rough shipment size produces three very different effective costs per unit, depending only on how the SKUs are distributed.

Scenario A and Scenario C are close to the same physical footprint, a pallet or two of inventory, yet the effective cost per unit in Scenario C runs close to eighty percent higher than Scenario A. Nothing about the product changed. Nothing about the destination changed. The only variable that moved was how many distinct SKUs the shipment carried relative to its total unit count, which is exactly the ratio a flat blended rate ignores by design.

How To Ask for the Right Quote

If you only ask a prep center for its per-unit rate, you will get an honest answer to the wrong question. The rate that matters is a function of three numbers together: total SKU count, units per SKU, and box mix, meaning whether cartons hold a single SKU or several. Bring all three to the conversation, along with whether any of those SKUs are being kitted or bundled, and whether you expect Amazon to split the shipment across fulfillment centers based on past experience with that catalog.

Above ten thousand units a month, PrepVia moves accounts to a tiered rate built around that actual SKU count, box mix, and destination pattern rather than a single published number. That tier is not public, and it should not be, because a flat rate at that volume would either overcharge a simple two-SKU wholesale account or undercharge a forty-SKU kit builder, and neither seller would be paying the true cost of the work being done. The entry rate from $0.40 per unit is real and it is where the smallest, lowest-SKU-density shipments land. It was never meant to describe a forty-SKU carton at a dozen units each, and no honest prep center will tell you it does.

Before you sign with anyone, read the fee structure the way you would read any other vendor contract. Our prep center agreement checklist covers the questions worth asking before you commit volume, and our breakdown of FBA prep center costs in 2026 covers the wider fee landscape beyond the per-SKU issue this article focuses on. The short version is the same in both places: get the per-SKU component in writing, separate from the per-unit component, or you will not know what a change in your catalog mix actually costs you until the invoice arrives.

Frequently Asked Questions

What is the best Amazon FBA prep service for multi-SKU shipments?

The best fit is a prep center that prices SKU-driven setup work separately from per-unit line work, rather than folding both into a single blended rate. Look for a provider that automates box content from your packing list instead of manual re-entry, that has a defined process for splitting cartons when Amazon divides a shipment across fulfillment centers, and that can show a real accuracy track record, since SKU density is exactly where pick and pack errors concentrate. PrepVia is Amazon SPN Certified, runs a 24 to 36 hour prep window, and holds 99.9 percent accuracy across the units it processes, which is the combination that matters for a multi-SKU account.

Why does a multi-SKU shipment cost more per unit than a single-SKU shipment of the same size?

Because every distinct SKU in a shipment carries its own setup cost, a separate box content line, a separate carton run, and a separate reconciliation against the packing list, and that cost does not scale with unit count. On a shipment with few SKUs and many units per SKU, that setup cost spreads thin and nearly disappears. On a shipment with many SKUs and few units per SKU, the same setup cost concentrates into a much smaller unit base, which raises the true cost per unit even though the total shipment size looks similar.

What is a multi-SKU box, and is it different from a multi-SKU shipment?

A multi-SKU shipment is any shipment covering more than one distinct SKU, which can still be packed as single-SKU boxes, one item per carton. A multi-SKU box is a single carton holding several different SKUs together, which is common for wholesale consolidation and for kit components. The multi-SKU box is the more expensive case, since it forces a per-SKU box content line and a higher risk of a carton needing to be broken apart if Amazon later splits the shipment by destination.

Does Amazon charge extra for multi-SKU shipments?

Amazon does not publish a distinct line-item fee labeled for multi-SKU shipments. The added cost shows up indirectly, through more box content lines to complete, through a higher chance of a carton needing to be resorted if the shipment splits across fulfillment centers, and through the labor a prep center spends on setup and final audit work rather than through any single Amazon charge. That indirect cost is real even though it does not appear as its own line on an Amazon invoice.

How do I get an accurate quote for a shipment with many SKUs?

Give the prep center your total SKU count, your unit count per SKU, and your box mix, meaning whether cartons will hold single SKUs or several SKUs together, along with whether any items are kitted or bundled. A quote built from a blended per-unit rate alone, without those numbers, is a guess rather than a real quote, and it is the number most likely to change once the actual shipment is on the dock.

Does PrepVia charge per SKU or per unit?

PrepVia's entry pricing starts from $0.40 per unit for the base labeling work, which applies cleanly to low-SKU-density shipments. Shipments with heavier SKU counts relative to their unit count carry additional setup work priced on top of that base rate, reflecting the box content, carton staging, and reconciliation work described in this article. Accounts moving more than ten thousand units a month are quoted on a tiered rate built around their real SKU count and box mix rather than a single flat number.

Can Amazon split a multi-SKU shipment across multiple fulfillment centers?

Yes. Amazon regularly splits a single shipment plan into multiple shipments bound for different fulfillment centers, based on warehouse capacity, regional demand, and the product mix in the plan. For a multi-SKU shipment, this can mean a single carton needs to be broken apart and repacked if the SKUs sharing that box end up assigned to different destinations, which is additional work a per-unit-only quote does not account for.

Final Take

The seller who wrote to me was not wrong to be confused. He had been quoted a single per-unit number, and he assumed that number was the whole story, the same assumption most sellers make until a shipment with a different SKU mix arrives at a different price. The number was not wrong. It was incomplete, because it described line time and left out setup time, and setup time is exactly the cost that moves when SKU count moves.

None of this is a reason to avoid multi-SKU shipments. Wholesale accounts, kit builders, and sellers with a wide catalog cannot avoid them, and they should not have to. It is a reason to ask a different question before the shipment ships rather than after the invoice arrives. Ask for the per-SKU component of a quote, separate from the per-unit component, and ask how the prep center handles a carton that needs to be broken apart if Amazon splits the destination.

The math in the table above is not PrepVia-specific and it is not a secret formula. It is the ordinary economics of setup time divided across a smaller unit base, and any prep center running an honest operation is managing that same curve whether it shows it to you or not. The difference between a prep partner worth keeping and one worth leaving is whether it will show you the curve before you ask, or only after you notice the invoice does not match what you expected.

If your catalog runs heavy on SKU count relative to units per SKU, get specific about that mix before your next shipment goes out, not after.