A collection can contain the product you wanted and still implement the wrong rule. A Clayline mug belongs in a collection intended for Clayline mugs, but that single positive case cannot show whether bowls from the same vendor or mugs from another vendor will slip in. Prepare the near-match cases before anyone touches the live store.
The useful output is a candidate membership rule and a review sheet, not a published collection. This workflow helps a merchandising coordinator explain what should enter, what should stay out and what still needs an authorized real-account check.
Separate Shopify behaviour from your proposal
Shopify’s current creating-collections guidance uses sources. New collections contain an empty Products source by default; other sources can include variants, existing collections and app sources. Products can be included through conditions or manual selection, and exclusions are also available. [1] Do not start from older instructions to choose a Smart collection type.
The conditions guidance says “is equal to” matches the whole value for product type and vendor. It distinguishes matching all conditions from matching any condition. Tag conditions instead use “includes” and “does not include”; they are not the operators needed for this example. [2]
Those are documented behaviours. The following MAJLS review sheet is our proposed preparation method. Its products, people and results expectations are synthetic and offline. It is not a tested Shopify account, an execution receipt or evidence of an available MAJLS integration.
1. Write the desired membership in ordinary language
Hala, the fictional merchandising coordinator, records: “Include only products whose Type is exactly Mug AND whose Vendor is exactly Clayline.” Nour, the fictional store owner, must approve any later store edit and publication.
Keep that sentence above the configuration. It gives Nour something to compare with the proposed operators. A product title such as “Clayline mug” is a convenient case label, not the source of truth for Type or Vendor. Missing or unknown values go to Hala and Nour for resolution; never infer them from a title or photograph.
2. Inventory the whole source scope
Before applying the simple rule, list every source, manual addition and exclusion. Shopify says manually selected products remain in a collection until manually removed, and conditions do not remove manually added products. Additional sources can bring in products too. [1][2]
For this proposed sheet, the scope is deliberately narrow:
- One Products source, selecting whole products.
- No manual additions and no exclusions.
- No other Products, collection, app or variant sources.
- No price, inventory, tax, discount or purchase conditions.
If a real collection differs, enumerate its additional inputs separately. Do not assume changing all to any explains its entire membership. An unexpected bowl might have arrived through manual selection or another source, not through the two conditions being reviewed.
3. Record exact attributes, operators and values
Hala’s filled candidate-rule record reads:
| Field | Proposed value |
|---|---|
| Review-sheet owner | Hala |
| Store-change and publication approver | Nour |
| Source scope | One Products source; whole products; no additions or exclusions |
| Condition 1 | Type — is equal to — Mug |
| Condition 2 | Vendor — is equal to — Clayline |
| Matching choice | Match all conditions |
| Intended membership in the cases below | A only |
| Actual results / evidence | Not yet run |
| Pending work | Authorized owner-run check in a confirmed unpublished candidate |
Use the whole attribute values, not a “contains” approximation. Under Match all, a product must satisfy both conditions. Under Match any, satisfying either condition is sufficient. [2] The comparison below makes that difference visible without making an account change.
4. Compare positive and negative cases
These are expected logical memberships for the stated scope, not observed Shopify results.
| Case | Product label | Type | Vendor | Expected: Match all | Expected: Match any |
|---|---|---|---|---|---|
| A | Clayline mug | Mug | Clayline | IN | IN |
| B | Clayline bowl | Bowl | Clayline | OUT | IN |
| C | Northbank mug | Mug | Northbank | OUT | IN |
| D | Northbank bowl | Bowl | Northbank | OUT | OUT |
A is the positive case: both attributes match. D matches neither condition. Neither distinguishes the intended all-condition rule from an accidental any-condition rule.
B and C are the important near-match negative tests. Each satisfies half the intended rule. Under Match any they enter, contradicting the ordinary-language goal. Keep them in the review sheet; they are not inconvenient catalogue data to delete.
Hala’s mismatch list therefore says: “Candidate Match all agrees with the intended membership for these synthetic cases. Alternative Match any would wrongly include B and C. Actual account mismatches: unknown; Not yet run.” That wording distinguishes logical comparison from execution.
5. Hand Nour a decision-ready sheet
Give Nour the candidate rule, complete source inventory, comparison cases, mismatch list and pending real-account test. Preparing the sheet does not authorize silently removing products, editing tags, renaming vendors, creating a live collection, scheduling publication or changing sales channels.
Recommend a separate, authorized owner-run check in a confirmed unpublished candidate while preserving the existing live state. Shopify documents that a collection can remain unpublished from all sales channels. [1] That is a capability to verify in the current admin, not permission to mutate an account or a guarantee that defaults are safe.
Before any Save, Nour should check actual channel availability and confirm the candidate remains unpublished. Save does not itself guarantee privacy. During the authorized check, record the actual included and excluded products, the source configuration and any mismatch evidence beside the expectations. Until then, the actual-results field stays “Not yet run.”
Nour separately decides public availability and customer-facing correctness. A successful membership comparison alone does not establish stock availability, variant promises or URL behaviour.
A possible MAJLS-agent role is drafting this candidate sheet from admitted catalogue fields, with unknowns preserved. That does not assert account access or autonomous store control. The reusable rule is simple: test products that match only half of the intended rule.
