Sales forecast
Three weeks ahead, by hour and by order type (dine-in, takeout, delivery). The model takes events and weather into account.
Syrve forecasts sales, turns the forecast into a prep list and links it to the schedule. We add a weekly check of whether the schedule matched the sales.
Live
Updated 2026-11-19
Three weeks ahead, by hour and by order type (dine-in, takeout, delivery). The model takes events and weather into account.
What share of sales each item or category is expected to take, so the forecast becomes a list of dishes, not just a dollar figure.
Dishes turn into ingredients through recipes, so you see expected usage of cheese, dough or fish by day.
A prep list for the kitchen by hour, before opening. Less over-prep, fewer stock-outs at the rush.
Test a price rise, a supplier switch or a volume change before you do it, and see the effect on margin. Covers up to 30 restaurants.
Holidays and one-off events are marked, so a private party or a local festival does not distort the baseline.
The forecast is only useful if it reaches the people who set staffing. Syrve connects to Deputy (Native): sales and forecast go to Deputy for scheduling, and clock-in records come back to Syrve. Deputy is a separate subscription.
We add a check on top, built by us (Via SmartyPOS): each week we compare the schedule with actual sales by hour. Hours per employee, overtime, kitchen and front-of-house coverage against demand, and the dollar value of over-scheduling. At Sole Mio it runs automatically on Mondays.
Read last week's schedule-versus-sales review. Note the two or three hours that were over or under staffed.
Open the three-week forecast. Mark upcoming events. Adjust the schedule in Deputy.
Use the Prep Plan for the day. Compare prepped quantities with what sold and correct the next day.
Run a What-If before a price or supplier change. Record the result and the actual outcome.
Syrve documents a three-week sales forecast by hour and order type, with events and weather taken into account.
Deputy is a Native integration. Other tools are On request.
Our own weekly analysis (Via SmartyPOS): hours per employee, overtime, coverage by hour against guests and dishes, and the cost of over-scheduling.
It is part of Syrve's web office for larger plans. We confirm which plan includes it on the demo.
Typing supplier invoices and guessing order quantities are two of the quietest costs in a restaurant. Syrve has tools for both, and we add a purchasing...
Read moreStock, recipes and costing are part of Syrve, down to the ingredient. You do not buy a second product to see food cost.
Read moreOne message a day per venue, a P&L portal and a set of watchdogs, all built on Syrve data.
Read moreSyrve was built for chains. Menus, prices, central kitchen and reports are managed at group level and pushed to each venue.
Read moreYes, add-on, partner, no, or not confirmed, row by row. We sell Syrve, so check the sources; where we could not confirm a competitor feature we...
Read more45 minutes, no pressure. We open Syrve around your concept, show what is live, and say plainly whether it is a fit.
Read moreWe run a private MCP server on top of the restaurant's own Syrve. Claude or ChatGPT connect to it, read your numbers and, if you allow...
LiveRead moreSyrve documents its Cloud and server APIs publicly. A restaurant, or the team it hires, can read data and change it: prices, menu cards, schedules, loyalty,...
LiveRead moreA branded ordering website wired straight into Syrve. Menu, modifiers, taxes and promos come from the POS, so there is nothing to keep in sync by...
LiveRead moreA 45-minute call. We open Syrve with your concept in mind, show what is live today, and tell you straight whether it fits.