Connecting ResDiary to Oracle Simphony requires specific system access and configuration details to be in place. This guide covers the onboarding process, outlines the prerequisites, and details the information required to complete the integration successfully.
Prepare your requirements
Before moving forward with the integration steps ensure you have completed the following pre requisites:
You have an active ResDiary account with admin access.
You are using Oracle Simphony POS version 19.2 or newer.
You have access to Oracle’s Transaction Services Gen2 STSG2 API.
Request your integration
Complete this form with the details of your venue and select Simphony from the EPOS options. Once the form has been completed reach out to our support team to flag your request.
Configure your Simphony API access
Please ensure the following details are in order:
Your Simphony POS is configured to allow external API access.
Work with your Oracle representative to:
Enable STSG2 API for front of house transactions.
Confirm access to reporting and analytics.
Obtain your API credentials: Client ID, Secret, Endpoint URL.
Share relevant details with us
Once you have completed the form and flagged us about this integration, please do share the following details with our support team:
Field | Description |
API Account username | Username for Simphony API access. |
API Account password | Password for Simphony API access. |
Enterprise Short Name | Identifier for your Simphony enterprise. |
ClientID | OAuth client ID for authentication. |
Authentication URL | URL used to authenticate API requests. |
STSGen2 API Base URL | Base URL for Simphony Transaction Services Gen2. |
Location Reference | Simphony location identifier. |
Revenue Centre IDs | List of revenue centre's to map with ResDiary. |
Employee ID | ID of the employee to associate actions with, can be a dedicated “ResDiary” user. Note the name of this user will appear on printed bills |
Order Type | Name of the order type used to open checks. |
Check Tender | Name of the check tender used to open checks. |
Enable your integration
Once all required credentials and configuration details have been provided, our team will activate the Simphony POS integration for your venue. Validate that the connection to Simphony is successful by testing the integration as follows:
Test | Expected Result |
Create a test booking in ResDiary for the current time, then update the booking to fully seated. | A corresponding check should open on Simphony. |
Add items to the check on Simphony. | Spend should update on corresponding booking in ResDiary. |
Close your check. | Related booking in ResDiary should also close. |
Open a new check on a table in Simphony that is available in ResDiary. | A corresponding walk in reservation opens on ResDiary. |
Complete your mapping
To ensure accurate synchronisation between ResDiary and Simphony POS, table numbers must match exactly in both systems. Each Revenue Centre, RVC, in Simphony must use table numbers that correspond directly to the tables configured in the linked ResDiary account, and table numbers must be unique across all RVCs connected to that account. For example, if ResDiary Table 12 is mapped to the Simphony RVC Main Dining, Simphony must also have a Table 12 in that RVC, and the same table number cannot exist in another RVC linked to the same ResDiary account.
Update your meal statuses
⚠️ Important : Meal status updates only occur when menu items in Simphony use recognised category tags. A menu item is treated as a match if any supported tag is found in a tag group, family group, or SLU, screen lookup category.
As the guest journey progresses, our integration will real time update the following events on your booking history if they are tagged as follows on Simphony:
Drinks: Drink or Drinks.
Starters: Starter, Starters, Appetisers or Appetizers.
Mains: Main, Mains or Main Courses.
Desserts: Dessert or Desserts.
Paid.
Closed.
📌 Note: In order to determine the latest course present in the meal we follow the below:
If only drinks exist: Meal status is set to Drinks.
If a starter is present: Meal status is set to Starters.
If a main is present: Meal Status is set to Mains.