Index
What is this integration?
The Ulyses Cloud integration connects Golfmanager with the Ulyses Cloud PMS (hotel management system). It lets staff, from the Golfmanager POS, charge a guest's purchases directly to their room.
The amount is no longer collected at the till and is instead added to the hotel account, so the guest pays it all together at check-out.
A PMS (Property Management System) is the program the hotel uses to manage rooms, reservations and each guest's account. Ulyses Cloud is one of those systems. This integration acts as a bridge between your POS and the guest's account in the hotel.
What problem does it solve?
The guest does not pay on the spot: they consume at the golf, the shop or the bar and everything accumulates in their hotel account.
Avoids double handling: the charge travels to the PMS instantly.
Improves the customer experience at resorts that combine hotel and golf.
Leaves a trace of every operation: charges and refunds are recorded.
Which systems does it connect and in which direction does the data flow?
It connects the Golfmanager POS with the Ulyses Cloud PMS (through its cloud service), in real time:
Golfmanager sends the charge (or the refund) to the guest's room/account.
Ulyses Cloud responds whether the operation was carried out, and Golfmanager records it.
What information is exchanged?
Information | Direction | What for |
Room search (registered guest) | Golfmanager ← Ulyses Cloud | Locate the guest's occupied room |
Charge: amount, concept (product code) and quantity | Golfmanager → Ulyses Cloud | Add the charge to the guest's account |
Confirmation / refund | Golfmanager ↔ Ulyses Cloud | Confirm or reverse the charge |
Prerequisites (before activating the integration)
The hotel uses the Ulyses Cloud PMS and has its service enabled.
Have the Ulyses module installed in your Golfmanager, together with the POS and billing modules.
The Ulyses Cloud credentials (URL, user, password) and the chain, property and property code identifiers.
The Ulyses article/department code for each product that will be charged to a room.
System management permissions to configure.
How to set it up (step by step)
Step 1 — Connection data
Log in to Golfmanager with an administrator user and go to Ulysses > Settings.
Choose the mode: leave production mode disabled to use the test environment, or enable it for production.
Enter the Ulyses Cloud URL, user and password (the password is stored encrypted).
Enter the hotel's chain (Chain), property (Property) and property code.
There is a set of fields for testing and another for production; fill in the one matching the active mode.
Save the changes.
Step 2 — Products
Go to the record of each product that can be charged to a room.
Enter its Ulysses Code (the corresponding article or department in Ulyses).
Save the changes.
⚠️ Recommendation: start in test mode with the test credentials, validate a sample charge, and enable production mode only when everything works. In production the charges are real on the guest's account.
Explanation of each field
Below is a description of each field in the integration: where it is, what it means, its impact on the system, and a usage example (what happens when it is used and how the system behaves).
A) Settings (Ulysses > Settings)
1. Production mode
Description: indicates whether the production or the test environment is used.
Impact on the system: it determines which credential set is used (the production or the test one).
Usage example: you leave it disabled while testing and enable it when going live.
What happens when it is used: enabled, the charges are real on the guest's account; disabled, they go to the test environment.
System behavior: the system uses the active mode's data on each charge.
2. URL
Description: the address of the Ulyses Cloud service.
Impact on the system: essential. It is where searches and charges are sent.
Usage example: you enter the URL the hotel/Tesipro provides.
What happens when it is used: Golfmanager connects to that address.
System behavior: if it is missing, "Ulyses: no URL configured" appears.
3. User and 4. Password
Description: the credentials to access the Ulyses service. The password is stored encrypted.
Impact on the system: essential to authenticate.
Usage example: you copy them from the data the hotel gives you.
What happens when it is used: each operation authenticates with them.
System behavior: if they are missing, "Ulyses: no user configured" or "Ulyses: no password set" appears.
5. Chain, 6. Property and 7. Property code
Description: they identify the specific hotel within Ulyses (the chain, the property and its code).
Impact on the system: essential. They state which hotel the charges belong to.
Usage example: you enter the identifiers the hotel provides.
What happens when it is used: the charges are applied to the guest's account in that hotel.
System behavior: if they are missing, "Ulyses: no chain configured" or "Ulyses: no property configured" appears.
ℹ️ There is an equivalent set of fields for testing (URL, user, password, chain, property and property code marked as "(Test)"). The system uses one or the other depending on whether production mode is enabled.
B) On the product
Field name: Ulysses Code.
Description: the Ulyses article or department the product corresponds to.
Impact on the system: it is mandatory in order to charge the product to a room.
Usage example: on a soft drink you set the beverages department code.
What happens when it is used: the charge reaches Ulyses with that concept.
System behavior: if it is missing, on charging "The product '…' doesn't have an Ulyses code" appears.
C) On the sale
Paid with Ulysses: indicates that the sale was successfully charged to a room. Behavior: it is read-only; it is marked when the charge completes.
Ulysses Room: the room the sale was charged to. Behavior: it is read-only; it is filled in with the charge and printed on the receipt/invoice.
D) On the transactions
Each operation sent to Ulyses is recorded with: the associated sale and invoice, the Ulysses ID (returned identifier), the operation (charge or refund), the room number, whether it was successful or not, and the detail of the request, the response and the error. Behavior: it is read-only and serves to diagnose.
How to use it day to day
Charge a sale to the room
In the POS, add the products to the cart as usual.
As the payment method, select "Room charge (Ulysses)".
Search for the guest's room by its number and select it (only occupied rooms appear).
Confirm. The charge is sent to Ulyses Cloud and the sale is marked paid; the room number is printed on the receipt/invoice.
ℹ️ The room charge does not allow split payment: the full amount is charged to the guest's account.
Refunds
To refund, cancel or return the charge from Golfmanager: the system sends Ulyses Cloud the reversal of the amount (with negative quantities). The refund must be done via Ulyses and all sales refunded together must be from the same room.
Reviewing the transactions
In Ulysses > Transactions you will see all the operations sent to Ulyses Cloud (charges and refunds), with the amount, the room, whether they were successful or failed and the error detail if any. It is the first screen to check when a charge has not been completed.
Limitations to keep in mind
It depends on the hotel: Ulyses Cloud must be reachable. If its service does not respond, rooms cannot be charged.
The guest must be registered (with check-in): only occupied rooms are offered.
Each product needs its Ulysses Code; without it, the sale cannot be charged.
The room charge does not allow split payment.
Refunds are done via Ulyses and must be from the same room.
The amounts are sent in euros (EUR).
Do not mix test mode with the real one: in production the charges are real on the guest's account.
Frequently asked questions
It gives a connection error with Ulyses Cloud.
Data is usually missing or wrong. Notices like "Ulyses: no URL configured / no user configured / no password set / no chain configured / no property configured" appear. Review the URL, the user, the password, the chain, the property and the property code of the active mode.
"No Ulysses service found" appears (error 404).
The URL or the path is not correct, or the service is unavailable. Check the URL and that the Ulyses service is active.
When searching for the room none appears.
Only occupied rooms are shown. If the guest has no check-in or the number does not match, it will not appear. Verify with reception that the guest is registered.
"The product '…' doesn't have an Ulyses code" appears.
That product has no Ulysses Code assigned. Go to its record, enter the Ulyses article/department code and try again.
"The amount to be collected does not match" appears.
The POS total does not match the sum of the sale lines. Review the cart and the amounts before charging again.
It does not let me split the payment.
The room charge does not allow split payment ("Split payment is not allowed"). Charge the full amount to the room.
I cannot refund a charge.
Refunds of room charges must be done via Ulyses; with another payment method "Charges cannot be returned to Ulyses with other forms of payment" appears. Also, a sale without a room cannot be refunded this way, and all sales refunded together must be from the same room.
The charge is rejected.
Ulyses did not accept the operation. Review the detail in Transactions: the guest may have checked out or the account may be closed.
A test charged for real (or vice versa).
Production mode was not as it should be. Check Production mode and that the active mode's credentials are the correct ones.
Where do I review what has been sent to Ulyses?
In Ulysses > Transactions. Each charge and refund is recorded with the room, the Ulysses ID, whether it was successful and the error detail if any.
What identifies the guest?
The room number (the occupied room). No card or membership number is needed.
In which currency are the amounts charged?
In euros (EUR).
Recommended best practices
Test first in test mode with the test credentials before enabling production.
Gather the credentials (URL, user, password, chain, property and property code) with the hotel's IT team.
Assign the Ulysses Code to all the products that will be charged to a room.
Always confirm the room and the guest before charging.
On a failed charge, check Transactions first: the error detail usually indicates the cause.