How to configure a Product with size for Oracle STSG2

Pontus Ridderström
  • Updated
Follow

Overview

A Product with size is a menu product offered in several sizes, where each size is a real product with its own price — for example, fries in Small, Medium, and Large. The customer chooses one size before adding the product to the Basket. Configuration spans three phases: the size products, a size container, and a virtual product 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, 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 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.

Phase 1 — Build the building blocks in Oracle Simphony EMC

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

  1. In Oracle Simphony EMC, create a real product for each size. For each size product, set the following datafields:
    • Consumer Item Name — the size's display name (example: Future fries small).
    • FO_UniqueIdentifiers — the size's Future Ordering identifier (example: 2001 - Future fries small).
    • Price record - Price — the size's price (example: 2.00), with Price record - Active On Level set to 0 - All level.
    • Images — attach the product image.
    • Repeat these datafields for every size (example: Medium 2.79, Large 3.79).
  2. Create the size container menu item, and set the following datafields:
    • FO_IsContainer — checked.
    • Consumer Item Name — the container name (example: Future Fries Size Container).
    • FO_UniqueIdentifiers — the container's Future Ordering identifier (example: 10000 - Future Fries Size Container).
    • FO_LinkedToDefinition — the Sequence numbers of the size products (example: 2001,2002,2003).
    • FO_SelectedItem — the Sequence number of the default size (example: 2002).
    • FO_SelectionOptions — {"max":1,"min":1} so the customer chooses exactly one size.
    • Price record — not required on a container.
  3. Create the virtual product menu item, and set the following datafields:
    • FO_VirtualProduct — checked.
    • Consumer Item Name — the product's display name (example: Future Fries).
    • FO_UniqueIdentifiers — the product's Future Ordering identifier (example: 2100 - Future Fries).
    • 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:web:display:quickadd, so the size choice is presented as soon as the customer clicks the product; see Tag combinations.
  4. 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, and all size 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 to be sold:

  • 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 is published and appears in the Frontend menu with a size choice for the stores, order classes, and period the Enable Product rule covers. When the customer selects a size, the price updates to that size and the product can be added to the Basket.

Verify the Configuration

Confirm the Product with size is live and orderable.

  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 all sizes are shown with the correct prices and that the default size is preselected.
  3. Select a size and add the product to the Basket, then confirm the basket line shows the chosen size and price. [SCREENSHOT: the Product with size shown in the Frontend with the size selector and a size added to the Basket]

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

Known Limitations

  • Each size is a real product with its own price, not a condiment. Price differences between sizes come from each size product's own price record, not from a surcharge on the parent.

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, the size container, and the size products, 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 is missing or the product fails to build on import — confirm every size product has a valid price record. See Known Menu import issues and solutions and Existing menu issues.