Shopify B2B Minimum Order Quantities: How to Enforce Them
Running a wholesale operation on Shopify comes with a challenge that most platforms weren't built to solve out of the box: making sure your business buyers actually order enough to make each transacti
Running a wholesale operation on Shopify comes with a challenge that most platforms weren't built to solve out of the box: making sure your business buyers actually order enough to make each transaction worth your while. Whether you're supplying corporate offices, retail chains, or event companies, a single-unit purchase from a wholesale account doesn't just break even — it often costs you money once you factor in picking, packing, invoicing, and account management. Minimum order quantities (MOQs) exist to protect your margins and keep your fulfilment operation sane.
The problem is that Shopify's native checkout doesn't enforce MOQs at the product, variant, or cart level without some additional configuration. A wholesale customer who stumbles into your store can technically add one unit to their cart and check out, leaving you to either fulfil an unprofitable order or chase them down manually. That's a process that doesn't scale, and it creates friction in relationships you've worked hard to build.
In this post, you'll learn exactly how to enforce minimum order quantities on Shopify — whether you're using Shopify's built-in B2B features, third-party apps, or custom logic. We'll cover the different types of MOQs, how to communicate them clearly, and how to avoid the edge cases that trip up most merchants.
Understanding the Different Types of Minimum Order Quantities
Before you start configuring anything, it helps to be clear on what kind of MOQ you actually need to enforce. There are three common types that Shopify merchants use in practice: per-product MOQs, per-variant MOQs, and cart-level order minimums. Each one serves a different commercial purpose, and conflating them leads to configurations that don't quite fit your business model.
A per-product MOQ means a buyer must purchase at least a certain number of units of a specific product — for example, a minimum of 12 units of your branded tote bag, regardless of colour or size. A per-variant MOQ goes one level deeper, requiring at least 6 units of a specific size or colour. This is common in apparel and accessories, where your production run economics are tied to individual SKUs rather than the product family as a whole.
A cart-level minimum is different again — it's a total order value or quantity threshold that the entire basket must meet before checkout is allowed. For example, you might require all wholesale orders to reach £250 before shipping, regardless of what's in the cart. Many merchants actually need a combination of all three: a per-variant MOQ to ensure sensible pick quantities, plus a cart minimum to justify the administrative cost of processing the order at all.
Shopify's Native B2B Features and Their Limitations
Shopify's B2B on Plus introduced several features aimed at wholesale merchants, including company profiles, price lists, and payment terms. For merchants on Shopify Plus, these tools provide a solid foundation for managing wholesale accounts — but they still have meaningful gaps when it comes to enforcing MOQs natively. Price lists, for instance, let you apply volume pricing and quantity breaks, but they don't prevent a customer from purchasing below your minimum.
As of 2024, Shopify's native B2B functionality does not include a built-in MOQ enforcement mechanism. You can set quantity increments at the product level in some configurations, which ensures buyers can only purchase in multiples of a set number — for instance, packs of 6 or 24. However, this is not the same as a hard minimum, and it still doesn't address cart-level order minimums or mixed-product basket requirements.
For merchants not on Shopify Plus, the native B2B tools aren't available at all, making third-party solutions the only real option. Even Plus merchants often find that the native tooling covers perhaps 60–70% of their wholesale logic, and that the remaining edge cases — like per-variant rules, mixed-account logic, or conditional minimums by customer tag — require additional apps or custom development to handle properly.
Using Shopify Scripts and Functions to Enforce MOQs
For merchants with development resource available, Shopify Functions (the modern successor to Shopify Scripts) offer a powerful way to enforce order rules at the checkout level. Functions run server-side and can validate cart contents against custom logic before allowing a buyer to proceed — making them genuinely reliable for MOQ enforcement rather than just a front-end warning that a savvy buyer could work around.
A typical Shopify Function for MOQ enforcement would check each line item in the cart against a metafield stored on the product or variant — for example, a metafield named wholesale.min_qty with a value of 12. If any line item falls below its threshold, the function blocks checkout and returns a descriptive error message. This approach is precise, scalable across large catalogues, and doesn't require a separate app subscription once it's built and deployed.
The catch, of course, is that building and maintaining custom Shopify Functions requires developer time and ongoing maintenance as your catalogue evolves. If your product range is relatively stable and your team has engineering capacity, this is a robust long-term solution. If you're a lean team adding SKUs regularly, you'll likely find that maintaining metafield values across hundreds of variants becomes its own operational overhead — at which point a well-built app starts to look like the smarter investment.
Enforcing MOQs with Third-Party Shopify Apps
The app ecosystem offers several solutions for MOQ enforcement, ranging from simple quantity restrictor tools to full wholesale management platforms. When evaluating apps, the key questions to ask are: does it enforce at checkout (not just display a warning), does it support both product-level and cart-level rules, and does it integrate cleanly with your existing customer tags or B2B account structure?
Some apps work by injecting JavaScript into your storefront to show warnings when quantities fall below minimums — but these client-side approaches are fragile. They can be bypassed by savvy buyers, they break when themes are updated, and they don't always play nicely with headless or custom storefronts. The better apps use Shopify's checkout extensibility APIs or Functions to enforce rules at the server level, which is far more reliable in production.
If you're managing wholesale alongside a standard DTC storefront — which many Shopify merchants do — you'll also want an app that applies MOQ rules conditionally based on customer type. For example, applying a 24-unit minimum only to accounts tagged wholesale, while letting retail customers purchase single units freely. QuoteFlow is one example of an app designed to handle exactly this kind of mixed-channel complexity, allowing you to configure rules that reflect the reality of how your wholesale business actually operates.
Communicating MOQs Clearly to Your Buyers
Enforcement is only half the job — clear communication prevents the confusion and frustration that leads to abandoned carts and support tickets. Many merchants make the mistake of burying their MOQ policy in a terms and conditions page that nobody reads, then wonder why wholesale customers keep attempting to place non-compliant orders. The most effective approach is to surface MOQ information at every point in the buying journey where a decision is being made.
On product pages, display the minimum order quantity directly beneath the quantity selector — something like "Minimum order: 12 units" in bold text adjacent to the add-to-cart button. In your cart, if the MOQ isn't met, show a specific message that tells the buyer exactly what they need to add, rather than a generic "your order doesn't meet our minimum" error. Specificity reduces support load and helps buyers self-serve.
For account-managed relationships — say, a buyer at a corporate client or a regional retail chain — it's also worth including MOQ details in your wholesale onboarding emails and any PDF order guides you send. When buyers understand the rules before they start ordering, compliance rates improve significantly and you spend less time manually reviewing and correcting orders before they reach your warehouse.
Testing and Maintaining Your MOQ Rules Over Time
Once you've configured MOQ enforcement, testing it thoroughly before going live is non-negotiable. Create a test wholesale account, add products at various quantities — including edge cases like exactly one unit below the minimum, exactly at the minimum, and above it — and verify that the checkout behaves correctly in every scenario. It's also worth testing what happens when a buyer has a mix of compliant and non-compliant line items in the same cart, as this is where many configurations fall apart.
MOQ rules also need to be treated as living configuration, not a set-and-forget task. As your product catalogue changes, new SKUs need to be assigned the correct minimums, and discontinued products should have their rules cleaned up to avoid ghost configurations causing unexpected behaviour. Building a simple internal process — even just a column in your product management spreadsheet — helps ensure that MOQ data stays accurate as your range evolves.
Finally, review your MOQ thresholds at least annually against your actual cost data. If your picking and packing cost per order has increased, or if you've onboarded new fulfilment infrastructure with different unit economics, your minimums may need to be revised upward to protect margin. The goal isn't to make ordering difficult — it's to make sure that every order that ships is one that makes commercial sense for your business.
Conclusion
Enforcing minimum order quantities on Shopify requires more than just displaying a number on a product page — it takes the right combination of platform features, app tooling, and clear communication to make the policy stick. Whether you're using Shopify Functions for custom logic, a third-party app for a no-code solution, or a combination of both, the key is ensuring that enforcement happens at the checkout level and applies consistently to the right customer accounts. Pair that with transparent MOQ messaging throughout the buying journey, and you'll reduce friction, protect your margins, and build wholesale relationships that actually scale.
Key takeaways: Know which type of MOQ you need before you build anything. Use server-side enforcement rather than front-end warnings. Communicate minimums clearly at every touchpoint. Review your thresholds regularly as your costs evolve.
Try QuoteFlow free at saltai.app — no credit card required.
SaltAI Team
SaltAI builds focused Shopify apps for food merchants and general merchants. Every app is tested in production at a real food store — including Vanda's Kitchen — before it ships.