Guide Overview
Welcome to the Toast–Opera Cloud integration setup guide. This document outlines the steps required to configure your integration through DataHub, enabling room charge posting.
To ensure a smooth onboarding experience and successful deployment, please review and complete each section of this guide in the order presented. Following these instructions carefully will help ensure that all systems are configured correctly and operating as expected.
1. Request the Toast integration
To start the setup process, you must first request the “Toast to Opera Cloud by Omniboost” integration via the Toast Marketplace.
This step is required for two reasons:
It allows Omniboost to receive the necessary credentials and information from Toast
It automatically triggers the onboarding process on the Omniboost side
You will automatically receive an email from Omniboost DataHub with instructions guiding you through the next required steps.
ℹ️ Note If you have not done so already, you can find more information on how to submit the request in the Toast Marketplace here: How to request the Toast integration in the Toast Marketplace? |
2. Integration Setup Requirements (Opera Cloud)
Before you can begin setting up the integration, please ensure the following steps are completed.
Standard Transaction Codes
Standard Transaction Codes
To map revenue from Toast to Opera Cloud, you must create transaction codes in Opera Cloud. Depending on the level of detail you want in your financial reporting, you can choose one of the following setup options:
| Maximum Detail Create transaction codes based on:
E.g. " |
| Detailled Create transaction codes based on:
E.g. " |
| Limited Detail Create transaction codes based on:
E.g. " |
| Create one unified transaction code for all Toast revenue. E.g. " |
Use this link to learn how to create a transaction code: Configuring Transaction Codes
❗Important “Manual posting’’ must be enabled for every transaction code. If this is not enabled the transaction code will not be loaded in to the DataHub. |
Tax transaction codes
Tax transaction codes
To map tax from Toast to Opera Cloud, you must create transaction codes in Opera Cloud. Depending on the level of detail you want in your financial reporting, you can choose one of the following setup options:
| Detailled
Create a transaction code for every tax percentage used in Toast. E.g. " |
| Simplified
Create one general transaction code for tax mapping. E.g. " |
Additional transaction codes within Opera Cloud
Additional transaction codes within Opera Cloud
In addition to your standard transaction codes in Opera Cloud, you must create several additional transaction codes to properly handle fallback postings and non-revenue transactions from Toast POS.
These transaction codes ensure that all transactions are correctly recorded, even in cases where standard mappings are missing, instead of turning to errors.
A transaction code called 'Fallback Toast'
A transaction code called 'Service Charge Toast'
A transaction code called 'Gratuity Toast'
Use this link to learn how to create a transaction code: Configuring Transaction Codes
3. Accessing DataHub
To access DataHub, follow these steps:
Obtain Login Credentials:
After requesting the integration in the Toast Marketplace you will receive your person login credentials via email. If you haven't received them, kindly request them from your designated contact at Omniboost or send an email to 'pos-support@omniboost.com'
Navigate to DataHub:
Open your web browser and go to https://datahub.omniboost.io/
Enter Your Credentials:
Use the email and password provided Omniboost
Select “Remember Me”:
Check the
Remember mebox to save your login details for future access.
Click “Login”:
Press the
Loginbutton to proceed.
4. Setting Up Two-Factor Authentication (2FA)
When logging into Omniboost DataHub for the first time, you will be prompted to set up Two-Factor Authentication (2FA).
This step is required and must be completed carefully, as you will need your 2FA device each time you log in going forward.
Download a 2FA Application
Install a 2FA application on your smartphone, such as: Google Authenticator, Microsoft Authenticator
Scan the QR Code
Open your 2FA app
Select the option to add a new account
Scan the QR code displayed on the DataHub screen. This will link your account and start generating authentication codes.
Generate and Enter 2FA Code
Your 2FA app will generate a new code every 30 seconds
Enter the current code into the DataHub screen to verify your setup
Save Recovery Codes
Carefully store the recovery codes shown on the screen
These codes allow you to regain access if you lose your phone or 2FA app
❗Important You will need your 2FA app every time you log in to DataHub. |
5. Starting the Integration Setup
Access the Next Screen: After successfully creating your user and setting up Two-Factor Authentication (2FA), you will be directed to the next screen.
Click “Start Setup”: On this screen, click the
Start Setupbutton to begin configuring the integration.
6. Configuring POS Settings
Configuring the 'On Room Payment Type'
Select the payment type that represents room charges (typically named
Room Charge)This ensures that these transactions are recognized and sent to Opera Cloud as revenue only (not as payments)
If you do not see the Room Charge option in the drop down menu, please do send an email to 'pos-support@omniboost.com'.
Fill in the 'Tip Name'
Define the description used for tip-related transaction codes in Opera Cloud.
Enter a name such as:
Toast Tip,Gratuity
This name will be used as a description for the corresponding transaction code.
Enable or disable 'Use Meal Periods'
Choose whether you want to include meal periods (e.g., breakfast, lunch, dinner) in your revenue mapping.
Please refer to the section “”Standard transaction codes
If you selected Option 1 - Maximum Detail, meal periods must be enabled and configured.
If you chose a less detailed setup (Options 2–4), enabling meal periods has no added value and should be left disabled.
When enabled:
You can map revenue in more detail, allowing for more detailed reporting in Opera Cloud
Example: "
Restaurant food breakfast", "Restaurant food lunch", "Restaurant beverage breakfast", "Restaurant beverage lunch"
When disabled:
Mapping will be simpler and less work
Example: "Restaurant food", "Restaurant beverage"
💡Tip Only enable meal periods if you plan to map all additional fields and mapping pages required for this higher level of reporting. It increases setup complexity but allows for more granular insights in Opera Cloud. |
Enable or disable 'Split Tax'
Enable the Split Tax checkbox if you want to split out the different taxes. Otherwise, the system will use the total tax rate.
Configure the 'Set Meal Periods' (only if 'Use Meal Periods' is enabled)
If you have enabled “Use Meal Periods”, you must define your meal periods. Transactions will be assigned to a meal period based on the opening time of the receipt in Toast, and will be mapped accordingly in Opera Cloud.
In order to do so please complete the next steps:
Select a meal period from the dropdown menu
Enter a name for the meal period (e.g.,
Breakfast,Lunch,Dinner)Set the start time and end time
Meal - must cover the full 24 hours of the day
There may be no gaps or overlaps between meal periods
Each meal period must start immediately when the previous one ends
Repeat these steps for each meal period you want to configure.
❗Important Incorrect configuration will result in mapping issues. |
7. Configuring PMS Settings
On top of the PMS settings page, you will find two tabs:
Default settings
Settings per revenue center
Complete the Default Settings first, following the instructions below. These settings will automatically apply to all revenue centers and meal periods.
If needed, you can customize the settings for specific revenue centers by overriding the default configuration in the Settings per Revenue Center tab.
Default Codes
These settings define where transactions are posted when no specific mapping is applied; for example, when a new sales category is added in Toast but not yet mapped in Omniboost DataHub, or when a new sales item is created in Toast that is not linked to an existing sales category.
Default Analysis Code → Select:
Fallback ToastUsed for revenue items without a mapping
Default Payment Code → Select:
Fallback ToastUsed for payments without a mapping
ℹ️ Note These fallback categories act as a safety net. If mappings are missing or incorrect, transactions will be posted here. |
Select Folio Window Number
The Folio Window Number is set to 1 by default. You can adjust this value using the arrow controls (up/down) on the right-hand side.
Enable or disable 'VAT/TAX Inc'
Enable if prices from Toast include VAT (e.g., Europe). Leave unchecked in tax-exclusive countries (e.g., US, Canada).
Tip and Service Charge Configuration
Configure how tips and service charges are posted in Opera Cloud:
Service Charge Code →
Service Charge ToastService Charge With VAT Code →
Service Charge ToastTip Code →
Gratuity Toast
Enter the Receipt Description
Defines how receipts from Toast POS will appear in folios within Oracle Opera Cloud (e.g., Restaurant Charge).
This description will be visible to hotel staff and guests, so we recommend using a clear and recognizable name that reflects the origin of the charge.
Once all fields are completed:
Click
Next Stepto continue
8. Configuring the Mapping
In this step, you will map all sales categories, service charges, and payment methods from Toast to Opera Cloud within Omniboost DataHub.
Navigation Tabs
At the top of the screen, you will see different tabs (e.g., Pool, Bar, Patio, Dining Room, Adjustment, etc.).
Each tab represents a (Toast) revenue center, meal period, or adjustment type
The first page acts as the default mapping for all tabs that are not configured
The “Adjustment” tab acts as the default for all adjustment-related tabs
Mapping additional tabs is not mandatory, however, configuring them allows for more detailed and accurate reporting in Opera Cloud
Any additional tab you configure will override the default mapping for that specific revenue center, meal period, or adjustment type
ℹ️ Note When using meal periods, you do not need to map the revenue center pages without a meal period assigned. All transactions are assigned to a meal period based on the receipt opening time, so the default revenue center pages without a meal period will not be used. |
Categories
All Toast sales categories are listed on the left-hand side of the screen. Map each Sales Category to the corresponding Transaction Code in Opera Cloud.
For each Sales Category (e.g., Beer, Food, Liquor, Wine):
Select the preferred Opera Cloud Transaction Code
You can configure this in four different ways, depending on the level of detail you want in your Opera Cloud reports (see section standard transaction codes)
Helpful Links:
Learn how to create a transaction code: Configuring Transaction Codes
Learn how to create Sales Categories in Toast: Configure Sales Categories
Both transaction codes and sales categories are fetched in real time. After creating new ones, simply refresh the page and they will appear in the dropdown options.
Service Charges
All Toast service charges are listed on the left-hand side of the screen. Map all these service charges to the correct Opera Cloud service charge transaction codes.
Examples:
Delivery FeeGratuity 10% / 18% / 20%
For each:
Select the corresponding Opera Cloud service charge transaction code.
Payment Methods
All Toast payment methods are listed at the bottom of the screen. Since this integration processes room charges only, direct payments are not posted to Opera Cloud. Map all payment methods to Toast Fallback Transaction code.
Final Step:
Click Save Mapping at the bottom of the screen. Make sure all required fields are completed, otherwise the page will not save.
After clicking Save Mapping & Continue, the integration setup is complete.
❗Important Full Revenue Push (direct payments) is not enabled automatically: you must email 📧 to request activation.pos-support@omniboost.com |
The integration is now ready for Room Charge transactions, and you can run a test using the Room Charge payment method in Toast (see testing section below).
Once Full Revenue Push is activated by our team, all direct payments will be synced to Opera Cloud every 15 minutes.
❗Important If you have multiple locations in Toast (e.g., Market, Rooftop), you must configure the integration for each location separately by following the same steps. You can switch between locations using the dropdown menu in the top-left corner of Omniboost DataHub. |
9. Testing the Integration
You can now test the integration using a Toast POS handheld or terminal with a checked-in room in Opera Cloud.
How to run a test:
Create a new receipt on a Toast handheld or terminal
Select the payment method Room Charge
Note: this may be located under “More payment options”
Search for and select the correct room number
Close the receipt
Verify in Opera Cloud:
Check the Logs page in Omniboost DataHub
Check if the transaction appears correctly in Opera Cloud
Test Adjustment (Recommended)
Void the receipt in Toast
Learn how in the following article: Void Items, Payments, and Checks
Verify that the transaction is also voided or adjusted correctly in Opera Cloud
All transactions and potential errors can be reviewed in the logs within Omniboost DataHub, accessible from the left-hand menu.
❗Important If you need to modify a receipt in Toast after the room charge has already been sent to Opera Cloud, you must void the entire receipt, make the necessary changes, and create a new room charge. Updating an existing receipt will not be reflected correctly in Opera Cloud. |
Support
Support Contact
If you encounter issues with the DataHub configuration or Data:
Omniboost Support 📧 pos-support@omniboost.ioIf you encounter issues with your Toast configuration.
Toast Support 📧 integrations-support@toasttab.comIf you encounter issues with your Opera configuration you need to open a Ticket via their support portal.
Opera cloud Customer Support Portal