Oracle Simphony integration

Simphony Onboarding Checklist

Use this checklist with your Simphony administrator to prepare Transaction Services Gen 2, authorize the integration, map your POS records, and validate a complete order before launch.

Complete the revenue-center steps for every venue you plan to offer in Club Order App.
1

Confirm STS Gen 2 availability

Make sure Oracle has enabled the services your environment needs.

  • Confirm your Simphony environment supports Transaction Services Gen 2.If it is not provisioned, contact your Oracle representative or hosting team before continuing.
  • Identify the organization short name and every location and revenue center to connect.Club Order App scopes requests using the organization short name, location reference, and revenue-center reference.
  • Confirm the cloud API endpoint and authentication endpoint for your environment.Keep the connection details supplied by Oracle or included with the API-account setup email.
2

Enable each revenue center

Checks cannot be routed until the revenue center and POS API client are ready.

  • Enable option 74 for the revenue center.In EMC, open Setup → RVC Parameters → Options, select 74 - Enable Simphony Transaction Services Gen 2, and save.
  • Configure or verify a workstation with type 3 - POS API Client.Enable the STS Gen 2 Location API and Cloud API options, and point its Service Host ID at the host running CAPS.
  • Select the correct default order type, order devices, printers, and revenue centers.Confirm online orders route and print where the operating team expects them.
  • Verify the workstation is online and the STS connection is active.For resiliency, Oracle recommends two eligible POS API client workstations when more than one is available.
3

Create integration access

Use dedicated credentials and grant only the locations and actions required.

  • Grant an administrator the Manage Simphony Transaction Services privilege.This exposes API Accounts in Reporting and Analytics so the integration account can be created.
  • Create a dedicated API account with type Simphony Transaction Services.Authorize all required locations, select client scope BOTH, record the client ID and username, and complete the password setup from the account email.
  • Create or select a dedicated check employee.Assign a role/job that can begin and create checks, add menu items, use the configured pickup and delivery order types, apply the selected tender, and apply the delivery service charge when used. Record the employee object number.
  • Enable zero-total and negative-value check creation for the check employee role.In the role's Operations → Transactions privileges, enable 38 - Authorize/Perform Closing of Checks with a Zero Balance and 39 - Authorize/Perform Closing of Checks with a Negative Balance. These permissions support tip-later and refund checks.
  • Store credentials securely.Do not send the API password in ordinary email or place it in shared onboarding notes.
The API account authenticates the integration. The check employee reference is a separate Simphony employee used on every check Club Order App creates.
4

Prepare the POS records

Record the object numbers exactly as configured in Simphony.

  • Create or select a dedicated external-paid tender.It should represent payments already collected by Club Order App/Stripe and be available to the check employee in each target revenue center. Record its name and numeric ID.
  • Record the pickup and delivery order-type references.Ensure both order types are enabled for the target revenue centers, employee role, workstation, taxes, and order-device routing.
  • Verify menus, prices, taxes, condiment rules, and availability are current.Club Order App imports these definitions and uses them to calculate and create checks.
  • If used Create or select the delivery service charge.Configure its tax behavior in Simphony and record the numeric service-charge ID. If it is percentage-based, configure the venue in Club Order App with the same delivery-fee percentage.
  • Tip later Create a dedicated menu item with a price of $0.00.This placeholder item is used when Club Order App creates a separate Simphony check for a tip added after the original order.
  • Refunds Create or select the refund-return menu item.Record the numeric menu-item IDs for both the $0 tip item and the refund-return item.
5

Connect Club Order App

Enter the credentials, choose revenue centers, and control what is imported.

  • Enter the Auth URL, API URL, organization short name, OIDC client ID, API username, and API password.
  • Enter the external-paid tender name and ID, pickup and delivery order-type refs, and check employee ref.
  • If used Enable the delivery service charge and enter its ID.When the Simphony service charge is a percentage, set the venue's delivery fee to the identical percentage in Club Order App.
  • Save the configuration and confirm that an authentication token is acquired.
  • Open Revenue Centers, verify each connection status, and activate only the revenue centers you want to import.
  • Create venues from the selected revenue centers.Review each generated venue’s name, schedule, fulfillment options, fees, taxes, and delivery configuration.
  • Add the tip and return menu-item IDs on the Simphony Integration page.Open Revenue Centers, select the revenue center's settings, expand Tip and Return Menu Item IDs, and enter the $0 tip item ID and refund-return item ID.
  • Review each revenue center’s remaining import settings.Configure enabled categories, SLUs, sync tags, and condiment or menu-item exclusions before the production sync.
6

Validate before launch

Test the exact payment and fulfillment paths guests will use.

  • Run a catalog sync and compare representative items.Check prices, taxes, categories, required condiments, optional condiments, combos, and unavailable items.
  • Place a test pickup order and a test delivery order.Confirm each check is created in the correct organization, location, and revenue center with the expected employee, order type, items, totals, tender, and guest reference.
  • Confirm routing and printing.Verify kitchen/bar order devices receive the order and staff can identify it as a Club Order App check.
  • Test the tip-later and refund workflows when enabled.Confirm the $0 tip item can create and close its separate check, the return item can create a negative-value check, and accounting totals reconcile.
  • Change an item’s availability in Simphony and confirm it updates in Club Order App.
  • Document support ownership.Record who owns Simphony credentials, menu changes, tender/order-type changes, failed-check alerts, and after-hours escalation.
Do not enable production ordering until a paid test order creates a valid Simphony check and reaches the intended order devices.