Connect Furama iPMS
Ask your Furama contact for all required connection details before you start. Setup takes about 10 minutes.
This guide helps you connect a property to Furama iPMS and confirm the connection is active.
Go to: Settings → Essentials → PMS Integration
Quick Reference
| Setting | Required | What It Controls |
|---|---|---|
| iPMS Base URL | Yes | Points AVA to the iPMS API and service path |
| Organisation Unit | Yes | Identifies your hotel in iPMS |
| Control Unit | No | Selects the unit used for catalogue lookups |
| User Code | Yes | Acquires the iPMS security token |
| Business User Code | No | Identifies the user on business requests |
| API Key | Yes | Authorises the iPMS connection |
Control Unit defaults to Organisation Unit. Business User Code defaults to User Code and preserves its letter case.
Before You Start
Confirm these requirements:
- Your property has been enabled for Furama iPMS
- You can edit Settings → Essentials
- You have the full iPMS API URL, including its service path
- You have the organisation unit, user code, and API key
- You know whether the property needs either optional value
Do not send the API key in screenshots or support messages. AVA masks the saved value after setup.
Connect the Property
- Go to Settings → Essentials.
- Open PMS Integration.
- Select Furama iPMS as the PMS provider.
- Enter the iPMS Base URL.
- Enter the Organisation Unit.
- Enter the User Code.
- Enter the API Key.
- Add the optional Control Unit when Furama provided a separate value.
- Add the optional Business User Code when it differs from User Code.
- Click Save PMS Settings.
✓ The page shows "Furama Integration Configured." ✓ The API key stays masked after the page reloads.
AVA selects the current Furama adapter automatically. You do not need to choose an adapter version.
Verify Daily Operations
After saving, verify the property with a safe test reservation.
-
Open Reservations.
-
Search for a known Furama booking.
-
Confirm its guest, room, stay dates, and status.
-
Open Rates & Availability and confirm expected rate plans appear.
-
Confirm room status appears in Housekeeping.
-
Complete your approved test check-in and check-out flow.
✓ AVA shows only the actions supported by the connected iPMS property.
Some AVA actions depend on the active PMS connection. Unsupported controls stay hidden or disabled instead of sending an unsafe request.
Update Connection Details
-
Return to Settings → Essentials → PMS Integration.
-
Update the non-secret fields you need to change.
-
Click Edit Secret only when replacing the API Key.
-
Enter the new API key.
-
Click Save PMS Settings.
✓ Leaving the masked API key unchanged keeps the current secret.
Troubleshooting
Furama iPMS is not listed
What you see: The provider list does not include Furama iPMS.
Fix:
- Refresh Settings → Essentials.
- Confirm you can edit PMS settings.
- Ask your AVA administrator to confirm the property rollout.
The settings do not save
What you see: "Failed to save PMS Integration" appears.
Fix:
- Complete every required field.
- Confirm the base URL includes the iPMS service path.
- Check the organisation unit and user code exactly.
- Re-enter the API key, then save again.
Catalogue data is missing
What you see: Rate plans, sources, or payment types do not appear.
Fix:
- Confirm the Control Unit with your Furama contact.
- Enter it when it differs from Organisation Unit.
- Click Save PMS Settings.
- Reload the affected AVA page.
Business requests are rejected
What you see: Reads work, but reservation updates fail.
Fix:
- Confirm the Business User Code.
- Preserve its exact letter case.
- Save the connection again.
- Retry with the approved test reservation.
Reservations do not appear
What you see: A known Furama booking is missing from Reservations.
Fix:
- Confirm the stay dates match the current search.
- Clear filters and search again.
- Check the booking in iPMS.
- Review PMS Connection Errors.
Still Stuck?
Contact success@vouch-technologies.com if:
- ❌ Furama stays remain missing after reconnecting
- ❌ Required fields are correct but saving still fails
- ❌ Supported check-in or check-out actions stay unavailable
Helpful to include:
- Property name
- Organisation Unit
- Time of the failed test
- Exact error message
- Screenshot with the API key hidden