Sprwt has one menu page per ordering channel, each with its own meal list per date:

• Meal Prep Menu (/admin/menus) - the main menu used by A la carte, Packs and Subscriptions. Shown when the A la carte, Packs or Subscriptions module is active.
• Catering Menu (/admin/menus/catering) - requires the Catering module; uses the kitchen's Catering fulfilment days and catering portion sizes.
• POS Menu (/admin/menus/pos) - requires the POS module; listed under the POS sidebar section.
• Real Time Menu (/admin/menus/realtime) - requires the Real Time module; listed under Real Time.
• In Store Menu (/admin/menus/instoremenu) - requires the In Store Menu module; listed under Retail.
• Wholesale Menu (/admin/menus/wholesale) - requires the Wholesale module, listed under Retail; you first create named wholesale menus, then build each one per date.
• Retail Menu (/admin/menus/retail) - requires the Retail module; built per retail location and includes stock handling.

They are separate so that, for example, your catering offer on a Friday can differ from the meal-prep offer for the same Friday. The Meal Prep, Catering, POS, Real Time, In Store and Wholesale menus are all built from the same underlying page: they share the same meal recipes, layout, Select Meals window, preset menus, random generation, clone and CSV export.

The Retail Menu is the exception: it runs on a separate admin page (its own controller, titled "RetailPoint Fulfilment") rather than the shared menu page. It still shares meal recipes, the Select Meals window and Clone, but it does not offer Select A Preset Menu, Randomly Generate a Menu, or Export to CSV, and it is protected by its own permissions rather than "Create menus" (see the access question).