How to Exclude Low-Margin Products From a Shopify Collection-Wide Discount

To exclude low-margin products from a Shopify collection-wide discount, define the eligible catalog before you configure the promotion. If your Shopify admin has the new collections model, you can exclude products directly from a collection. If it does not—or if every new product should remain ineligible until someone approves it—build a positive discount-eligible collection instead.

Then connect the native product discount or app deal to that approved scope. The final test has two parts: a protected product must not help the cart reach the quantity threshold, and it must not receive the discount after eligible products qualify.

For a visible multi-tier offer that pools approved products added from different pages, Kaching Bundles & Upsells is a documented fit through Collection Breaks. Native Shopify remains the simpler option when one minimum-quantity threshold is enough.

An excluded product has to pass two different tests

“Excluded from the discount” is too vague for a quantity offer. Write the expected behavior for both the counter and the discounted lines.

Suppose Products A and B are eligible. Product X is protected. The first tier requires three eligible units.

These controls solve different problems. A protected product can remain full price and still cause margin leakage if it helps other lines qualify too early. The reverse is also possible: the threshold counts correctly, but the discount spills onto a line that should remain protected.

Shopify documents this distinction for native amount-off product discounts. When a discount is scoped to specific products or collections, only those eligible items contribute to its minimum purchase amount or minimum quantity. That is the behavior your app-based setup should reproduce in representative carts, even when its labels differ.

Decide which products can enter the deal

Do not begin with a tag. Begin with the deepest tier you intend to show.

A product that can carry 10% off may not be able to carry 20% off after payment charges, product cost, packaging, shipping subsidy, pick-and-pack cost, and expected returns. Screening the first tier alone gives the riskiest tier permission to borrow margin that was never checked.

Use complete variable costs, not Shopify gross margin alone

Shopify’s Cost per item field is useful, and the product CSV includes SKU, price, tags, and cost per item. But Shopify’s profit-report documentation describes cost per item as what it costs to make or acquire the product; it excludes shipping and other costs. Add the variable expenses that actually change the contribution from your promoted order.

For a first admission screen, calculate:

Screened contribution at the deepest tier = price × (1 − deepest discount) × (1 − revenue-linked cost rate) − non-revenue variable costs

Non-revenue variable costs can include unit COGS, expected fulfillment, packaging, shipping subsidy, and a returns allowance that you have not already included in the revenue-linked rate.

Compare the result with the contribution floor you require from that item. This does not replace a complete order-level profitability model. Its job is narrower: stop a clearly unsuitable product from entering a shared promotion.

Discount Eligibility Control Sheet

The example below is hypothetical. It assumes a 20% deepest tier and a 5% revenue-linked cost rate.

The Serum clears its floor. The Refill Pouch does not. The Glass Duo passes the displayed calculation, but the missing shipping step makes the result incomplete. The Vendor Accessory passes the math but fails a hard commercial restriction.

That produces three useful states:

• ELIGIBLE: the deepest tier clears the selected floor and no known restriction blocks the product;
• EXCLUDE: the product misses the floor or fails a hard commercial or operational rule;
• REVIEW: a material cost, restriction, or variant behavior is unknown.

Do not turn REVIEW into ELIGIBLE because the launch date is close. Missing data is part of the decision.

Treat the product screen as an admission gate

Some costs exist only at the cart or order level. Six mixed units may cross a shipping or packaging step that no per-item row can predict. Products that pass the sheet are candidates for the promotion; they are not proof that the complete ladder is profitable.

The final offer still needs order-level contribution checks and live measurement. The purpose of this sheet is to keep obviously unsafe and unresolved items out of the eligible pool while you do that work.

Choose the catalog rule by how you want it to fail

The right architecture depends less on how many products you have than on what should happen when the catalog changes.

Positive eligibility is the fail-closed route

Create a collection that contains only products marked discount-eligible. A new product stays outside until a staff member reviews its economics and applies the approved membership.

This adds work at launch, but the failure is visible: the new item does not receive the offer. For a store where one unreviewed SKU can erase the tier’s contribution, that is usually the safer trade-off.

Direct exclusions are the lower-maintenance route

Shopify’s new collections model can exclude products manually, through conditions, or by excluding another collection. Shopify also states that product exclusions override manual or automatic product inclusions within that collection source.

This is useful when most of the catalog is eligible and the protected list is small. The failure mode is different: a newly added product can match the broad inclusion source before anyone marks it for exclusion.

Direct exclusions are therefore not automatically safer than an eligible list. They are easier when their default behavior matches your risk.

Hybrid control separates approval from hard restrictions

A hybrid design might use positive eligibility for financial approval and a direct exclusion for products that must never join the promotion, such as vendor-restricted items.

Keep the rule understandable. If staff cannot explain why a product is in or out without opening three collections and a spreadsheet, the architecture is already difficult to maintain.

Set up the eligible collection in Shopify

First check which collection interface your store has. Shopify says its new collections model is replacing the legacy manual and smart collection model, but stores without the new model can continue using the legacy controls.

Path A: use direct exclusions in the new collections model

1. In Shopify admin, go to Products → Collections.
2. Open the collection that will control discount eligibility, or create a dedicated unpublished collection for the promotion.
3. Add the broad product source or inclusion conditions.
4. In the Products source, select Add → Exclude.
5. Choose one exclusion method:
   • automatic conditions;
   • specific products; or
   • another collection containing protected products.
6. Save, then inspect the resulting product list before connecting it to the discount.

Shopify documents two limitations worth noting. Within one source, you can exclude individual products or another collection, but not both at the same time. Shopify also currently limits a store to five collections that exclude another collection. If your exception structure is already close to that boundary, a positive eligible collection may be easier to reason about.

Path B: use a positive eligible collection

Use this route when the new controls are unavailable or when unreviewed products must stay outside by default.

1. Create a product tag such as discount-eligible.
2. Apply it only after the product receives an ELIGIBLE decision in the control sheet.
3. Create an automated collection whose inclusion condition is Product tag is equal to discount-eligible.
4. Keep the collection unpublished if customers do not need to browse it.
5. Review its members before every promotion launch and after material catalog changes.

This is safer than building a broad collection with several is not equal to conditions. Shopify warns that negative conditions can behave unexpectedly, especially when Match any is used: a product can be included simply because it fails to match one of several exclusion criteria.

A positive tag has a simpler test. The product either has approval or it does not.

Do not assume one product rule protects one unsafe variant

Shopify’s new collection model can use product or variant sources, and Shopify records cost per item at the variant level. That matters when one size, pack, or material has different economics.

Kaching’s public Collection Breaks documentation describes inheritance from the parent deal’s product or collection visibility. It does not document every variant-level exclusion and overlapping-collection precedence case.

If one variant is unsafe, use variant-level eligibility only when the complete discount mechanism can express and reproduce that boundary. Otherwise, exclude the whole product or choose a more granular implementation. A conservative exclusion is better than publishing a variant promise the checkout cannot enforce.

Connect the approved catalog to the discount

The eligible collection is only a source of truth. The promotion still has to point to it.

Use native Shopify for one threshold

A native amount-off product discount can apply to specific products or collections and can require a minimum quantity. Shopify says only eligible items contribute to that minimum.

Use this route when you need one rule such as:

Buy any three eligible products and receive 10% off those eligible products.

In Shopify admin:

1. Create an Amount off products discount.
2. Choose automatic discount or discount code.
3. Set the percentage or fixed amount.
4. Under Applies to, select the approved collection.
5. Set the minimum quantity.
6. Configure customer eligibility, dates, and combinations.
7. Save and run the audit below.

Native Shopify is a good stopping point when the checkout rule matters more than a visible multi-tier product-page experience.

Use Kaching Collection Breaks for visible cross-page tiers

Kaching’s current Collection Breaks documentation describes a Same products as deal visibility setting. With it enabled, qualifying products can be added through the deal widget, individual product pages, or collection pages, while Collection Breaks inherits the parent deal’s product or collection visibility.

The safe setup order is:

1. Finish the Discount Eligibility Control Sheet.
2. Make the approved catalog expressible through the parent deal visibility.
3. Configure the quantity tiers and pricing.
4. In Collection Breaks, choose Same products as deal visibility.
5. Save the deal.
6. Test eligible, protected, overlapping, and newly added products through every add-to-cart path customers use.

Do not confuse this with Kaching’s separate “volume discount bundle with other products” flow. That mix-and-match selector has its own eligible-product choices, including All products except selected, Products in selected collections, and Selected products. It is a different customer journey from Collection Breaks that pools products added while browsing.

Run an eight-case catalog-drift and mixed-cart audit

Use named test products rather than “random items.” The test must be repeatable after a collection rule, price, product cost, theme, cart, or app setting changes.

Assume:

• Products A and B are ELIGIBLE.
• Product X is EXCLUDE.
• Product Y is a new, unreviewed product.
• Three to five eligible units receive 10% off.
• Six or more eligible units receive 15% off.

Cases 6–8 are why this is more than a checkout test. They test whether the catalog rule still represents the financial decision.

If a case fails, inspect one layer at a time:

1. Control-sheet status.
2. Product, variant, tag, and collection membership.
3. Shopify discount scope or Kaching parent deal visibility.
4. Collection Breaks setting.
5. Add-to-cart path and cart behavior.
6. Other active discounts and combination rules.

Changing several layers at once may make the next test pass without revealing which rule was wrong.

Keep the eligible catalog current

Assign one owner to the eligibility rule. That person does not need to own product pricing or the app, but someone must be responsible for moving products among ELIGIBLE, EXCLUDE, and REVIEW.

Recheck membership when any of these events occurs:

Monitor exceptions, not only averages. Useful controls include:

• number of products in REVIEW;
• protected-product incidents;
• audit pass rate after catalog changes;
• discount cost per eligible order;
• contribution per eligible order at each observed tier.

A rising AOV does not prove that the eligible catalog is sound. The promotion can raise order value while one protected product loses contribution or unlocks a deeper tier too early.

Which implementation should you choose?

Choose native Shopify when one minimum-quantity product discount across an approved collection is enough.

Choose Kaching Collection Breaks when the same approved products should pool across pages and shoppers need a visible multi-tier ladder. Kaching handles the offer presentation and documented cross-page behavior; the eligibility sheet, margin floor, catalog ownership, and representative-cart QA remain yours.

Choose a different or custom architecture when the discount must evaluate complex dynamic data, protect one variant that the chosen scope cannot isolate, or create an inventory-managed bundle rather than a shared discount. The Shopify bundle apps guide covers broader fulfillment and bundle structures.

If Collection Breaks matches the shopping flow you want, claim 20% OFF Kaching for your first 3 months. Use the ShopSideK form on that page to receive the code after you confirm the eligible catalog and test plan.

If you prefer to inspect the listing first, you can also view Kaching on the Shopify App Store.

Frequently asked questions

Can I exclude products from a Shopify collection discount?

Yes. In Shopify’s new collections model, a collection can exclude products manually, through conditions, or through another collection. If those controls are not available in your admin, create a positive eligible collection and scope the product discount to it. Shopify says only eligible products count toward a collection-scoped minimum.

Do excluded products count toward the minimum quantity?

They should not when the discount or deal counter is correctly scoped to eligible products. Test this separately from discount receipt. A cart containing two eligible units and one protected unit should not reach a three-unit tier.

What if a product belongs to both an eligible and a protected collection?

Do not infer the result from the collection names. In Shopify’s new collection model, product exclusions override inclusions within the documented collection source. Kaching’s public Collection Breaks documentation does not explain every overlapping-collection precedence case, so inspect the final parent deal visibility and test that product in the cart.

Should I use a no-discount tag or a discount-eligible tag?

Use discount-eligible when new products must remain outside until approved. A no-discount approach can be easier when nearly everything is eligible, but its default is less conservative. Avoid building complex negative inclusion logic with Match any; Shopify warns that it can include products unexpectedly.

Can I exclude only one product variant?

Shopify’s new collection model can use variant sources, but the entire discount path must preserve that variant-level boundary. If the app or deal visibility cannot reliably do so, exclude the whole product or choose a more granular implementation. Do not assume a product-level exclusion protects one variant.

Does Kaching automatically identify low-margin products?

No documented Kaching feature chooses products from your unit economics or sets your contribution floor. Collection Breaks applies tiers to products matching the deal scope. You still need to classify the catalog, maintain membership, and test protected products.