Our review of StoreBuilt’s collection guidance separates two jobs that are often mixed together: deciding which products qualify and deciding where those products appear. A collection can have a sensible sort order and still contain the wrong items. When that happens, a merchandising adjustment will not repair a faulty condition.
This guide focuses on Shopify smart collection conditions, including the all-versus-any choice and exclusion rules. It is written for UK ecommerce teams managing collections such as mugs under £30, a particular material range or an in-stock campaign selection. The aim is a rule another colleague can explain and test, rather than a collection that happens to look right today.
In this guide
- Write the rule in plain English first
- Understand all and any with a tiny sample
- Inspect the data the condition actually reads
- Treat exclusion rules with particular care
- Recognise when the rule needs a different structure
- Separate membership from storefront visibility
- Test price and inventory boundaries deliberately
- Create a release sheet for the change
- Check the next catalogue update
- StoreBuilt point of view
Write the rule in plain English first
Describe the intended set before opening the admin. “All mugs priced below £30” contains two requirements. “Mugs or anything priced below £30” describes a much wider set. Both can be implemented faithfully, but only one matches the first brief. Have the commercial owner confirm the sentence.
Include exclusions and boundary choices. Does below £30 exclude an item at exactly £30? Does the selection refer to normal price or the price the customer sees in a particular market? Should a product with several variants qualify if only one matches? Do not answer those questions by guessing how a field behaves. Record them as requirements, then check the available collection source and condition semantics in the current Shopify admin and documentation.
Understand all and any with a tiny sample
Use four deliberately different products to make the logic visible. In this illustrative example, the conditions are a mug classification and a price below £30. The prices are test values, not market research or client data. A small truth table exposes an incorrect combination faster than scrolling through hundreds of product cards.
| Sample item | Mug condition | Below £30 | Match all | Match any |
|---|---|---|---|---|
| £20 mug | Pass | Pass | Included | Included |
| £40 mug | Pass | Fail | Excluded | Included |
| £20 bowl | Fail | Pass | Excluded | Included |
| £40 bowl | Fail | Fail | Excluded | Excluded |
If the unwanted bowl appears under any, Shopify may be applying the configured logic correctly. The error is then in the rule’s translation, rather than a broken collection engine.
Inspect the data the condition actually reads
A product can look like a mug to a human and still carry an inconsistent tag or type. Read the exact field used by the condition. Check spelling, unintended spaces, supplier imports and whether the team has mixed product types, tags and categories as though they were interchangeable.
Avoid changing the title solely to make the rule pass. A title is customer-facing content with uses beyond this collection. Prefer correcting the intended classification field or changing the condition to the appropriate data source. For a bulk correction, export or otherwise preserve the original values and test a small set first. A catalogue integration may own the field, in which case its next update can overwrite a manual repair and recreate the problem.
Treat exclusion rules with particular care
Negative conditions are easy to read incorrectly when combined with any. Suppose the intention is to exclude both clearance and sample products. An item that is clearance but not a sample can satisfy one of two negative conditions and remain included under any. The rule can therefore appear to ignore the very exclusion the merchant added.
Write a second truth table for the excluded groups. Test an item in neither group, one in each group and one in both. Confirm which condition types support exclusion in Shopify’s current documentation. Do not assume that every field offers the same operators. If the intended logic combines several positive alternatives with several mandatory exclusions, a simple flat list may not represent it clearly.
Contact StoreBuilt for a scoped review of the affected Shopify journey.
Recognise when the rule needs a different structure
A brief such as “mugs or bowls, always ceramic, never samples” mixes alternatives and mandatory requirements. Before building a long condition list, check whether the current collection controls express that grouping. Replacing the sentence with a broad any rule can accidentally admit non-ceramic products or samples.
One possible design is a deliberately maintained qualification tag or metafield, supported by an agreed process that determines eligibility. That moves complexity into data ownership, so it is not free automation. The field needs an owner, refresh trigger and review method. Another option is a simpler collection structure. Choose the approach that the merchandising team can maintain accurately; an elaborate rule with no accountable owner is fragile even when its initial output is correct.
Separate membership from storefront visibility
First compare the expected sample with the collection’s admin membership. Then compare it with the live storefront. If admin membership is correct but a product is absent or unexpectedly visible on the page, investigate publication, availability, filtering and the section or app that supplies the product grid.
Shopify’s terminology and collection capabilities evolve, so confirm whether the store is using a product or variant source before applying an older tutorial. Do not infer that a variant-based condition guarantees a particular card or image treatment in every theme. The data selection and its rendering need separate checks. This distinction also prevents a product status issue from being misdiagnosed as an all-versus-any error.
Test price and inventory boundaries deliberately
Boundary conditions deserve explicit samples. For a price rule, test below, exactly at and above the threshold. For an inventory-related condition, consider the store’s location and selling configuration instead of assuming that one positive number represents stock available to every customer.
An illustrative ceramics retailer may expect a campaign collection to contain only immediately dispatchable mugs. If the collection uses a loose classification condition while stock handling is left to another system, the visible result may not match that promise. The solution begins with agreeing what dispatchable means for that store. It is not necessarily another collection condition. Test the actual product page and checkout alongside membership when the collection title makes an availability promise.
Create a release sheet for the change
Record the original rule, proposed rule and expected sample before editing the live collection. Keep the collection URL stable unless there is a separate reason to change it. Ask colleagues to avoid simultaneous edits while the test runs, so the observed result can be attributed to one change.
| Sample to include | Expected result to record | Risk it catches |
|---|---|---|
| Clear positive match | Included | Missing qualification data |
| Clear negative match | Excluded | Overly broad any logic |
| Exact threshold value | Agreed boundary outcome | Wrong comparison operator |
| Each excluded group | Excluded where required | Negative-condition logic error |
| Recently imported product | Correct classification | Integration overwriting fields |
| Multiple-variant product | Matches the chosen source behaviour | Product-versus-variant assumptions |
Save screenshots or exports of the sample results. When Shopify needs time to recalculate, check again after the update settles before changing the rule a second time.
Check the next catalogue update
A collection is not stable merely because it passes immediately after a manual correction. Run the next normal product import, supplier feed or merchandising update through the same sample. If a classification field changes, find out which system owns it and whether the new value is intentional.
Add a short review to the campaign preparation routine. Check for empty collections, unexpected category mixing and key products that have fallen out. Review customer-facing labels alongside the data: “under £30” and “available now” are promises readers can assess. Link the collection naturally from relevant navigation and content once the selection is dependable. The broader collection merchandising guide covers ordering and trading decisions after membership is correct.
StoreBuilt point of view
The strongest collection rule is one a merchandiser can explain using a handful of real products. Start with the intended set, translate it carefully, and test both inclusion and exclusion. Our Shopify implementation services can help when data feeds, complex eligibility or custom theme grids make the result difficult to control. More conditions are useful only when they make the customer-facing selection more accurate.
Related reading: Shopify collection merchandising rules uk 2026.
Sources and next step
Platform guidance checked on 20 September 2026. The diagnostic examples and acceptance frameworks are StoreBuilt editorial recommendations; no client performance figures are claimed.
Contact StoreBuilt to turn the findings into a tested implementation plan.