Verify rule matching, storefront feedback, and checkout behavior together. Use one cart that should pass and one that should fail. An enabled badge on the dashboard alone is not a complete test.
Before you test
- The rule is active and the current time is within its effective period.
- The test product, collection, or variant matches the rule and is not excluded.
- If the rule targets customer tags, email, country, or login state, use a matching test customer.
- The Theme App Embed is on in the published theme.
- Shop-level and rule-level Checkout Validation are on, and Allow all customers to complete checkout is off.
Paired test: Maximum of two items
| Test | Cart | Expected result |
|---|---|---|
| Passing | Two units of matching products | This rule does not block checkout |
| Failing | Three units of the same products | Limit feedback appears; checkout is blocked |
| Outside scope | Only products that do not match the rule | This rule does not block checkout |
- Test the passing cart on the storefront. Record the items, quantities, and checkout result.
- Increase the same cart beyond the limit. Look for a product-page or cart message, then try checkout.
- For a scoped rule, test out-of-scope items separately.
- If you use a cart drawer or Buy now, repeat the test through each of those entry points.
If the result is different
No storefront message: Check the Theme App Embed, published theme, rule scope, and warning trigger.
Message appears but checkout proceeds: Check shop-level and rule-level checkout validation and the allow-all checkout preference.
A compliant cart is blocked: Look for another active rule, a minimum threshold, or a customer or time condition. Record the rule name, cart contents, customer state, and error message before investigating further.
Use a test product or cart to check the outcome before applying this setup across your store.
All guides