Restaurant profile (modelled)
Type
Izakaya · banquet-capable
Locations
5 stores (greater Yokohama)
Seats / store
40 – 70 seats
Staff
8 – 12 / store (incl. part-time)
Avg. ticket
¥3,500 – 4,800
Hours
17:00 – 00:30
SIMULATION CASE · Scenario #01
"Aburiya" — 5 stores,
missed reservations 40/mo → 0 in three months
A scenario for a hypothetical 5-location izakaya chain in greater Yokohama, moving from Air Regi + three booking portals into a single RestaurantOS install over three months.
Missed reservations: 40/mo → 0/mo
Before — the situation pre-migration
Gurunavi, Tabelog, Hot Pepper Gourmet — three booking portals on three tablets. On a Friday night we genuinely had no idea what was happening.
We probably missed 30 – 40 reservations a month. We'd return the call too late, and the slot was already taken. Customer trust eroded slowly.
Shift changes for all 5 stores came via LINE to managers, then someone at head office typed them into Excel. Same-day swaps didn't reach the floor.
— Modelled owner / male 50s / 5-store operator
Why RestaurantOS — deciding factors
- Air Regi and Toreta were on the shortlist, but "POS only" or "reservations only" wouldn't fix the 3-portal consolidation.
- The external-reservation-parser plugin, which auto-merges three portals into one registry, was the deciding feature.
- HQ-side oversight of 5 stores (shifts, sales analytics) on the same screen — manage 5 stores without adding load to the floor.
Migration process (3 months)
Day 1 – 14
Parallel-run phase
Air Regi and RestaurantOS run in parallel. Yokohama main store pilots first, reservation data flowing into RestaurantOS for accuracy validation.
Day 15 – 30
POS cutover
Yokohama main store cuts over to RestaurantOS POS. Air Regi kept read-only for 30 days, then fully retired.
Day 31 – 60
Roll out to remaining 4
One store per week. Three-day parallel run → cutover pattern, repeated.
Day 61 – 90
Shift & analytics consolidation
All 5 stores' shifts merged into RestaurantOS's shift-adjustment plugin. HQ Excel work drops to zero.
Six plugins deployed (modelled)
Reservations
5-store unified registry
Portal parser
3-portal auto-ingest
POS
Migrated from Air Regi
Shift optimisation
Multi-store scheduling
Sales analytics
Per-store KPIs
AI chat
HQ ↔ store comms
After — three-month numbers
Missed bookings
0 /mo
40/mo → 0
HQ aggregation hours
−12 h/wk
16h → 4h
Shift errors
−85 %
Perceived metric
Portal sync latency
<5 min
30 min → 5 min
HQ-floor info flow
+3 ×
Volume
Owner on-site
−2 d/wk
Decisions from home
Owner's voice (modelled)
On a Friday at eight, when three portals all ring at once, everything still lands in one registry. That alone took half the load off my manager's head.
The 16 hours I lost in Excel turned into time visiting the floor. That doesn't show cleanly in metrics — but as an operator, it's the biggest change.
The system was scary at first. So we piloted one store, got comfortable, and rolled out the rest. Parallel running meant we never had to close.
— Modelled owner
Related
What would the numbers look like for your store?
Answer 12 questions and find out free whether RestaurantOS fits your store.