Skip to content
WebOperations

A production line made of recipes.

End-to-end workflow management for culinary teams — ingredient prep, sub-recipe creation, jar filling and dish execution with real-time status, clear assignments and automated tracking.

+47%Recipe consistency
−82%Allergen incidents
−60%Site ramp time
Unified Recipe System
ClientFeelEat (Switzerland)
IndustryOperations · FoodTech
PlatformWeb · Kitchen tablets
DisciplinesCustom · ERP · Data
The brief

A commercial kitchen is a factory that never wrote down its process.

ClientFeelEat Sàrl · Switzerland
Consistency+47% recipe
Allergen incidents−82%
SurfacesWeb · Kitchen tablets

Hundreds of fresh meals a day depend on prep chains: base recipes feeding sub-recipes feeding dishes, across stations and shifts. That choreography lived in chefs’ heads and whiteboards — invisible to planning, unverifiable for allergens, and fragile every time a key person was off.

We modelled the kitchen as the production system it really is: recipes as bills of materials, prep as tracked work orders, stations as assignable capacity. Every batch — from ingredient prep to jar filling to finished dish — now moves through real-time statuses with automated tracking behind it.

Treated as a production system, the kitchen started behaving like one: recipe consistency up 47%, allergen incidents down 82%, and new locations ramping 60% faster — every batch tracked from prep to jar to plate.

The challenge

The process lived in chefs’ heads.

A factory’s worth of choreography — invisible to planning, unverifiable for allergens, fragile to absence.

01 — The problem

An unwritten production line.

Prep chains spanned stations and shifts with no system underneath them.

  • Knowledge walks outa key chef off sick stalled entire prep chains.
  • Allergens unverifiableno traceable line from ingredient to finished jar.
  • Planning was blindprep status lived on whiteboards and in heads.
  • Onboarding by shadowingnew kitchens took months to ramp.
02 — The solution

The kitchen, modelled honestly.

Recipes as bills of materials, prep as tracked work orders, stations as assignable capacity.

  • Recipe BOMsbase recipes feeding sub-recipes feeding dishes, explicitly.
  • Tracked batchesingredient prep to jar filling to dish, with live status.
  • Allergen traceabilityincidents down 82% through the traceable chain.
  • Repeatable sitesnew kitchens ramp 60% faster on a written process.
What we built

Mise en place, systematised.

The culinary workflow, modelled honestly — not flattened into a generic task app.

01

Recipe & sub-recipe graph

Dishes modelled as layered recipes with yields, costs and allergens inherited correctly.

02

Prep work orders

Daily production translated into station-level tasks with quantities and deadlines.

03

Jar-filling workflow

Batch portioning tracked unit by unit — the bridge between kitchen and fridge retail.

04

Real-time status board

Every batch’s state visible across the kitchen — no shoulder-tapping to find out.

05

Task assignments

Clear ownership per station and shift — handovers survive whoever is off today.

06

Automated tracking

Lot-level traceability from ingredient to dish — allergen and quality answers in seconds.

How we built it

Writing down the choreography.

Four phases, starting with time spent in the production kitchen.

1

Conceptualisation

Spent time in production kitchens mapping the real prep chains, station by station.

2

Design

Station screens chefs can use mid-shift — gloves on, glance up, tap once.

3

Development

The workflow engine: recipe BOMs, work orders, live statuses, automated tracking.

4

Deployment

Site-by-site rollout — +47% recipe consistency in production.

The hard parts

What kept us up at night.

The problems that decided whether the product worked at all.

01

Modelling without flattening

Generic task apps die in kitchens. Sub-recipes, par levels and station capacity had to be modelled the way chefs actually think.

02

Allergen-proof traceability

Every dish traces back through every sub-recipe to ingredient lots — the chain a recall or an allergy incident demands.

03

Software at kitchen pace

Updates mid-rush, with wet hands, in seconds. The interface had to survive a real service, not a demo.

Architecture

Tech stack.

A manufacturing system that speaks kitchen.

Node.jsNestJSMySQLRedisElasticSearch
The outcome

Numbers the owners watch.

The kitchen’s tribal knowledge became an operating system it can hire against.

+47%Recipe consistency score

Every site cooks the same dish — the recipe graph enforces it.

−82%Allergen incident rate

Lot-level traceability turned allergen control from hope into arithmetic.

−60%New-location ramp time

New kitchens onboard against a written, running process.

Your turn

Have a problem worth
solving well?

Tell us about your product, your timeline and your constraints. We reply within one business day with an honest read on fit, scope and the right team.