Bundles vs Volume Discounts: Which to Run

Look at the last hundred orders for your best selling product. Count how many contained that product and nothing else, then count how many contained two or more units of it. Those two numbers are the entire argument.

Most stores reach for a discount ladder because it is the easier thing to configure, then wonder why revenue looks flat three months later. The units went up. The orders did not. Bundles vs volume discounts is not a preference question, it is a question about what your catalogue can honestly offer and how often your customers come back on their own.

Both mechanics put more into a single order. Only one of them creates demand that did not exist. Getting that backwards is expensive, and the damage takes a full purchase cycle to show up in your reports.

What problem is each offer actually built to solve?

A bundle solves a choosing problem. The shopper knows they want the coffee, they have not thought about the grinder, and asking them to evaluate the grinder as a separate purchase means most of them never will. The bundle makes it one decision instead of two, and the discount is only there to make the decision feel resolved.

A quantity tier solves a timing problem. The shopper already wants the coffee. They will want more coffee in six weeks. The tier gives them a reason to buy that future bag now, while their card is already out.

• Different customer states. A bundle targets someone who has not considered the second item. A tier targets someone who has already priced the item and is only deciding how much.
• Different failure modes. A bad bundle gets ignored, which costs you the discount only on orders that convert. A bad tier gets accepted enthusiastically, which is worse.
• Different catalogue requirements. Bundles need genuine companions. Tiers need a product with a real consumption rate.

If your catalogue is one hero product with no natural companion, the bundle is not available to you and the tier is the only honest option.

Which one widens the basket, and which one only pulls demand forward?

This is the split that decides most cases, and it is easiest to see in a table.

The row that matters is the third one. A bundle adds a line to an order and leaves the customer's future behaviour untouched. A quantity tier borrows from a purchase you were going to get anyway, and the loan comes due on the date they would otherwise have reordered.

That does not make tiers bad. Pulling demand forward is valuable when it clears seasonal stock or moves a customer past a shipping threshold you are already paying for. It is only bad when you count the pulled-forward revenue as growth.

How do the per-order costs differ once shipping and pick-pack are counted?

Unit economics change the answer more than most merchants expect, because the two mechanics load your warehouse differently.

A quantity tier is usually the cheaper of the two to fulfil. It is the same SKU, the same pick face, often the same outer carton. Your picker touches one location. A bundle of three different products means three pick locations, three chances of a mispick, and frequently a larger box.

• Pick and pack. Cost scales with distinct SKUs far more than with units. Six of one thing is cheap. One each of six things is not.
• Shipping bands. Adding a second unit of a dense product can tip you into the next weight band and quietly eat the whole discount. Adding a light accessory often does not.
• Free shipping thresholds. Both offers can lift an order over the line. Extra costs at checkout are the most cited abandonment reason during checkout, at 40 percent Baymard, so clearing that threshold is worth real money on its own.

What does your repeat-purchase cadence tell you about which to run?

Cadence is the best predictor here, and you already have the data. Pull your orders for one product, group by customer, and look at the median gap between first and second purchase. That number tells you which mechanic your catalogue is asking for.

• No second purchase for most customers. Your product is durable or one-off. A quantity tier has nothing to pull forward. Bundle it with a companion.
• A tight, predictable gap. Consumable with a real burn rate. A tier is genuinely useful to the customer and cheap for you to fulfil.
• A tight gap with strong retention already. Be careful. These customers were going to reorder anyway, and a tier hands them a discount for behaviour you already had.

The awkward truth is that the customers most likely to accept a quantity tier are your best ones. That is not a reason to skip it, but it is a reason to gate it: offer the ladder to first-time buyers and lapsed customers, and leave your steady reorderers alone. If retention is already the strong part of your store, read our cart abandonment breakdown before you assume a discount is the missing piece.

When does a volume discount cannibalise revenue you already had?

Cannibalisation is not an edge case with quantity tiers. It is the default state, and the only question is what share of the gain it eats.

The pattern is always the same. Week one looks like a win, because everyone who was about to buy takes the ladder. Weeks two through eight look flat. Then the reorders do not arrive, and the flatness turns into a dip exactly one cycle out from launch.

Watch for these signals specifically:

• Units per order up, orders per customer per quarter down. The clearest tell there is.
• A tier that almost everyone takes. If your two-unit tier has a very high take rate, the discount is not changing behaviour, it is just cheaper pricing.
• The dip lands one median cycle after launch. If it does, that is cannibalisation, not seasonality.

The fix is rarely to kill the tier. It is to move the first rung further from normal behaviour. If most customers already buy two, the two-unit tier is a giveaway and the ladder should start at three.

Can you run both at once without them fighting in the cart?

Yes, and on most catalogues you should, because they address different products. The failure is never the strategy. It is the cart.

Two things go wrong. Offers stack, so a shopper who qualifies for both gets two discounts on overlapping lines. Or they compete, and the shopper sees two prices for a similar basket and trusts neither.

Set these rules before you publish anything:

1. Decide precedence in writing. One offer wins per line item. Usually the better deal for the shopper, which is also the one that will not generate a support ticket.
2. Keep the eligible product sets separate where you can. A product in a bundle should not usually be the same product carrying a quantity ladder.
3. Never let a site-wide sale code stack on either. Test this on a draft order before your busiest weekend, not during it.
4. Show one saving in the cart. A single clear line the shopper understands beats two they have to add up.
5. Test the overlap case deliberately. Build the exact basket that qualifies for both and check the total by hand.

If the same product genuinely needs both, run them at different quantities: the bundle at one unit plus companions, the ladder starting at three. They stop competing when they occupy different parts of the ladder.

Which should you launch first, and how will you know you chose right?

Launch the bundle first, in almost every case. It is the lower-risk experiment. If shoppers ignore it, you lose nothing but the build time, because the discount only applies to orders that took the offer. A quantity tier that lands badly costs you margin on demand you already owned, and you will not see the bill for a full cycle.

Then judge it properly:

1. Fix a baseline. Record margin per order and orders per customer per quarter for the four weeks before launch.
2. Run one offer at a time. Two launched together are uninterpretable.
3. Watch margin per order, not order value. Order value going up while margin per order stays flat means you moved money, not made it.
4. Wait one median repeat cycle past launch. Two if your cadence is long.
5. Check the cohort, not the day. Compare the customers who took the offer against those who did not, over the same window.

If the bundle works, the second product often becomes a repeat line of its own, and you have widened the catalogue rather than discounted it. That is the outcome worth chasing. The pillar on Shopify product bundles covers which bundle shape to build once you have decided a bundle is the right mechanic.

Where does Edge Bundles fit when you run both side by side?

Edge Bundles is our own app, and it is new, so take this as a description of what it does rather than a claim about how many stores rely on it.

It builds fixed sets, mix and match, and quantity tiers from the same rules engine, which matters for the precedence problem above: one place decides which offer applies to a line, so a shopper cannot silently take two. Bundles draw down component stock rather than holding their own inventory number, so a bundle sale and a single-item sale cannot drift apart. There is a free plan. Edge Bundles on the Shopify App Store

Pricing and features checked on 22 August 2026. App Store listings change without notice, so verify on the listing before you commit to a plan.

Be honest about when you do not need us. If you run one consumable product and want a simple three-tier ladder, Shopify's native quantity rules and a discount function will do that without another app in your theme. If your catalogue is deep and the offers overlap, a single engine that resolves the conflict is worth having. That is the case we built for.