Prime MOQ

Check A Product

Pick any product and see exactly which rule enforces it, what a buyer has to do to check out, and why every other matching rule lost. Free on every plan.

Prime MOQ Team

Prime MOQ Team

Updated · 3 min read

Short answer

Check a product, in the Rules list header, takes one product and shows which rule enforces it for each limit type, the plain-language outcome for a buyer, and every other rule that matched the product but lost, with the reason. It is the fastest answer to "why isn't my rule working" and it is free on every plan.

  • Open it from the Rules list header. Pick a product, or use Change product to switch.
  • It shows the enforcing rule for each limit type, Quantity, Order value and Weight, separately.
  • Matched but not enforced lists every rule that lost the product, and why.
  • No rule enforced means the product is outside every active rule's scope.
  • Create a rule for this product starts a new rule with that product already selected.
  • Free on every plan, by design.

What it answers

The page describes itself in one line:

Check a product Pick any product to see exactly which rule enforces it, and why every other matching rule lost.

Most "my rule is not working" questions are really "a different rule is enforcing this product" or "no rule covers this product". This page answers both for one product, from the live rules, without you reading through every rule's scope.

Open it

Go to Rules and click Check a product in the page header. Click Choose a product and pick one from your catalogue. To look at another one afterwards, click Change product.

Reading the result

SectionWhat it shows
Enforced on this productOne line for each limit type, Quantity, Order value and Weight, with the rule that enforces it, shown as "{name} · {scope} scope", or No rule enforced for that type.
The outcomeA plain sentence: "A buyer must satisfy" followed by the limits that apply, or "A buyer can order any amount of this product."
Matched but not enforcedEvery other rule whose scope includes this product but which lost it, with the reason it lost and an Open rule link.

Limit types are checked separately because a product can be held by one Quantity rule, one Order value rule and one Weight rule at the same time. Only rules of the same limit type compete with each other.

Why a rule lost

Each row under Matched but not enforced gives one of three reasons, in the order precedence applies them:

ReasonWhat it means
More specificThe enforcing rule targets a narrower scope, for example specific products rather than a collection.
Higher priorityBoth scopes are equally specific, and the enforcing rule has the higher Priority.
Created earlierSame kind of scope, same priority, and the enforcing rule was created first.

That list is the precedence described in When Two Rules Cover the Same Product, applied to one product.

No rule enforced

If a limit type reads No rule enforced and nothing appears under Matched but not enforced, no active rule's scope includes this product. Check the scope, schedule and status of the rule you expected, as covered in Troubleshooting, Why a Rule Is Not Working.

If you want one, click Create a rule for this product. It opens a new rule with this product already selected in the Products card, so you do not have to pick it again.

What it does not check

The page answers which rule owns a product. It does not run a cart, so it does not tell you whether a particular shopper is affected. Customer eligibility, countries and the counting mode still decide that at checkout. If the right rule is enforcing and a test still is not blocked, those are the next things to check.

Free on every plan

Check a product is never gated. Understanding what is enforced, and why, is free in Prime MOQ. What Pro adds is acting across the whole store at once, such as the Overlaps page, which gathers every competing pair of rules shop-wide.

Common mistakes

  • Reading No rule enforced as a broken rule. It usually means the rule is not active, has not started yet, or does not include this product. The rule itself may be fine.
  • Expecting one rule per product. A product can have a different enforcing rule for each limit type. Read every line under Enforced on this product.
  • Testing with a variant outside the rule. Precedence is decided per variant. If some variants of a product follow one rule and some another, open the enforcing rule's coverage card for the variant breakdown.
  • Stopping at the right rule. If the enforcing rule is the one you expected, the problem is eligibility, countries or counting mode, not precedence.

Frequently asked questions

Is Check a product a paid feature?

No. It is free on every plan and is designed never to be paywalled, because it is the page that answers why a rule is not working.

Why does a product show a rule I did not expect?

Another rule of the same limit type won it, usually because its scope is more specific. The Matched but not enforced list shows your expected rule and the reason it lost. To change the outcome, narrow the other rule, raise your rule's priority on Pro, or take the product over from the losing rule's page.

Why is a rule listed under Matched but not enforced when it is active?

Being active is not enough. When two active rules of the same limit type include the same product, only one enforces it, and the other appears here with the reason it lost.

Does the page reflect changes immediately?

Yes. It reads the current rules each time you pick a product, so after you change a scope or priority, pick the product again to see the new outcome.

Can I check a whole collection at once?

No. The page checks one product at a time. To see every conflict in the store together, use the Overlaps page on Pro, or the Coverage column in the Rules list, which is free.

Best for: Anyone whose rule is not applying to a product they expected it to, before working through a longer checklist.

Applies to: All rule types, All plans

Did this answer your question?

Related articles

Still stuck?

Tell us what you are trying to set up and we will reply within 24 hours.

Contact support

We use one cookie to remember this choice, and Google Analytics only if you say yes. Nothing analytics related loads until you do. Read the cookie policy.