When Your Replenishment Plan Says 700 Units but Your Supplier Says 1,500

A business can make a perfectly reasonable demand forecast, calculate a sensible replenishment requirement, and still end up buying too much inventory.

The reason may have nothing to do with forecasting.

Consider a simple example.

A SKU is selling approximately 300 units per month.

After considering expected demand, current inventory, available supply, lead time and the required inventory buffer, the business calculates that it needs to purchase:

700 units.

Then the supplier's commercial terms enter the calculation.

Minimum Order Quantity: 1,500 units.

The business doesn't need 1,500 units based on its current replenishment requirement.

But it cannot order 700.

So what exactly is the business deciding?

The 800 Units Deserve Attention

The difference is straightforward:

Calculated replenishment requirement: 700 units

Supplier MOQ: 1,500 units

Additional inventory created by the MOQ: 800 units

At approximately 300 units of monthly demand, those additional 800 units represent about 2.7 months of demand.

They also represent cash.

If the landed inventory cost were $20 per unit, for example, the difference between purchasing 700 and 1,500 units would be:

800 × $20 = $16,000

That is $16,000 of additional inventory investment created not by the immediate replenishment requirement, but by the supplier's minimum order constraint.

The MOQ may still be the right decision.

But the additional commitment should be visible.

MOQ Is More Than a Purchasing Term

MOQ is often treated as supplier master data.

Supplier: X
Lead time: X days
MOQ: X units
Unit cost: $X

Operationally, however, MOQ can affect much more than purchasing.

It can influence:

Inventory coverage

Working capital

Storage requirements

Inventory turns

Excess inventory exposure

Future purchasing flexibility

And ultimately, the economics of carrying the SKU.

That makes MOQ relevant to demand planning and inventory management, not just procurement.

The Lowest Unit Cost May Not Produce the Lowest Inventory Cost

This becomes even more important when suppliers offer price breaks.

Suppose the business has two choices:

Order closer to actual demand at a higher unit cost.

Or:

Order substantially more inventory to achieve a lower unit cost.

Looking only at purchase price can make the larger order appear more attractive.

But the business isn't purchasing a unit cost.

It is committing cash to inventory.

The larger order may require more working capital, occupy storage for longer, reduce inventory turns and expose more units to future demand uncertainty.

If the SKU sells as expected, those risks may be manageable.

If demand slows, the economics change quickly.

The savings achieved on the purchase price can eventually be competing against storage cost, markdowns, liquidation losses, or capital that could have been deployed into faster-moving inventory.

That doesn't make volume pricing wrong.

It means unit cost should not be evaluated independently from inventory exposure.

Sometimes the Forecast Isn't the Problem

This distinction becomes especially important when reviewing excess inventory.

Imagine six months later the SKU is carrying substantially more inventory than management would like.

It is tempting to conclude:

We overforecasted.

Maybe.

But what if the forecast was reasonably close?

What if the replenishment calculation originally required 700 units, but the supplier required the business to purchase 1,500?

The eventual excess position may have been influenced by a purchasing constraint, not simply a demand-planning error.

That distinction matters because the corrective action is different.

Improving the forecast will not necessarily solve an MOQ mismatch.

The business may instead need to examine its sourcing structure.

What Should Management Evaluate?

When MOQ materially exceeds the underlying replenishment requirement, I would want the decision to become more explicit.

Not simply:

Can we meet the MOQ?

But:

How much inventory does the MOQ force us to purchase beyond the calculated requirement?

How much additional working capital does that represent?

How much additional inventory coverage will it create?

How stable is the SKU's demand?

Is demand growing quickly enough to absorb the additional inventory?

Are more units already inbound or committed elsewhere in the supply pipeline?

Does the product have shelf-life, obsolescence or seasonality risk?

What does the additional inventory cost to hold?

What other inventory or business priorities could use that cash?

Only then can management properly evaluate the purchasing decision.

The Answer Isn't Always "Negotiate the MOQ"

Sometimes accepting the MOQ will still make sense.

The SKU may be growing quickly.

Demand may be highly predictable.

The inventory may have a long useful life.

The unit-cost economics may strongly favor the larger production run.

Or the supplier relationship may be strategically important.

Other situations may justify exploring alternatives.

Could production be split into releases?

Could the MOQ be negotiated?

Could purchasing be consolidated differently?

Could the supplier hold part of a production run under an appropriate commercial arrangement?

Could another sourcing structure better match the SKU's demand profile?

And eventually there is a harder strategic question:

Does this SKU generate enough demand to support the economics of its current supply arrangement?

If a product repeatedly requires the business to purchase far beyond its replenishment requirement simply to satisfy MOQ, that deserves management attention.

A Useful Distinction: Demand-Required Inventory vs. MOQ-Required Inventory

I think there is value in separating these two quantities analytically.

Demand-required inventory represents what the replenishment plan says the business needs.

MOQ-required inventory represents the additional commitment created when the supplier's minimum exceeds that requirement.

That distinction can help management understand why inventory is accumulating.

Instead of simply seeing:

Recommended PO: 1,500 units

the decision becomes:

Underlying replenishment requirement: 700 units

MOQ-constrained purchase: 1,500 units

Additional MOQ-driven commitment: 800 units

That tells a much richer story.

It also creates the possibility of translating the difference into additional inventory coverage and working-capital exposure.

This Is an Area We're Exploring Further at McKeeleen

At McKeeleen Advisory, we look at inventory, demand, replenishment, purchasing and working capital as connected decisions.

One area we're exploring more deeply in our planning methodology is how supplier constraints such as MOQ can be made more visible when they materially change the inventory outcome.

Not simply:

Did the purchase order meet MOQ?

But:

What did meeting that MOQ do to inventory and working capital?

Because a purchasing recommendation shouldn't lose its connection to the demand that created the requirement in the first place.

A supplier may require 1,500 units.

The business may decide that ordering 1,500 is absolutely the right decision.

But if the underlying requirement was only 700 units, management should be able to see the difference.

The MOQ tells you what the supplier requires.

It doesn't tell you what the business economically needs.

Is Your Purchasing Strategy Creating Inventory You Didn't Plan For?

If supplier constraints, purchasing requirements or replenishment decisions are creating inventory and working-capital challenges in your business, McKeeleen Advisory can help you examine how those decisions connect across demand, inventory and supply.

Better inventory decisions start with understanding not only what you are buying, but why you are buying it.

Discuss Your Inventory Challenges