Minimum order quantity, or MOQ, is the smallest quantity a supplier agrees to sell in one order or production run. It may reflect manufacturing setup, packaging, freight, or handling economics and can affect inventory, cash flow, and the buyer's effective unit cost.
The boundary worth keeping clear
The definition matters because nearby terms can describe a different document, event or responsibility. Use Minimum order quantity (MOQ) only when the record matches the conditions above. A familiar label attached to the wrong stage creates cleaner-looking data and worse decisions. That discipline also makes reports comparable across teams, systems and reporting periods.
Review points before the transaction moves
- Confirm the party responsible for the pricing decision.
- Keep the source data and approval with the transaction.
- Record exceptions instead of silently changing the original instruction.
- Make the downstream owner able to reconstruct what happened without an email search.
Related terms and distinctions
- Quantity discount: A quantity discount reduces the price when a buyer purchases a defined volume.
| Checkpoint | What the record should show |
|---|---|
| Inputs | Identify cost, quantity, currency and customer conditions |
| Rule | Show the formula, threshold or agreed price source |
| Exception | Name the approver when the result falls outside policy |
| Output | Carry the approved amount and assumptions into the quotation |
The trade-off
More controls add work at the start. That cost is visible. The cost of weak records arrives later as rework, delayed approval, margin leakage, a payment investigation or a delivery dispute. Set the control depth according to the amount, risk and reversibility of the decision.
Related Quotable resources
Continue with RFQ software, product catalogue management and Quantity discount. These pages cover the commercial workflow and the records that connect Minimum order quantity (MOQ) to the next transaction step.
