Build or Buy Kitting at the Pick Face on Shopify?
Kitting at the pick face is a CUSTOMIZE on Shopify: no dedicated kitting app exists, and Shopify Bundles deducts component stock but tracks it by overall stock, never by location. Assemble-to-order lives inside a warehouse platform, where Cin7 Core starts at $349/month (verified Sep 2026). Build only the thin layer: component reservation and a build sheet on the pick ticket.
Your profile — see how the verdict shifts
- Confidence
- High — Searched the App Store for a dedicated kitting or work-order listing and found none. Assemble-to-order kitting exists only as a feature inside two warehouse-grade platforms: ShipHero documents Kits and Work Orders for build-at-pick assembly, and Cin7 Core documents bill of materials, multi-level assembly and a picking-for-kitting workflow. Read Shopify's own Bundles documentation the same day: fixed bundles are capped at 30 components, dynamic bundles at 150 with a maximum of 3 options and 100 variants, bundles are supported only on the Online Store and headless storefronts, and Shopify states plainly that bundles do not track inventory by location, only by overall stock. Merchandising is native; the physical build is not.
- Reference scenario
- $20M–$100M GMV · 800–2,500 orders a day · one or two fulfillment locations · 15–60 kit SKUs sharing components · agency dev bench · no full WMS in place yet
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Kits under 5% of orders, one location | WAIT | Shopify Bundles plus a printed build sheet covers this. A handful of kits a day does not justify a warehouse platform or a custom reservation layer. |
| Kits 5–25% of orders, one location | CUSTOMIZE | Bundles handles the storefront and the stock deduction; what breaks is two kits claiming the same component. Build the reservation ledger and the build sheet, and skip the platform. |
| Two or more locations, or a 3PL | BUY | Bundles tracks overall stock, not stock by location, so multi-location kitting has no native answer. A warehouse platform that already models components per site is the shorter road. |
| Kits are the core product (gift sets, subscription boxes) | BUY | When most of what ships is assembled, work orders, labor tracking and component forecasting are the business. Cin7 Core at $349–$1,199/month (verified Sep 2026) is cheap against a build of that scope. |
What Kitting at the pick face Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Operational efficiency | High | A build sheet with bin locations turns a multi-aisle hunt per kit order into one route and one assembly station, which is where the labor cost of kitting actually sits. |
| Revenue — direct | Medium | Assemble-to-order keeps a kit sellable while its components are in stock, instead of showing sold out because nobody pre-built the box. |
| Customer experience | Medium | Component-level pick verification stops the gift set arriving with the wrong shade or a missing part, which is the complaint kits generate most. |
| Data & insight | Medium | Component-level demand tells buyers what to reorder when the same part sits inside six kits and three standalone SKUs. |
Spend ceiling: Pay for the physical build, not the merchandising, because Shopify Bundles already sells the kit for free on every plan. Size the spend against labor per kit order times daily kit volume, and stop well short of a warehouse platform unless a second location is in play.
What buying enables (top apps)
- + Real work orders with build-to-order assembly at pick and pack time, documented in ShipHero's help center
- + Multi-level assembly and bill of materials in Cin7 Core, including a picking-for-kitting workflow for assembling at pick time
- + Component stock modeled per warehouse, which Shopify Bundles does not do at all
- + Labor and production scheduling around builds, for merchants where assembly is most of the day's work
What building additionally unlocks
- + Component reservation against in-flight orders, so two kit orders cannot claim the same unit between sale and pick
- + A build sheet shaped to your actual pick path and station layout rather than a vendor's generic work order
- + Component demand history kept inside Shopify, feeding purchase orders without an export from a warehouse platform
Find Your Verdict in 3 Questions
Do you already run a warehouse platform such as ShipHero or Cin7 Core?
Yes: Your verdict: BUY — kitting is already in the licence; turn on work orders or assembly before you scope any custom work.
No: Go to question 2.
Can more than one location fulfill the same kit?
Yes: Your verdict: BUY — Shopify Bundles tracks overall stock rather than stock by location, and no native path closes that gap.
No: Go to question 3.
Do several kits share the same components, with kits above roughly 5% of daily orders?
Yes: Your verdict: CUSTOMIZE — keep Bundles for merchandising and build the reservation ledger and build sheet ($15,000–$40,000, Deploi estimate, illustrative).
No: Your verdict: WAIT — Bundles plus a printed build sheet is enough until kit volume or component sharing grows.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A warehouse platform is a 6–16 week implementation touching every SKU and every process; the glue layer is an estimated 5–9 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Cin7 Core runs $349–$1,199/month (verified Sep 2026) and ShipHero quotes by demo; a Bundles-plus-glue path adds no subscription line at all. | ||
| Maintenance & upgrades | The platform vendor maintains the assembly engine; a custom reservation ledger needs care whenever you add a location, a channel or a component-sharing kit. | ||
| Switching & exit | A warehouse platform becomes the system of record for stock, so leaving means re-cutting inventory truth; a glue layer leaves Shopify as the record and can be deleted. | ||
| Risk | |||
| Vendor risk | Neither listing is a kitting product: ShipHero carries 4.3★ across 115 reviews and Cin7 Core 4.6★ across 49, so you are buying a platform and hoping its assembly module fits. | ||
| Security & compliance surface | A warehouse platform reads and writes your full order and inventory graph; a reservation ledger touches only component quantities and pick documents. | ||
| Platform-deprecation exposure | Bundles is first-party and stable, but its component caps and lack of location tracking are product limits you cannot appeal, and both lanes inherit them. | ||
| Value | |||
| Fit to requirement | Work orders and multi-level assembly are exactly the requirement; a custom layer fits your pick path precisely but stops short of labor tracking and production scheduling. | ||
| Time to market | Neither lane is fast: a platform rollout and a reservation build both land in the same quarter, which is why the choice turns on scope rather than speed. | ||
| Performance & scale | Warehouse platforms are built for thousands of daily picks across sites; a bolt-on ledger holds fine at one location and strains at three. | ||
| Data ownership & AI-readiness | The decisive dimension for single-site merchants: component-level demand and build history stay in Shopify, feeding buying decisions without an export request. | ||
| Focus & opportunity cost | Nobody should write a warehouse platform, but a reservation ledger is a two-month project that removes a daily source of mis-picks. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Shopify Bundles | Native — First-party and free; fixed, merchant-curated combos only, no AI assembly (per July 2026 research) | Free (verified Sep 2026) | The merchandising and stock-deduction half of a kit, on one location |
| ShipHero Inventory & Shipping | Live — 4.3★, 115 reviews. Not a kitting app: a full warehouse platform whose help center documents Kits, kit creation and editing, and Work Orders for build-to-order assembly at pick and pack time. Free to install, with additional charges applying. | Pricing not listed; the listing directs you to book a demo with sales (verified Sep 2026) | Merchants who need real work orders and are already replacing their warehouse system |
| Cin7 Core | Live — 4.6★, 49 reviews; listed under its legacy DEAR Inventory slug; no Built for Shopify badge | Standard $349/month (5 users, 2 integrations, 6,000 sale orders a year, unlimited locations), Pro $599/month (10 users, 4 integrations, 24,000 orders, material requirements planning), Advanced $1,199/month (15 users, 6 integrations, 120,000 orders, advanced warehouse management); annual billing saves 8%; 14-day free trial (verified Sep 2026) | Multi-level assembly and component forecasting when kits are most of what you ship |
| Component reservation layer (custom) | Build lane — The gap between the two lanes above: a reservation ledger that stops two kit orders claiming the same component, plus a build sheet on the pick ticket and location-aware component counts that Bundles does not keep. | $15,000–$40,000 one-time, plus upkeep (Deploi estimate, illustrative) | Single-location merchants who want assemble-to-order without adopting a warehouse platform |
The Build Path
- Component reservation ledger: A reservation record written when a kit order lands, holding each component quantity against that order until the build is confirmed. Shopify Bundles deducts on sale but does not reserve components against an in-flight pick, which is how two kits end up short one part on the same afternoon.
- Build sheet on the pick ticket: The pick document renders the kit's components with bin locations, quantities and the assembly sequence, so the picker walks one route and assembles at the station rather than hunting parts per order. This is the difference between kitting slowing a pick path and barely touching it.
- Location-aware component stock: A per-location component count maintained alongside Shopify's overall bundle stock, since Shopify states bundles track overall stock rather than stock by location. Needed the moment a second warehouse or a retail backroom can fulfill the same kit.
- Effort band
- $15,000–$40,000 for the reservation ledger, build sheet and location-aware counts — Deploi estimate (illustrative); lands in the $25–75K contact-form band
- Typical timeline
- 5–9 weeks, longer where a 3PL's system has to accept the build sheet (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $2,200–$8,000/yr (Deploi estimate, illustrative) to keep reservation logic correct as kits share more components, absorb Admin API version changes, and re-test whenever you add a fulfillment location.
- What you own — and what you take on
- You own: the reservation logic, the build sheet layout, component-level demand history and the pick path it produces. You take on: correctness under concurrency, which is the hard part, and the reconciliation job when a build is abandoned mid-pick.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $6,000–$25,000 | $15,000–$40,000 |
| Years 1–3 (recurring) | $12,600–$21,600 | $6,600–$24,000 (upkeep) |
| 3-year total | ≈$18,600–$46,600 | ≈$21,600–$64,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: Cin7 Core Standard to Pro pricing (verified Sep 2026) plus an implementation partner; ShipHero excluded because it publishes no plan price.
- † Build column: Shopify Bundles for merchandising plus a custom reservation ledger, build sheet and location-aware counts; three-year horizon.
What the Sticker Price Hides
On the buy path
- — Buying a full warehouse platform to get one feature: kitting is a module inside ShipHero and Cin7 Core, not a product either sells on its own
- — ShipHero publishes no plan pricing, so the real number arrives only after a demo cycle (verified Sep 2026)
- — Implementation is the hidden line: re-cutting every SKU, bin and process usually costs more than the first year of subscription
- — Once the platform owns inventory truth, Shopify becomes a downstream consumer, and that is hard to reverse
On the build path
- — Concurrency is the whole risk: two kit orders reserving the same component is a race condition, not a UI problem
- — Bundles caps at 30 components for fixed bundles and 150 for dynamic ones, and those caps apply to the build lane too
- — Bundles is unsupported outside the Online Store and headless storefronts, so wholesale and POS kits need their own path
- — ~$2,200–$8,000/yr upkeep (Deploi estimate, illustrative)
What Merchants Say
Operations leads describe the same trade: pre-kitting a gift set ties up cash and a shelf, while building it to order sends a picker across three aisles for one line item.
The recurring low-star theme on inventory platforms is the rollout rather than the features: months of setup, and a period where two systems disagree about what is on hand.
If You Change Your Mind Later
If you bought and outgrow it
A warehouse platform becomes the system of record for stock, so leaving means deciding which system is right about every SKU on the day you cut over. Export component definitions, bills of materials and on-hand counts before you give notice, and plan a physical count for the switchover week rather than trusting either system's numbers.
If you built and want out
Nothing strands, because Shopify stays the system of record throughout. Reservations, build history and component counts live in metaobjects and metafields you can export or hand to a warehouse platform later as its opening balances. Deleting the layer leaves you exactly where Shopify Bundles alone would have left you.
When This Answer Changes
We're watching for:
- ▸ Shopify Bundles adding inventory tracking by location (bundles track overall stock only as of September 2026)
- ▸ Shopify Bundles becoming supported on sales channels beyond the Online Store and headless storefronts
- ▸ A dedicated kitting or work-order listing appearing in the App Store instead of kitting living inside full warehouse platforms
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Does Shopify Bundles support kitting at the pick face?
Shopify Bundles does not support kitting at the pick face. Bundles creates fixed, pre-defined bundles from the admin on every Shopify plan, capped at 30 components for fixed bundles and 150 for dynamic ones, and deducts component stock when the bundle sells. Shopify's documentation states bundles do not track inventory by location, only by overall stock (verified Sep 2026).
Which Shopify apps actually do assemble-to-order kitting?
Two warehouse-grade apps do assemble-to-order kitting: ShipHero, through Kits and Work Orders, and Cin7 Core, through bill of materials, multi-level assembly and a picking-for-kitting workflow. Neither is a kitting app. Both are full inventory platforms priced accordingly: Cin7 Core runs $349 to $1,199 a month across three tiers, and ShipHero quotes only after a demo (verified Sep 2026).
When is pre-kitting cheaper than building at the pick face?
Pre-kitting wins when a kit sells predictably and its components are cheap to hold. Building at the pick face wins when components are expensive, shared across several kits, or seasonal, because unsold pre-built kits freeze both cash and shelf space. The crossover sits where a kit's weekly velocity stops covering the 14 days of component inventory you tie up to keep it built.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Map every kit to its components and mark which components appear in more than one kit
- Measure kit orders as a share of daily volume, and count how often a shared component runs short
- Build the reservation ledger first, since concurrency is the failure everyone else papers over
- Render components, bin locations and assembly order onto the pick ticket, then time a picker against the old path
- Check the 30-component fixed and 150-component dynamic Bundles caps against your largest kit before you commit
If you're going with BUY
- Ask each vendor to demo assembly against your three most complex kits, not a sample catalog
- Get ShipHero's number in writing early, since the listing publishes no plan pricing (verified Sep 2026)
- Price implementation separately from subscription; the rollout usually costs more than year one
- Decide explicitly which system owns inventory truth after go-live, and write it down
- Plan a physical count for cutover week rather than trusting either system's opening balance
Official Docs & Sources
- Shopify Bundles — Shopify Help Center
- Build bundles (Shopify dev) — shopify.dev
- Locations — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Build or Buy Assortment Planning and Open-to-Buy on Shopify?
Stocky ended 2026-08-31 with no native open-to-buy replacement, and the apps that name OTB carry 12, 0 and 7 reviews. Build the planning model on data you own.
Build or Buy Inbound PO Email and PDF Capture on Shopify?
Two young apps parse emailed and PDF purchase orders into Shopify draft orders, capped near 100 a month. Above that, buy extraction and build the mapping layer.
Build or Buy Order Merge and Consolidation on Shopify?
Two Built for Shopify apps merge same-customer orders for a few dollars per merge; nothing native does. Buy, and build only a hold window ahead of your 3PL feed.
Build or Buy Packing Verification and Mis-Ship Prevention on Shopify?
The two purpose-built scan-verification apps carry 0 and 8 reviews. A scan-to-verify pack station is a bounded build for merchants packing in-house without a WMS.
Should You Build or Buy Your NetSuite Integration on Shopify?
NetSuite integration is the honest DEPENDS: buy a connector for standard flows, build middleware when the flows are the business.
Make kitting stop slowing your pick path
Shopify Bundles sells the kit. It will not reserve a component, print a build sheet or count parts per location. We build the layer between Bundles and your warehouse floor, so assemble-to-order costs one extra station instead of an extra platform.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.