The MRP report said the line needed four hundred and twenty kilograms of pectin to cover the next thirty days of production. The buyer placed the order. The supplier confirmed the dispatch and shipped a thousand kilograms, because the minimum order quantity on that grade of pectin was a full pallet, and a pallet held one thousand kilos. The buyer protested. The supplier shrugged. The five hundred and eighty kilograms of overage went into the corner of the warehouse, where it sat for three months until the next planning cycle finally consumed it. By that point, the company had paid to store it, paid to insure it, and tied up working capital that could have funded other purchases. Worse, when the next planning cycle came around, the MRP report ignored the overage entirely and recommended ordering another four hundred and twenty kilograms, because the planner had never gone back to flag it as future supply.
This is the quiet cost of minimum order quantity mismatches. It is not the headline disaster of a stockout. It is the slow drag of working capital sitting in pallets that nobody planned for, holding costs accruing every month, and planning recommendations that fail to account for what is actually on the shelf because the original order quantity did not match the original net requirement. MOQ purchase order optimization is the discipline of reconciling these two numbers in a way that does not leave overage stranded.
The fix lives inside the MRP engine. A planning system that takes net requirements seriously has to round them honestly to supplier pack sizes, and it has to do that rounding visibly, with the holding cost implications surfaced before the order goes out the door.
The Hidden Cost of MOQ Mismatches
Every supplier has constraints. Pectin comes in pallet quantities. Cocoa butter ships in twenty-five kilogram drums or full pallets. Aluminium cans ship in cases of two hundred and forty. Labels print in runs of ten thousand. The constraints are not arbitrary. They reflect manufacturing economics, transport efficiency, and the supplier's own working capital model. When you place an order, you are not picking a quantity from a continuous range. You are picking from a discrete menu of pack sizes, and the menu rarely lines up with what your MRP says you need.
The cost of the mismatch shows up in three places. The first is direct holding cost: the warehouse space, the insurance, the cost of capital tied up in inventory that will not be consumed for weeks or months. For an item with a six-week consumption cycle, ordering twice the net requirement effectively doubles the holding cost on that line for the period in question. Across hundreds of stock-keeping units, the aggregate effect on working capital is significant.
The second cost is planning distortion. When MRP recommends four hundred and twenty kilograms but the order is for one thousand, the next planning cycle has to know that five hundred and eighty kilograms of future supply already exists. If it does not know, it will recommend ordering again to cover the same demand. If it does know, the planner has to manually reconcile the overage against future requirements, which is exactly the kind of manual work that MRP was supposed to eliminate. Either way, the system loses some of its credibility.
The third cost is harder to quantify but real: shelf life and obsolescence risk. Many manufacturing inputs have finite shelf lives. Ingredients spoil. Packaging gets superseded. Labels get redesigned when marketing updates the brand. Inventory that sits beyond its consumption window becomes write-off, and the write-off traces directly back to the MOQ-versus-net-requirement gap that the original order ignored.
Honest Quantity Rounding in MRP
The discipline that prevents these costs is honest quantity rounding inside the MRP engine. When the engine calculates net requirements across a planning horizon and identifies a shortfall, the next step is not to print the raw shortfall number on the recommendation. The next step is to round that number up to the supplier's minimum order quantity, then round again to the supplier's incremental pack size if there is one, and present the final quantity to the planner with the rounding logic visible.
FalOrb generates purchase recommendations with quantities rounded to the supplier's MOQ as a built-in property of the MRP engine. The recommendation surfaces the net requirement that drove it, the MOQ that was applied, and the resulting suggested order quantity. The planner sees both numbers. They can see immediately when the MOQ is forcing a significant overage and can decide whether to proceed, split the order across multiple suppliers, or push the production schedule out to a date where the demand catches up with the pack size.
This visibility matters because not every MOQ mismatch is worth solving. If the net requirement is four hundred and twenty kilograms and the MOQ is five hundred, the eighty kilogram overage will be consumed within a week or two of the next cycle, and the holding cost is trivial. If the net requirement is four hundred and twenty kilograms and the MOQ is four thousand, the overage represents months of supply, and the planner should pause before proceeding. The same engine logic produces both recommendations. The planner uses judgement to decide whether the rounding is acceptable or whether it warrants a different approach.
The alternative, where MRP either ignores MOQ entirely (producing recommendations that suppliers will round up anyway) or rounds silently (hiding the implications from the planner), undermines the whole point of running MRP in the first place. The recommendations have to be operationally usable, and operationally usable means honest about the constraints.
Horizon-Based Net Requirement Calculation
The other half of MOQ purchase order optimization is calculating the net requirement against the right horizon. This is where many MRP setups go wrong, and the wrongness gets amplified by MOQ rounding.
If the net requirement is calculated against a seven-day horizon, you will be ordering small quantities frequently, and every order will hit the MOQ floor. Across a year, you end up paying the MOQ overage cost dozens of times for the same item. If the net requirement is calculated against a sixty-day horizon, the demand quantity is large enough that the MOQ is often a small percentage of it, and the rounding waste shrinks dramatically. The same supplier, the same MOQ, the same item, very different working capital outcome depending on which horizon drives the recommendation.
This is one of the practical reasons FalOrb structures its MRP engine around four configurable horizons of seven, fourteen, thirty, and sixty days. The seven-day horizon is for tactical visibility. The thirty and sixty-day horizons are for placing orders, because they aggregate enough demand that MOQ rounding is rarely the dominant cost. Our piece on MRP planning horizons explores the broader logic of why these horizons exist, but the relevant insight for procurement is that horizon choice and MOQ economics are tightly coupled. You cannot optimise one without thinking about the other.
A planner who is operating well will look at the recommendation, see the suggested order quantity, see the horizon it was calculated against, and decide whether to lengthen the horizon to absorb the MOQ more efficiently. Sometimes the right answer is to order slightly more than the immediate need because doing so brings the order in line with a clean pack size and saves a future order entirely. Sometimes the right answer is to wait a week, let demand accumulate, and place a single larger order that fits MOQ without overage. The system surfaces the trade-off. The planner makes the call.
Holding Cost Awareness as a Design Property
A planning system that does MOQ rounding without holding cost awareness is incomplete. The rounded quantity might be operationally clean, but it can still represent serious working capital tied up in inventory. Holding cost awareness means that the system can express the overage in terms a planner can act on: how many days of cover does this order represent, how much working capital is being committed, what is the equivalent storage cost, what is the risk of obsolescence on a perishable item.
FalOrb's purchase recommendation surface the projected days of cover that an order will provide, calculated against current consumption rates. When that number drifts beyond a reasonable horizon (sixty days, ninety days, six months), the planner has a clear signal that the MOQ is forcing a longer commitment than the demand justifies. They can split the order, qualify a secondary supplier with a smaller MOQ, or escalate to procurement leadership for a conversation about whether the supplier relationship needs to be renegotiated.
The connection between MOQ economics and supplier negotiation is where the procurement function adds its real value. Suppliers set MOQs based on their own production economics, but those MOQs are not set in stone. A volume commitment for the year, a longer payment term, or a different transport arrangement can often unlock smaller pack sizes. The planner cannot have that conversation with the supplier unless the data on what the current MOQ is actually costing the business is clear and current. A planning system that buries the MOQ overage cost makes that conversation impossible. A system that surfaces it makes the conversation routine.
Reconciling Net Need Without Bloating Inventory
The deeper principle behind all of this is that purchase planning is a reconciliation problem. There is a net need (calculated by MRP), there is a supplier constraint (encoded as MOQ and pack size), and there is a working capital constraint (encoded as holding cost and target days of cover). A good system reconciles all three explicitly, in a way the planner can see and adjust. A bad system reconciles two of them and lets the third absorb the slack, which is how warehouses end up holding pallets nobody planned for.
The behavioural shift is small but important. Planners stop thinking of MOQ as a fixed friction they have to live with, and start thinking of it as a variable they can negotiate. They stop thinking of net requirements as absolute numbers, and start thinking of them as functions of horizon choice. They stop thinking of holding cost as something the finance team complains about, and start thinking of it as a real input into every order they place. The recommendations the system produces are better not because the math is more sophisticated, but because the constraints are visible and the trade-offs are explicit.
The relationship between these planning decisions and the underlying data integrity that makes them possible is explored in our piece on why spreadsheet inventory fails at scale. The short version is that you cannot do honest MOQ rounding if you do not have a reliable picture of current stock, in-transit inventory, and scheduled receipts. Spreadsheets fail at this because they cannot keep all three in sync. Purpose-built planning systems do not fail at it because they were designed for exactly this reconciliation.
The pectin pallet in the corner of the warehouse is not really a procurement problem. It is a planning problem that procurement was forced to solve at the moment of order placement, with no good options. Move the reconciliation upstream into the planning logic, surface the trade-offs honestly, and the pallet stops appearing.
FalOrb helps manufacturers reconcile MRP net requirements with supplier MOQs through transparent quantity rounding and horizon-aware purchase recommendations. Book a 30-minute walkthrough or email us at [email protected] to see how it applies to your operation.