Orbis is the intelligence layer independent restaurants have never had — connecting what you expect to sell, to what you prep, to what you order, to what it costs you in labour. Before the week starts.
Not from carelessness. From operating without the data layer that makes better decisions possible. Orbis is that layer.
You prepped for Saturday's crowd on a Tuesday that looked busy. Forty portions of salmon went in the bin at close. The data to predict Tuesday existed. Nobody was reading it.
Five on the floor for a service that needed three. Payroll for that shift exceeded what the kitchen earned. The rota was written on a gut feeling about a day that didn't arrive.
Supplier invoices arrive and you've overbought again. Or you ran out mid-service. Ordering without a demand forecast is a guess dressed up as a process.
TES collective agreement rules — Sunday premiums, evening rates, three-week averaging — calculated manually every payroll cycle. Hours spent on arithmetic that should be automatic.
Most restaurant software gives you tools to react. Orbis gives you a loop that runs before the shift starts — so decisions are made on data, not instinct.
Orbis reads your POS history alongside weather, confirmed reservations, local events, and day-of-week patterns. Not just what sold — the signal behind it.
POS integration · External signals · Reservation dataA demand forecast per dish, with the logic shown. Not a black box. "Meatballs 30–50 portions — last 4 Tuesdays, rain forecast −10%, match day nearby +15%." You see why.
Demand forecast · Reasoning shown · Override logged as training dataThe misa list — quantities per dish, sequenced by station and prep time. One tap to confirm. Every correction you make feeds the next prediction.
Mise-en-place list · Station sequencing · Confirmation in one tapConfirmed misa quantities are deducted from live inventory using your recipe graph. Shortfalls are identified automatically — you don't count backwards from what's on the shelf.
Recipe-locked deduction · Live inventory · Shortfall flagsA draft purchase cart per supplier, quantities in pack sizes, prices pulled from your own invoice history. You approve. Orbis learns your supplier relationships over time.
Draft cart · Supplier price history from invoices · Human approvalDemand forecast → staffing need per hour → draft rota that is TES-legal by construction. Labor cost as a percentage of forecast revenue, visible before a single hour is worked.
TES-compliant scheduling · Labor cost view · Draft rota for approvalThe biggest fear any restaurant owner has with a new system is being wrong at the wrong moment. Orbis was designed to earn trust before it asks for it. Shadow mode runs the full loop silently alongside your kitchen — forecasting, calculating, comparing its predictions against what actually happens. You see the accuracy improve in real time. You decide when you trust it enough to act on it.
Orbis is in active R&D with Helsinki design partners. This is the honest picture of where the product is and where it's going — no horizon collapsed into a feature list.
Every H1 feature was chosen because it captures data that makes an H3 feature possible. The loop isn't a product decision — it's a data accumulation strategy. A competitor who starts building tomorrow cannot buy three years of per-kitchen learned patterns, override histories, and supplier price data. That's the moat. It compounds with time.
We're onboarding a deliberate cohort of independent restaurants for the R&D phase. Not chains. Not franchises. Kitchens where the owner is still in the room — because that's where the real decisions happen and the real feedback comes from.