What it is
The availability floor is the share of the commitment's range that must be in stock, declared as a percentage with a basis. It is one of the five numbers a commitment declares. Below the floor the promise is at risk; above it there is nothing to say. It is a floor, so it carries no band: any point under it is already a deviation.
The share is counted in variant-days. For each variant and each day, stock is summed across the variant's locations, and the day counts as in stock when that sum is above zero. It measures stock on hand across the network, not what is on a shelf in one store, and not whether every size is there.
How Tightly decides it
You declare it on Declare, under Budget & targets, as the Availability target. The page describes it as "Target share of variant-days in stock". A suggested figure is the commitment's own in-stock share over the trailing 180 days, rounded down past one point of headroom, so a measured 99.5 becomes 98. Where no stock history was ever kept, the suggestion rests on today's position, which is a weaker basis and is not described as a trend.
Once the commitment is signed and its window is open, each week Tightly scores the floor over the retail week that closed:
- Fewer than 20 known variant-days in the week reads not measured, because the slice is too thin to speak for the range.
- Where there is no stock history, only today's position is available, and a position cannot stand in for a week, so it also reads not measured.
- One week under the floor reads needs review. It becomes urgent after three weeks running, or when the week is more than five points under.
- Before the window opens the number reads not applicable yet, with the open date named. It is never shown as green.
- A range whose population moves sharply from one week to the next is not compared, because a change in the number would then be a change in the book.
Tightly puts no money figure on lost availability.
When you compile a declaration, the floor is bound to the replenishment engine's bounds for the variant and channel pairs that carry a live forecast, and the preview says how many pairs that is.
The words on the face
| Word | Where | What it means |
|---|---|---|
| holding | Hover on a number's marker | "scored inside the declaration" |
| watch | Hover on a number's marker | "off-band but below the alert threshold" |
| breached | Hover on a number's marker | "an emitted alert this week" |
| not scored | Hover on a number's marker | "not scored this week"; never read as holding |
| Holds, Breach, Watch, Not scored | The chip beside the number | The same four states in one word, with Over where a recorded breach is above a ceiling |
| on track, needs review, urgent, not measured, not applicable yet | Tasks, the week's verdict | The weekly verdict for the number |
The declared figure and its basis are on the declaration, beside what has moved since. Each amendment that changed it is a version.
What you can do about it
Declare sets it, and Amend moves it as a new version. Where it reads breached or watch, the usual next step is replenishment in season, and Add to Bench stages what a person decides to buy. Nothing here buys anything by itself: the engines propose a quantity and a person approves it.
Lifecycle availability
In Add lifecycle targets, an Availability % can be set separately for Initial buy, In-season top-up and Season exit. Weekly scoring uses the phase that applies. This is a commercial target for the range. It is not a service probability or a safety-stock formula.