Overview
To run Juno Hospitality Suite with Oracle OPERA Cloud, OPERA v5 or Oracle Simphony, your hotel needs a configured Oracle environment, a stable internet connection, reliable WiFi wherever payments are taken, and a named contact to work with 934 during onboarding. Most hotels already have these in place. This article lists the minimum requirements, recommended payment terminals for each area of the hotel and the checks to complete before go-live.
Applies to
| Product | Juno Hospitality Suite |
| Integration | Oracle OPERA Cloud; Oracle OPERA v5 (on-premise); Oracle Simphony |
| Audience | Hotel project leads, IT teams and System Integrators preparing for Juno onboarding |
What you'll achieve
After reviewing this article, you'll know what your hotel needs in place before 934 can activate Juno with your Oracle OPERA or Simphony environment, and which checks confirm you're ready for go-live.
Minimum requirements
- Oracle OPERA Cloud, OPERA v5 or Simphony, configured. Your Oracle environment must be set up and ready for Juno activation. No minimum version is required.
- Stable internet connection. A reliable business connection, available throughout service hours.
- Reliable WiFi where payments take place. Strong coverage in every area where guests pay.
- An assigned hotel contact. One named person to coordinate onboarding with 934.
- Staff available for testing. Team members who can run test payments during go-live.
- 934 Support contact details shared with the relevant hotel teams.
Recommended payment terminals
The right terminal depends on how payments work in each area of your hotel. Front desk, pay-at-table and order-at-table workflows may need different devices. Your 934 team will help confirm the right terminal during onboarding.
| Area | Typical use | Recommended terminal |
|---|---|---|
| Front Desk | Guest check-in, check-out, deposits and other front-office payments | PAX A920 or A920 Pro |
| Food & Beverage | Pay-at-table: mobile service at the table and high-volume outlets | PAX A77 or A50 |
| Back Office | Fixed payment positions for back-office workflows | PAX A35 |
Connectivity
- Stable internet: a reliable business connection, available during service hours.
- Reliable WiFi: strong coverage wherever guests pay, including restaurants, bars and other outlets using mobile terminals.
- Dedicated operational WiFi (preferred): where possible, keep payment traffic on a separate network from guest WiFi.
Your hotel IT team or System Integrator can confirm WiFi readiness before deployment.
Working with your System Integrator
Many Oracle hospitality environments are configured and supported by the hotel's appointed System Integrator (SI). Juno works alongside this setup. Your SI will usually:
- configure and validate the required Oracle OPERA or Simphony settings;
- share the required environment details with 934 to support onboarding;
- support testing before Go Live
934 will tell you and your SI what information is needed and guide you through onboarding.
Go-live checklist
Complete these checks before going live:
- Your Oracle OPERA or Simphony environment is ready for Juno activation.
- WiFi coverage has been tested in every payment area.
- Test payments have been completed successfully.
- Receipts are working.
- Staff have been trained.
- The first transaction has been completed.
Expected result
Once your Oracle setup is complete and every item on the checklist above has been confirmed, your hotel is ready for go-live with Juno.
Need more help?
For detailed deployment and integration guidance, contact your Customer Success Manager. Include your hotel name and which Oracle system you use (OPERA Cloud, OPERA v5 or Simphony).
Comments
0 comments
Article is closed for comments.