Opera PMS Spa Integration
Look up an in-house guest, post the spa charge to the Opera folio, apply a credit, and close night audit. One certified OHIP interface, supported by the same team that supports Paired Plus.
4 exciting reasons to use the Opera PMS spa integration
Room charges
Post a treatment, add-on, or retail sale to the guest folio in Opera Cloud. The spa ticket and the room charge stay in the same transaction.
Guest lookup
Find an in-house guest by name, reservation number, or room before the service is closed. The front desk does not have to read the folio back.
Room credits
Reverse or adjust a spa charge on the same folio when a service is voided or comped. Finance does not need a side spreadsheet.
Night audit
Spa revenue is already on the Opera folio when the night audit runs. Credits, voids, and departmental codes close with the rest of the property.
Trusted by Leading Hotels & Resorts
Opera Cloud hotels
Opera PMS spa integration at Shutters and Casa del Mar
Shutters on the Beach and Casa del Mar run Paired Plus with Opera Cloud. Spa staff look up the in-house guest, post the charge to the Opera folio through OHIP, and night audit closes without a second payment or a call to the front desk.
- In-house guest lookup by name, reservation, or room
- Spa treatments and retail posted to the Opera folio
- Credits and voids on the same room charge
- Night audit closed without a spa spreadsheet
- Supported by the Paired Plus team, not a handoff to Oracle
ONE Spa at Shutters on the Beach
Opera PMS spa integration support
Room-charge and night-audit questions stay with Paired Plus. The support team is in California and Oregon, knows the Opera folio posting through OHIP, and does not send you to Oracle for a spa ticket that failed to post. Button labels can be renamed in the software for the wording your desk uses.
Opera PMS spa integration FAQ
These are the questions resort IT and spa managers ask before connecting Paired Plus to Opera Cloud through OHIP: what posts to the folio, how a guest is found, and who supports a charge that does not post.
Paired Plus connects the spa desk to Opera Cloud so an in-house guest can be charged without a second card. The Opera PMS spa integration sends the closed ticket to the Opera folio through OHIP: a treatment, an add-on, or a retail sale, using the transaction code the property already uses. A void or a comp returns as a credit on that same folio. Staff do not retype the sale into Opera, and the front desk does not have to read the room number back over the phone. If a charge does not post, the Paired Plus team in California and Oregon works it with the spa instead of sending the ticket to Oracle.
Before a ticket is closed, the desk searches the in-house list and confirms the person is still checked in. The Opera OHIP spa integration matches on name, reservation number, or room, then shows the folio the charge will hit. That check matters when two guests share a surname, a group block has several rooms, or the guest has already checked out. A match stops the sale from posting to the wrong room. The front desk does not have to stay on the phone while the therapist is finishing the service. Lookup is the first step of the charge, not a separate report the accounting team runs the next morning.
Opera Cloud keeps the reservation, the room, and the folio. Paired Plus keeps the book. Opera spa software is the spa side of that split: the appointment book, the provider schedule, retail, packages, and the ticket that becomes the room charge. A hotel can run one spa or several outlets from the same login, with reporting by location. Button labels can be renamed for the wording that desk uses. Opera is not replaced, and the spa is not asked to live inside a room-reservation screen that was built for the front desk.
The desk stays in Paired Plus. The Opera Cloud spa interface is the lookup and posting layer behind the ticket, not a second program the therapist has to open. Staff find the guest, confirm the room, close the service, and send the amount to the folio through OHIP. A retail add-on on the same ticket posts with the service. If the guest wants to pay by card instead of charging the room, the sale stays in the spa system and never goes to Opera. The interface is there for in-house room charges, not for every transaction the spa takes.
The desk confirms the guest is in-house, then closes the ticket. Opera room charges post to that folio as a treatment, an add-on, or retail, with the transaction code the property already uses for the spa. A package split can post as more than one line if accounting wants service and retail separated. Staff do not retype the amount into Opera Cloud, and the front desk does not take a second card. A charge that fails stays with Paired Plus support, with the room, the ticket number, and the time of the sale.
Spa revenue needs to be on the folio before the property closes the day. The Opera night audit reads those posted charges, credits, and voids with the rest of the outlets, using the transaction codes set up for the spa. A ticket still open in Paired Plus is not on the folio yet, so the desk should close or void it before audit starts. Once it has posted, accounting can see the spa total inside Opera Cloud instead of importing a separate file. That is the point of the connection: one set of numbers when the night is closed.