A buyer at a mid-sized contract manufacturer pulls up the reorder report on Monday morning. The system flags fourteen items as needing replenishment this week. For each one, the buyer types a quantity into a purchase order draft, and that quantity comes from a mixture of memory, the last order, what the supplier said in an email three months ago, and a gut feel about how fast the line will burn through it. By Friday, two of those orders will be too small to qualify for the supplier's price break, one will exceed the available bin space at the receiving dock, and one will get rejected because the supplier ships only in cases of forty-eight while the order was placed for fifty. None of these outcomes show up as errors. They show up as friction, written off as the cost of doing business. They are not. They are the cost of guessing.
The economic order quantity calculation is the textbook answer to the question of how much to order, and it has been the textbook answer for nearly a century. It is a useful starting point, but it is not the answer. Treating it as the answer is what produces the kind of reorder list described above, where every line item carries a hidden tax of approximation.
Why the EOQ Formula Is Necessary but Insufficient
The EOQ formula balances ordering cost against carrying cost to find the order quantity that minimizes total inventory cost. The classic version is the square root of two times annual demand times order cost, divided by carrying cost per unit per year. It produces a single number, and that number is mathematically optimal under a specific set of assumptions: demand is constant, lead time is fixed, no quantity discounts apply, and you can order any quantity you want.
Almost none of those assumptions hold in a real manufacturing environment. Demand fluctuates with production schedules. Lead times shift based on supplier capacity. Quantity discounts change the unit cost as soon as you cross a threshold. And the most consequential gap of all is that you cannot order any quantity you want. Suppliers impose minimum order quantities. They ship in packs, cases, pallets, drums, or rolls. They charge full freight whether you fill the truck or not.
So the economic order quantity calculation produces a number that is correct in a world that does not exist. The job of a reorder quantity calculation is to take that number and reconcile it against the world that does. That reconciliation is where most operations teams fall back on guessing, because the system in front of them does not perform the reconciliation automatically. It hands them an EOQ and lets them figure out the rest.
Net Requirement Is the Real Anchor
Before EOQ matters, net requirement matters more. Net requirement is the quantity you actually need to cover demand within your planning horizon, after subtracting current available stock and any incoming purchase orders or production receipts already scheduled to arrive in time. If your net requirement is two hundred kilograms of a raw material over the next thirty days, ordering an EOQ of five hundred kilograms is not optimization. It is overstock dressed up in a formula.
The discipline that holds reorder quantities together is calculating net requirement first, then asking whether the EOQ-suggested quantity is reasonable in that context. If net requirement is four hundred and EOQ says five hundred, ordering five hundred makes sense because the extra hundred extends coverage and probably reduces the next order's urgency. If net requirement is fifty and EOQ says five hundred, the EOQ is wrong for this situation, because the formula is averaging across an annual demand profile that does not reflect what the next thirty days actually require.
This is why horizon-based planning produces better reorder quantities than static reorder points. Running net requirements across configurable horizons of seven, fourteen, thirty, and sixty days lets the system show what is needed within each window, against what is on hand and what is on order. Reorder quantity calculation starts from that net number, not from an annualized abstraction. FalOrb's MRP engine performs exactly this layered calculation, surfacing net requirement per item and using it as the foundation for purchase recommendations rather than substituting a generic EOQ. The relationship between horizon depth and decision quality is explored further in the discussion of MRP planning horizons.
MOQ and Supplier Pack Reconciliation
Once net requirement establishes the floor, the next step is reconciling against supplier constraints. Two constraints dominate. The first is minimum order quantity, the threshold below which a supplier will not accept an order or below which the unit price increases sharply. The second is pack size, the indivisible unit in which the supplier ships, whether that is a case of twenty-four, a pallet of forty bags, a drum of two hundred liters, or a roll of one thousand meters.
A defensible reorder quantity satisfies both. It must equal or exceed the MOQ, and it must be a whole multiple of the pack size. An MOQ-rounded order that ignores pack size results in a partial pack that the supplier either will not split or will charge an extra handling fee for. A pack-rounded order that ignores MOQ may technically ship but at a higher unit cost or with a small-order surcharge that wipes out the savings the EOQ was supposed to deliver.
The reconciliation logic, written out, looks like this. Take the larger of net requirement and the EOQ suggestion. Round that quantity up to the next multiple of the supplier's pack size. If the rounded quantity is below MOQ, increase it to MOQ and round up to the next pack multiple from there. The result is the smallest order quantity that satisfies need, EOQ guidance, MOQ, and pack constraints simultaneously. It is not an optimization in the textbook sense. It is a feasibility solution, which is what a buyer actually needs.
When this calculation runs inside the planning system rather than inside the buyer's head, the reorder quantity calculation stops being a guess. FalOrb's restock intelligence engine performs MOQ-rounded order quantity reconciliation on every purchase recommendation, so the suggested quantity is one the supplier will accept and the receiving dock can handle.
Where Order Quantity Optimization Actually Lives
Order quantity optimization is often described as a search for the lowest total cost. In a real operation, optimization happens across more dimensions than cost alone. Cash flow matters, because tying up working capital in inventory has a real opportunity cost that the carrying-cost component of EOQ underestimates. Storage matters, because every extra pack consumes square meters that have to come from somewhere. Shelf life matters, because perishable or batch-sensitive materials degrade if held too long. Supplier relationships matter, because predictable order patterns earn preferred treatment in tight supply windows.
The economic order quantity calculation cannot incorporate all of these, and it does not need to. What needs to incorporate them is the policy layer that sits above EOQ. That policy might say: never exceed sixty days of forward coverage on items with a shelf life under one hundred and twenty days. Never order more than two pallets at a time for items stored in the climate-controlled bay. Always honor preferred supplier pack sizes even if a secondary supplier offers a marginally lower unit price. These rules constrain the EOQ output, narrowing the range within which the reconciliation logic operates.
A planning system that respects these constraints produces reorder quantities that are sustainable, not just optimal in isolation. The reactive-to-predictive procurement shift that mature manufacturers make depends on encoding this policy into the system rather than relying on individual buyers to remember it.
Building a Defensible Reorder Recommendation
A reorder recommendation that holds up to scrutiny carries a short audit trail. It shows the net requirement that triggered it, the EOQ figure that informed the suggested quantity, the supplier MOQ and pack size that shaped the rounding, and the resulting order quantity with its forward coverage in days. When a buyer or controller asks why the system recommended ordering eight hundred when the immediate need was five hundred, the answer is visible: net requirement was five hundred, EOQ suggested seven hundred, the supplier pack is one hundred, MOQ is six hundred, the smallest pack-aligned quantity meeting all constraints is eight hundred.
That kind of recommendation does not need defending because the logic is on the page. Compare that to the buyer who typed eight hundred from memory because that is what was ordered last quarter. Both numbers may be the same. Only one of them survives an audit, a procurement review, or a supplier renegotiation with its reasoning intact.
The point of moving away from guessing is not to remove judgment from the buyer. It is to ensure that judgment is applied to the parts of the decision that genuinely require it, like supplier negotiation, exception handling, and capacity planning, rather than spent on the routine arithmetic of reconciling EOQ against MOQ on fourteen items every Monday morning. A planning system that does the arithmetic for you frees the buyer to do the work that only a buyer can do.
The Reorder Quantity as a Composite Output
The reorder quantity is not a number. It is the composite output of a sequence of calculations, each one constrained by the next. Net requirement defines the floor. EOQ suggests an efficient size. MOQ enforces a supplier minimum. Pack size enforces an indivisible shipping unit. Policy layers above all of these enforce organizational constraints on cash, space, and shelf life. The final number that lands on a purchase order draft is the smallest quantity that satisfies every constraint in the chain.
When operations teams stop treating any single one of those calculations as the answer, the conversation about reorder quantities changes. It stops being about whether the buyer made the right call and starts being about whether the policy the system encodes is the policy the business actually wants. That is a much more productive conversation, because it can be answered, adjusted, and audited. Guessing cannot. Visit falorb.com to see how horizon-based net requirements and MOQ-aware purchase recommendations come together in a single planning view.
FalOrb helps manufacturers move from guess-and-check reordering to a defensible reorder quantity calculation that respects net need, supplier MOQs, and pack sizes. Book a 30-minute walkthrough or email us at [email protected] to see how it applies to your operation.