Duve can post the upsells your guests buy straight to the guest's folio in OPERA Cloud (OHIP), so your front desk and accounting team see every upsell in the PMS without manual entry. To make this work, you create a transaction code in OPERA for each type of upsell and then add that code to the matching upsell in Duve. This article walks you through both sides of the setup and explains how Duve posts each order.
You can choose, per upsell, whether Duve syncs it to OHIP as a regular charge (covered here) or as a package. To sync upsells as packages, see Sync Upsells back to OHIP as 'Packages'.
Quick navigation:
- Use cases and supported upsells
- Before you start
- How to set it up
- How orders are posted to OHIP
- Troubleshooting
- Restrictions & Limitations
- Tips & Tricks
- FAQs
- Related articles
Use cases and supported upsells
- Late check-out and early check-in: Post the fee to the guest's folio as soon as the guest pays, so the front desk does not need to add it manually.
- Room upgrades: Record upgrade revenue under its own transaction code for cleaner revenue reporting.
- Custom products and menu items: Post breakfast, parking, welcome amenities, or F&B orders under the right revenue group in OPERA.
- Spa treatments: Post spa bookings made through Duve to the folio under a dedicated spa code.
- Accurate reporting: Use OPERA subgroups so every upsell lands in the correct revenue bucket in your financial reports.
Before you start
- Your property must already be connected to Duve through the OHIP integration. If it is not, see OHIP | How to Connect.
- You need admin access in OPERA Cloud to create transaction codes.
- Decide which upsells should share a code and which need their own. You can use one code for several upsells or a separate code for each.
How to set it up
Step 1: Create the transaction code in OPERA Cloud
Follow Oracle's process to create a transaction code for each upsell type you want to sync:
-
In OPERA Cloud, go to Admin > Financial > Transaction Management > Transaction Codes.
- Click New on the far right to create a new transaction code.
- Enter the code in the Code field.
-
Set the group and subgroup you want this code to report under.
- Leave the price fields empty. Duve sends the price with every posting.
- Make sure the Manual Posting checkbox is selected.
- Save the transaction code.
Note: Write down the exact code you created. You will paste it into Duve in the next step.
Step 2: Add the transaction code to your upsells in Duve
Each upsell has a Billing identifier field. This is where the OPERA transaction code goes. Duve does not post an upsell to OHIP if this field is empty.
Custom product and spa upsells
- Open the upsell you want to sync.
- Scroll to Advanced options (optional).
-
Enter the transaction code in the Billing identifier field.
- Save the upsell.
Menu product upsells
- Open the menu product.
- Go to its advanced options.
-
Enter the transaction code in the Billing identifier field.
- Save.
Smart Tools: Early check-in, late check-out, and room upgrade
- Open the settings page for the Smart Tool (Early Check-In, Late Check-Out, or Room Upgrade).
- Go to the advanced options.
-
Enter the transaction code in the Billing identifier field.
- Save.
About the second field: Billing identifier (Transaction Code)
On OHIP accounts, upsells also show a second field called Billing identifier (Transaction Code). You only need it when Sync as package is turned on for that upsell. In that case:
- Billing identifier holds the OPERA package code.
- Billing identifier (Transaction Code) holds the transaction code Duve uses if the order cannot be added as a package and is posted as a regular charge instead (for example, when the order is pushed after the guest's last night).
If you are syncing the upsell as a regular charge, leave Sync as package off and fill in only the Billing identifier.
Step 3: Review the OHIP integration posting settings
A few settings on your OHIP integration control where and how upsell charges are posted. Ask your Duve contact or review them in your OHIP integration settings:
- Cashier ID: The OPERA cashier ID Duve posts charges and payments under. This is required.
- Guest folio window number: The folio window charges are posted to. If left empty, Duve uses window 1.
- Push additional charges to folio: When on, extra charges added to a menu or custom product order are posted together with the main charge. When off, only the base price is posted.
- Shift packages charges from checkout day: When on, a charge that would land on the checkout day is moved to the last night of the stay, so the PMS night audit captures it.
- Visa, Mastercard, Amex, Diners, Maestro, and other card identifiers: The OPERA payment method codes Duve uses when it posts the guest's card payment for the upsell.
How orders are posted to OHIP
Host experience
- When a guest buys an upsell and the payment is captured, Duve posts it to the guest's folio under the transaction code you set.
- If the guest is already checked in, Duve posts the upsell as a charge on the folio.
- If the guest is not yet checked in, Duve adds it as a fixed charge on the reservation. Late check-out is scheduled for the check-out date, early check-in for the arrival date, and other upsells for the arrival date or the date the guest selected.
- If the guest paid by card, Duve also posts the payment to the folio, so the upsell is balanced. Before check-in, this is posted as a deposit.
- Duve adds a comment on the reservation with the order details.
- If an order is canceled, Duve posts a reversing (negative) charge. If the guest paid by card and canceled the order themselves, Duve also posts the refund.
Troubleshooting
- The upsell did not appear in OPERA: Check that the Billing identifier field is filled in for that upsell. Duve skips orders that do not have one.
- OPERA rejects the posting: Make sure the code in Duve matches the OPERA transaction code exactly, and that Manual Posting is selected on the code in OPERA.
- An order is still missing: It may still be waiting for host approval or payment capture. Duve only posts it once it is approved and captured. For more help, see How to troubleshoot Orders sync to PMS.
Restrictions & Limitations
- Only these upsell types are posted to OHIP: early check-in, late check-out, room upgrade, custom products, menu products, and spa products.
- Orders that need host approval, or whose payment is still on hold, are not posted until they are approved and captured.
- Orders with a total of zero (for example, fully comped orders) are not posted as charges, because OPERA does not accept zero-amount postings.
- If a guest cancels a cash or "add to bill" order and no refund is due, the original charge stays in OPERA and Duve adds a cancellation comment only.
- Payment for Stay is not posted with a transaction code. It is posted as a payment using the card identifiers from your OHIP integration settings. See How to sync Payment for Stay back to OHIP.
Tips & Tricks
- Create separate transaction codes for upsell categories you want to report on separately (for example, F&B, spa, and room upgrades).
- Use OPERA subgroups to group upsell revenue in your reports without creating too many codes.
- Test the setup with one upsell on a test reservation before rolling it out to all upsells.
FAQs
Q: Can I use the same transaction code for more than one upsell?
A: Yes. You can enter the same code in the Billing identifier field of several upsells.
Q: What happens if I leave the Billing identifier field empty?
A: Duve does not post that upsell to OHIP. The order still works in Duve, but nothing is sent to the folio.
Q: Do I need to set a price on the transaction code in OPERA?
A: No. Leave the price fields empty. Duve sends the order amount with each posting.
Q: Should I fill in both Billing identifier fields?
A: Only if Sync as package is turned on for the upsell. Otherwise, fill in Billing identifier only.
Q: Where do I set the transaction code for Payment for Stay?
A: You do not need one for OHIP. Payment for Stay is posted to OHIP as a payment using the card identifiers in your OHIP integration settings. See [How to sync Payment for Stay back to OHIP].
Q: What happens in OPERA when a guest cancels an upsell?
A: Duve posts a reversing charge for the same amount. If the guest paid by card and canceled the order, Duve also posts the refund.
Related articles:
How to troubleshoot Orders sync to PMS
Comments
0 comments
Article is closed for comments.