Base parameters
Unit cost, lead time, average daily demand, and demand variability for each fictional SKU, hand-written in datagen/main.go.
Methodology
Every number here traces back to a formula.
Product names, prices, and collection stories on this site are fiction. The operational numbers built on top of them — reorder points, demand segments, forecast trends, landed costs — are not. They're computed by scmgo, a real Go supply-chain formulas library, through the pipeline below.
scmgo, in Go
A small Go program calls the real scmgo library — reorder points, ABC/XYZ segmentation, forecast trends, landed cost — against those parameters.
One JSON artifact
Results are written to lib/generated/scmgo.json — a static file, checked into the repo, read at build time. No server, no database.
This site
TypeScript merges that JSON with the authored creative fields (names, images, prices). No number here is guessed.
Function reference
What computes what
inventory.BuildPolicySummaryWithServiceLevelReorder point, safety stock, target level — used in Catalog restock dates, Insights, Dashboard alertView source ↗abc.Classify + ClassifyVariability + CombineABC (value) x XYZ (variability) segmentation — used in Catalog segment badges (e.g. "AY")View source ↗forecast.LinearTrend12-week demand trend forecast — used in Catalog trend %, Insights "demand" cardView source ↗forecast.AccuracyBacktested forecast confidence (MAPE-derived) — used in Insights confidence scoresView source ↗procurement.LandedCostUnit cost + freight + duty — used in Suppliers purchase order valuesView source ↗production.WIPFromLittlesLawWork-in-process from throughput x cycle time — used in Production "units in motion"View source ↗Try it yourself
This isn't a JavaScript reimplementation.
The sliders below call the real scmgo Go library, compiled to WebAssembly and running directly in your browser. Same code, same formula, same source file as the table above — just live instead of pre-computed.
Loading the compiled scmgo binary…