Glossary
Plain-language definitions of the terms you’ll meet across KeyOne. Skim it once, refer back as needed. About 6 minutes.
KeyOne borrows vocabulary from retail, analytics, and its own way of working. Here’s what each term means in practice.
Core concepts
SKU × Store × Day The lowest grain KeyOne holds data at — every SKU, in every Store, on every Day. Almost every metric is computed from this base and rolled up. Because the data lives at this grain, you can always drill from a national number down to one product in one store on one date. (See Connecting Your Data.)
SKU (Stock Keeping Unit) A single, distinct sellable product variant — a specific size, flavour, or pack of a brand. “500ml Cola” and “2L Cola” are different SKUs.
Principal The brand owner — the FMCG company whose products sell through retailers. KeyOne is built for principals. Each principal is an isolated tenant.
Tenant An isolated workspace and dataset belonging to one principal. Your data is yours; tenants don’t see each other’s data.
Decisions & work
Work item The atomic unit of work in KeyOne — a single tracked thing to look at or do. Risks, decisions, tasks, decisions, signals, goals, and initiatives are all kinds of work item. (See Working a Decision.)
Risk A work item representing value at risk if nothing is done — e.g. revenue exposed by an out-of-stock. Shown with red exposure.
Decision A work item representing value to be gained by acting — e.g. a distribution gap worth filling. Shown with green upside.
Task A concrete action to be carried out, often in the field — e.g. replenish a shelf or fix a price. Reps see tasks in KeyLink.
Decision A work item representing an explicit choice or sign-off a person must make — e.g. approve a promotional price or a range change. A decision is distinct from an decision (value to be gained) and a task (an action to carry out): it is the call itself that unblocks the work. Decisions are their own type in the Work Queue, shown alongside — not merged with — risks, decisions, and tasks.
Work Queue Your inbox of work items, grouped and ranked by value and severity. (See Decision Inbox & Win List.)
Win List The engine’s nightly-ranked list of the highest-value actions, each with a weekly rand value and a priority score. It’s also what feeds field reps’ daily tasks.
Work Graph The web of typed relationships between work items — addresses, mitigates, caused-by, blocks, depends-on, and so on. It’s how an executive’s high-level risk and a rep’s in-store task are revealed as one tracked problem seen from different angles. You see it as the Relationships section on a work item.
Resolution code A short, type-aware reason you pick when closing a work item (e.g. “Replenished from backroom”). It feeds KeyOne’s learning loop, so accurate codes make future recommendations sharper.
Impact estimate The rand figure attached to a work item, with a P10–P90 range and a confidence percentage. (See Understanding Impact Estimates.)
P10 / Point / P90 The low (P10), central (point), and high (P90) of an estimate’s range. Roughly 80% of likely outcomes fall between P10 and P90.
Confidence A percentage saying how much KeyOne trusts a given estimate, based on how much comparable history informed it.
T+30 verification The loop that, about 30 days after an action, checks an estimate against what actually happened — improving calibration over time.
Closed loop KeyOne’s core idea: a problem is detected → turned into a tracked action → executed → and the result measured, feeding back to sharpen the next recommendation.
DiagramDetect, decide, act, re-measure — then repeat
Retail metrics
Rate of sale (ROS) How fast a product sells — typically units sold per store per day across your range. The pulse of demand.
OSA (On-Shelf Availability) Of the stores where a product is listed, the percentage that actually have it on the shelf right now. High distribution with low OSA means you’re listed but out of stock where it counts.
Distribution The percentage of targeted stores that have your SKU listed / ranged. Answers “where are we present?” — as opposed to OSA’s “is it actually on the shelf?”
Share of shelf The percentage of linear shelf space occupied by your products in a category — a key signal of in-store presence, often read from shelf photos.
Category share How your products perform versus the whole category and competitors.
Void / void-fill A void is a gap where a product should be on shelf but isn’t; void-fill is the action of closing it.
Planogram compliance Whether a store’s shelf actually follows the approved layout (the planogram).
Revenue at risk An estimate of the weekly revenue impacted by current out-of-stocks and distribution gaps.
Surfaces & tools
Hub A focused analytics workspace for one commercial or operational area (Price & Promo, OSA, Waste, etc.), with a narrative, KPI strip, charts, and a Decisions & Actions panel. (See Using a Hub.)
KeyChat The conversational analyst — ask questions in plain language, get grounded, cited answers. (See KeyChat.)
KeyLink The mobile field companion for reps — route, store visits, shelf audits, and task completion. (See KeyLink for Field Reps.)
Command palette The ⌘K search box that jumps you to any page or hub. (See Keyboard Shortcuts.)
Decision Feed The always-on bottom bar showing live counts of open risks, decisions, and tasks. (See Notifications & the Decision Feed.)
Image recognition (IR) Turning shelf photos into structured data — gaps, share of shelf, compliance, competitor presence.
Honest note: image recognition is currently simulated — the capture, write-back, and task creation are real, but the part that identifies what’s in the photo is a placeholder, and results are labelled as simulated. (See KeyLink.)
Statuses you’ll see
| Status | Meaning |
|---|---|
| Open | Active and awaiting attention |
| Blocked | Held up by a dependency |
| Critical | Highest urgency; bubbles to the top of the queue |
| Monitoring | Acted on; awaiting verification |
| Resolved | Closed successfully (with a resolution code) |
| Dismissed | Closed as not worth acting on |
| Failed | Acted on, but the outcome didn’t hold |
DiagramHow an item progresses — with dismissed and failed as off-ramps
Next: FAQ & Troubleshooting