What it does
Normally you type a limit into the rule: a minimum of 12, a maximum of 200, a pack size of 6. With a metafield as the source, the rule reads that number from your store's data instead. Change the metafield in Shopify admin, or from another system that writes to it, and the limit follows without anyone editing the rule.
The control is Value source, a small connect icon beside each limit field in the Conditions card. It offers two choices:
- A number I type, the normal behaviour.
- Shop metafield, which connects the field to a metafield you choose.
It works on any limit field: minimum, maximum and multiple on Quantity rules, and the minimum and maximum on Order value and Weight rules.
Shop metafield is the only choice today
This is the most important thing to know about this feature. The only metafield owner you can pick is a shop metafield: one value for the whole store. Variant and product metafields have been removed from the picker, and customer metafields are temporarily hidden.
That is a change to the picker only. A rule connected earlier to a variant, product or customer metafield keeps working. It still resolves, still shows its connection in the editor, and still enforces. You cannot connect a new field to those owners, or switch a field to them, but nothing you already set up has stopped.
If you have read "Shop metafield sets min, max, pack size" on the App Store listing, that is the whole of what is offered for new rules: one store-wide value per field.
Connect a field
Create the metafield first. In Shopify admin, add a custom shop metafield definition with a number type. If none exists, the picker says so: "No custom shop metafields found. Create one in Shopify admin first."
Open Value source beside the field, choose Shop metafield, then pick the metafield from the list. The field shows a Connected badge.
Set the fallback. Every connected field needs a value under Falls back to this when empty. It is used whenever the metafield has no value. A rule will not save without it.
Set Never above, if you want a ceiling. Or leave it on No ceiling.
Check the summary, then save.
The supporting controls
| Control | In-app text | What it is for |
|---|---|---|
| Fallback | "Falls back to this when empty" | The value used when the metafield is empty. Required. |
| Never above | "A safety ceiling on whatever the metafield returns, even a wrong one." | The highest value the field can take, whatever the metafield says. Or No ceiling. |
| Resolution summary | "Resolved on {resolved} of {total} variants · {fallback} use the fallback" | How many variants got a value from the metafield, and how many fell through to the fallback. |
| Freshness | "last synced {time}" | When Prime MOQ last read the metafield values. |
Why Never above matters
The value now comes from data you edit outside Prime MOQ, where there is no check that it makes sense. Type 1000 instead of 100 into the metafield and that is your live maximum. Never above is the guard: the field never goes higher than it, even when the metafield is wrong.
The editor also warns you about two combinations that cannot work. A Never above lower than the rule's minimum makes every order impossible. A fallback higher than Never above means the ceiling always wins.
Reading the resolution summary
The summary tells you, before you activate, how the rule will behave across the variants in its scope. With a shop metafield the value is the same for every variant, so you will normally see all of them resolved, or all of them on the fallback when the metafield is empty. Rules connected earlier to variant or product metafields are where the split matters: every variant without its own value falls back.
Common mistakes
- Looking for variant or product metafields in the picker. They are no longer offered for new connections. Use a shop metafield, or type the number.
- Assuming an old variant metafield rule has stopped. It has not. It keeps resolving and enforcing as before.
- Leaving Never above on No ceiling for a maximum. A typo in the metafield then becomes the real limit. Set a ceiling you would never go above.
- Creating the metafield with a text type. The limit needs a number. Use a number definition.
- Expecting an instant change. Check "last synced" after editing the metafield to see when the new value was read.