How to set B2B minimum order quantities
Minimum order quantities protect margin, warehouse time and freight economics, but they only work when buyers see the rule before checkout. This guide shows how to model product MOQs, minimum order values and case-pack increments in a wholesale flow connected to ChannelDock’s B2B Portal.
SKU, cart and customer rules
before the buyer submits
clean orders to the warehouse
Why this matters: Shopify’s B2B guidance separates unit quantity rules from cart-value minimums, Salesforce models minimum, maximum and increment rules per product, and forum threads show merchants still struggle to make minimums visible and enforceable.
Before you start: separate the three minimums
Most B2B minimum-order projects fail because every rule is called “MOQ”. In practice, a wholesale seller usually needs three different controls: a product minimum, a cart minimum and a customer exception model.
The lowest quantity of a SKU, variant or pack a buyer may order. Use it for case packs, inner packs, production lots or fragile pick faces.
The minimum subtotal required before the order can be submitted. Use it to protect freight, handling and admin costs across mixed baskets.
A temporary or permanent override by account, tier, country, warehouse or launch phase. Connect it to customer-specific B2B pricing so minimums and prices stay aligned.
Step-by-step workflow to configure B2B minimums
Use this sequence when moving wholesale customers from email orders, PDF order forms or sales-rep messages into a self-service B2B portal.
Audit the orders that were too small to serve profitably
Export the last six to twelve months of wholesale orders and flag orders with low line count, low margin, special handling, repeated freight exceptions or manual sales follow-up. Do not start with a round number. Start with the orders that caused operational drag.
Translate warehouse reality into buyer-facing units
Decide whether each product is sold as pieces, inner packs, cases, pallets or display units. If the warehouse picks a case of 12, the B2B portal should not invite a buyer to order 11. Match the visible unit to the pick, pack and stock unit used by inventory control.
Define product minimum, maximum and increment rules
For each relevant SKU or product group, set the minimum quantity, optional maximum quantity and required increment. A product might require a minimum of 12, allow up to 240, and increase only in multiples of 6. Maximums are useful when stock is constrained or when you want to protect allocation across retailers.
Add an order-value minimum for the complete cart
A product MOQ protects the SKU, but it does not protect the cost of a mixed order. Set a cart-level threshold such as €300, €500 or €1,000 based on freight, picking time, packaging and admin cost. Show progress in the cart so the buyer knows what is missing before checkout.
Create customer-specific exceptions with expiry dates
Starter accounts, key accounts, export buyers and seasonal pre-order customers may need different thresholds. Keep exceptions explicit: who gets the lower minimum, why, who approved it and when it expires. Route risky exceptions through the same control logic used for B2B approval workflows.
Test the rule stack with real buyer scenarios
Test at least five carts: below SKU minimum, wrong increment, below order value, above maximum allocation and valid order. Include a sales-rep order through manual order entry so phone and portal orders follow the same rules.
Release approved orders into one operational queue
Once a B2B order passes minimums, price checks, stock checks and approval gates, it should move into the same order-management and pick & pack process as marketplace and webshop orders. The warehouse should not have to interpret the commercial rules again.
The minimum-order rule flow
A good B2B portal does not make the buyer memorize rules. It checks the rules continuously and explains the next valid action: add six units, choose a case pack, increase the cart value or request approval.
Minimums work best when they feel like buying guidance, not a surprise rejection at checkout.
Common MOQ pitfalls
- Using a retail storefront rule for wholesale buyers, then discovering it cannot handle company-specific thresholds.
- Letting a B2B portal accept orders below the ERP or warehouse minimum, creating rework after submission.
- Setting MOQs without checking case packs, pallet layers, export packaging and carrier pricing.
- Making every exception a private sales note instead of a visible account rule with approval history.
- Forgetting that minimums affect forecasting: too high blocks new accounts, too low creates unprofitable micro-orders.
Manual minimum checks vs. ChannelDock B2B Portal
Manual checks feel flexible, but they make buyers wait and force your team to police the same rule again and again.
Without ChannelDock
- Sales reps catch below-minimum orders after the customer already sent an email or PDF form.
- Warehouse teams discover broken case packs during picking, not when the cart was created.
- Customer exceptions live in spreadsheets, making margin and approval history hard to audit.
With ChannelDock
- Buyers see allowed quantities, order thresholds and account rules inside a branded B2B ordering flow.
- Submitted orders already respect product, price, stock and approval controls.
- Accepted orders flow into order management, picking, shipping and history without retyping.
B2B minimum order quantity FAQ
Related workflows to improve next
After minimum-order rules are clear, tighten the B2B workflows that depend on them.
Turn minimum-order rules into clean B2B orders
Use ChannelDock’s B2B Portal to show buyers the right quantities, thresholds, prices and approval path before orders reach the warehouse.