Set different quantity breaks for Shopify products or collections by creating separate deals only for groups that need different rules, then scope each deal to its intended products. The harder decision is how many deals you actually need.
Do not default to one ladder for the entire catalog, and do not create one deal per SKU. Start with the product economics and buying behavior, compress compatible products into the smallest viable number of groups, and keep every product in one intended quantity-break scope.
Kaching Bundles & Upsells is a practical implementation option because it supports multiple deals, product or collection visibility, and cross-page Collection Breaks. It does not decide which products can safely share a ladder.
Separate three decisions before creating deals
“Apply this bundle to a collection” can describe three different controls. Mixing them is how a clean catalog plan turns into an unpredictable cart.
| Decision | Question it answers | Example |
|---|---|---|
| Widget visibility | Where does the offer appear? | Show the Replenishment deal on Serum and Cleanser PDPs |
| Eligible products | Which products may the shopper choose? | Let the shopper mix selected skincare products in one bundle |
| Quantity counting | Which units combine toward a tier? | Count Serum separately, or pool Serum and Cleanser toward three eligible units |
These controls can point to the same products, but they do not mean the same thing.
Kaching’s mix-and-match quantity-discount tutorial explicitly separates Visibility—where the bundle appears—from the products eligible for selection. Its Collection Breaks documentation describes another behavior: eligible quantities can pool across product, collection, and widget add paths using the parent deal’s visibility scope.
Before grouping products, write the intended rule in one sentence:
Count quantities separately for each product, but show the same ladder to every product in Group A.
Or:
Pool quantities across all eligible products in Group B, no matter which eligible page added them.
Two groups can display identical percentages and still require different deals because their counting rules differ.
Build the product input sheet before opening the app
The grouping decision should reuse work you have already done. It should not recalculate every tier from scratch.
Create one row per product—or per variant when size, material, flavor, cost, or shipping behavior changes materially—and record:
- eligibility status;
- observed units per order;
- candidate breakpoint quantities;
- safe discount ceiling at each candidate quantity;
- replenishment or realistic use cadence;
- price and margin band;
- shipping, packaging, and handling steps;
- inventory or vendor restrictions;
- intended counting model;
- current product and collection memberships;
- deal owner and review date.
Shopify’s order reports provide broad quantity and order context. For a product-level distribution, use an order export, group the line items by order, and remove test orders or periods where an existing promotion distorted quantity.
Do not treat historical units as predicted demand. They tell you where current behavior begins, not how buyers will respond to a new offer.
Cost inputs need the same caution. Shopify’s profit-report documentation explains that useful profit reporting depends on Cost per item. That field does not automatically include every shipping, packaging, payment, fulfillment, or return cost needed for a promotion decision.
This article assumes the safe discount ceilings and candidate breakpoints have already been approved. Its job is to decide which products can reuse them.
Compress products into the smallest viable tier groups
Product similarity is not enough. Two products belong in the same tier group only when they can share the commercial rule.
Begin with hard vetoes
Before attempting to merge products, remove or flag anything that fails one of these gates:
- the product has no reliable cost or restriction data;
- even the shallowest candidate tier violates its contribution requirement;
- the proposed quantity exceeds plausible use, storage, shelf-life, or replenishment;
- a tier crosses an unacceptable shipping, packaging, or fulfillment step;
- inventory cannot support plausible multi-unit uptake;
- the product needs a different counting model;
- the offer would conflict with a vendor, subscription, market, or channel rule.
Use REVIEW for a missing material input. Do not turn uncertainty into eligibility simply to keep the launch date.
Merge products only when quantities and ceilings align
For every proposed group, compare the shared ladder with its most constrained member.
Suppose three products would use:
- Buy 2, save 8%;
- Buy 3, save 12%;
- Buy 5, save 15%.
The group passes the financial gate only if every product can safely carry each percentage at the corresponding quantity. One product with a 10% ceiling at Buy 5 blocks the 15% group ladder, even if the other products have much more headroom.
Do not solve that conflict by silently letting the weak product receive a deeper tier. Either:
- reduce the shared ladder;
- move the constrained product to a shallower group;
- give it a justified product-specific deal; or
- exclude it.
The lowest safe member sets the group boundary. That does not mean the group must discount all the way to that boundary.
Keep different counting models separate
A same-product ladder answers:
How many units of this SKU did the shopper buy?
A pooled collection ladder answers:
How many eligible units did the shopper buy across this group?
Those offers can produce different qualifying carts. If Serum and Cleanser use the same displayed Buy 3 tier but only Serum quantities should count toward Serum’s discount, do not place them in a pooled Collection Breaks rule merely because the percentages match.
Shared presentation does not require shared counting.
Tier Group Compression Matrix
The example below is hypothetical. The ceilings are assumed outputs from a separate contribution analysis; they are not universal recommendations.
| Product | Observed pattern | Candidate quantities | Lowest safe ceiling across candidate tiers | Main constraint | Provisional result |
|---|---|---|---|---|---|
| Replenishing Serum | Mostly 1; some 2 | 2 / 3 / 5 | 18% | Replenishment | Group A |
| Cleanser Refill | Regular repeat purchase | 2 / 3 / 5 | 16% | Package volume | Group A |
| Daily Gummies | One unit covers one month | 2 / 4 / 6 | 20% | Stock-up horizon | Group B |
| Protein Pouch | Some multi-unit orders | 2 / 4 / 6 | 15% | Shipping check at 6 | Group B after QA |
| Ceramic Candle | Mostly gifts or pairs | 2 / 3 | 9% | Fragile packaging | Group C, shallow |
| Glass Duo | Mostly single unit | 2 only | 4% | Package and shipping step at 2 | EXCLUDE |
The provisional ladders might be:
| Group | Hypothetical ladder | Why it remains separate |
|---|---|---|
| A | Buy 2: 8%; Buy 3: 12%; Buy 5: 15% | Compatible replenishment quantities and ceilings |
| B | Buy 2: 6%; Buy 4: 9%; Buy 6: 12% | Longer stock-up ladder; Protein Pouch requires shipping validation |
| C | Buy 2: 5%; Buy 3: 8% | Fragile product needs a shallower, shorter ladder |
| EXCLUDE | No quantity break | Glass Duo fails the current economic/operational gate |
Why not merge A and B? Their discount ceilings could accommodate a common shallow offer, but the quantity logic is different. A Buy 5 tier can represent a plausible replenishment decision for Group A while Group B’s pack/use pattern supports a 2/4/6 structure.
Why not merge C into A? The Candle’s lowest ceiling is below Group A’s 12% and 15% tiers, and its fragile-packaging behavior differs.
Why exclude the Glass Duo rather than create Group D? A technically possible one-product group is not automatically worth maintaining. With only a 4% ceiling and an adverse shipping step, it has not earned another storefront offer and governance path.
The example ends with three groups and one exclusion. Another catalog might end with one universal ladder or several product-specific deals. The method—not these percentages—is the reusable part.
Choose one ladder, several groups, or a product-specific deal
Use the simplest architecture that passes every hard gate.
| Architecture | Choose it when | Main danger |
|---|---|---|
| Universal ladder | Nearly all eligible products share quantities, safe depth, counting logic, and operational behavior | Weak members inherit a ladder designed for stronger products |
| Two groups | One material split explains most differences, such as replenishable versus fragile | Broad collections can hide internal exceptions |
| Three groups | Two different constraints materially change quantities or discount depth | Governance and overlap work increases |
| Product-specific | A high-volume product has unique economics or buying behavior worth its own offer | One-deal-per-SKU sprawl |
| Exclude | The product lacks headroom, plausible multi-unit use, data, stock, or operational fit | Lost opportunity if the exclusion is never reviewed |
A separate deal is justified by different logic, not different nouns.
If two products share tiers and pricing but need different titles, images, or product names, use dynamic content where possible. Kaching’s personalization documentation specifically recommends variables instead of creating separate bundle blocks for simple product-specific text.
Assign products directly or use a dedicated collection
Direct product assignment is easier to audit when a group contains a small, stable list. A dedicated collection is easier when:
- membership changes regularly;
- an existing catalog rule can express the group clearly;
- new products should follow a defined approval process;
- staff need one visible source of truth.
Do not reuse a merchandising collection merely because it already exists. “Best Sellers” or “Summer Collection” may mix products with incompatible ceilings, replenishment, and shipping behavior.
Create an operational collection for the tier group when needed, such as:
- Quantity Group A — Replenishment;
- Quantity Group B — Stock-Up;
- Quantity Group C — Shallow Fragile.
The customer-facing name can remain different or the collection can remain unpublished if it is only an assignment control.
Use positive membership when new products should remain outside until approved. Record why each product belongs. A tag or collection automates membership; it does not perform the economic review.
Overlapping merchandising collections deserve special attention. A product can belong to “Best Sellers,” “Skincare,” and “Holiday” simultaneously. If several active deals use those collections, the catalog structure no longer proves which offer should own the product.
Prefer non-overlapping operational tier groups. If overlap is intentional, obtain current app-specific confirmation and test the live storefront and cart. Kaching’s public documentation does not currently establish every priority outcome among independent overlapping bundle deals.
Implement the approved groups in Kaching
Kaching’s billing documentation says its plans do not impose a feature-based limit on the number of bundle deals. That makes several tier groups technically possible. It does not make hundreds of deals easy to govern.
For each approved group:
- Create or duplicate one quantity-break deal.
- Enter only the approved quantities and pricing.
- Set Visibility to the intended products or operational collection.
- Use personalization variables for product-specific text instead of duplicating the logic.
- Decide whether quantities count separately by product or pool across eligible products.
- Use Collection Breaks only when cross-page, cross-product pooling is intended.
- Save the deal and test representative products before publishing the campaign.
For a single-product quantity break, Kaching documents percentage, fixed-amount, and custom-total pricing through its Quantity Break offer type.
For a shopper-facing mix-and-match selector, configure both where the widget appears and which products can be selected. Do not assume one setting supplies both.
For a pooled collection offer, Collection Breaks can apply the parent deal’s volume tiers when qualifying products are added from different eligible pages. This is not the same as displaying one same-product ladder across several PDPs.
Run a Coverage and Conflict Audit
Test the group system as a catalog, not only as one successful product page.
For each group, choose:
- one typical product;
- the lowest-margin product;
- the product closest to a shipping or packaging step;
- one product intentionally outside the group;
- one product that belongs to overlapping merchandising collections.
Then run this audit:
| Case | Test | Expected result |
|---|---|---|
| 1 | Open a typical Group A PDP | Group A ladder appears |
| 2 | Open another Group A product | The same intended ladder appears with correct product details |
| 3 | Open a Group B product | Group B ladder appears; Group A does not |
| 4 | Open an excluded product | No quantity-break deal appears |
| 5 | Add a nonqualifying quantity | No unintended tier applies |
| 6 | Add the exact qualifying quantity | Correct quantity, variant, and price reach the cart |
| 7 | Mix products inside a same-product group | Quantities remain separate |
| 8 | Mix products inside an intended pooled group | Eligible quantities combine as documented |
| 9 | Test an overlapping-collection product | One documented intended offer owns the product |
| 10 | Repeat on mobile and the published theme | Deal, selected state, button, and cart remain correct |
Case 9 blocks launch when the expected owner cannot be proven. Do not choose the most attractive result after seeing what happens; define the intended owner before the test.
Also confirm that the deal-level analytics can be reviewed separately. Kaching’s current bundle analytics documentation describes all-deal and single-deal filtering, UPT, visitors, add-to-cart rate, conversion, revenue, AOV, and cost-dependent profit fields.
Treat those profit fields as directional when Shopify Cost per item omits other variable costs. For the commercial verdict, combine offer outcomes with the merchant’s complete contribution inputs.
Maintain the tier groups as the catalog changes
Assign one owner to the grouping system and review it when:
- a product or variant launches;
- price, cost, payment fees, returns, or vendor terms change;
- packaging or shipping rates change;
- observed unit distribution or replenishment behavior shifts;
- a product enters or leaves an operational collection;
- a subscription, market, or channel rule changes;
- a deal, theme, cart, or app configuration changes.
New products should enter REVIEW, not inherit the nearest-looking group automatically.
Keep a short register:
| Field | Purpose |
|---|---|
| Product or variant | Defines the item being governed |
| Tier group | Identifies the intended ladder owner |
| Reason | Records the dominant compatibility constraint |
| Last ceiling/breakpoint check | Shows whether the underlying decision is current |
| Collection and deal scope | Exposes assignment and overlap |
| Owner | Assigns responsibility |
| Next review trigger | Prevents indefinite assumptions |
The objective is not to preserve the original groups forever. It is to make changes deliberate and auditable.
When different quantity breaks are the wrong solution
Do not add another tier group when:
- the only difference is product title or image;
- one simple Shopify minimum-quantity discount is enough;
- the candidate product has no credible multi-unit use;
- the economics are unresolved;
- the actual need is a fixed kit, inventory-managed bundle, or complementary-product upsell;
- the storefront already presents too many competing purchase choices;
- the team cannot maintain product membership or audit overlaps.
If the offer requires customers to choose several different components as one product, the Shopify bundle apps guide covers architectures beyond product-page quantity breaks.
Segmentation is useful only while the extra precision is worth the extra operational surface.
Choose the catalog architecture
Use one universal ladder when the same quantities, safe discount depth, counting model, and operating constraints genuinely fit almost every eligible product.
Use two or three groups when a small number of recurring constraints explains the catalog. Keep a product-specific deal for an important outlier only when its volume or economics justifies the maintenance. Exclude products that fail the offer or data gate.
Then prove that every product has one intended deal owner. A sophisticated matrix does not matter if a broad collection silently places the same SKU into two live offers.
If Kaching fits the tier groups you have approved, claim 20% OFF Kaching for your first 3 months. Use the ShopSideK form on that page to receive the code after you define the group scopes and conflict tests.
If you prefer to inspect the listing first, you can also view Kaching on the Shopify App Store.
Frequently asked questions
Can each Shopify product have different quantity breaks?
Yes, when your discount implementation supports product-specific deal scopes. However, create separate deals only when quantities, pricing, eligibility, counting, or operational constraints differ. Use shared deals and dynamic product text when the logic is the same.
Can I apply one quantity-break ladder to a Shopify collection?
Yes. A product or collection scope can control which products receive a deal. Decide separately whether quantities count per product or pool across eligible products. Collection membership alone does not define the counting model.
What happens if a product belongs to two quantity-break collections?
Do not assume a priority rule. Define which deal should own the product, inspect the current app documentation or obtain support confirmation, and test the live PDP and cart. Kaching’s public documentation does not currently explain every overlap outcome among independent deals.
How many quantity-break groups should a store have?
Use the smallest number that preserves meaningful differences in quantities, safe discount depth, counting, and operations. One group can be enough; the hypothetical catalog above needs three. There is no universal maximum.
Can native Shopify set different volume pricing by product?
Shopify B2B catalogs support product-level quantity rules and volume pricing. For DTC, native amount-off discounts can cover simple minimum-quantity rules scoped to products or collections. A visible multi-tier product-page experience and reusable grouping workflow often require an app or custom implementation.
Does Kaching automatically group products by margin or order data?
No documented feature performs the Tier Group Compression analysis. Kaching can implement product and collection scopes, personalize deal content, pool eligible quantities through Collection Breaks, and report deal performance. The merchant still owns cost inputs, group design, exclusions, and overlap QA.
