Integrating Oracle Simphony and Opera with a digital ordering solution

Simphony and Opera: you know them, you live with them

If your hotel is part of a group or chain, chances are you run Oracle MICROS Simphony for your POS and Oracle Opera for guest and room management. They're the industry standard — and for good reason: they handle everything from order-taking to guest folio posting.

But you know as well as we do: these are powerful tools with real depth of configuration. Every hotel has its own setup. Your Revenue Centers, your menus, your pricing rules, your payment methods — everything is calibrated to your property. And that's exactly why adding a digital layer on top can't be done haphazardly.

What happens when integration is done poorly

You may have already tried a digital ordering solution. And maybe it didn't work as expected. Here's what we hear from hotels that came to SKEAT after a bad first experience:

• "Hundreds of condiments synced on every single product — kitchen tickets were completely unreadable"
• "The menu wasn't guest-friendly at all — item names and modifiers were designed for staff use, not for a customer-facing experience"
• "Orders kept failing silently" — usually a workstation configuration issue that the previous vendor couldn't diagnose
• "No stock synchronization — guests could order items that were already sold out"
• "The automatic service charge didn't apply correctly"
• "F&B revenue wasn't posting back to the PMS"

These problems all come from the same place: a lack of deep Oracle expertise. Simphony's back-office (EMC) requires real menu engineering knowledge to build a digital ordering experience that works for guests — not just a raw data dump of your POS configuration.

What a real Simphony integration needs to handle

Your Simphony isn't just a product catalog with prices. It's a complete ecosystem:

• Multiple Revenue Centers: your restaurant, bar, pool bar and room service each have their own menus, prices and rules. The digital solution must distinguish them and route each order to the right place.
• Modifiers and options: "no ice", "medium rare", "extra guacamole" — all configured in Simphony. Your guest must see exactly the same options on their phone.
• Dynamic pricing: happy hour, weekend rates, loyalty member pricing — Simphony handles all of this. The ordering solution must apply the right price at the right time, not a static one.
• Kitchen printing: when a guest orders from their phone, the ticket must print in the kitchen exactly as if your waiter had entered it on the POS. Same format, same printer, same routing logic.
• Financial reconciliation: at the end of the day, digital orders must appear in your Simphony reports with the correct tender types and taxes. No gaps, no double entry.

And on the Opera side, it's a whole different story

Room posting — charging to the guest's room — is THE feature your guests expect for room service and the pool bar. On paper it's simple: the guest gives their name, room number, and signs.

In practice, there's a whole chain of checks that must work every single time:

• Verify the guest is actually in-house: the room is occupied, the name matches, the stay is active
• Respect hotel rules: some guests have a block on their folio (exhausted pre-payment, corporate restriction...). The solution must detect this before authorizing the charge.
• Handle spending limits: if your hotel caps the amount chargeable to a room, the solution needs to know
• Digital signature: the guest signs on their phone, and that signature is archived and linked to the posting. Essential for your audits.
• Post to the right place: the charge must land on the correct folio window, according to your internal rules

Get any one of these wrong, and you've got a guest dispute or an accounting problem.

Why not all solutions are equal

The reality is that every hotel has a different Oracle setup. Simphony versions vary (cloud, on-premise...), Opera configurations are never identical from one property to another, and network constraints change.

A solution built for standalone restaurants has never had to deal with this complexity. It might read a menu and send an order, but it doesn't know how to handle your multiple RVCs, your price levels, or your room posting with digital signature and NOPOST verification.

That's where the choice of partner makes all the difference.

SKEAT and Oracle: 8+ years of hands-on expertise

At SKEAT, we work with Simphony and Opera every single day and have been for over 8 years. We've deployed our solution in over 20 countries, across hundreds of hotels — from economy to luxury.

What sets us apart:

• We know Simphony inside out: multiple RVCs, menu classes, condiments, price levels, discount rules, tender types — we handle all of it natively. Every digital order prints in the kitchen like a server order and shows up in your reports with zero re-entry.
• We've mastered Opera: real-time guest authentication, posting status checks, spending limit enforcement, digital signature, posting to the correct window. Room posting works first time, every time.
• We're an Oracle partner: SKEAT is recognized within the Oracle Hospitality ecosystem. That means access to the latest developments, priority support, and Oracle-validated integrations.
• We handle integration end-to-end: when you deploy SKEAT, our technical team takes care of everything Oracle. Configuration, testing, validation — you don't need to become a Simphony expert. We already are.

On average, a hotel is live in 4 weeks.

What your teams will see day-to-day

• Digital orders print in the kitchen exactly like server orders — same ticket, same printer
• Your end-of-day reports are clean — everything reconciled, zero re-entry
• Room charging works without friction — the guest signs, the folio updates, done
• When you change your menu in Simphony, the digital menu updates automatically
• Your staff doesn't need to learn anything new — orders arrive like before, just faster and error-free