A product bundle, a gift set, a kit, a multi-pack assembled from components, is a promise about several stock counts at once. Its honest availability is the minimum available across every component, and its sale must decrement each of them. Systems that treat a bundle as just another SKU with its own independent count end up overselling either the bundle or the components it quietly shares stock with.
The two ways to run bundles
Pre-assembled (kitted) bundles. You physically build sets in advance; the bundle is its own inventory item with its own count. Honest, simple, and it LOCKS stock: units committed to kits cannot serve component sales. Right for genuinely manufactured sets and high-velocity kits.
Virtual (component-based) bundles. The bundle exists as a listing; stock stays with the components. Availability = min(component availability / quantity required), and a bundle sale decrements every component. Flexible, capital-efficient, and entirely dependent on the inventory layer doing the math continuously.
Most small sellers should default to virtual bundles: the same units serve both individual and bundle demand, and nothing is locked into a guess about which form buyers will choose.
The math that keeps bundles honest
For a bundle requiring 2x candle + 1x holder:
- Candles on hand: 10, holders: 3 = bundle availability = min(10/2, 3/1) = 3.
- A bundle sale decrements candles by 2 and holders by 1, and every channel’s numbers, for the bundle AND both components, update together.
- Buffers apply at the component level; the bundle inherits them through the min().
The failure modes are all violations of that arithmetic: a bundle with a manually set count drifting from component reality; a bundle sale decrementing only the bundle; components sold individually while the bundle count never notices. Each is an oversell with extra steps.
Bundles as strategy, not just packaging
- Order-value lift: sets price above their pieces’ psychological sum while discounting against the arithmetic sum, both sides feel the win.
- Clearance that preserves dignity: slow stock rides a fast mover out the door inside a set, without a naked discount on the struggling SKU.
- Fee efficiency on small items: marketplaces’ fixed fee components punish tiny orders; bundling lifts the base, the Etsy fee math makes this explicit.
- Gifting seasons: Q4 is bundle season structurally, plan the components as one buy.
Marketplace rules worth knowing
Bundles have platform-specific constraints: Amazon has explicit bundle policy (a bundle is its own product with its own identifier, not a multi-pack of an existing ASIN, and category rules apply); eBay and Etsy are more permissive but reward clear set titles and photos of exactly what arrives. Your bundle gets its own SKU everywhere (a BND- prefix keeps them findable), and the component mapping lives in your inventory layer, not in the listing copy.
Common questions
Can a component belong to several bundles?
Yes, that is virtual bundling’s point. Availability math runs per bundle over shared components, and every bundle’s advertised count moves when any of them (or the component alone) sells.
How do returns work for bundles?
Return the set, restock the components (inspected individually). Partial returns are a policy decision, decide before the first one, not during.
Do bundles complicate forecasting?
They enrich it: component demand = direct sales + bundle-driven draw. Days-of-cover on components should include bundle velocity, which component-based tracking gives you for free.
Should bundle pricing be rule-driven too?
Yes, bundle price relative to component sum is a strategy knob, and per-channel markups apply to bundles like any SKU, the pricing model.
Sets that never lie
Real-time sync across every channel from $49/month with unlimited orders, and component-mapped bundles with min() availability arrive on Plus. See pricing.