Shopify's native quantity rules live in Products → Catalogs and let you set a minimum, maximum and increment per product. They apply to B2B customers buying from that catalog, and within that boundary they are the better option — nothing beats a native feature for reliability. Outside it, they do not apply at all. This is where the boundary sits, so you can tell which side of it you are on before installing anything.
What the native feature does
Shopify B2B lets you build catalogs — a set of products with their own prices, assigned to companies. Quantity rules attach to a product within a catalog:
- Minimum. The fewest units a buyer can order.
- Maximum. The most.
- Increment. The step between valid quantities, which is how case packs are expressed — increment 6 makes 6, 12 and 18 valid and 7 invalid.
These are enforced by Shopify itself, so they hold everywhere. That is the same property a Functions-based app has, and it is the property that matters.
If your requirement is "this product, this catalog, min/max/increment", you are done. Use the native feature, skip the app, and stop reading.
The boundary, stated plainly
Catalog quantity rules apply to B2B customers buying from a catalog. Everything below falls outside that sentence.
You have no B2B setup. A DTC store wanting a minimum on one product has nowhere to put a catalog rule. B2B is a Shopify Plus feature, so for most stores this is where the conversation ends.
Your wholesale buyers are not B2B companies. Plenty of stores serve wholesale through tagged customer accounts rather than the B2B objects — same storefront, same checkout, different terms. Catalog rules do not see those customers.
The rule is about the cart, not a product. A minimum order value, or a minimum across a collection, is not a per-product rule and has no catalog equivalent.
The rule is about a customer over time. "Two per customer, ever" counts across orders. Catalog rules evaluate one cart.
The rule is conditional on something else. Weight, a date range, whether a discount is applied.
The mixed store, which is most stores
The common case is not "B2B" or "DTC" but both, through one storefront.
A brand sells to consumers at retail and to twenty stockists at wholesale, distinguished by a customer tag and a discount, not by a Shopify B2B company record. The stockists need a twelve-unit minimum; the consumers must not see one.
Catalog rules cannot express that, because the stockists are not buying from a catalog. The rule has to key off the customer tag, which is app territory.
It is worth asking whether moving those stockists into B2B proper is the better answer. Sometimes it is — B2B brings payment terms, price lists and company-level accounts. Often it is not, because it is a larger change than the problem justifies, and B2B requires Plus.
Comparing them honestly
| Requirement | Native catalog rules | Functions-based app |
|---|---|---|
| Min / max / increment per product | Yes | Yes |
| Enforced at checkout | Yes | Yes, if built on Functions |
| Applies to non-B2B customers | No | Yes |
| Rules by customer tag | No | Usually |
| Cart-level minimum quantity or value | No | Usually |
| Per-customer limits across orders | No | Sometimes |
| Collection or product-group rules | No | Sometimes |
| Scheduled rules | No | Sometimes |
| Custom error messages | Limited | Usually |
| Cost | Included, needs Plus | Monthly, no Plus needed |
The "sometimes" entries are why the next section exists: the app category is not uniform, and the differences are not on the listing page.
What to check if you do need an app
The only question that separates an app worth having from one that is not: does it enforce at checkout through Shopify Functions, or in your theme?
Theme-level rules are walked around by a cart permalink, a saved cart, a dynamic checkout button or a draft order. If a customer can reach checkout without your rule being evaluated, it is a suggestion.
The test: build a cart permalink that violates the rule — yourstore.com/cart/VARIANTID:1 for a product with a minimum of six — and open it. Blocked at checkout with your message means the rule is real. Reaching payment means it is not, whatever the listing says.
After that, the things that differ: scope (tag, collection, cart, weight), whether limits can count across orders, whether rules can be scheduled, and whether the error message is yours to write. Limit puts checkout enforcement on the free plan, which is unusual — it is often held back for paid tiers, which makes the free plan untestable for the thing that matters most.
What changes if you are not on Plus
Worth stating because it settles the question for most stores: Shopify B2B, and therefore catalogs and their quantity rules, is a Plus feature.
So on Basic, Grow or Advanced the comparison is not "native versus app" at all. It is "app, or nothing", and the decision collapses to which app.
That reframes the cost, too. An MOQ app at a few dollars a month is not competing with a free native feature — it is competing with the Plus upgrade you would need to reach the native feature, which is a different order of magnitude. For a store whose only reason to consider Plus is quantity rules, the app is obviously right.
The reverse is also worth saying. If you are already on Plus and already running B2B, reaching for an app before checking the catalog rules is a small waste. Look at what you have first.
Using both
They are not mutually exclusive, and on a Plus store running real B2B the sensible split is:
- Catalog rules for straightforward per-product minimums for B2B companies. Native, free, reliable.
- An app for everything outside that: DTC limits, tag-based wholesale, cart-level minimums, per-customer caps.
The one thing to avoid is expressing the same rule in both places. When they disagree — and they will, eventually, because somebody updates one — the behaviour is confusing and the debugging is worse. Pick one home per rule and write down which.
One thing native rules do better
Worth saying, because this article could otherwise read as a case for buying something.
Native catalog rules are visible in the buyer's experience in a way an app's usually are not. A B2B buyer in a Shopify catalog sees the increment reflected in the quantity stepper — the field moves in sixes because the catalog says six — rather than discovering the rule when checkout refuses them.
An app can reproduce that with a product-page block, and most good ones do, but it is a block you have to add and position. The native version is simply how the store behaves.
Reliability, too. A native rule cannot be broken by a theme update, an app conflict or a subscription lapsing. For a rule that must hold for years on a Plus store already running B2B, that is a real argument for keeping it where Shopify keeps it.
Where to go next
Work out which side of the boundary each of your rules sits on before choosing anything. If they are all per-product and all B2B, use what you already have.
If they are not, the MOQ guide covers scope, multipliers and how to test enforcement properly. And if your rules used to run on Shopify Scripts, they stopped on 30 June 2026 — worth confirming they were actually migrated.
