Operating question · Inventory risk radar
Catch the stockout — and the supplier price spike — before service.
Before Service blends on-hand counts, forecasted usage, supplier lead times and live invoice prices into a risk-ranked list of what to order, sub or re-price today.
Focused output
IN REVIEWInventory radar
System generated — operator review required.
What it answers
By the time inventory tells you, the dish is already 86'd.
Counting tools tell you what you have. They don't tell you what you'll need by 13:00 on a Tuesday with rain forecast and a 220-cover brunch coming.
Avocado out by 13:00 — no one knew at 06:00.
Supplier price up 6.2% on chicken thigh, no alert.
Lead time missed; weekend prep short on a key SKU.
Same SKU 86'd three Tuesdays in a row, no root-cause flagged.
Inputs
Signals used to prepare the brief
- Stockout risk ranked by cost-of-86 in covers, not units
- Supplier price spikes flagged the day they hit the invoice
- Suggested subs preserve the menu and the margin
- Lead-time alerts on slow-moving but critical SKUs
Output artifact
A radar that ranks every SKU by today's risk.
- Stockout risk ranked by cost-of-86 in covers, not units
- Supplier price spikes flagged the day they hit the invoice
- Suggested subs preserve the menu and the margin
Confidence + rationale
Readable evidence, not a black box
- Invoices, recipes, on-hand counts, sales mix, and recorded waste
- Confidence shown beside the recommendation
- Source signals stay available for review
Operator boundary
The system prepares the call. Your team confirms it.
Realistic pre-service scenario
Cream coverage falls below the dinner par while its supplier cost rises. The operator confirms the response.
No automatic action. A human operator reviews every decision.
Service sequence
How a chef clears the morning risk list.
- 06:00
Risk radar ranks 4 SKUs at high stockout risk for today.
- 06:15
Avocado flagged out by 13:00 — chef approves smashed-pea sub.
- 06:20
Chicken thigh price up 6%; menu margin board nudges a $1 re-price.
- 06:30
Order suggestions drafted for operator review before tomorrow's deliveries.
- Post-shift
Actual usage reconciles against forecast and updates lead-time signals.
Connected workflows
Inventory risk drives prep, menu and the daily brief.
See tomorrow's 86 list — today.
Connect your inventory counts and recent supplier invoices — the radar lights up after one count.
FAQ
Questions operators actually ask.
No. Before Service sits on top of the POS, schedule and vendor invoices you already use. We turn that data into the daily decisions a POS won't tell you — what to prep, who to staff, what to re-price, what to 86.