Skip to main content

Fetching and managing Menus

Menus for all Pepper ordering journeys are fetched from POS and then augmented in the Pepper platform. This allows a merchant to avoid duplicating data entry, whilst being able to manage additional information needed for customer presentation of the menus which POS may not be able to provide.

The menus from which the User can build their basket are specific to each Location; allowing for differences in the Merchant's offering from store to store.

Menu Fetch Flow

The Pepper menu structure makes the following assumptions:

  1. A menu may be assigned to one or more locations
  2. Only one menu at a time may be available to a single location
    • Different menus may be available on a schedule
    • Where different menus are used in the POS for different categories (e.g. Drinks vs. Food) it is expected that the merchant configure a single menu for use with Pepper which separates these into categories
  3. Pepper supports two levels of categorisation, "Parent Categories and Categories"
  4. Product Groups in the Pepper Menu are used to describe sizes, or variants of products. A product group may be mapped to a single PLU/SKU in a POS, but have multiple variants with a unique itemId in the Pepper menu.
  5. Modifiers (aka choices, options, condiments) which are chooseable by a customer for a selected product are mapped in the Pepper menus either as options or as products. Modifier options exist only in the context of a menu item, or category of items e.g. Cooking temperatures on Steaks, whereas Modifier products may include products that are available in their own right, e.g. a side of fries, which may be included with an item as a modifier or as a separate additional item.