Minimum order quantity, or MOQ, is the smallest amount a supplier will accept on a single order. Below it, the order is refused, repriced, or carries a small-order charge that closes the gap.

The number is supposed to come from arithmetic. Every order carries fixed handling regardless of size, so somewhere on the way down the volume curve the order stops paying for itself, and the MOQ is meant to sit at that crossover. Setup time, picking, packing, freight, invoicing, and credit administration are the usual components. Where the crossover actually falls is a cost to serve question, and most MOQs were never asked it. They came from a previous system, a competitor’s catalog, or a decision nobody remembers making.

That misfiling matters, because operations owns the rule and pricing owns the consequence. A minimum set too high pushes small buyers to competitors and invites exceptions that reps grant without a policy behind them. Set too low, it fills the book with orders that consume capacity and return nothing, and the loss is buried in overhead where no margin report will find it.

Exceptions are where the structure comes apart. Waiving a minimum for one account creates the precedent for the next, and because the waiver is an operations decision it never touches discount management or any approval level. The concession is real, the margin impact is real, and nothing in the pricing data records that it happened.

An MOQ is a price threshold wearing an operations label. Set with the cost math, it protects margin on every small order. Set by inheritance, it is a number defending nothing. Reach out to Acustrategy to find out what your minimums are actually costing you to honor.