A subscription bundle is a single recurring delivery containing multiple products curated by the merchant. The customer subscribes to the bundle as one item, gets one charge per cycle, and one box arrives containing two, three, or more SKUs. It's different from build-a-box (where the customer assembles the contents themselves) and different from a multi-line subscription (where the customer subscribes to each product separately). Bundles are merchant-curated, sold as a unit, and priced as a unit. Done well they raise AOV, reduce decision fatigue at signup, and create natural cross-sell paths. Done badly they create inventory headaches, confuse the customer about pricing, and break when one component is out of stock. This guide walks through how to structure bundles on Shopify, how to price them so the unit economics work, how to handle mix-and-match rules, and how to operate them when a single SKU in a 4-SKU bundle goes out of stock.
Bundle vs build-a-box vs multi-line: pick the right pattern
These three patterns get confused constantly and they're not interchangeable. Picking the wrong one means rebuilding your entire subscription product later. Read the differences first.
A subscription bundle is merchant-curated. You define the contents. The customer subscribes to the bundle as a single SKU. Pricing is fixed per cycle. The customer can typically swap variants within rules you set, but they can't fundamentally change what the bundle contains.
A build-a-box is customer-curated. The customer picks N items from your catalog (often within a category like "pick 6 coffees from our 12 SKUs"). Each cycle they can re-pick. The price is typically fixed per box regardless of which SKUs they pick (within a tier). See our build-a-box guide for that pattern.
A multi-line subscription is just multiple individual subscriptions in one customer's portal. Each line has its own selling plan, its own price, its own cadence. There's no bundle — they're separate subscriptions that happen to belong to the same customer. Useful but operationally and pricing-wise it's not a bundle.
If your customers know what they want and you want lower complexity, bundle. If your catalog has variety and customers enjoy choosing each cycle, build-a-box. Bundles tend to have higher signup conversion (one decision to subscribe), build-a-box tends to have higher retention (engagement from each cycle's choice). Many mature subscription stores run both.
When subscription bundles actually fit
Bundles work best when the contents are genuinely complementary — items the customer wants together rather than in isolation. Coffee + filter + mug. Shampoo + conditioner + scalp treatment. Razor handle + 4 blade cartridges + shave gel. Each item amplifies the value of the others, and the bundle is more useful than the sum of its parts.
Bundles also work for routine completeness — "everything you need for [purpose]" framing. Pet care bundle (food + treats + toy). Skincare routine bundle (cleanser + serum + moisturizer). Cooking bundle (3 spices + cookbook + apron). The bundle removes decision fatigue for the customer and surfaces products they might not have added individually.
- Routine bundles — everything for a habit (skincare routine, coffee setup, supplement stack)
- Discovery bundles — sampler of 3-5 variants the customer hasn't tried (3 coffee origins, 4 tea blends)
- Tier bundles — small/medium/large versions of the same bundle for different consumption rates
- Themed bundles — seasonal or occasion-driven (summer skincare, holiday baking)
- Combo bundles — pairing a fast-consumed item with a slow-consumed item (coffee + filter)
The temptation is to bundle a popular product with a slow-moving one to clear inventory. Customers notice. If the bundle obviously exists to push the slow SKU, signup conversion drops and churn rises. Every item in a bundle should genuinely make sense alongside the others — the bundle has to read as a curator's pick, not a clearance.
How to structure a subscription bundle on Shopify
Shopify offers a native Bundles feature (via the Shopify Bundles app or Shopify's built-in bundles for some plans). For subscription bundles, you have two viable patterns: a single SKU bundle product that contains a list of component SKUs, or a multi-line selling plan that ships several SKUs together as one delivery.
The single-SKU bundle pattern is cleaner from a customer perspective — the customer sees one product, one price, one subscription line. Inventory is tracked as the bundle SKU, but you'll typically also deduct from the component SKUs at fulfillment time. Most modern subscription apps including SimpleSubscription support this natively.
- Create the bundle as a single product (or single SKU) with a clear name ("Morning Coffee Bundle — Coffee, Filter, Mug")
- Configure the bundle contents in your subscription app — list the component SKUs and quantities per cycle
- Set the bundle price (typically 10-20% less than buying components individually)
- Configure component inventory behavior — deduct from each component SKU on fulfillment, or track the bundle separately
- Decide swap rules — can customers pick a variant of each component, or is the bundle fixed?
- Test fulfillment: when the subscription renews, your fulfillment system needs to know to pull from all the component SKUs
Pricing the bundle: discount math that doesn't break margin
Bundle pricing is the trickiest part. Price too high and the bundle feels like a worse deal than picking items individually. Price too low and you're giving away margin to customers who would have bought multiple items anyway. The right price reflects the value-add of curation plus a modest discount for the bundle commitment.
A workable framework: take the sum of the individual item prices. Apply a 10-15% bundle discount (you're rewarding the customer for taking the curated set instead of picking individually). Then apply your usual subscription discount (10%) on top. The result is the subscribed bundle price — typically 20-25% off the list price of buying everything separately.
Example: a routine bundle of three skincare products at $30, $40, $25 individually = $95 list price. Bundle discount 12% = $83.60 bundle price. Subscription discount 10% on top = $75.24 subscribed bundle price. That's roughly $20 off the $95 list — meaningful enough to drive bundle signup, modest enough to preserve margin.
Don't stack too many discounts. Customers who see 30%+ off a bundle subscription wonder what's wrong with the product. A bundle that's 20% off list price reads as "good value, curated, worth the commitment." 40% off reads as either clearance or low-quality. Test pricing carefully — bundle discounts that feel too generous often signal-trap.
Mix-and-match rules: how much customization within the bundle?
Pure bundles (fixed contents, no customer choice) convert at the highest rate but churn faster — customers get bored of the same three SKUs every month. Pure customization (customer picks every item every cycle) is build-a-box, not a bundle. The middle ground — bundle with constrained customization — is where most successful programs land.
Define the constraints clearly. Coffee bundle: customer picks one variant of coffee from 4 options, but the filter and mug components are fixed. Skincare bundle: customer picks the scent (lavender, citrus, unscented) for all three products from a single dropdown. Variety pack: customer picks 3 of 6 available variants, no repeats. Each pattern is a bundle with rules, not a free-form box.
- Variant choice per component — customer picks the variant of each item (size, scent, flavor)
- Single dropdown — one choice affects all items ("choose your scent profile")
- Pick-N-of-M — customer picks 3 from 6 available, no repeats (variety packs)
- Tier upgrades — customer can upgrade the bundle tier (3-item to 5-item) but not the items themselves
- Add-on slots — fixed core bundle + 1-2 optional add-ons
If customers can swap 50%+ of the bundle contents each cycle, you've built a box, not a bundle. Box pattern has different economics (price-per-slot tiers, no component pricing), different operations (inventory must support flexible combinations), and different software (build-a-box widgets). If you find yourself wanting that much flexibility, switch to a box product and skip the half-built bundle.
When one component goes out of stock
This is the operational nightmare scenario for bundles. The bundle is in stock as far as the customer can see, but one of the three components is at zero. Your fulfillment system tries to ship and fails. The customer's card has been charged. What now?
Pick a policy before launch and configure your subscription app to enforce it. Three viable strategies, all worse than "keep components in stock" but you'll need one anyway because stockouts happen.
- Skip the cycle for affected subscribers — don't charge, push next renewal forward, email the customer ("we're restocking item X — your next bundle ships 2026-06-15"). Cleanest customer experience, no revenue this cycle.
- Substitute the component automatically — your app picks the next-closest variant or a defined substitute SKU and ships the bundle with the substitution. Email the customer about the swap. Requires a substitution mapping for every component.
- Notify the customer and let them choose — pause the renewal, email the customer with options (skip, substitute with [X], substitute with [Y]). Highest customer agency, highest support overhead, longest delay to delivery.
Most established bundle programs use strategy 1 (skip) for small components and strategy 2 (substitute) for variant-level swaps. Pure notify-and-pause has the worst churn impact because the delay and back-and-forth create exit ramps for indecisive subscribers.
- Each component has a defined stockout policy (skip, substitute with SKU X, substitute by category)
- Substitution mapping documented for every variant
- Email template for stockout notification — clear, honest, no spin
- Inventory monitoring alerts when component stock drops below 2 weeks of bundle demand
- Forecast bundle demand per component — a 1,000-bundle subscription base means the slowest-moving component still needs 1,000 units a month
The customer portal experience for bundle subscribers
Bundle subscribers manage more complexity than single-product subscribers. They have a bundle with multiple components, each potentially with variants, and they often want to tweak. A bundle subscription portal needs to surface the bundle contents clearly, let the customer modify within your defined rules, and give them visibility into what's shipping when.
The portal should let the subscriber see each component of their current bundle, swap a variant per component (if allowed), upgrade the bundle tier (if offered), skip a cycle, swap to a different bundle entirely, and pause/cancel. Hide the customizations behind the rules you've defined — don't let them swap to invalid combinations.
Importantly, the portal should also show the upcoming shipment preview: "your next bundle on 2026-06-01 will contain: coffee (Ethiopia, 12oz), filter (paper, white), mug (ceramic, white)." Bundle subscribers want to verify before each cycle. The transparency reduces support volume because customers can self-confirm rather than emailing.
- Display each component of the current bundle separately
- Allow variant swap per component within defined rules
- Allow tier upgrade or bundle swap (different bundle product entirely)
- Show next-shipment preview with the exact components and variants
- Skip / pause / cancel controls — same as single-product subs
- Cycle history — show what shipped in each past cycle so customers can re-order favorites
Marketing bundles: positioning that converts
Bundles sell differently from single products. The customer is buying a curated experience, not a product — and the marketing has to reflect that. Generic "3 items for $X" copy underperforms compared to specific framing around the customer outcome the bundle solves.
Use outcome-led names. "Morning Coffee Ritual" beats "Coffee + Filter + Mug Bundle." "Skincare Starter" beats "3-Product Skincare Bundle." The name carries the promise. Then in the product copy, surface why each component matters and why the curation creates more value than picking the same items separately.
- Outcome-led bundle names — describe the use, not the contents
- Curator framing — "our team picked these three because they work together"
- Component value — for each component, one sentence on why it matters
- Total value comparison — "buying individually: $95. Bundled: $75." Show the savings explicitly
- Social proof per bundle — testimonials specific to this bundle, not generic brand reviews
- Visual unboxing — show the contents arranged together, not just as a list
Many bundle product pages bury the bundle behind 5 individual product cards. Customers shopping for a bundle want to see the bundle — name, outcome, total price, contents in one view. Don't make them mentally re-assemble the offering from component pages. Build a dedicated bundle product page that treats the bundle as the primary unit.
Bundle subscription mistakes that kill the program
Bundle programs fail in patterns. Most failures are either operational (stockouts not handled) or product-design (bundle contents don't actually work together). Watch for these.
- Bundle contents don't make sense together — customers spot the inventory-clearance angle immediately, conversion drops, churn rises
- Bundle discount stacked with site-wide promotions — your 20% bundle discount + Black Friday 25% = subscriber locked at 45% off forever. Disable or revert.
- No stockout policy — first component shortage triggers a refund firestorm
- Too much customization — bundle becomes a half-built box without the build-a-box infrastructure
- Bundle price not visibly compared to component list price — customers don't perceive the discount, conversion suffers
- Portal hides bundle components — subscribers can't tell what's shipping, support tickets pile up
- One bundle SKU shared across many variants — inventory tracking breaks because Shopify can't see what's actually in stock
- Bundle launched without a non-subscription one-time option — customers want to try the bundle once before committing to recurring
Bundle subscription questions
How is a subscription bundle different from a build-a-box?
A bundle is merchant-curated — you define the contents and the customer subscribes to the bundle as a single SKU. A build-a-box is customer-curated — the customer picks N items from your catalog each cycle. Bundles have higher signup conversion (less decision fatigue). Build-a-box has higher retention (customer engagement each cycle). Many stores run both.
How do I handle inventory for a bundle?
Configure component-level inventory deduction in your subscription app. When the bundle renews, your fulfillment system pulls one unit from each component SKU. Track each component independently — never share inventory between a 'bundle SKU' and the individual product SKUs, that's how oversells happen.
What's a typical bundle discount?
10-15% off the sum of individual prices, then 10% subscription discount on top — total ~20-25% off list price. Less than 10% feels like no discount. More than 25% kills margin and signals desperation. Test against your actual margin.
Can I let customers swap components within a bundle?
Yes, within rules you define. Common patterns: variant choice per component (pick the size/scent/flavor of each item), single dropdown (one choice affects all items), pick-N-of-M (variety pack from a curated set). Don't let customers swap 50%+ of components — at that point it's a build-a-box, not a bundle.
What happens when one component of the bundle goes out of stock?
Configure a per-component stockout policy: skip the cycle for affected subscribers (don't charge, push the renewal forward), substitute with a defined replacement SKU, or notify and pause. Never charge for a bundle you can't ship complete — that's the fastest way to chargebacks.
Should I offer the bundle as a one-time purchase too?
Yes, almost always. Many customers want to try the bundle once before committing to a subscription. Offer one-time at full bundle price, subscription at the bundle + subscription discount. The one-time buyers often convert to subscribers within 2-3 purchases.
How do I price a tier upgrade within a bundle (small / medium / large)?
Price per unit of value, not per item. If your medium bundle has 3 items at $75 and the large has 5 items, the large should price at the marginal value of items 4 and 5 plus a small upgrade incentive — typically $115-125, not a strict 5/3 multiplier. The tier exists to capture customers with higher consumption rates, not to maximize price.
Do bundle subscribers have higher or lower LTV than single-product subscribers?
Usually higher AOV per cycle (multiple items per delivery), comparable or slightly lower retention (the additional complexity adds churn pressure if portal flexibility isn't strong). Net LTV is typically 1.5-2x a single-product subscription, but only if the bundle is genuinely useful — bundle-of-convenience customers churn fast.
Can I mix subscription products with one-time products in a bundle?
Technically yes (some apps support it), but the customer-experience cost is high. The customer sees a single subscription line that 'sometimes ships a one-time item, sometimes not,' which is confusing. Cleaner pattern: keep bundles fully subscription, offer one-time products as separate cross-sells in the portal.
How do I market a new bundle to existing single-product subscribers?
Email campaign offering an upgrade to the bundle at the prorated price. The customer's current subscription becomes the 'anchor' component of the bundle and they pay only the marginal price for the added components. Best run as a one-click upgrade in the portal so the friction is minimal.
Can I run seasonal or limited-time bundles?
Yes, and they can drive significant attention. Create a bundle product with a defined lifespan (e.g. 'Summer Skincare Bundle, available June-August'). Subscribers who joined during the season can continue at the same price after, or auto-rotate to a different bundle. Plan the rotation logic before launching the seasonal product — it's a question that surfaces fast.
What's the right number of components per bundle?
3-5 components is the sweet spot. Two components feel like a pairing, not a curated bundle. Six+ components overwhelm at signup and create more stockout risk per cycle. Three is the most common starting point — enough to feel curated, simple enough to manage.