# Troubleshooting, Why a Rule Is Not Working

> Source: https://primemoq.app/help/troubleshooting/why-a-rule-is-not-working
> Collection: Troubleshooting
> Updated: 2026-08-02

A checklist in the order that actually catches the problem, covering rules that do not block, messages that do not show, and weight and repurchase edge cases.

**Short answer.** Check the status badge first. Scheduled, Expired or Deactivated explains most cases before you look at the rule logic. Then check the Products scope really includes your test product, that How to count matches your intent, and that Customer eligibility and Countries are not excluding your test account.

## Key takeaways

- The status badge catches the problem more often than anything else. Start there.
- A message that does not show is nearly always the app embed, not the rule.
- The storefront message and the checkout block are separate. Always confirm by attempting a checkout.
- A weight rule that never triggers usually means missing product weights in Shopify.

## Why is my rule not blocking checkout?

Work through this in order. It covers the checks in the order they actually catch
the problem, most often first.

1. **Check the status badge in the Rules list.** **Scheduled** means the start
   date has not arrived. **Expired** means the end date has passed. **Deactivated**
   with a tooltip means the rule currently matches zero products. Only **Active**
   rules enforce. See [Rule Statuses](/help/managing-rules/rule-statuses).
2. **Check the Products scope includes the product you are testing.** Use
   **Calculate items count** in the rule editor to confirm your test product is
   genuinely in scope.
3. **Check How to count matches your expectation.** A "minimum 6" rule set to
   *Each item separately* will not block a cart holding 3 plus 3 of two different
   matching products. That combination only fails under *Combined total*. See
   [How to Count](/help/rule-types/per-item-vs-combined-total).
4. **Check Customer eligibility.** A rule scoped to a tag, segment or named
   customers will not trigger for anyone outside that group, including your own
   test account if it is not tagged the same way.
5. **Check Countries.** If country restrictions are set, the rule only applies to
   shoppers checking out from those countries.
6. **Remember the message and the enforcement are separate.** Even if the message
   is not visible, checkout enforcement runs independently. Always confirm by
   actually attempting checkout with an invalid cart, not by looking at the
   product page.

## Why can I not edit my rule's fields?

If every field is greyed out, the rule is currently **Active**. Existing active
rules are locked on purpose, so a scope or condition change cannot silently alter
what is blocked while shoppers are hitting it. Click **Deactivate rule** in the
page header, make your changes, then reactivate. See
[Editing, Duplicating and Deleting a Rule](/help/managing-rules/edit-duplicate-and-delete-rules).

## Why is the limit message not showing on my product page?

This is almost always a storefront setup issue rather than a rule configuration
one.

1. **Confirm the app embed is enabled** in your theme editor, through **Settings >
   Message position > Edit theme**, or **Online Store > Themes > Customize > App
   embeds**. This is by far the most common cause.
2. **Confirm your theme supports Online Store 2.0 app embeds.** Legacy pre-2.0
   themes do not support app embeds or app blocks at all.
3. **If you are using an app block instead**, confirm it was actually added to the
   section and template you are viewing. App blocks are placed per template,
   unlike the embed which applies automatically.
4. **Confirm the rule is Active and matches the product.** A message never shows
   for a product with no matching active rule.
5. **Test in an incognito tab.** Some themes cache admin and preview sessions in a
   way that hides live storefront elements.

## Why did my rule start or stop enforcing unexpectedly?

- **Check the Schedule card.** A rule with a future start date shows as
  *Scheduled* and only begins at that time. A rule with a past end date shows as
  *Expired* and stops on its own.
- **Check whether the product scope changed.** With the auto-update toggle on,
  new products matching your scope get pulled in over time, so a rule can start
  applying to products it did not originally cover.
- **Check whether someone deactivated it.** The **Deactivate rule** action in the
  page header takes effect immediately.

## My rule shows "Calculating"

That is a normal, temporary loading state, not an error. Saving a rule, or a bulk
activate or deactivate, triggers a background job that resolves the exact list of
matching products and variants. The Rules list polls automatically and updates
within a few seconds. No action needed.

## A weight-based rule is not triggering

Check that every product in scope has a **weight set on the product or variant in
Shopify**. A product with no weight, or a weight of 0, contributes nothing to the
total, which can make a genuinely heavy cart pass a maximum-weight check. See
[Weight-Based Order Limits](/help/rule-types/order-weight-limits).

## A repurchase limit is not blocking a repeat order

Confirm the customer was **logged in** for both the original and the repeat order.
Repurchase checks rely on account purchase history and cannot be evaluated for
guest checkouts. See
[Repurchase Limits](/help/rule-types/limit-purchases-per-customer).

## Still stuck?

Reach out from the **Need help?** card on any rule editor page, or contact support
directly. We are glad to dig into a specific rule with you.

## FAQ

### What should I check first when a rule does not work?

The status badge in the Rules list. Scheduled, Expired and Deactivated between them explain most reports, and each points at a different fix: the schedule, the schedule again, or the product scope.

### My rule is Active but nothing is blocked. What now?

Confirm the test product is genuinely in scope with Calculate items count, then check How to count. A per-item minimum will not block a cart that only meets the threshold when several products are added together.

### The message shows on the product page but checkout goes through. Is that possible?

That combination points at the rule not matching the final cart, most often because of customer eligibility, a country restriction, or a scope that covers fewer products than you thought. The checkout Function and the message read the same rule, so a mismatch means the conditions differ from your expectation.

### Checkout is blocked but no message appears anywhere. Why?

The app embed is not enabled. Enforcement runs regardless of the embed, so shoppers get stopped with no earlier explanation. Turning the embed on fixes the explanation, not the block.

### Why does my rule apply to products I never selected?

Check whether the auto-update, "on the fly", toggle is on. It pulls in new products matching your scope as your catalogue grows, which is intended but can be surprising months later.

### Does testing from my Shopify admin session give accurate results?

Not always. Use an incognito tab, since some themes cache admin and preview sessions in ways that change what renders on the storefront.

**Best for:** Any rule that is not doing what you expected, before contacting support.

**Applies to:** All limit types