Lot-for-lot ordering means ordering or making exactly the net requirement for each period, so nothing is carried forward. Fixed order quantity means ordering the same preset amount every time, carrying whatever is left over. Lot-for-lot drives holding cost to almost zero and setup frequency to the max; fixed order quantity does the reverse.

These are the two endpoints of the same decision: how much to order or make each time a material requirements planning run says you need something. Get it wrong toward one side and you drown in setups and small orders; wrong toward the other and you tie up cash and floor space in stock you will not use for weeks. This post compares lot-for-lot and fixed order quantity, adds period order quantity as the middle ground, and shows how to pick. It is educational and names no products.

What is lot-for-lot ordering?

Lot-for-lot (L4L) ordering, also called the discrete rule, sets each planned order equal to the exact net requirement for that period, no more and no less. Net requirement is gross requirement minus on-hand inventory and scheduled receipts, so lot-for-lot orders precisely what is still needed after existing stock is used up. Because it never orders ahead, lot-for-lot carries essentially no cycle inventory between periods: what arrives is what gets consumed. That makes holding cost about as low as a rule can make it, at the price of a separate order or setup every period there is demand.

Lot-for-lot is the natural fit when carrying cost dominates or when setups are cheap. It shines for expensive items you do not want sitting on a shelf, for made-to-order components, and for any pull-style flow where the whole point is to make only what the next step needs. It is one of the standard rules covered in lot sizing in MRP and its low-inventory logic is exactly the instinct behind lean manufacturing.

Inventory profile: lot-for-lot versus fixed order quantityHow each rule holds inventorylot-for-lotmany orders, near-zero carryfixed order quantityavg on handfew orders, high carry
Lot-for-lot barely holds inventory but reorders constantly. Fixed order quantity reorders rarely but carries a large average balance between orders. Same demand, opposite trade.

What is fixed order quantity, and how does it differ?

Fixed order quantity (FOQ) orders a preset, unchanging amount every time an order is triggered, regardless of the exact net requirement. If the fixed quantity is 500 and this period needs 180, you still order 500 and carry the 320 leftover into future periods, where it reduces or eliminates the next few net requirements. The result is fewer, larger orders and a meaningful average inventory that sits on the shelf between them. FOQ is the opposite trade from lot-for-lot: it minimizes setup frequency and pays for it with carrying cost.

FOQ is the right call when setup or ordering cost dominates, when a supplier enforces a minimum or a pack multiple, or when a process is only economical in a certain batch size. The fixed quantity itself is often set to the economic order quantity, the batch size that mathematically balances ordering cost against holding cost for steady demand, though a real plant just as often uses a pallet, a tank, or a supplier minimum as the number. Either way, the defining feature is the same: the quantity does not flex with the period's need. Setting good FOQ values is a core question in production scheduling and feeds directly into the master production schedule.

Where does period order quantity fit between them?

Period order quantity (POQ) is the middle ground: it orders the exact combined net requirement for a fixed number of future periods, then repeats. Say you set POQ to cover three periods. You add up the net requirements for periods one through three, order that sum once, then do the same for periods four through six. Like lot-for-lot, POQ orders only what is truly needed, so it carries no permanent excess; like fixed order quantity, it batches several periods together, so it cuts the number of setups. The number of periods it covers is often derived from the economic order quantity divided by average demand, tying the batch back to the same setup-versus-holding math.

RuleOrder quantityInventory carriedSetups / ordersBest when
Lot-for-lot (L4L)Exact net requirement, each periodNear zeroMost frequentHolding cost high, setups cheap
Period order quantity (POQ)Combined need for N periodsModerate, no permanent excessFewerLumpy demand, moderate setup cost
Fixed order quantity (FOQ)Same preset amount every timeHigh, leftover carriedLeast frequentSetup cost high, minimums or pack sizes
Three rules along one axis. Lot-for-lot and fixed order quantity are the endpoints of the setup-versus-carrying trade; period order quantity sits between them.

How do you choose between them?

The choice is a single trade-off wearing three costumes: setup and ordering cost on one side, holding cost on the other. Picture the two costs as curves against batch size. Holding cost climbs as batches grow, because bigger orders leave more on the shelf. Setup and ordering cost falls as batches grow, because you order less often. Their sum is a U, and the bottom of that U is the batch that balances the two, the economic order quantity. Lot-for-lot lives on the far left of the curve, fixed order quantity out to the right, and the rule you should run depends on which cost is steeper for that item.

The setup-versus-holding cost trade-offTwo costs, one balance pointcostbatch sizeholding costsetup / order costtotal costeconomic batchL4Llarge FOQ
Holding cost rises with batch size while ordering cost falls; the total-cost U bottoms out at the economic batch. Lot-for-lot sits far left, a large fixed quantity far right.

With the picture in mind, work the choice in this order:

  1. Estimate the two costs. Put a real number on the cost of one setup or order, and on the cost to hold one unit for one period.
  2. See which dominates. If holding cost clearly outweighs setup cost, lean toward lot-for-lot; if setup cost dominates, lean toward fixed order quantity.
  3. Check the demand pattern. Steady demand favors a fixed economic quantity; lumpy, discrete demand favors lot-for-lot or period order quantity, which do not over-order in thin periods.
  4. Respect hard constraints. Honor supplier minimums, pack multiples, shelf life, and process batch sizes, which can force a fixed quantity regardless of the math.
  5. Weigh the item's value. Expensive or perishable items push toward lot-for-lot to avoid tying up cash or risking spoilage; cheap, stable items tolerate larger batches.
  6. Reduce the setup, then re-decide. If setups are the only reason you batch, cutting setup time with quick changeover lets you move toward lot-for-lot and its lower inventory.

That last step is the lean punchline. Fixed order quantity often exists only because setups are expensive, and expensive setups are usually a problem to solve, not a law to obey. Attack changeover time with quick changeover and the economic batch size shrinks until lot-for-lot becomes affordable. The rule you should run is not fixed forever; it moves as your setup cost moves.

What do the standards and data say?

Context from bodies of knowledge and primary data:

The standards agree on the frame: there is no universally best rule, only the rule that best fits an item's setup cost, holding cost, and demand pattern.

Which rule should a lean plant lean toward?

All else equal, lot-for-lot is the direction lean pushes, because carried inventory hides problems and ties up cash, and the discrete rule holds almost none. But all else is rarely equal. A component with a genuine minimum buy, a process that is only economical in tank-sized batches, or a supplier a thousand miles away can make a fixed or period quantity the honest answer. The lean move is not to force lot-for-lot everywhere; it is to keep asking why a larger batch is necessary and to remove the reasons one at a time until small lots become cheap. This is the same logic behind kanban sizing where you deliberately shrink the loop as the process improves.

Where the lot-sizing choice lives or dies: the data underneath

Every one of these rules leans on two numbers that plants rarely keep current: the real cost of a setup and the real cost of holding a unit. Setup costs get stamped on a routing years ago and never revisited even after a changeover project halved them; holding cost gets treated as a corporate constant even as space, capital, and scrap risk change. Feed a lot-sizing rule stale costs and it confidently recommends the wrong batch, usually a bigger one than the plant now needs, and the excess inventory quietly returns. The failure is not the rule; it is the inputs. Harmony is an AI-native layer that connects machines, software, and paperwork into one operational layer, with no rip-and-replace, so the numbers behind a lot-sizing decision, actual changeover times, real on-hand and scheduled receipts, current usage, become one live record instead of scattered stale ones. AI search returns cited answers across those records, so a planner can ask what a part's true setup time has been since the last kaizen or how much of an item is really on hand and get a grounded answer, and Harmony's digital workflows keep the lot-sizing inputs tied to what the floor is actually doing. It is the same paper-to-digital move Harmony makes elsewhere in the plant (see the CLS case study): the batch size stops being a fossil in a routing and becomes a current, defensible decision.