MOQ (Minimum Order Quantity)
MOQ (Minimum Order Quantity) is the smallest quantity — expressed as a unit count or a minimum order value — that a supplier will accept in a single order. Suppliers set an MOQ because fixed costs (production setup, pick-and-pack labor, documentation, shipping arrangement) don't scale down with order size, so an order below the threshold can cost more to fulfill than it's worth. On a distributor's or manufacturer's product catalog, MOQ is typically a per-SKU attribute alongside unit of measure and case pack quantity, and it directly affects whether a buyer can actually purchase the quantity they searched for.
Why suppliers set an MOQ
MOQs exist because per-order costs don't scale linearly with order size. Setting up a production run, picking and packing a shipment, generating documentation, and arranging freight each carry a mostly fixed cost regardless of whether the order is for 10 units or 10,000. Below a certain volume, that fixed cost exceeds what the supplier makes on the sale.
MOQ can be set at different levels depending on the business: a manufacturer might set it at the production-batch level (the smallest run that's economical to tool up for), while a distributor might set it at the order-administration level (a minimum order value, like $250, below which a small-order surcharge applies instead of an outright rejection).
How MOQ is expressed and where it lives in product data
MOQ shows up in two common forms: a unit-count minimum ("minimum order: 500 units") or a value minimum ("minimum order: $250"). It's frequently tied to case pack quantity — a supplier might set an MOQ of one full case rather than a raw unit count, so the two attributes need to agree with each other in the catalog, not just each be individually correct.
MOQ belongs in structured product data, not just a separate price sheet or terms document, because it changes purchasing behavior at the point of decision: a buyer filtering a catalog by quantity needed should see the MOQ before adding to cart, not discover it at checkout or on a rejected order confirmation. Missing or stale MOQ data is a common source of order-processing friction in B2B catalogs, especially where SKUs were onboarded from a supplier feed that didn't carry the field at all.
MOQ vs. related order-quantity concepts
MOQ is often confused with a few adjacent terms that mean something distinct:
| Term | What it constrains |
|---|---|
| MOQ (Minimum Order Quantity) | The smallest quantity acceptable across an entire order |
| Case pack quantity | The fixed number of units in one sellable case or inner pack |
| Order increment (or "order multiple") | The step size an order must be a multiple of above the MOQ — e.g., MOQ 500, increment 100, so 500/600/700 are valid but 550 is not |
| Reorder point | An inventory threshold that triggers a new order, unrelated to how large that order must be |
A catalog that only captures MOQ and ignores order increment can still generate an invalid order — the quantity clears the minimum but doesn't land on a valid step.
Frequently asked questions
Is MOQ the same as case pack quantity?
No, though they're often related. Case pack quantity is the fixed count of units in one case or inner pack — a packaging fact. MOQ is the smallest total order a supplier will accept, which may be expressed as a number of cases, a raw unit count, or a minimum order value. A supplier can set an MOQ of several cases even though the case pack itself is a smaller, fixed number.
Can MOQ vary by customer?
Yes. Many B2B suppliers set a standard MOQ in their catalog data but negotiate different thresholds for specific accounts — a high-volume distributor might get a lower MOQ than a new or occasional buyer. When MOQ varies by customer tier, the catalog's published MOQ should be treated as the default, with account-specific overrides handled in the pricing or contract layer rather than the shared product record.
What happens if a buyer orders below the MOQ?
Handling varies by supplier: some systems reject the order outright and prompt the buyer to increase quantity, others allow it with a small-order surcharge, and some round the order up automatically to the MOQ. Whichever policy applies, it works best when the MOQ is visible in the product data before checkout, not surfaced only as an error after the buyer submits.
Why is MOQ often missing or wrong in supplier catalogs?
MOQ commonly lives in a separate pricing agreement, terms sheet, or ERP contract record rather than the core product attribute set, so it doesn't always make it into the PIM or the customer-facing catalog feed during onboarding. It's also prone to going stale, since suppliers adjust MOQs for cost or capacity reasons more often than they revise core specifications.