# One standard, every kitchen: oppiPantry | OPPI

> A brand menu branched for each site, costed where it is cooked, with the same limits and the same count everywhere.

Canonical URL: https://oppi.au/oppipantry/outcomes/standard
Site index for agents: https://oppi.au/llms.txt

---
[oppiPantry](https://oppi.au/oppipantry)Outcomes

Outcome

## One standard, every kitchen

The same menu, the same costing, the same rules, site after site.

One kitchen run well is a habit. Three hundred is a system. The menu, the costing and the rules travel with the brand.

[Get early access](https://oppi.au/getOPPI) [Back to the plan](https://oppi.au/oppipantry?layer=outcomes)

### Before

### With oppiPantry

-   Before

    Each site costing the same dish its own way

    With oppiPantry

    One recipe, costed where it is cooked

-   Before

    A menu change emailed round and half applied

    With oppiPantry

    A brand menu branched for each site, live when activated

-   Before

    Every kitchen with its own rules for ordering

    With oppiPantry

    The 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.

### What delivers it

-   [The menu by the passMenu managementPlan it. Change it. Know what it makes.](https://oppi.au/oppipantry/menus)

-   [The passGP managementWhat every plate makes you.](https://oppi.au/oppipantry/gp)

-   [Dry store and coolroomInventory, with OPPI's spatial memoryEvery item has an address.](https://oppi.au/oppipantry/inventory)

### Runs on

-   [Roles, limits and checklistsWho can do what, what goes by itself, and what becomes a task.](https://oppi.au/oppipantry/capabilities/control)

-   [Your point of saleWhat sold, and for how much.](https://oppi.au/oppipantry/capabilities/pos)

### 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.

[Previous The paperwork, handled](https://oppi.au/oppipantry/outcomes/time) [Next Know what every plate makes](https://oppi.au/oppipantry/outcomes/plate)

### Every kitchen has a manager. Now it has two.

oppiPantry is in early access, on oppiOS.

[Get early access](https://oppi.au/getOPPI) [Book a demo](https://oppi.au/demo)