Can Shopify enforce a minimum order quantity for wholesale?

Yes, but properly requires two layers. Storefront messaging tells wholesale customers the MOQ and updates as they add items, while a checkout validation Shopify Function blocks the order if it's still under the minimum. Messaging alone can be bypassed via direct or accelerated checkout, so enforcement needs the server-side check.

How do I set a minimum order quantity for only wholesale customers on Shopify?

Apply the rule by customer eligibility — for example customers tagged as wholesale or in a B2B company. Checkout validation can require a minimum quantity (or value) only for those customers, so retail shoppers are unaffected while wholesale orders must meet the MOQ before they can complete.

Why isn't a storefront MOQ message enough for wholesale?

Because it's advisory. A customer can reach checkout via a direct link, a saved cart, or accelerated checkout that skips the message, and place an order under the minimum. To actually stop under-MOQ orders you need server-side checkout validation, with the message there to guide, not to enforce.

Shopify Minimum Order Quantity for Wholesale: How to Enforce It

How to enforce a minimum order quantity (MOQ) for Shopify wholesale customers — storefront messaging to guide them and checkout validation to enforce it, so orders can't slip through under the minimum.

To enforce a minimum order quantity for wholesale customers on Shopify, you need two layers working together. The first is storefront messaging that tells a wholesale buyer the MOQ and updates as they add units, so they know where they stand. The second is checkout validation — a Shopify Function that blocks the order server-side if the cart is still under the minimum. And both are applied by customer eligibility, so the rule only affects wholesale accounts, not retail shoppers. Messaging guides; the Function enforces. Skip the second layer and orders slip through under your minimum through paths the message never sees.

The two-layer principle

A working MOQ is not one feature — it’s a guide layer and an enforce layer that do different jobs:

Guide (storefront messaging). Set expectations early. A wholesale customer landing on a product or in the cart should see the minimum (“Wholesale orders require at least 24 units”) and, ideally, their progress toward it. This reduces failed checkouts and frustration.
Enforce (checkout validation). Guarantee the rule holds. A Shopify Function inspects the cart at checkout and blocks the order if the quantity is below the MOQ — for eligible customers only.

Messaging improves the experience for the honest majority. Validation catches everyone else. You need both, because each covers what the other can’t.

Why messaging alone fails

The most common wholesale MOQ setup is cosmetic: a theme snippet or cart app checks the quantity and, if it’s too low, hides the checkout button or shows “Add 6 more units.” That helps honest buyers, but it isn’t enforcement. The check lives in JavaScript on the storefront — and the storefront is not where orders are created.

Everyday paths walk straight past it:

Direct checkout links and accelerated checkout. Shop Pay, PayPal, Apple Pay and Google Pay buttons — plus a bookmarked /checkout URL or a saved cart — can skip the cart page entirely, so a rule that only lives on the cart never runs.
Timing and edits. A buyer can reach the minimum, let the button appear, then reduce a quantity in a way the storefront check doesn’t re-evaluate before they check out.

The result is wholesale orders below your fulfilment minimum — orders that cost you money to pick, pack and ship. If the MOQ is a real business term, advisory messaging isn’t enough.

How checkout validation works

Shopify’s enforcement mechanism is cart and checkout validation, delivered as a Shopify Function. It’s code you deploy that Shopify runs on its own servers during checkout. It receives the cart — line items, quantities, totals, the signed-in customer and their tags or company — evaluates it against your rules, and can return an error that blocks the order until the cart qualifies.

Because it runs inside Shopify’s checkout rather than in the browser, it can’t be skipped by a direct link, an accelerated checkout button, or a last-second cart edit. If the cart is under the MOQ, the buyer sees your message and cannot complete payment. That’s the difference between showing a rule and enforcing one. For the general mechanics beyond wholesale MOQs, see minimum and maximum order rules in Shopify checkout.

Applying it to wholesale only

The piece that makes this a wholesale MOQ rather than a store-wide one is customer eligibility. A validation Function can read the signed-in customer and apply the rule conditionally:

Customer tags — e.g. only carts belonging to a customer tagged wholesale must meet the MOQ.
B2B company / location — with Shopify B2B, the rule keys to the company or company location the buyer is purchasing for.
Metafields — a per-account or per-company MOQ stored as a metafield, so different wholesale tiers can have different minimums.

Retail shoppers never see the rule; wholesale accounts can’t check out under it. This is also how you keep separate B2B pricing and rules from leaking into the retail storefront — the same discipline behind tiered pricing by customer group.

MOQ by quantity, value, or per product

“Minimum order quantity” can mean a few different things — decide which matches your fulfilment economics:

MOQ type	Example rule	When to use
Total units	”At least 24 units across the cart.”	Simple case pack / shipping minimum.
Order value	”At least €500 before checkout.”	When cost is driven by invoice value, not units.
Per product / per variant	”Each SKU ordered in multiples of 12.”	Case-pack products that ship by the box.
Per collection	”Made-to-order lines need a minimum of 3 each.”	Different rules for different product families.

A validation Function can enforce any of these — or several at once — because they share one shape: read the cart, decide if it qualifies, block it with a message if not. Most wholesale programs use total units or order value; per-product case packs are common in apparel and food.

Storefront UX: show progress toward the MOQ

The Function is the enforcement layer, but it shouldn’t be the first time a wholesale buyer learns about the minimum. Good storefront UX does the guiding:

State the rule up front on wholesale product pages and in the cart (“Wholesale minimum: 24 units”).
Show progress — “18 of 24 units — add 6 more to check out” updates as they build the cart.
Keep the copy specific. A clear number a buyer can act on beats a vague “minimum not met.”

Do this well and most wholesale carts arrive at checkout already qualifying, so the validation Function rarely has to fire. The message drives conversion; the Function guarantees correctness.

Native vs app vs custom

There’s no native Shopify toggle that enforces a wholesale-only MOQ at checkout, so your options are:

A validation app. Several apps expose min-quantity or min-value rules through a UI, built on the validation Function API. Fastest path if your rule is standard (a global minimum, a simple per-tag condition) and you’re happy to configure rather than code. Verify it enforces at checkout, not just on the cart page, and that it can scope to your wholesale customers.
A custom Shopify Function. When the logic is specific — per-company or per-tier MOQs, rules that read metafields or an external system, per-product case packs, or a MOQ combined with other B2B conditions — a custom validation Function gives you exactly the rule you need. It’s also the right call when you’re consolidating overlapping apps.
Storefront messaging. Regardless of which enforcement path you choose, add the guide layer in the theme so buyers see the rule early.

Common mistakes

Trusting a storefront message as enforcement. The biggest one — if it isn’t a server-side validation Function, it can be bypassed.
Only testing the cart page. Accelerated checkout skips it; if you didn’t test wallet buttons, you didn’t test the rule.
Applying the MOQ to everyone. Forgetting customer eligibility blocks retail shoppers too. Scope the rule to wholesale tags or company.
Vague error copy. A blocked checkout with no clear reason reads as a broken store and loses the order you were trying to protect.
Confusing MOQ with pricing. A minimum-quantity rule is separate from wholesale discounts. If your prices aren’t applying correctly, that’s a different problem — wholesale discount not working covers it.

Implementation notes

Decide where the rules live. Hard-coded is simplest; metafields or an app UI let staff change minimums per account without a deploy. Choose based on who needs to edit them.
Test the boundaries. Exactly at the MOQ, one unit under, mixed carts, guest vs logged-in wholesale, and each customer tag or company. And always test accelerated checkout — that’s where storefront-only rules leak.
Write actionable error messages. “Add 6 units to reach the 24-unit wholesale minimum” beats “Order not valid.” The message is the whole UX of a blocked checkout.

When to build

Reach for a custom validation Function when your MOQ is specific to your wholesale program, must be checkout-safe, or combines with other B2B conditions no single app configures cleanly — per-company minimums, per-product case packs, or eligibility tied to customer data. If a maintained, checkout-enforcing app already covers a standard minimum and can scope to your wholesale customers, use it. If the logic is genuinely yours, own it as a Function so it can’t be bypassed. For how MOQs fit alongside catalog and pricing controls, see our Shopify B2B & wholesale solution, or get a free profit audit to find out whether an app covers your case or a build is justified.

Wholesale orders slipping under your minimum? Tell us your MOQ rules — we’ll set up storefront messaging plus checkout validation so under-minimum wholesale orders can’t complete. See Custom Apps & Shopify Functions or get a free profit audit.