Formulas and methodology
What formula does safety stock use?
SS = Z × √( LT × σD² + D² × σLT² )
Where Z is the inverse normal at your service level,
LT the lead time in days, σD the standard deviation of
daily demand, D the average daily demand and σLT the
standard deviation of lead time.
It covers variability in both demand and lead time. A simpler
demand-only formula understates the buffer for items whose supplier is
unreliable.
Where do the Z-scores come from?
A continuous inverse-normal approximation (Acklam), not a lookup table. A
94.9% service level gets a 94.9% buffer rather than being rounded down to the
nearest tabulated bucket.
How is the reorder point calculated?
ROP = (average daily demand × lead time) + safety stock
Capped at the item’s Maximum Inventory when one is set. The safety stock used
is the freshly calculated one, not the value stored on the item.
How is EOQ calculated?
EOQ = √( 2 × D × S / H )
The Wilson formula, where D is annual demand, S the
ordering cost, and H the annual holding cost per unit — unit cost
multiplied by your holding rate. The result is capped at a configurable number
of months of demand and reconciled with the item’s Minimum Order Quantity,
Maximum Order Quantity and Order Multiple.
How are demand patterns classified?
By the Syntetos–Boylan scheme, using ADI (how often demand occurs)
and CV² (how variable the quantities are):
| Pattern | ADI | CV² | Recommended policy |
|---|---|---|---|
| Smooth | < 1.32 | < 0.49 | Fixed Reorder Qty. |
| Erratic | < 1.32 | ≥ 0.49 | Fixed Reorder Qty. |
| Intermittent | ≥ 1.32 | < 0.49 | Lot-for-Lot |
| Lumpy | ≥ 1.32 | ≥ 0.49 | Lot-for-Lot |
Two overrides come first: an item with an Expiration Calculation, or one that
already has a Maximum Inventory, is steered to Maximum Qty.
instead. Make-to-order items are recommended Order.
Both thresholds are configurable.
What counts as demand?
Sales, netted against same-day returns, measured across every calendar day in
the history window. Days with no demand count toward the average, which is what
makes the daily rate comparable with a lead time expressed in calendar days.
With Count Consumption as Demand enabled, production and assembly
consumption count too.
How is lead time determined?
- Purchase receipt history — mean and standard deviation of
order-to-receipt days from the trailing two years. The only source that also
yields variability. - The item’s Lead Time Calculation — also used for produced
and assembled items. - The fallback you set in setup.
The source used is recorded on every log entry. Safety stock and reorder
point share this resolution, so they cannot disagree.
Is this forecasting or AI?
No. It is descriptive statistics over posted history. That is deliberate:
every number can be traced back to transactions you can open and check. The app
tells you when history is a poor guide to the present — see the trend warning —
rather than predicting around it.
Behaviour
Will it overwrite values my planners maintain?
Only if you let it. Tick
Exclude from Inventory Planning on
those items and no calculator, bulk run or scheduled job will touch them. You
can also turn off any individual Write … to Item switch to calculate
and log without writing at all.
Does it change my reordering policies?
Only with two separate opt-ins. Auto-Update Item Reordering Policy is
off by default; recommendations are logged either way. And even when enabled, it
never sets a policy of Order automatically.
Separately, Set Policy to Fixed Reorder Qty. when None gives a policy
to items that have none, so a calculated reorder point does something. It is
suppressed for any item whose advice recommends a different policy.
What happens if I uninstall the app?
The values it calculated stay on your items, because they live in standard
Business Central fields. You lose the setup, the calculation log and the
per-item controls.
Does it work per location?
No. It calculates at item level. When an item has Stockkeeping Units, standard
planning reads the SKU values at a location rather than the item card — and the
app says so explicitly in the calculation note, rather than leaving you to
discover it.
Does it work in a demo or evaluation company?
Yes. History windows anchor to the work date, not the system
date, so a company whose demo data sits in the past still produces real results.
In production the two are the same.
Can I run different calculators on different schedules?
Yes. Create several Job Queue entries with different Parameter Strings — see
Running the calculators.
Data and privacy
Does my data leave my tenant?
No. The app reads item ledger entries, purchase receipt lines and item master
data, and writes to standard item planning fields plus its own setup and log
tables. All of it stays in your environment.
What telemetry does the app collect?
Diagnostic events on the standard Business Central telemetry channel, sent to
the publisher’s Application Insights resource:
| Event | Raised when | Data |
|---|---|---|
GSO0001 |
A scheduled run completes | Mode, item count |
GSO0002 |
An interactive bulk run completes | Calculation type, item count |
GSO0003 |
The dynamic provider computes values | Event count only |
These carry counts and codes only — never item numbers, quantities, costs,
customer names or any other business data. Telemetry also flows to your own
environment’s Application Insights resource if you have configured one. See the
privacy statement.
Licensing and support
What does it cost?
Nothing. It is free and MIT licensed, source at
github.com/GmsoftLtd/bc-inventory-planning.
Which Business Central versions are supported?
Business Central 2026 release wave 2 (v29) or later, cloud.
How do I get help?
Contact support — we reply
within 2 business days. You can also raise an issue on GitHub.
