How Do I Set Up a Bundle Discount That Applies Automatically When All Items Are Selected?
What an Automatic Bundle Discount Actually Does
An automatic bundle discount is a rule that evaluates the cart continuously and applies a price reduction when the cart matches your conditions. The shopper never enters anything.
The mental model that helps is a light switch with a sensor. The discount is not attached to a product or a coupon. It is attached to a state of the cart, and it turns on and off as that state changes.
That last part matters more than merchants expect. If a shopper adds all three bundle items, gets the $12 saving, then removes one item, the discount must disappear. A rule that applies once and sticks around is how stores accidentally ship $200 of product for $140.
For merchants on OpoShop, the practical benefit is that the offer works everywhere at once. A shopper who assembles the bundle piece by piece across three product pages still gets the saving, because the rule is watching the cart rather than a button.
The Three Conditions Every Rule Needs
A bundle rule that behaves well in the wild is built from three explicit conditions. Skipping any one of them creates a class of edge case you will meet eventually.
- Membership: Which exact products or variants count toward the bundle, including whether a substitute size qualifies.
- Quantity: How many of each item are required, and whether buying two of the same item counts as two members or one.
- Scope: Whether the discount applies once per cart, once per complete set, or on every eligible item in the cart.
Membership is where most rules on an OpoShop store go wrong. If your rule says "any candle from the Home collection," and someone adds the $9 travel tin three times, they just triggered your "3 for $54" bundle at a $27 cart value. Precision here is not pedantry, it is margin.
Quantity is the second trap. A shopper who buys three of the same shirt in the same size is usually a legitimate bundle. A shopper who buys three of your loss-leading sample size probably is not. Decide which one your store means, then write the rule to say it.
Scope is the one that surprises people at scale. If a customer puts two complete sets in the cart, do they get the discount twice? Most stores say yes, because the customer genuinely bought two bundles. But you need to have decided that before a $600 order shows up.
Why Automatic Beats a Discount Code
Automatic rules outperform codes because they remove the two failure points that kill code-based promotions: remembering and typing.
A shopper who sees "use code TRIO10 at checkout" has to hold a string in working memory across several screens. A meaningful share simply do not, and then they either pay full price and feel cheated or abandon the cart to go hunt for the code in their email.
There is a second, quieter cost. Codes leak. Post one in an email and it ends up on a coupon aggregator within days, applied to orders that were never part of your promotion. An automatic rule cannot leak because there is nothing to copy.
Automatic rules also let you promote honestly. You can write "add all three and save $12 automatically" on the product page, and it is true without an asterisk. That clarity is worth more on an OpoShop product page than any extra percentage point of discount.
How to Build the Rule Step by Step
The build is five steps. Do them in this order and you will not have to unwind anything later.
Here is what the tricky parts look like in practice.
1. Write the rule in a plain sentence first
Before touching any settings, write the offer as one sentence a human could enforce. "Any 8 oz candle, plus any wick trimmer, plus any matchbox, gets ten percent off those three items."
If you cannot write that sentence without using the word "usually," your rule is not ready. Ambiguity in the sentence becomes ambiguity in the cart, and the cart resolves ambiguity in the shopper's favor.
2. Decide what happens to partial carts
The most common live question is what a shopper sees when they have two of the three items. The best answer is a visible prompt, not silence.
A cart that says "add a matchbox to save $6" converts noticeably better than a cart that says nothing, because the shopper is one click from a better deal and now knows it. In your OpoShop store this prompt is doing the same job the product page widget does, just later in the funnel.
3. Stack the rule against your other promotions
Decide up front whether the bundle discount combines with a sitewide sale, a first-order code, or free shipping thresholds. Every combination you allow is a total you need to be comfortable paying for.
The conservative default is that bundle discounts do not stack with other percentage discounts, but they do count toward free shipping thresholds. That keeps the math sane while still feeling generous.
Automatic Rule vs Discount Code vs Manual Adjustment
Merchants generally reach for one of three mechanisms. They differ in reliability far more than in effort.
| Mechanism | Shopper effort | Failure mode | Best for |
|---|---|---|---|
| Automatic cart rule | None, it just fires | Misconfigured membership lets cheap items qualify | Always-on bundle offers you want running unattended |
| Discount code | Must remember and type a code | Forgotten codes, leaked codes, unhappy support tickets | Time-boxed campaigns tied to a specific email or influencer |
| Manual order adjustment | None, but the refund comes later | Slow, inconsistent, and impossible past a few orders a day | Rare one-off goodwill gestures, not a bundle strategy |
Automatic cart rules are the only one of the three that scales without a person in the loop. Once the membership definition is tight, the rule runs correctly at three orders a day and at three hundred. That is the property you want going into a busy season, because a mechanism that needs supervision is the first thing to break the week you are busiest.
The other advantage is speed of iteration. Changing a percentage on an OpoShop bundle rule takes a few seconds and applies to every cart from that moment forward, with no reissued codes and no stale emails pointing at a promotion that no longer exists.
Discount codes still have a real job. When you want to attribute revenue to a specific newsletter or partner, a code is the cleanest way to measure it. Just do not use one as the mechanism for your permanent bundle.
Manual adjustments are a trap disguised as flexibility. Refunding the difference after the fact means the shopper saw full price at checkout, which is exactly the moment the discount was supposed to be persuading them.
How to Test It Before You Announce It
Testing takes fifteen minutes and it is the difference between a smooth launch and a week of apologies. Run these cases with real carts on a real device.
Start with the happy path on your live OpoShop storefront. Add every bundle item, confirm the discount line appears with the right name and the right amount, and check that the order total matches your own arithmetic rather than just looking plausible.
Then attack it. Remove one item and confirm the saving vanishes. Add a duplicate and confirm the rule does what you decided about quantities. Add two complete sets and confirm the discount either doubles or does not, according to your scope choice.
Finally, test the sneaky one. Add the cheapest qualifying variant of each item and check the resulting margin. If a shopper can trigger a $12 saving on a $34 cart of samples, tighten the membership list before this goes live. Every OpoShop merchant who has run bundles for a while has a story about exactly this cart.
What We Recommend for [OpoShop](https://oposhop.io) Merchants
For OpoShop merchants, run one automatic rule, keep the membership list explicit, and make the saving visible in the cart. That combination handles the overwhelming majority of bundle scenarios without maintenance.
Resist the urge to launch four overlapping rules in week one. Overlapping rules are where unexpected totals come from, and untangling them after orders have shipped is genuinely unpleasant.
Apps like Bundlr exist to keep this at the level of a merchandising decision rather than a development project. You describe the offer, the rule enforces it, and the cart tells the shopper what happened.
Once the first rule is stable, expand deliberately. Add a second bundle on a different collection, keep the two membership lists from overlapping, and check your average order value after two weeks against the two weeks before.
Best answer: Set up an automatic bundle discount as a conditional cart rule with three explicit parts: exactly which products or variants count, exactly how many of each are required, and whether the discount repeats for multiple sets. Show the saving as a named line in the cart, and make sure removing an item removes the discount. Configured that way in an OpoShop store, the offer runs unattended and no shopper ever needs a code.
FAQs
Does the shopper need to enter a code for an automatic bundle discount?
No. The rule watches the cart and applies the saving the moment the required items are present, which removes the two biggest failure points of code-based promotions.
What happens if the shopper removes one bundle item?
The discount should be withdrawn immediately, because the cart no longer satisfies the rule. If a saving sticks around after a removal, that is a configuration problem worth fixing before it costs real money.
Can an automatic bundle discount apply more than once in a cart?
Yes, if you scope it that way. A shopper buying two complete sets can receive the discount twice, but you should decide this deliberately rather than discovering it on a large order.
Will the bundle discount stack with a sitewide sale?
Only if you allow it. The safer default is to prevent stacking with other percentage discounts while still letting the bundle subtotal count toward free shipping thresholds.
How do I show the shopper that the discount worked?
Add a named discount line in the cart and at checkout, showing both the rule name and the amount saved. Silent discounts get missed, and a shopper who does not notice the saving was not persuaded by it.
What if a shopper adds two of the same product instead of two different ones?
That depends on your quantity condition. Decide whether duplicates satisfy the bundle, then write the rule explicitly, because leaving it undefined usually resolves in a way that costs you margin.
Ready to let the cart do the discounting for you? Build the rule where your store already sells.
