How to configure a Product with size and configuration for Oracle STSG2

Pontus Ridderström
  • Updated
Follow

Overview

A Product with size and configuration is a menu product offered in several sizes where each size can also be customised — for example, a burger available in 90g and 150g, each with the full set of condiment add, change, and remove options. Configuration spans three phases: the virtual product, the size container, the size products, the add, change, and remove containers, and the condiment products are built in Oracle Simphony EMC; the menu is imported and the virtual product building block is verified in Rule Manager; and the product is published with an Enable Product rule in Rule Manager.

Prerequisites

Before configuring a Product with size and configuration, 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.
  • Product type reference — the Product with size and configuration datafield set is defined in the parent article Configure product types for STSG2.

Steps

The steps below use these terms. For full definitions, constraints, and the exact datafield values, follow the linked articles.

  • Virtual product — the sellable parent item marked with FO_VirtualProduct that presents the size choice. See Configure product types for STSG2.
  • Size product — a real product for one size (for example, 90g) that itself carries the configuration containers. See Configure product types for STSG2.
  • Container — a building block marked with FO_IsContainer; this product uses a size container plus add, change, and remove containers. See Configure product types for STSG2.
  • FO_LinkedToDefinition — the EMC datafield that links the virtual product to the size container, the size container to the size products, and each size product to its configuration containers. Its values are EMC Product Sequence numbers, separated by commas; to target a specific definition record, use the format Sequence number:Definition Record nr. See Data extensions in Oracle Simphony EMC for Future Ordering.
  • FO_SelectedItem — the EMC Product Sequence number of the default selected item in a container (same Sequence number:Definition Record nr format is supported). See Data extensions in Oracle Simphony EMC for Future Ordering.
  • FO_SelectionOptions — set on a container only; controls how many items can be selected (for example {"max":1,"min":1} or {"min":0}). Condiment products do not use it. See Data extensions in Oracle Simphony EMC for Future Ordering.
  • Enable Product rule — the Rule Manager rule type that publishes a product so it is sold online. See Rule Manager.

Phase 1 — Build the building blocks in Oracle Simphony EMC

This phase creates the configuration containers, the condiment products, the size products, the size container, and the virtual product in Oracle Simphony EMC. Use the Product with size and configuration 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: each product must use a Menu Item Class configured as a Product, not a Condiment, and each condiment product must use a Menu Item Class that is configured as a condiment.

  1. In Oracle Simphony EMC, build the Add, Change, and Remove containers and their Add and Remove condiment products as described in How to configure a Product with configuration for STSG2, so the configuration set is ready to attach to each size. An add-on and its removal are two separate condiment products: a priced Add condiment and a zero-cost Remove condiment.
  2. Create a real product for each size. For each size product, set the following datafields:
    • Consumer Item Name — the size's display name (example: BBQ Burger - 90g).
    • Consumer Item Description — the product's description.
    • FO_UniqueIdentifiers — the size's Future Ordering identifier (example: 3111 - BBQ Burger - 90g).
    • Price record - Price — the size's price (example: 15.00), with Price record - Active On Level set to 0 - All level.
    • FO_LinkedToDefinition — the Sequence numbers of the Add, Change, and Remove containers, so every size carries the full configuration.
    • Images — attach the product image.
    • Repeat these datafields for every size (example: 150g at 20.00).
  3. Create the size container, and set the following datafields:
    • FO_IsContainer — checked.
    • Consumer Item Name — the container name.
    • FO_UniqueIdentifiers — the container's Future Ordering identifier.
    • FO_LinkedToDefinition — the Sequence numbers of the size products (example: 3111,3112).
    • FO_SelectedItem — the Sequence number of the default size.
    • FO_SelectionOptions — {"max":1,"min":1}.
    • Tags — fo:web:configurator:ignore (required on the size container); see Tag combinations.
    • Price record — not required on a container.
  4. Create the virtual product, and set the following datafields:
    • FO_VirtualProduct — checked.
    • Consumer Item Name — the product's display name (example: BBQ Burger).
    • FO_UniqueIdentifiers — the product's Future Ordering identifier.
    • Price record - Price — 0.00, with Price record - Active On Level set to 0 - All level.
    • FO_LinkedToDefinition — the Sequence number of the size container.
    • Tags — fo:web:display:quickconfigurator and fo:services:tagconventions:disable:display:quickadd, so clicking the product opens the configuration view where the customer chooses the size and customises the product, rather than quick-adding it; see Tag combinations.
  5. Save the menu items. 

Phase 2 — Import the menu and verify the building block

This phase imports the EMC menu items into Future Ordering and confirms the virtual product building block exists before it is 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 virtual product by name or its FO_UniqueIdentifiers value and confirm it appears in the results — this confirms the building block was imported. 

Phase 3 — Publish the product with an Enable Product rule

This phase publishes the imported virtual product so it is sold online, by creating a new Enable Product rule or adding the product 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 product should be available.
  4. Set Order classes to the order classes the product should be sold on.
  5. Set Stores to the stores the product applies to, using Specific rather than All where possible.
  6. In the Products field, select every building block created for this product — the virtual product, the size container, all size products, the Add, Change, and Remove containers, and all Add and Remove condiment products. All imported menu blocks must be enabled as Products for the menu to build correctly.
  7. Save the rule. 

To add the product to an existing Enable Product rule instead, open that rule, add these building blocks in its Products field, and save.

Additional Options

These are optional and not required for the Product with size and configuration to be sold:

  • Allow quick add without opening the configurator — remove the fo:services:tagconventions:disable:display:quickadd tag from the virtual product so the customer is not forced into the configuration view and can add the product directly from the category view. See Tag combinations.
  • Allow multiple of the same add-on (Incrementer) — add the fo:web:display:incrementer tag to a priced Add condiment product so the customer can add several portions of it, for example ten extra bacon. Use this only on condiments that add a cost. See Tag combinations.
  • Different prices per order type — add multiple Price record entries to a size product, each on a specific menu level (Price record - Active On Level), to charge different prices for different order types such as Eat In, Take away, and Delivery. Separate price records can also apply different VAT. To apply a different tax class to a whole order type rather than to a single product, request that configuration from Future Ordering; see 2. Configure EMC Enterprise level for the Future Ordering platform.
  • Schedule availability — restrict the product to certain times or days using Schedule start/stop and Schedule days on the Enable Product rule. See Rule Manager.
  • Cross-sell the product — promote the product in a cross-sell step with an Upsell Product rule. An upsell rule does not publish the product, so the Enable Product rule is still required. See Rule Manager.

Expected Outcome

The Product with size and configuration is published and appears in the Frontend menu with a size choice and the add, change, and remove options for each size, for the stores, order classes, and period the Enable Product rule covers. The customer can choose a size, customise it, and add it to the Basket, with the price reflecting the chosen size and any priced additions.

Verify the Configuration

Confirm the Product with size and configuration 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 product, open it, and confirm the size choice appears and that selecting each size shows the add, change, and remove options.
  3. Select a size, customise it with an add, a change, and a remove, then confirm the size price plus any additions are reflected when the product is added to the Basket. 

If a size or option does not appear, see the Troubleshooting section below.

Known Limitations

  • The configuration containers must be linked from each size product, not from the virtual product, so that every size carries its own add, change, and remove options.

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

Troubleshooting

Common issues and how to resolve them:

  • The product does not appear online — confirm an Enable Product rule selects the virtual product and all its building blocks, and that the product's category and store are published with Enable Category and Enable Store rules. A product is only visible where all three apply.
  • The product is hidden even though it is enabled — a Disable Product rule with a higher Index overrides the Enable Product rule. Check for a conflicting Disable Product rule and adjust its Index or remove it.
  • A size appears without its configuration options — the Add, Change, and Remove containers are linked from the virtual product instead of from each size product. Confirm each size product links to the configuration containers.
  • Import failures — see Known Menu import issues and solutions and Existing menu issues.