Every calculation carries a result code and a note. Start
there — the app almost always tells you what stopped it.
Result codes
| Code | Meaning | What to do |
|---|---|---|
| OK | Calculated and usable | Nothing |
| Cap Applied | Usable, but a configured cap limited the result | Check Maximum EOQ (Months of Demand), or the item’s Maximum Inventory for a capped reorder point |
| Insufficient Demand Data | Fewer days with demand than Min Demand Observations | Lengthen the history window, lower the minimum, or accept the item is too sporadic to model |
| Zero Demand | No demand at all in the window | New item, dead item — or a manufacturing component with Count Consumption as Demand off |
| No Lead Time Data | No lead time from any source | Set the item’s Lead Time Calculation, or a fallback in setup |
| Item Blocked | The item is blocked | Expected |
| Make-to-Order Skipped | Make-to-order item, and skipping is on | Expected — turn the setting off to include them |
| Not an Inventory Item | Type is Service or Non-Inventory | Expected |
| Excluded by Item Setting | Exclude from Inventory Planning is ticked | Expected — untick it to include the item |
| Zero Unit Cost | EOQ needs a unit cost | Populate the chosen cost source, or switch Unit Cost Source |
| Zero Ordering Cost | EOQ needs an ordering cost | Set Ordering Cost (S) in setup |
| Zero Result | The formula produced zero | Reported rather than written, so a real value is never replaced with nothing |
| Error | Unexpected failure | Read the note on the log entry, then contact support |
Warnings in the note
Trend warning
Recent demand — the last quarter of the window, minimum 30 days — deviates
from the full-window average by more than your threshold. History-based planning
lags a ramp-up and overstates a phase-out. Consider a shorter window for
fast-moving ranges, or set the values by hand and exclude the item.
Stockkeeping Unit notice
The item has Stockkeeping Units. Standard planning reads SKU values at a
location, not the item card — so a value calculated here may
appear to have no effect. This app calculates at item level by design.
Intermittent or lumpy demand warning
Safety stock rests on a normal approximation that does not really hold for
this demand shape. The number is still the best available estimate, but it
deserves review rather than trust.
Common situations
Every item reports Zero Demand
You manufacture, and Count Consumption as Demand is off. Components
are consumed, never sold, so there is no sales history to find. Turn it on in
setup.
Every item reports Insufficient Demand Data
Observations count days with demand, not transaction lines.
An item with 200 sales lines across 12 busy days has 12 observations, and the
default minimum is 20.
Lengthen the window or lower the minimum — but understand what you are
agreeing to: a statistic from five days of demand is a statistic from five days
of demand.
The calculated values are ignored by planning
Check for Stockkeeping Units on the item. Standard planning reads the SKU at
a location rather than the item card. The calculation note says so whenever SKUs
exist.
Also check the item’s Reordering Policy. A reorder point on
an item with no policy, or on Lot-for-Lot, does nothing.
The reorder point looks too low for a growing product
Read the note — there will be a trend warning. History-based planning lags
growth by design.
EOQ returns Zero Unit Cost
The Unit Cost Source you chose is empty on that item. Populate it, or
switch the source in setup to one your items actually carry.
Values changed and nobody knows why
Open the calculation log for the item.
Every run records the previous value, the new value, the user, and every input
that produced it.
A scheduled run overwrote values somebody had tuned
Tick Exclude from Inventory
Planning on those items. Restore the old values from the
Previous Value field in the log.
The results moved a lot after a setup change
Expected — the history window, service level, ordering cost and holding rate
all feed the formulas directly. Use the
Planning Worksheet to see the effect
of a change before applying it anywhere.
Still stuck?
Contact support — we reply
within 2 business days. Include the item number and a screenshot of the
calculation log entry; that usually contains the whole answer.
The app is open source, so you can also read the calculation code or raise an
issue at
github.com/GmsoftLtd/bc-inventory-planning.
