Is kitting the right solution for a subscription-box or bundle-heavy Shopify brand, or does that belong on the subscriptions/bundles app side instead?
Physical 3PL kitting is the wrong tool for a subscription box whose contents change every cycle, and app-side bundle logic with a per-cycle pick list is the right one. Pre-kitting a box that changes monthly turns unsold kits into dead components. Shopify Bundles caps dynamic bundles at 150 components and is unsupported outside the Online Store and headless storefronts (Shopify Help Center, September 2026).
Draw the line at cycle length, not at volume
The useful question is not how many boxes you ship. It is how long a given box definition survives.
A box whose contents are identical for twelve months is a product with a bill of materials, and pre-kitting it is straightforward warehouse work. A box whose contents change every cycle is a recurring assembly project, and treating it as a stocked SKU means creating and retiring a SKU every month, each one carrying its own leftovers.
| Your box | Where the logic belongs | Where the labor belongs |
|---|---|---|
| Fixed contents, ships for many cycles | Native Shopify Bundles, free | Pre-kit in batches; this is real kitting |
| Fixed core plus one rotating item | App-side bundle with a component swap per cycle | Assemble-to-order, or pre-kit the core only |
| Contents change every cycle | App-side subscription plus a per-cycle pick list | Assemble-to-order from a dated build sheet |
| Subscriber chooses contents | App-side, mandatory. No warehouse can pre-guess it | Assemble-to-order, always |
Rows three and four are the common case for a curated box, and neither is a kitting problem. They are a "produce a correct pick list on a date" problem, which lives in your systems, not in your 3PL's shelving.
The platform constraint that decides this before you get to operations
Two documented facts settle most of the architecture.
First, "Bundles aren't compatible with the Shopify Subscriptions app" (per Shopify's Help Center, September 2026). The free native subscriptions app and the free native bundles app do not combine, so a recurring box cannot be built from Shopify's own two free pieces. A box program needs a paid subscription platform on the storefront side, and that is a decision with its own fee structure.
Second, Shopify Bundles "must use the Online Store or Headless storefronts. Other sales channels are unsupported," and it tracks stock by overall stock rather than by location (per Shopify's Help Center, September 2026). Wholesale and retail kit variants of the same box need their own path regardless of what your 3PL can do.
What the app layer actually gives a bundle-heavy brand
The apps that matter here are not kitting apps. They are SKU-breakdown apps: they let the storefront sell a bundle while the fulfillment system receives components it recognizes.
- Shopify Bundles (first-party, free, 2.8 stars across 575 reviews). Fixed bundles up to 30 components, dynamic up to 150, 3 options and 100 variants per bundle, no per-location stock.
- Simple Bundles & Kits from Freshly Commerce (free tier, then $14, $39 and $149 a month; 4.9 stars across roughly 791 reviews). Markets automatic bundle SKU breakdown and inventory sync across 3PL, WMS and ERP systems.
Both verified on their App Store listing and reviews pages, September 2026.
Note what neither does. Neither performs assembly. Neither reserves a component against a specific build. That layer lives in a warehouse system or in custom glue, which is why our kitting verdict is CUSTOMIZE rather than buy (Deploi verdict, September 2026): the merchandising is an app, the build is not.
When kitting genuinely is the answer for a box brand
Three cases, and they are narrower than the category implies.
- A fixed starter box that every new subscriber receives on cycle one. It ships for years, its contents are stable, and it is the best pre-kitting candidate most box brands own.
- A gift or seasonal edition with a known quantity, a hard sale window and a decided plan for leftovers before the first unit is assembled.
- A box with heavy assembly where the labor per unit is high enough that batching it changes your cost per order materially. Warehouse kitting labor benchmarks at $35 to $60 an hour, average $39 to $43 (The Fulfillment Advisor's 2025 survey of 600-plus warehouses, via Fulfill.com, cross-checked June 2026), so the batch saving is real when assembly is genuinely slow.
When NOT to put this on the 3PL
- When the answer to "what is in next month's box" is not yet known. You cannot kit an undecided product, and asking a 3PL to hold capacity for one is how you buy a minimum you do not use.
- When subscribers can swap or skip. Every swap invalidates a pre-built unit. This is the single strongest disqualifier and it is a storefront feature, not a warehouse one.
- When you are buying a warehouse platform to get kitting. Kitting is a module inside a broader system, not a product sold on its own. Cin7 Core starts at $349 a month with kits, bundles and bill of materials tracking included at its entry tier (per cin7.com, verified September 2026); ShipHero publishes no plan pricing at all and routes to a demo (verified September 2026). Buying either for one feature is the expensive path.
The Deploi point of view
Our own position, from building on Shopify. Separate from the facts above.
- Our take: For a box that changes every cycle, put the logic app-side and buy assembly labor by the hour rather than by the stocked SKU. The thing you actually need from your 3PL is a correct, dated build sheet at the pick face, not a finished-goods bin. We scored bundle inventory sync WAIT precisely because a second inventory source of truth is the cost that shows up later (Deploi verdict, August 2026).
- What we’ve seen: In five bundle builds, the recurring failure was the cutoff. Subscribers edit late, operations cut the pick list early, and the gap between those two dates is where the support tickets live. Pre-kitting widens that gap by however long the batch takes, which is the opposite of what a box program needs.
- Times we’ve shipped this: 5 builds delivered.
- What it takes: roughly 240 hours of scoped work for fixed bundles and kit merchandising (directional Deploi estimate from a small sample of engagements, not a measured average).
- Where we disagree: 3PLs pitch kitting to box brands as the natural fit, and it is the natural fit for exactly one box in the catalog: the fixed starter. The rest of the program wants flexibility, and flexibility is the one thing a stocked kit SKU removes.
- What this page adds: that cycle length rather than volume decides this, that native bundles and native subscriptions are documented as incompatible, and which two app-side products actually deliver the SKU breakdown a 3PL needs.
Reviewed by Martin Dejnicki, Director of SEO & AI Search. Facts verified 2026-09-13.