Almost every wholesale operator we talk to has Minimum Order Quantities. Almost none of them enforce them. The MOQ lives on the spec sheet, the sales rep mentions it during the kickoff call, and then it’s gradually relaxed for “just this one” orders that compound into a quarter of below-margin revenue. We sampled 47 mid-market wholesalers; the median enforcement rate was 38%.
The reason is mechanical: enforcing MOQs requires telling buyers no, in real time, at the moment they’re placing an order. Sales reps don’t want to. Email-based ordering can’t. Shopify’s defaults won’t. So MOQs become an aspiration.
The math nobody runs
Pick a SKU with a $5/unit price, a $4.20 cost, and an MOQ of 100 units. The unit margin is $0.80, or 16%. That margin assumes a setup cost (per-run printing, palletizing, picking) amortized across 100 units.
When you accept a 50-unit order at the same price, you don’t lose half the margin, you lose more than half, because the setup cost is fixed. If setup runs you $30/order, you’re distributing it across 50 units instead of 100. Per-unit setup goes from $0.30 to $0.60. Your $0.80 margin becomes $0.50. You’ve given up 37% of margin to take an order at MOQ-violating volume.
Now multiply across 200 below-MOQ orders a quarter at an average $400 ticket. That’s $80,000 in revenue with $30,000 in real margin instead of $48,000. $18,000 left on the table per quarter. $72,000 per year. For one SKU.
Why “suggested MOQ” doesn’t work
The standard advice is to make the MOQ a soft suggestion: “recommended minimum 100 units.” This protects the relationship without enforcing the policy. The result is exactly what you’d predict: most buyers ignore it; the rest order suspiciously close to the floor.
Soft MOQs work in two scenarios: (a) you’re a marketplace where pricing dynamics enforce volume by themselves, or (b) you have so much capacity slack that producing 50-unit runs costs you nothing extra. Almost no operator we work with is in either bucket.
What enforcement actually looks like
MOQ enforcement is a software feature, not a willpower feature. Three rules:
- Per-SKU MOQ floors set in the catalog, not the rep’s memory.
- Per-buyer-tier overrides for legitimate exceptions (a long-standing strategic buyer; a new-product sample run).
- Below-MOQ pricing surcharges that mathematically compensate for the lost amortization. If the floor is 100 and a buyer wants 50, the unit price goes up enough to preserve the original margin.
Notice rule three: this isn’t about saying no. It’s about making the no expensive enough that the buyer either upsizes or pays the real cost. Mercantyl handles this natively; most platforms make you build it.
The objection: “but my buyers will leave”
They won’t. We’ve watched dozens of operators turn enforcement on. The pattern is always the same: a small fraction of buyers complain in the first month, half of those upsize their orders to clear the floor, and the rest stick around at the surcharged price. Net revenue goes up; margin goes way up.
Buyers who genuinely can’t support your floor were never going to be profitable anyway. Letting them go is fine. The risk isn’t that you lose buyers, it’s that you don’t enforce, and gradually convince yourself that wholesale is just a low-margin business.
What this looks like on Mercantyl
MOQ enforcement is built into the catalog. Set a floor per SKU. Optionally set a tiered surcharge for below-floor orders. Optionally allow per-account overrides for strategic buyers. Buyers see the floor at the moment of order, not after they’ve negotiated a price.
No app required. No agency to wire it up. No willpower needed.