How to configure a simple combo meal for STSG2

Pontus Ridderström
  • Updated
Follow

Overview

A simple combo meal combines a fixed main item with a single-choice side and a single-choice drink into one product that carries its own combo price — the worked example here is a Burger Meal (a set burger, a chosen side, and a chosen drink). Configuration spans three phases: building the combo meal building blocks in Oracle Simphony EMC and configuring the Combo Meal Groups, importing the menu and verifying the blocks in Rule Manager, and publishing the meal with an Enable Product rule.

Prerequisites

  • EMC access — you need access to Oracle Simphony EMC at the Enterprise level to create menu item definitions, Combo Meal Groups, and tags.
  • Navigator access — the operator needs access to the relevant Navigator app (Orchestrator and Rule Manager); see Managing access to Navigator applications.
  • A working STSG2 menu import — a configured STSG2 import flow in Orchestrator that generates Future Ordering Masterdata for the menu; see Orchestrator navigator app.
  • All combined products already configured — every product that the meal combines must already be configured as its own product type before the meal is built: the burger (Product with configuration), the side options (for example Fries as a Product with sizes), and the drink options (Single products and Product with sizes). See Configure product types for STSG2 and Creating the first menu building blocks.
  • Base EMC configuration done — the Future Ordering tags must already exist at the Enterprise level; see Configure EMC Enterprise level for the Future Ordering platform.
  • Parent reference articles — Combo Meals describes what a combo meal is and what each combo meal datafield does, and Configure product types for STSG2 describes the building-block product types this meal reuses.

Steps

This guide configures a simple combo meal — a fixed main item with a single-choice side and a single-choice drink, published for STSG2. The steps below reference Future Ordering-specific terms and datafields (Combo Meal, Menu Item Master, Combo Group, Container, the FO_ data extension fields, Rule Manager, the Enable Product rule, and the configurator tags). For the full definition, constraints, and examples of each, see the linked Feature article Combo Meals and the building-block reference Configure product types for STSG2; they are not re-explained here.

Phase 1 — Build the combo meal in Oracle Simphony EMC

This phase builds the combo meal building blocks and configures the Combo Meal Groups in Oracle Simphony EMC. The Sequence number (#), Menu Item Class, Main Level, and Sub Level follow the customer's existing EMC POS menu setup and are not specific to Future Ordering. All sequence numbers, FO_UniqueIdentifiers, FO_LinkedToDefinition, and FO_SelectedItem values shown below are examples that depend on the customer's specific environment — they illustrate the pattern and are not prescribed values.

Important: a container does not need a Price record, and the Menu Item Class used for a container must allow a 0.00 cost. A product must use a Menu Item Class configured as a Product (not a Condiment); condiment items must use a Menu Item Class configured as a condiment.

  1. Create the main item container (the fixed burger slot) as a menu item and set the following datafields:

    • Consumer Item Name — BBQ burger container
    • FO_UniqueIdentifiers — 910010 - BBQ burger container (example)
    • FO_LinkedToDefinition — 3100 (example — the burger product)
    • FO_SelectedItem — 3100 (example — the burger is the fixed, pre-selected choice)
    • FO_SelectionOptions — {"max":1,"min":1}
    • FO_IsContainer — Checked
    • Tags — fo:web:configurator:ignore (hides the selection of the single burger and instead shows the configuration for that burger, or the choice made)

  2. Create the side container as a menu item and set the following datafields:

    • Consumer Item Name — Choose side
    • FO_UniqueIdentifiers — 910011 - Combo side container (example)
    • FO_LinkedToDefinition — 2100,2200,2300,2400 (example — the side products)
    • FO_SelectedItem — 2100 (example — the default side)
    • FO_SelectionOptions — {"max":1,"min":1}
    • FO_IsContainer — Checked

  3. Create the drink container as a menu item and set the following datafields:

    • Consumer Item Name — Choose drink
    • FO_UniqueIdentifiers — 910012 - Combo drink container (example)
    • FO_LinkedToDefinition — 1001,1002,1003,1004,1005,1006 (example — the drink products)
    • FO_SelectedItem — leave empty (no default option is set; the guest must choose)
    • FO_SelectionOptions — {"max":1,"min":1}
    • FO_IsContainer — Checked

  4. Create the combo meal product (the Menu Item Master that carries the meal price) and set the following datafields:

    • Consumer Item Name — BBQ Burger Meal
    • Consumer Item Description — Combine to create a complete product meal
    • FO_UniqueIdentifiers — 9200001 - BBQ Burger Meal (example)
    • FO_LinkedToDefinition — 910010,910011,910012 (example — the three containers, one per combo group)
    • Price record - Price — 13.00 (example — the combo meal price for all combined choices)
    • Price record - Active On Level — 0 - All Levels
    • Tags — fo:web:configurator:meal, fo:services:tagconventions:disable:display:quickadd
    • Images — Product image

  5. Save the Menu Item maintenance.

  6. Open Combo Meal Groups in the Menu Level configuration and create one Combo Meal Group for each container created above. When adding items to a Combo Meal Group:

    • Only add main items — no virtual products or containers may be added as Combo Group Items.
    • The real products in a container must match the products linked to its Combo Meal Group one to one. [SCREENSHOT: the Combo Meal Groups area in Menu Level configuration with the three groups listed]

  7. Configure the primary Combo Meal Group (the burger group): set the Primary Menu Item to the referred menu item, add the burger to Add Combo Group Item, and mark this group as Primary. [SCREENSHOT: the Items tab of the burger Combo Meal Group showing the Primary Menu Item and the burger added]

  8. Configure the side Combo Meal Group: add each side as a Combo Group Item.

  9. Configure the drink Combo Meal Group: add each drink as a Combo Group Item.

  10. Open Combo Meal configuration and create the combo meal: set the Menu Item Master to the combo meal product created in step 4, add each Combo Meal Group, and confirm the burger group is set to Primary. [SCREENSHOT: the Combo Meal configuration screen showing the Menu Item Master and the three combo groups with the burger group marked Primary]

  11. Link the combo meal to its category by adding the combo meal product's sequence number to the category's FO_LinkedToDefinition.

Phase 2 — Import the menu and verify the combo meal

This phase imports the menu and confirms the combo meal building blocks reached Future Ordering Masterdata. The work is done in the Orchestrator and Rule Manager Navigator apps.

  1. In Orchestrator, run the STSG2 menu import flow, or wait for the scheduled run to complete.

  2. Confirm the run finished successfully — the run result shows Finished with no failed jobs.

  3. Open Rule Manager, select Add Rule +, choose the Enable Product rule type under Select Rule Type, and select Continue.

  4. In the Products field, search for the combo meal and its building blocks by name or by FO_UniqueIdentifiers and confirm each one is present: the combo meal product, the main item container, the side container, the drink container, and every option product (burger, sides, drinks). [SCREENSHOT: the Products search in Rule Manager listing the combo meal product and its containers]

Phase 3 — Publish the combo meal with an Enable Product rule

This phase publishes the combo meal to the Frontend with an Enable Product rule in Rule Manager. Create a new rule or add to an existing Enable Product rule.

  1. In Rule Manager, select Add Rule +, choose Enable Product under Select Rule Type, and select Continue.

  2. Set a Name for the rule and an Index.

  3. Set the Publish start and Publish stop dates for the period the meal should be available.

  4. Select the relevant Order classes for the meal.

  5. Under Stores, select Specific and choose the stores that should offer the meal, rather than All.

  6. In the Products field, select every block that makes up the meal as a Product: the combo meal product, the main item container, the side container, the drink container, and every option product (burger, sides, drinks). All imported menu blocks must be selected here for the meal to publish correctly. [SCREENSHOT: the Enable Product rule with the combo meal product and all containers and option products selected]

  7. Save the rule.

Additional Options

These are optional and not required for the simple combo meal to work:

  • Add an additional cost for premium choices — give a Combo Group Item a price in its Combo Meal Group so that choosing it adds that amount to the meal. A choice with no price adds no additional cost. See Combo Meals.
  • Handle different VAT rates within one meal — when the combined products carry different VAT rates, configure the meal product as a Virtual product. The price and VAT information is then collected from each individual product rather than from the combo meal product.
  • Reuse a combo group more than once in the same meal — you can add the same container and Combo Meal Group pairing to a combo meal multiple times, provided you update the FO_LinkedToDefinition values so the containers match the Combo Meal Groups.
  • Different prices per Order Class — add multiple Price records to the combo meal product, each on a specific menu level (Price record - Active On Level) for Eat In, Take away, and Delivery; these can carry different VAT. A different tax class for a whole Order Class is requested from Future Ordering internally.
  • Schedule availability — restrict the meal to a publish window using the Publish start and stop dates on the Enable Product rule.

Expected Outcome

The combo meal appears in the Frontend at its combo price, and selecting it opens a configurator where the burger is fixed and the guest chooses one side and one drink. Choices that carry a Combo Group Item price add that amount to the meal price.

Verify the Configuration

  1. Open the Frontend for a store published by the Enable Product rule and locate the combo meal in its category.
  2. Select the meal and confirm the configurator shows the fixed burger, a single-choice side, and a single-choice drink, with the configured defaults pre-selected. [SCREENSHOT: the combo meal configurator in the Frontend showing the fixed burger, side choice, and drink choice]
  3. Add the meal to the Basket and confirm the price equals the combo price, plus any additive cost for a premium side or drink.
  4. If the meal does not appear or behaves incorrectly, see the Troubleshooting section below.

Known Limitations

  • A given menu item can be the Menu Item Master of only one combo meal — a menu item cannot be reused as the master of a second combo meal.
  • Important: the real products in a container must match the products linked to its Combo Meal Group one to one. The same container and Combo Meal Group pairing can then be reused multiple times within the combo meal.
  • Combo Group Items must be main items only — virtual products, containers, and condiment products cannot be added directly as Combo Group Items.

Note: This list reflects the limitations identified as of 29 June 2026. Additional limitations may exist that have not yet been identified.

Troubleshooting

  • The meal does not appear online — confirm an Enable Product rule selects the combo meal product and all of its containers and option products, and that the category and store are also published (Enable Store, Enable Category, and Enable Product all apply).
  • The meal is hidden even though it is enabled — a Disable rule with a higher Index overrides the Enable Product rule; check the Index values and adjust.
  • A side item is rejected on order — the chosen item is not part of the combo meal configuration in Simphony; see Known Order errors - Solutions and workarounds.
  • The import fails — see Known Menu import issues and solutions and Existing menu issues.