One standard, every kitchen

• BeforeEach site costing the same dish its own way

  With oppiPantryOne recipe, costed where it is cooked

• BeforeA menu change emailed round and half applied

  With oppiPantryA brand menu branched for each site, live when activated

• BeforeEvery kitchen with its own rules for ordering

  With oppiPantryThe same roles and limits at every kitchen

• The brand menu

  Write it once. Branch it for the region.

  Write the menu at the brand level, then branch it for a region or a site. Each branch is costed where it is cooked, and nothing goes live at a site until someone activates it there.

• The local twist

  One site's twist leaves the base recipe alone.

  Recipes are shared, so a correction to the base recipe reaches every menu that uses it. When one site needs the dish done differently, fork the recipe for that menu and the rest of the group keeps the original.

• Kitchen against kitchen

  What each kitchen used, against what it should.

  The recipes say what each kitchen should have used. The count says what it did. Set against each other by ingredient and by kitchen, the site drifting from the standard shows up in the numbers.

• The menu by the passMenu managementPlan it. Change it. Know what it makes.
• The passGP managementWhat every plate makes you.
• Dry store and coolroomInventory, with OPPI's spatial memoryEvery item has an address.

Questions.

Can one menu run across all our sites?

Yes. A brand menu is branched for a region or a site and costed where it is cooked. Each branch goes live at a site when it is activated there.

Do the same rules apply at every kitchen?

Yes. Roles and approval limits carry across the group, so ordering and sign-off work the same way at the tenth site as at the first.