O

Oracle Simphony

Active

Cloud-based restaurant point of sale integration for catalog synchronization and direct order injection from POS Hub.

25-40 minutes

Hard

Overview

Oracle Simphony is a cloud-based restaurant management platform. The POS Hub integration imports the selected Simphony menu and supported tax configuration, then creates marketplace orders as checks in the configured location and revenue center.

The integration supports standard menu items, categories, condiment groups, modifiers, prices, images, availability, fulfillment order types, tenders, service charges, tips, and discounts. It is designed for orders that originate in POS Hub; it does not import Simphony-originated orders or receive later check-status changes from Simphony.

⚠️Important current limitation

Combo meals are detected during catalog synchronization but their root products are kept offline because combo check injection is not yet supported. Do not manually publish those products.

Supported Features

Catalog Sync

✅

CategoriesSynchronizes menu categories and organizational structure

Supported

⚠️

Products & VariantsEach standard menu-item definition is imported as one POS Hub product with one price selected for the configured Catalog Menu Level. Combo meals are kept offline because combo order injection is not yet supported.

Partial

✅

Modifier GroupsSynchronizes modifier group structure

Supported

✅

ModifiersSyncs individual modifiers and options

Supported

✅

ImagesProduct and category image synchronization

Supported

❌

Nutritional InfoNutritional information and calorie data

Not Supported

⚠️

Dietary InfoAlcohol indicators are imported; other dietary and allergen information is not currently synchronized.

Partial

Order Integration

✅

Order InjectionDelivery, collection, and dine-in orders are created as checks in the configured Simphony revenue center.

Supported

❌

Receive POS OrdersSimphony-originated orders and subsequent check-status updates are not received by POS Hub.

Not Supported

Configuration

❌

Business HoursSynchronize standard operating hours

Not Supported

❌

Collection/Delivery HoursSeparate hours for pickup and delivery services

Not Supported

✅

Tax RatesSupported Simphony percentage, included-percentage, and surcharge tax rates are imported with the catalog.

Supported

❌

Special HoursHoliday and special event hours

Not Supported

Legend:✅ Supported|⚠️ Partial|❌ Not Supported|🔄 Coming Soon

Onboarding

Prerequisites

Before you begin, ensure you have:

An active Oracle Simphony account with administrative access

Access to the Simphony Reporting and Analytics portal

A Simphony user with Transaction Services API access

Your Simphony organization short name and base64-encoded client ID

The authentication and API server URLs for your Simphony environment

An active POS Hub location

Setup Guide

1

Install Oracle Simphony

1-2 min

Install the integration on your POS Hub location

1. Open the required location in POS Hub
2. Select APPS, then Point of Sale
3. Find Oracle Simphony and select Install

2

Connect your Simphony account

2-5 min

Authenticate POS Hub with your Simphony environment

1. Enter your Simphony username and current password
2. Enter the organization short name and base64-encoded client ID
3. Enter the authentication server and API server as HTTPS origins without paths or query parameters
4. Select Connect and wait for the credentials to be verified

Use the endpoints assigned to your Simphony environment. POS Hub uses the password to sign in but does not save it in the integration configuration.

3

Select the location and revenue center

2-3 min

Choose where POS Hub orders will be created

1. Select the Simphony location that corresponds to the POS Hub location
2. Select the revenue center that should receive orders
3. Select Test POS Connection and confirm that the workstation reports a connected status
4. Enter an employee ID for that location and revenue center
5. Wait for POS Hub to confirm that the employee ID is valid

Changing the connected Simphony account or environment clears dependent location and order mappings so they cannot be reused accidentally.

4

Select the menu and catalog menu level

1-2 min

Choose the Simphony menu and the price level to import into POS Hub

1. Select the menu associated with the chosen revenue center
2. Confirm that it contains the items and condiment groups required for online ordering
3. Leave Catalog Menu Level at 0 for the default all-level pricing, or enter the Simphony menu level used for this online channel
4. Optionally enter case-sensitive Tags to Include and Tags to Exclude; press Enter after each tag
5. Confirm that every definition intended for sale has a price for the selected level or an all-level price

A menu must be selected before the catalog can be synchronized. One menu level is applied to the entire imported catalog; changing it requires another synchronization.

5

Map order types

2-3 min

Map POS Hub fulfillment types to Simphony order types

1. Select the Simphony order type for delivery orders
2. Select the Simphony order type for collection orders
3. Select the Simphony order type for dine-in orders

All three order-type mappings are required before the integration can be saved.

6

Configure the tender and charges

3-5 min

Choose how payment, fees, tips, and discounts are sent to Simphony

1. Select the required POS Hub Order Tender
2. Select the default service charge for general fees
3. Select the service charges for delivery fees and driver tips
4. Optionally select the default Simphony discount type
5. Review the amount behavior shown for every selected tender, service charge, and discount

Percentage-based service charges and discounts are rejected. See Tender and charge behavior below before choosing preset definitions.

7

Save and synchronize

5-10 min

Validate the complete configuration and import the initial catalog

1. Select Save Progress after completing every required field
2. Select Sync Catalog to save the configuration and start a fresh catalog import
3. Wait for synchronization to finish and review its status, completion time, and any warnings
4. Select Close when the catalog is ready

8

Validate a first order

5-10 min

Confirm the live Simphony mappings before opening the location to traffic

1. Review the imported catalog in POS Hub and keep unavailable products offline
2. Send a low-value test order using one of the configured fulfillment types
3. Confirm that the check, items, tender, and applicable charges appear in the intended Simphony revenue center

ℹ️Secure authentication

Your Simphony password is used only to obtain access and refresh tokens and is not saved in the integration configuration. Tokens are held by the server and are never returned to the browser. If the password changes or the connection expires, reconnect the integration before continuing setup.

Catalog Synchronization

The selected menu controls which family groups, menu items, condiment groups, and condiments are imported. A synchronization also imports supported tax rates, images, alcohol indicators, and the current Simphony availability of menu items.

How Simphony products map to POS Hub

Simphony can expose several layers for what a customer sees as one item. POS Hub keeps the layers required to send an order back to the correct Simphony definition:

Simphony data	POS Hub behavior
Menu item	The parent item returned by the selected Simphony menu.
Definition	Each definition becomes a separate POS Hub product or modifier. Definitions commonly represent sellable versions such as Single and Double or Small and Large.
Price sequence	A definition can contain several price records. POS Hub selects one price sequence for the configured Catalog Menu Level; price sequences do not create additional products.
Menu level	A number from 0 to 8 used to select pricing across the whole catalog. Level 0 is the default and means an all-level price.

When an item has multiple definitions, POS Hub uses each definition's customer-facing name. When a definition name is missing, it falls back to the parent menu-item or condiment name. POS Hub does not add labels such as (Definition 1) or (Price 2), so configure distinct definition names in Simphony whenever customers need to tell the entries apart.

ℹ️Definitions create products; price sequences select prices

A product is created for each definition, not for every price sequence. The selected definition and price sequence are retained internally and sent back to Simphony during order injection.

Catalog Menu Level and price selection

Use Catalog Menu Level to choose the Simphony pricing context for the imported catalog:

• Use level 0 unless the Simphony menu deliberately uses another level for online ordering.
• For a selected level from 1 to 8, both that level and all-level (0) prices are eligible.
• Among eligible prices, Simphony price-sequence priority is preserved: the lowest price sequence is selected.
• If a definition has no price for the selected level and no all-level price, POS Hub falls back to its lowest price sequence so the definition can still be imported. Review these fallback prices before publishing.
• The same selection rules apply to products and modifiers.

POS Hub imports one selected Simphony menu into one catalog. Menu levels do not create separate POS Hub menus or duplicate a product for every price. To use a different price level, change Catalog Menu Level, save, and synchronize the catalog again.

Tag filtering

The Simphony app provides two optional free-entry fields. Type the tag exactly as it appears in Simphony and press Enter to add it:

• Tags to Include is an allow-list. When it is empty, products and modifiers do not need an inclusion tag. When it contains values, an item or its exact definition must have at least one matching tag to be online.
• Tags to Exclude is a deny-list. Any matching tag keeps the product or modifier offline. Online Disabled is the default for new or previously unconfigured installations.
• Matching is case-sensitive: Online Enabled and online enabled are different tags.
• If an item matches both lists, exclusion takes precedence.

Filters inspect tags on both the parent menu item or condiment and its exact definition. Items that do not pass the filter remain in the POS Hub catalog with showOnline disabled, which keeps them available for review without publishing them to customer channels.

Product content and availability

For each definition, POS Hub imports the best available customer-facing name, description, first image, price, tax references, alcohol indicator, supported nutrition and allergen data, availability, and matching barcode data exposed by Simphony. It reads tags to apply online filtering and supported dietary or spiciness indicators; general Simphony tags are not exposed as separate POS Hub catalog fields. Content varies according to what has been configured on that exact definition.

Barcodes are matched to the exact menu item, definition, and selected price sequence when those references are supplied by Simphony. A barcode attached to a different definition or price sequence is not copied onto the product.

During synchronization, POS Hub:

• Stores the exact Simphony item definition and price sequence required for order injection.
• Imports one product or modifier per definition and one price per definition for the configured Catalog Menu Level.
• Applies the configured case-sensitive include and exclude tags, and keeps filtered or unavailable items offline.
• Keeps unsupported combo root items offline and reports a warning rather than failing the entire import.
• Records the synchronization result, completion time, and any warnings so they remain visible when onboarding is reopened.

Catalog synchronization is a snapshot. Simphony menu and availability changes are not pushed to POS Hub in real time, so run Sync Catalog again after changing menu definitions, prices, availability, or online tags.

⚠️Synchronize after upgrading an existing installation

Products imported by an older version may not contain the exact item-definition and price references now required for safe order injection. Run a fresh catalog synchronization before sending more orders.

Tender and Charge Behavior

The POS Hub Order Tender is required. Simphony amount handling depends on how each selected definition is configured:

Simphony definition	Supported behavior
Payment tender	POS Hub sends the marketplace payment total to Simphony.
Service-total tender	POS Hub sends a zero total so Simphony closes the check using its service total behavior.
Open-amount service charge or discount	A definition with a configured value of zero receives the order's fee or discount amount.
Preset-amount service charge or discount	The order amount must exactly match the preset Simphony value.
Percentage-based service charge or discount	Not supported; POS Hub rejects the order instead of sending an ambiguous amount.

Select mappings that match the fees produced by your marketplaces. A preset delivery fee, tip, general charge, or discount cannot safely represent arbitrary order amounts.

Order Processing

• Delivery, collection, and dine-in orders use their corresponding required Simphony order-type mapping.
• Scheduled orders include the expected fulfillment time when one is supplied by POS Hub.
• Taxes are not manually added to the check; Simphony calculates them from the synchronized menu definitions and its own tax configuration.
• A successful create-check response marks the POS Hub order as accepted. A definitive Simphony error marks it as rejected, while transient failures remain retryable.
• Order retries use a persisted Simphony check reference and duplicate detection to avoid creating a second check for the same POS Hub order. Correlation data is retained for seven days.
• Later Simphony check-status updates are not synchronized back to POS Hub. Simphony subscriptions and order-notification handling are disabled for this integration.

Configuration Reference

Connection details

Field	Description
Username	The username of a Simphony user with Transaction Services API access.
Password	The user's current password. It is used to connect and is not saved by POS Hub.
Organization short name	The short name or code registered for the organization in Simphony.
Client ID	The base64-encoded client ID issued for the Simphony environment.
Authentication server	The HTTPS origin of the Simphony identity server, without a path, query, or fragment.
API server	The HTTPS origin of the Simphony Transaction Services API, without a path, query, or fragment.

Only approved Oracle Simphony HTTPS endpoints are accepted. The authentication and API servers must belong to the intended Simphony environment.

Location details

Field	Description
Location	The Simphony location associated with this POS Hub location.
Revenue center	The revenue center where POS Hub orders will be created.
Test POS Connection	A read-only check of the last workstation connection status reported by Simphony.
Employee ID	An active employee at the selected location and revenue center. POS Hub validates it before setup can continue.
Menu	The menu imported when catalog synchronization runs.
Catalog Menu Level	The Simphony pricing level applied to every product and modifier during synchronization. Accepts 0 to 8 and defaults to 0.
Tags to Include	Optional case-sensitive allow-list. If populated, a product or modifier must match at least one tag to be online.
Tags to Exclude	Optional case-sensitive deny-list. A match keeps the product or modifier offline and takes precedence over the include list. Defaults to Online Disabled.

Order mappings

Field	Description
Delivery order type	The Simphony order type used for delivery orders. Required.
Collection order type	The Simphony order type used for pickup or collection orders. Required.
Dine-in order type	The Simphony order type used for dine-in orders. Required.
POS Hub Order Tender	The tender applied to orders paid through a connected marketplace. Required.
Default service charge	The optional fallback Simphony service charge for general order fees.
Delivery service charge	The optional service charge used for delivery fees.
Tip service charge	The optional service charge used for driver tips and gratuities.
Default discount type	The optional Simphony discount applied to POS Hub order discounts.

Go-Live Checklist

Before enabling real customer orders:

1. Reconnect if the Simphony password, account, client ID, or endpoint has changed.
2. Re-save the complete configuration and confirm that employee validation passes.
3. Run Test POS Connection for the selected location and revenue center.
4. Run a fresh catalog synchronization and review the saved status and every warning.
5. Review definition names, tag-filter results, product and modifier prices, barcodes, and availability in POS Hub; keep combo and unavailable products offline.
6. Send a low-value test order for each fulfillment type you intend to offer.
7. Confirm the Simphony check contains the expected items, tender, charges, discount, and scheduled time.

⚠️Keep configuration references valid

If menu, employee, order-type, tender, service-charge, or discount references are removed or replaced in Simphony, update the POS Hub configuration and synchronize the catalog before processing more orders.

Troubleshooting

If the problem continues, contact POS Hub support with the POS Hub location ID, POS Hub order ID when applicable, and the approximate time of the failed connection, synchronization, or order.