How to configure a reusable cup choice for a drink for Oracle STSG2

Pontus Ridderström
  • Updated
Follow

Overview

A reusable cup choice lets the customer pick between a reusable cup and a single-use cup before adding a drink to the Basket, with one cup preselected as the default. Configuration spans three phases: the two cup products and a single-select cup container are built in Oracle Simphony EMC and the container is linked to the drink product; the menu is imported and the cup building blocks are verified in Rule Manager; and the drink and its cup building blocks are published with an Enable Product rule in Rule Manager. Because the cup container is linked to the drink product itself, the cup choice travels with the drink and also appears when the drink is sold as a change option inside a meal.

Prerequisites

Before configuring a reusable cup choice, confirm the following are in place.

  • Oracle Simphony EMC access — the operator needs access to the property's Oracle Simphony EMC to create and edit menu items.
  • Navigator access — the operator needs access to the relevant Navigator app; see Managing access to Navigator applications. Both Orchestrator and Rule Manager are used in this guide.
  • A working STSG2 menu import — the STSG2 menu import must be configured in Orchestrator so EMC changes can be imported into Future Ordering; see Orchestrator navigator app.
  • Base EMC configuration completed — the enterprise and property level EMC configuration for the Future Ordering platform must already be done; see 2. Configure EMC Enterprise level for the Future Ordering platform.
  • An existing drink product — the drink the cup choice attaches to (for example, Small Coca-Cola) must already exist in EMC, or be created during Phase 1.

Steps

The steps below reference the cup container, the two cup condiment products, the FO_ EMC datafields (FO_IsContainer, FO_LinkedToDefinition, FO_SelectedItem, FO_SelectionOptions), and the Enable Product rule. For full definitions, constraints, and the exact datafield values, see Configure product types for STSG2, Data extensions in Oracle Simphony EMC for Future Ordering, and Rule Manager.

Phase 1 — Build the cup container and cup products in Oracle Simphony EMC

This phase creates the two cup products and the cup container in Oracle Simphony EMC and links the container to the drink product. Use the container and condiment values in the product type reference; substitute your own product details.

The Sequence number (#), Menu Item Class, Main Level, and Sub Level of each menu item follow the customer's existing EMC POS menu setup and are not specific to Future Ordering; set them according to the POS menu configuration. Important: the drink must use a Menu Item Class configured as a Product, not a Condiment, and each cup product must use a Menu Item Class that is configured as a condiment.

  1. In Oracle Simphony EMC, confirm the drink product menu item exists, or create it, with the following datafields:
    • Consumer Item Name — the drink's display name (example: Small Coca-Cola).
    • FO_UniqueIdentifiers — the drink's Future Ordering identifier (example: 4100 - Small Coca-Cola).
    • Price record - Price — the drink price (example: 2.00), with Price record - Active On Level set to 0 - All level.
    • Menu Item Class — a class configured as a Product.
    • Images — attach the drink image.
  2. Create the Reusable cup condiment product, and set the following datafields:
    • Menu Item Class — a class configured as a condiment.
    • Consumer Item Name — Reusable cup.
    • FO_UniqueIdentifiers — the cup's Future Ordering identifier (example: 4201 - Reusable cup).
    • Price record - Price — 0.00, with Price record - Active On Level set to 0 - All level.
    • Images — attach the cup image.
  3. Create the Single-use cup condiment product, and set the following datafields:
    • Menu Item Class — a class configured as a condiment.
    • Consumer Item Name — Single-use cup.
    • FO_UniqueIdentifiers — the cup's Future Ordering identifier (example: 4202 - Single-use cup).
    • Price record - Price — 0.00, with Price record - Active On Level set to 0 - All level.
    • Images — attach the cup image.
  4. Create the Cup container, and set the following datafields:
    • FO_IsContainer — checked.
    • Consumer Item Name — Cup.
    • FO_UniqueIdentifiers — the container's Future Ordering identifier (example: 14001 - Drink cup container).
    • FO_LinkedToDefinition — the Sequence numbers of the two cup products (example: 4201,4202).
    • FO_SelectedItem — the Sequence number of the default cup (example: 4202, the single-use cup).
    • FO_SelectionOptions — {"max":1,"min":1} so the customer always selects exactly one cup.
    • Price record — not required on a container.
    [SCREENSHOT: the EMC Cup container showing FO_LinkedToDefinition listing both cup products and FO_SelectedItem set to the default cup]
  5. On the drink product, set FO_LinkedToDefinition to include the Sequence number of the Cup container, alongside any containers the drink already uses (for example a size container), then save the menu items. [SCREENSHOT: the EMC drink product showing FO_LinkedToDefinition pointing to the Cup container]

Phase 2 — Import the menu and verify the cup building blocks

This phase imports the EMC menu items into Future Ordering and confirms the cup container and cup products exist before they are published.

  1. In Orchestrator, run the STSG2 menu import (or wait for the scheduled import to complete); see Orchestrator navigator app.
  2. Confirm the import Run finished successfully before continuing.
  3. In Rule Manager, click Add Rule +, choose Enable Product in Select Rule Type, and click Continue to open a rule where you can search products.
  4. In the Products field, search for the Cup container and both cup products by name or their FO_UniqueIdentifiers values and confirm they appear in the results — this confirms the building blocks were imported. [SCREENSHOT: the Rule Manager Products search showing the imported Cup container and the two cup products in the results]

Phase 3 — Publish the drink and cup building blocks with an Enable Product rule

This phase publishes the drink and its cup building blocks so the cup choice is sold online, by creating a new Enable Product rule or adding the building blocks to an existing one.

To create a new Enable Product rule:

  1. In Rule Manager, click Add Rule +, choose Enable Product in Select Rule Type, and click Continue.
  2. Enter a Name for the rule and set the Index so it reads in the correct order relative to other rules.
  3. Set Publish start/stop for the period the drink should be available.
  4. Set Order classes to the order classes the drink should be sold on.
  5. Set Stores to the stores the drink applies to, using Specific rather than All where possible.
  6. In the Products field, select every building block created for this cup choice — the drink product, the Cup container, and both cup products (Reusable cup and Single-use cup). All imported menu blocks must be enabled as Products for the configurator to build correctly.
  7. Save the rule. [SCREENSHOT: the Enable Product rule with the drink, the Cup container, and both cup products selected in the Products field]

To add the cup choice to an existing Enable Product rule instead, open that rule, add the drink product, the Cup container, and both cup products in its Products field, and save.

To make the cup choice appear inside a meal, confirm the same drink product, the Cup container, and both cup products are selected by an Enable Product rule whose Stores and Order classes also cover the meal. The cup choice renders inside the meal only where these building blocks are enabled.

Additional Options

These are optional and not required for the cup choice to work:

  • Charge a deposit or surcharge on a cup — add a priced Price record to the relevant cup product (for example a deposit on the reusable cup) on Price record - Active On Level 0 - All level, so the price updates when the customer selects that cup. See Configure product types for STSG2.
  • Default to the reusable cup — set FO_SelectedItem on the Cup container to the reusable cup's Sequence number to preselect the reusable option and support the reusable packaging directive. See Reusable food packaging.
  • Show a reusable packaging message — surface information about the reusable option on the start screen or a heropromo, as described in Reusable food packaging.
  • Different prices per order type — add multiple Price record entries to a cup product, each on a specific menu level (Price record - Active On Level), to charge a different cup price for order types such as Eat In, Take away, and Delivery. See 2. Configure EMC Enterprise level for the Future Ordering platform.

Expected Outcome

The drink is published with a single-select cup choice — Reusable cup and Single-use cup — with the configured cup preselected, and the customer selects the cup type before adding the drink to the Basket. The same cup choice appears when the drink is offered inside a meal, wherever the drink product and both cup products are enabled by an Enable Product rule.

Verify the Configuration

Confirm the cup choice is live and works as configured.

  1. Open the Frontend for a store and order class the Enable Product rule covers.
  2. Browse to the category that contains the drink, open it, and confirm the cup choice appears with both cups and the default cup preselected. Switch the cup, then add the drink to the Basket and confirm the basket line reflects the chosen cup. [SCREENSHOT: the drink configurator in the Frontend showing the Reusable cup and Single-use cup choice with the default cup preselected]
  3. Open a meal that offers the drink, select the drink inside the meal, and confirm the same cup choice appears in the meal configurator. [SCREENSHOT: the meal configurator in the Frontend showing the cup choice on the selected drink]

If the cup choice does not appear or behaves incorrectly, see the Troubleshooting section below.

Known Limitations

  • The cup choice always requires exactly one cup — the Cup container uses FO_SelectionOptions {"max":1,"min":1}, so the customer cannot order the drink with no cup or with more than one cup type.
  • The reusable cup and the single-use cup are two separate EMC products. There is no single product that represents both cups.
  • The cup choice appears inside a meal only where the drink product, the Cup container, and both cup products are enabled by an Enable Product rule whose stores and order classes cover the meal. If they are enabled only for standalone sale, the cup choice does not render inside the meal.
  • Rendering the cup choice nested inside a meal configurator depends on the Frontend support for a container on a change option. Confirm the meal surface in the Verify step for your environment before relying on it.

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

Troubleshooting

Common issues and how to resolve them:

  • The cup choice does not appear online — confirm an Enable Product rule selects the drink product, the Cup container, and both cup products, and that the drink's category and store are published with Enable Category and Enable Store rules. The cup choice is only visible where all three apply.
  • No default cup is shown, or the customer cannot change the cup — confirm the Cup container's FO_LinkedToDefinition lists both cup products, FO_SelectedItem is set to the default cup's Sequence number, and FO_SelectionOptions is {"max":1,"min":1}.
  • The cup choice is missing inside a meal — confirm the drink product, the Cup container, and both cup products are enabled by an Enable Product rule covering the meal's stores and order classes, and that the drink's FO_LinkedToDefinition includes the Cup container.
  • Import failures — see Known Menu import issues and solutions and Existing menu issues.