Minimum Order Quantity (MOQ): What It Is and How to Optimize Around It

A minimum order quantity (MOQ) is the smallest quantity a supplier will accept on a single purchase order. MOQs come in two flavors: per-item MOQ (you must order at least N units of item) and order-total MOQ (the order itself must be worth at least $X to qualify for delivery).

Why suppliers set MOQs

MOQs exist for three reasons, in order of frequency:

1. Cost-to-serve. Picking, packing, and delivering a 4-unit order to a small business costs the supplier roughly the same as a 40-unit order. MOQs ensure each order covers its handling cost.
2. Production economics. For made-to-order or batched goods, the run cost is fixed. The supplier passes the minimum batch size through as an MOQ.
3. Channel management. Distributors set MOQs to discourage retail customers from buying wholesale. This is policy, not economics.

Why MOQs distort replenishment math

Statistical replenishment computes the optimal order quantity from consumption, lead time, and order frequency. MOQ ignores all of that and forces a floor. When MOQ > computed optimal, you over-order — carrying excess inventory and paying carrying costs you didn't budget for.

This becomes acute for slow-moving items. If your computed PAR is 12 units but the supplier's MOQ is 48, you're carrying four cycles of stock minimum, every cycle. Working capital trapped, decay risk amplified, shelf space consumed.

How LineNow handles MOQ

For every line item, LineNow stores the moq (per-item minimum) and per-line minimumOrderAmount (order-total minimum). The replenishment engine:

1. Computes the statistically optimal order quantity.
2. Rounds up to the next pack size (separate constraint).
3. If still below MOQ, raises to MOQ and flags the item as MOQ-bound with a visible warning.
4. For order-total MOQ, attempts to consolidate other items from the same supplier into the same order to clear the threshold without artificially padding.

The MOQ-bound flag is one of the most useful signals in the system. It tells the operator which line items would be cheaper to source elsewhere or which suppliers are forcing structural over-ordering. Several customers have used the report to negotiate MOQ reductions or to consolidate to a lower-MOQ supplier.

How to push back on MOQ

Most MOQs are softer than they appear. Tactics that work:

• Multi-item orders: combine several SKUs from the same supplier to clear the order-total minimum without violating any single per-item minimum.
• Standing orders: agree to a recurring weekly or biweekly delivery. The supplier's cost-to-serve drops with predictability, and they often waive the per-order MOQ.
• Direct-to-route negotiation: ask the supplier's sales rep what the minimum is on a route they're already running through your zone. Often lower than the published MOQ.
• Pre-pay: offer to pay upfront for several deliveries. The supplier's working-capital math improves, the MOQ comes off.

The data to negotiate from is the per-item, per-supplier history that LineNow exposes by default. Walking into the conversation with twelve months of order data is materially different from walking in with a hunch.