Skip to content

Starter Templates and Map Presets

Choose creation presets and update supported saved recipe copies.

Choose the kitchen starting point and the physical environment separately. A starter template1 seeds reusable recipes. A map preset2 supplies locations for a particular installed map.

Choose a restaurant type before creating#

ChoiceWhat you can configureSuitable use
Manual restaurantCustom recipes, independent Operation Points and Supply offersYour own ingredient-processing chains
Template restaurantReady recipe catalogProduct workflows such as Pizza, Taco and Coffee

Choose Manual for custom recipes and independent Operation Points. Choose Template for the ready recipe catalog. The template editor hides Add custom recipe and independent-point creation. Existing supported custom records can remain, but you cannot create them through those hidden controls.

Use Ready and Custom Recipes before choosing. Choose the restaurant type when creating it; the template selector is not a switch for converting an existing restaurant.

Select a map preset only for its map#

  1. Install and start the matching map/MLO resource.
  2. In Create Restaurant, select the intended starter and compatible map preset.
  3. Review any prefilled management/menu positions and seeded recipes.
  4. Walk through the building and inspect the resulting step placements.
  5. Correct the draft placements where needed before saving and publishing.

The preset does not download a building. Coordinates for another map can point to empty air or inaccessible interiors. Choose No map preset when placing your own layout.

A map preset can choose matching independent ready recipes and their material dependencies. The map reservation remains until hard deletion; disabling its restaurant does not free the reservation.

Add another ready recipe later#

Open Kitchen > Recipes and select the preset from the ready recipe catalog. You can add more than one copy. Place each copy separately; staff can work on each one.

Where offered, explicitly apply matching locations from the restaurant's enabled map preset. Manual placement is the default. Only matching steps receive those locations; inspect unmatched steps yourself. Adding another recipe never silently repositions older copies.

Shared material definitions are reused by Item Name without overwriting existing labels, units or enabled state. Removing a recipe leaves those materials in the restaurant.

Update saved recipes#

Replacing resource files does not update all saved recipes. Use a template upgrade3 when offered. It updates the matching preset copies in the draft, leaving manual recipes and other presets alone.

Review the upgraded draft and publish when ready. Existing matching placements are preserved by the upgrade flow; map positions are not applied again automatically. Product-specific compatibility repairs may instead require removing the damaged preset and adding the current one. Follow the panel's server-provided recovery guidance.

When a recipe is Incompatible#

Do not assume its food or inventory has been migrated. Other healthy recipes can continue loading while the incompatible copy stays visible for repair. Use the supported upgrade when the panel offers one; otherwise remove the affected copy, add the current preset, place it, save and publish. Startup does not delete or rewrite the damaged records.

Before updating a live restaurant, use Safe Updates, Templates and Backups. Review Product Guides for placement and workflow changes specific to that food.

Footnotes

  1. A creation-time setup that seeds a restaurant with ready recipes and their shared definitions. Read the definition. ↩

  2. A set of predefined locations for a particular installed map. Read the definition. ↩

  3. Updating a saved recipe with the latest preset definition. Read the definition. ↩