Minimum Order Quantity (MOQ) defines the lowest number of items a customer must purchase before they can add a product to the cart or complete checkout. Merchants use MOQ to protect margins, offset packaging and shipping costs, and apply wholesale-style rules such as case packs.
The key point is that Shopify does not offer a single native switch that works for every business model. The right setup depends on whether you sell DTC or B2B, and whether your MOQ applies per product or variant, in fixed multiples, or at the cart level. Understanding this distinction is the foundation for implementing MOQ correctly and without hurting conversion.
Don’t confuse MOQ with a “minimum order amount” (MOV)
Many guides say “minimum order amount” when they actually mean MOQ. These terms are different:
MOQ (Minimum Order Quantity): the minimum number of units a customer must buy (for example, 5+ units of a product).
MOV (Minimum Order Value / Amount): the minimum cart value required to check out (for example, the cart must be ₫300,000+).
Minimum items in cart: the minimum total item count across the cart (for example, at least 3 items, any products).
If your goal is “avoid small orders,” MOQ and MOV can lead to different outcomes. MOQ is best when the rule must apply at the product or variant level, especially for case packs, lot sizes, pack multiples, wholesale (B2B), or packaging and handling constraints.
Does Shopify support MOQ “natively”?
If you run B2B or wholesale using Shopify B2B Catalogs, Shopify can support quantity rules and quantity increments that match common wholesale logic. This includes minimum purchase quantities, buying in multiples (case packs), and tiered pricing based on quantity.
This is the most “system-native” path because the rules live inside the B2B catalog and align with the Shopify B2B workflow.
If you sell DTC, or you are not using B2B Catalogs, you will need a different approach to enforce MOQ on the storefront (product page, cart, or checkout).
3 Common Ways to Set MOQ on Shopify (Choose Based on Your Use Case)
Method 1 — Product/Variant-Level MOQ Using an App (Fast, Flexible, No Code)
This is the most practical option when you need precise control without touching theme code. It works best if you want:
- MOQ per product or per variant
- Extra rules such as maximum quantity, quantity increments, or customer-tag targeting
- A no-code setup that is easy to manage at scale
Most merchants use apps in the “quantity breaks / order limit” category. In the Orichi ecosystem, this is handled by OC Quantity Breaks & Order Limit, which lets you set MOQ, control purchase limits, and expand into volume pricing when needed.
Typical setup flow for product-level MOQ:
- Install an MOQ or order limit app from the Shopify App Store.
- Enable the app embed so rules run on the storefront.
- Open the Limit or Purchase Rules section (label varies by app).
- Select Minimum Quantity and add a maximum if required.
- Choose the scope: product, collection, or variant.
- Save the rule and test it directly on the storefront.
This method is ideal if you manage many SKUs, use different MOQ rules per product, or need flexible logic by customer group.
Method 2 — MOQ by Multiples (Sell in Packs or Cases)
Wholesale-style selling often requires customers to buy in fixed multiples such as 6, 12, or 24 units. In this case, a simple minimum quantity is not enough. You also need quantity increments or enforced multiples.
For best results, enforcement must be clear and consistent:
- On the product page to prevent errors early
- In the cart to stop customers from bypassing rules by editing quantities
Implementation checklist:
- Clearly state “sold by pack” or “sold by case” near the quantity selector
- Ensure the rule also applies in the cart
- Use plain-language error messages instead of technical alerts
When done correctly, this reduces friction and avoids failed checkouts.
Method 3 — Cart-Level MOQ or Minimum Order Value (MOV)
If your goal is profitability rather than SKU control, a cart-level rule is often more effective. MOV or minimum item count focuses on the total order, not individual products.
This approach works well when:
- You sell many low-priced items with high fulfillment costs
- You want to reduce small, unprofitable orders while keeping product choice flexible
In AOV optimization workflows, minimum cart value rules usually pair with free shipping thresholds, bundles, and volume pricing. Instead of treating this as a hard checkout block, it should be part of a broader conversion and profitability strategy.
How to Verify That MOQ Actually Works (and Why It Often Fails)
Test at the Right Touchpoints: PDP → Cart → Checkout
Many merchants believe MOQ is set correctly, yet customers can still complete checkout. The reason is simple: the rule is visible at one step but not enforced at the next.
You should always test across all three stages:
- Product page (PDP): Enter a quantity below the MOQ and confirm the system blocks the action or shows a clear warning.
- Cart: Reduce the quantity below the MOQ. This is the most common failure point.
- Checkout: Make sure checkout cannot proceed unless the MOQ condition is met.
A working MOQ must hold across the entire purchase flow, not just on the product page.
Common Reasons MOQ Rules Do Not Enforce
Several issues cause MOQ rules to fail silently:
- The app is not enabled in the theme’s app embed settings.
- The theme uses a custom cart drawer or AJAX cart that the rule does not hook into.
- The rule is set at the product level, but you are testing a variant, or the opposite.
- Another app also modifies quantity or discounts, creating a conflict.
If you are optimizing a Shopify store with a data-driven mindset, these issues matter. Broken MOQ rules distort metrics such as cart abandonment and conversion rate, making it hard to diagnose whether problems come from UX or enforcement logic. Proper testing is mandatory before running ads or scaling traffic.
Best Practices for Setting MOQ Without Hurting Conversion
Base MOQ on Order Fulfillment Cost, Not Gut Feeling
MOQ should reflect real operating costs. This includes packaging, shipping, handling, and target margin. If MOQ is set too high, a direct-to-consumer offer starts to behave like wholesale. The result is a lower conversion rate and weaker product-market fit on a Shopify store.
A cost-driven MOQ protects profit without pushing away qualified buyers.
Always Explain the “Why” at the Quantity Selection Point
A short explanation near the quantity selector reduces friction. Customers accept limits more easily when the reason is clear.
Examples that work well:
- “Sold in sets to ensure safe packaging.”
- “Minimum quantity helps optimize shipping cost.”
This small UX detail often prevents confusion and drop-offs.
Combine MOQ With AOV Growth Tactics Instead of Hard Blocks
Blocking purchases alone breaks the experience. Guiding customers forward improves cooperation and revenue.
Instead of showing only an error, pair MOQ with:
- Relevant product bundles
- Tiered volume pricing
- A prompt such as “Add X more items to meet the order requirement”
In a broader average order value strategy, MOQ works best alongside bundles, volume discounts, and minimum–maximum quantity rules at the product level. When these elements are connected, MOQ becomes a growth lever rather than a conversion barrier.
Conclusion
To set minimum order quantity in Shopify the right way, first define what you actually need. Decide whether MOQ should apply per SKU, in fixed multiples, or at the cart level through minimum order value. Then choose the correct implementation path, using B2B catalogs for wholesale models or storefront apps and rules for DTC setups. Always test across all three touchpoints: product page, cart, and checkout.
When designed properly, MOQ does more than block small orders. It becomes part of a broader strategy to protect margins, streamline operations, and increase average order value within the Shopify ecosystem.
Ready to impress your B2B customers? Start Wholesaling like a pro!
FAQ About MOQ on Shopify
Does Shopify Have a Native Setting for MOQ?
For most DTC stores, Shopify does not offer a simple native setting to define MOQ per product. In practice, you either use B2B catalogs for wholesale models or apply rules through storefront apps that enforce quantity logic.
Should MOQ Be Set at the Product or Variant Level?
If price, packaging, or case size differs by size or color, set MOQ at the variant level to avoid logic conflicts. If all variants share the same case pack and cost structure, a product-level MOQ is easier to manage and maintain.
Does MOQ Slow Down the Store?
Any app can add load if misused. The safest approach is to install only what you need, enable only the required modules, and test site speed after setup. Because MOQ directly affects user interaction, stability matters more than feature count. Choose a reliable solution over a patched setup.
