​

Coverage

Coverage — days of supply (DOS) — is how the planning surfaces express inventory health: how many days the current position lasts at the projected consumption rate. This page explains where coverage appears, how the before/after impact sections in drawers work, and the vocabulary behind the numbers.

​

Coverage status

Coverage status is computed server-side from your position versus the policies you author, and rendered directly — the client never re-derives it: Grids show these as tinted chips; drawers show them as colored bars. A location with no authored policy is not judged at all: it renders Not set, with no pill. A row with no status (a plan solved before the current model) reads Awaiting re-solve until the next solve.

​

Coverage impact in drawers

Recommendation drawers carry a Coverage impact section showing what the movement does to days of supply:

• Purchase and Production recommendations show an Across network row on top, then per-node rows.
• Transfer recommendations are headed Coverage impact — source & destination, and highlight the source and destination nodes; there is no network row.

Each node row is a before/after bar: a muted segment for the current position and a delta segment for the change — green-tinted when the movement lifts coverage, red-tinted when it drops it. Up to three threshold ticks overlay the bar — S (Safety days), T (Target days), M (Max days) — rendered only where that layer is authored.

​

The measurement date

A caption under the heading names the date the before/after numbers are measured at — they are forward-looking projections at the moment the supply lands, not “today”:

• Purchases: Coverage on PO Land Date
• Production: Coverage on Run Completion Date
• Transfers: Coverage on Arrival Date

​

What the rows do and don’t show

• Nodes with no coverage signal and no authored threshold (suppliers, off-SKU warehouses the plan touches but never stocks) are suppressed — they’d tell you nothing.
• A zero-DOS node with an authored target is kept and rendered as a red bar: that’s a managed stocking location that is out of stock.
• When a recommendation bundles several SKUs, transfer and production drawers show one SKU’s walk at a time — the heading says “Showing this SKU only (N SKUs on the rec)” and you click another row to switch. Purchase impact already aggregates across the PO’s items.

​

Special outcomes

Two outcomes deliberately render without a number:

• Beyond the horizon — the position outlives the planning horizon at its (very slow) depletion rate. Rendered as a fully-covered bar, not “0d”.
• N/A — no demand signal — nothing consumes this SKU from this point forward in this scenario, so coverage is unmeasurable — not zero, and not the same as overstocked.

​

Coverage per lens

Coverage is lens-scoped. Each scenario lens is walked end to end — supply and demand: “Do nothing” and “Follow my plan” drop the supply their decision set excludes and re-derive the consumption that supply would have driven. They are true counterfactuals, not the full-plan demand shape with supply removed. Consequently the same cell can legitimately show different DOS values — and different chip tints — under different lenses, and a chip never falls back to another lens’s numbers. If a value can’t be measured under the active lens, it says so rather than borrowing one.

​

Coverage glossary

The same word — “coverage” — is rendered at more than one grain, and the grains are not interchangeable:

​

Best practices

​

Troubleshooting

​

Next Steps