Skip to content

Replenishment planning

Reorder rules fail on thousands of items, shifting lead times and supplier minimums. A model plans every order within those limits, at the lowest cost.

  • Free 30-minute call
  • No commitment
  • You own the code
Typical industries
Retail and e-commerce, Supply chain
Problem type
Supply chain
You receive
A documented model, run on your data

In short: A replenishment plan decides when to reorder each item and how much, across thousands of items. It takes into account changing lead times, the minimum quantities your suppliers require and fixed order days. And it keeps the total cost of ordering and holding stock as low as possible.

The problem

Every Tuesday at nine, you work through the reorder list from your ERP. One suggested order falls short of the supplier’s minimum. So you round it up, add a few more items from the same supplier by feel and send it. A month later, some of those items are still on the shelf.

Replenishment means reordering stock before it runs out. The theory fits on a sticky note: when stock drops to a set level, order enough to last until the next delivery. In practice you have thousands of stock-keeping units (SKUs), each line with its own demand pattern. Each supplier has its own lead times, the time from order to delivery, and its own minimums. The sticky note turns into an optimisation problem where every decision depends on many others.

Signs your replenishment has outgrown its rules

You round orders up by hand to clear supplier minimums, and the warehouse fills with stock you didn’t need yet. You check the stock of every SKU at the same interval, taken over from a default setting in your ERP. The order size the system suggests is one no supplier will accept. During promotions and seasonal peaks, shelves are empty before the next order arrives.

Why the textbook rule fails

With every order, you decide: order more, and you pay more for storage. Order less, and the item is more likely to run out. The best quantity differs by SKU, by supplier and by week, yet a fixed rule in your ERP sets it once for everyone. And the classic textbook formula knows no minimum order quantities and no pack sizes, so its answer often can’t be ordered at all. You patch it by hand, and the extra stock fills your warehouse.

What changes

Today, you take the system’s suggestion, round it up to the supplier’s minimum and add lines by feel. Our model proposes each supplier’s order already grouped to clear the minimum. The model orders items that rarely sell earlier than you need them, but only as far ahead as the minimum requires. Best-selling items stay close to what you need. Replenishment planning optimisation finds the cheapest order for each item, each supplier and each week.

What you get

We rebuild your replenishment on your own demand history, your suppliers’ lead-time records and their minimum order rules. For each SKU, we set how often you check stock and when you order. Every order the model proposes keeps your suppliers’ rules. Before anything goes live, we test the model on a holdout: past demand the model never saw. After the test, the model becomes your automated replenishment. It proposes the orders, and you check and release them.

  • A model written around your own replenishment planning rules.
  • Results measured in the numbers you already track.
  • It slots into how you already work, and you can check every answer it gives.

How it works

Forecasts, stock and decisions about your warehouse network go into one model instead of three spreadsheets. By network we mean all your warehouses, distribution centres and branches, and which site supplies which. The model plans forecasts, stock and network decisions together in a single run. So a fix in one warehouse no longer creates a new problem at another site.

Continuous or periodic review

The first choice is the review policy: how often you check stock and how you decide to order. Continuous review, written (s, Q), watches each SKU all the time. It orders a fixed quantity Q the moment stock hits the reorder point s. That’s the same trigger your safety stock and reorder point policy sets.

Periodic review, written (S, T), checks the whole catalogue on a fixed cycle T. Each time, it orders enough to bring stock back up to a target level S. It fits a supplier’s order calendar much more easily. It needs bigger buffers, though. Say you check stock only on Mondays. If an item suddenly sells fast on Tuesday, you don’t reorder until the next Monday, and the safety stock has to last until then.

Best sellers that must almost never run out belong in continuous review. Items that sell only now and then are often cheaper to check on a fixed cycle. So we set the policy SKU by SKU, instead of inheriting it from an ERP default.

EOQ and supplier constraints

Order quantity looks settled by the classic formula, the economic order quantity (EOQ). Order rarely and in bulk, and holding costs rise. Order often and in small amounts, and ordering costs rise. EOQ finds the quantity in between, but it assumes demand never changes. In practice, the supplier sets a minimum order quantity (MOQ). And it delivers only full cases or full pallets. These rules often make the “optimal” EOQ impossible to order.

EOQ optimisation software that ignores supplier rules gives you a number nobody can place an order for. The task is harder than the textbook one: keep total cost low and keep every supplier rule. A model that knows the rules gives you an order the supplier will accept.

What rounding up to the MOQ really costs

It’s tempting to treat any order above the EOQ as waste. The formula says otherwise. Its ordering-plus-holding cost is flat near the bottom. At any quantity Q, that cost is half of (Q divided by EOQ, plus EOQ divided by Q) times its minimum.

Say your EOQ is 400 units and the supplier’s MOQ is 600. Ordering 600 raises ordering and holding cost by about 8 percent. At an MOQ of 800, it’s a quarter more. At 1,600, it more than doubles. So when the minimum is close to your EOQ, it rarely pays to negotiate it down with the supplier. When it’s four times higher, it does. Either way, the larger order has to fit in your warehouse and sell before it expires.

MOQ consolidation

Replenishment planning pays off most when it groups orders to reach the MOQ. This is called MOQ consolidation. Each supplier sets a minimum order quantity, and often a minimum order value, and one SKU rarely reaches either on its own. Consolidation groups SKUs from the same supplier so the combined order clears the minimum. The model orders an item that rarely sells earlier than needed, but only as far ahead as the minimum requires. Best sellers stay close to what you need.

The same applies when two suppliers can both deliver an item. Then the model decides how much you order from each. That’s dynamic replenishment optimisation: each order keeps its supplier’s rules and costs as little as possible in total.

From single orders to a system

Add warehouse space, shelf life for fresh goods and stock for the season, and your orders depend on each other. A plan that ignores warehouse space overfills the warehouse the day the goods arrive. Before a seasonal peak, you build up stock. When you size it, allow for a forecast that is too high. Otherwise, if the forecast is too high, the extra stock fills your warehouse.

The demand forecast sets how much buffer the plan needs in the first place. The stock the plan builds has to be held where your inventory optimisation wants it. In retail and e-commerce, a promotion leaves you only a few days to reorder. Miss a reorder, and the shelf is empty before the week is out.

Common questions.

Something else? Ask us directly.

Often yes, because the cost curve around the economic order quantity (EOQ) is flat. Order one and a half times the EOQ, and ordering plus holding cost rises by about 8 percent. At twice the EOQ, it’s a quarter more. Push back when the minimum is several times your EOQ, or when shelf life and space can’t take it.

Use both, item by item. With continuous review, you order on the day stock falls to a set level, the reorder point. That suits best-selling items with high service targets. With periodic review, you check stock on a fixed cycle, say every Monday. That fits a supplier’s order calendar, so you can group several items into one order. It needs more safety stock, though. If an item suddenly sells fast on Tuesday, you don’t reorder until the next Monday. The safety stock has to last that much longer. For cheap items that sell rarely, a fixed cycle is usually enough.

For most items, yes, after a while. We’d start with you releasing every proposed order, so you learn where the model is right. Then routine orders go out on their own, and the model flags the exceptions: a jump in demand, a missed delivery, an order far above normal. You spend your time on those, and on suppliers.

Sometimes it can, and if that’s the case, we’ll tell you. Standard software is built for an average operation, though. Yours runs on its own rules: your contracts, your exceptions, the things you know by heart. A custom model writes those rules in, and that’s where the better plan comes from.

You don’t need either to start. We build the model from the data you’ve already got, even if it lives in three spreadsheets and one person’s head. You get a system you run yourself. We train your team until they no longer need us.

You see a first result with the prototype, before you commit to anything bigger. We start with a free 30-minute call about your operation and the model that would fit it. Then we build a working prototype and run it on your numbers.

Tell us what you’re planning.

In a free 30-minute call with a specialist, you find out whether optimisation can help.

  • Free, no commitment
  • You talk to a specialist directly
  • A clear go or no-go