net sales, daily, all three locations · day-of-week x heat x events
ActualForecast80% bandToday (projected)
The summer story is in the model: a July heat dome held the patio down, the storm week of Aug 19 to 25 gave covers a break, and Labor Day weekend ran 26% over baseline. The cool stretch that started Sep 21 is the run-rate the forecast carries forward, not the July one. Hover any day for the high temperature behind it.
Today · Sun Sep 27
projected close
district net sales
Arcadia / rest of district
Projected guests
Avg check · brunch vs dinner
Peak windows
vs same day last week
Foot Traffic · Today by Hour
checks opened vs outdoor temp
Checks openedOutdoor temp (right axis)
Brunch 9:30 to 2, then the 3 to 7 PM happy hour (daily, per their specials), then the dinner ramp. The temp line is why the 3 to 5 PM happy hour skews to Abby's Oyster Bar and the alcove while the misted patio fills after 6. Patio-heavy days live and die on the forecast.
Location Comparison · Last 7 Days
the district view a DM actually runs
Location
Net sales
WoW
Guests
Avg check
Labor %
Sales / labor h
Perishables · Projected Outflow
on hand vs 7-day usage ratecover = days of stock at current usage
Item
Category
On hand
7-day outflow
Cover
Status
Daily fly-ins (oysters, day-boat fish) are ordered against the forecast, not against last week. This ingredient-level view comes from the recipe layer: purchases entered, usage = items sold x recipe, verified by close-out counts. That layer is the part the POS does not provide.
Staffing vs Sales · Next 7 Days
district schedule vs model recommendation
Role
Scheduled h
Recommended h
Delta cost / wk
Rate
District scheduling flags from the model
Waste and Shrinkage · This Week
expected vs actual outflow
Expected (sales x recipe)Actual (usage + close-out)
Profit Forecast · Next 4 Weeks · District
stacked: cost of goods, labor, fixed · green = projected gross profit
Assumes current recipe costs, 25.2% district labor rate of sales, $38,500 fixed per week across the three locations. Sales band 3 to 9% over the horizon (MAPE vs 7-day naive: over the last 28 days). Forecasting figures, not GAAP.
Where Each Panel's Data Comes From
Toast platform APIs plus the ABM recipe layer
Panel
What we ingest
Source
District Sales and Forecast
84-day daily net sales, guests, order counts, grouped by location and revenue center
/era/v1/metrics + one-time /ordersBulk backfill
Foot Traffic
Per-check open time by hour, dining option (patio vs main), server
/era/v1/check
Staffing
Scheduled shifts, time entries, hours and cost by job, sales per labor hour
/era/v1/labor + /labor API (shifts, employees)
Perishables
Item stock status and quantity (webhook push), usage = items sold x recipe, close-out counts
/stock API + stock webhook + ABM recipe layer
Waste and Shrinkage
Item waste counts, excess-food orders, expected vs actual ingredient outflow
Per-item quantity sold x recipe cost, labor %, fixed costs by location
/era/v1/menu + recipe cost card (ABM layer)
This page runs on simulated data.
The numbers above are generated to look like what the live system produces for the Buck & Rider district. The live build connects to your Toast POS at every location, and the same panels run on your numbers: real sales by location, real check times, real labor, real fly-in orders against real sell-through. Book a free 20-minute consult. No sales pitch, just a look at where the hours and the dollars are going.