Setting up HubAmenity

Fifteen minutes, no training required

HubAmenity takes about fifteen minutes to set up, and your housekeeping team needs no training at all. This guide covers the whole thing.

Before you start, you need: an Apaleo account with the property you want to connect, permission to install applications on it, your item list with selling prices, and roughly what each item costs you.


Step 1 · Connect your property

The connection starts from a link we send you, and it happens entirely inside Apaleo. Once HubAmenity is listed in the Apaleo Store, you will also be able to start it from there.

Apaleo asks you to approve five permissions: reading reservations, reading your property setup, reading and managing folios, and keeping the connection alive between shifts. The first four are the data we request. The fifth is what lets the app keep working after a token expires mid-shift, so nobody on the floor is ever asked to sign in again.

We do not request access to guest personal data. Our application is configured to omit it, so guest names, addresses and contact details are never sent to us.

Step 2 · One property per connection

Each property is connected separately, with its own catalogue, team and reports. The separation is deliberate: consumption recorded in one hotel can never reach a folio in another.

If your Apaleo account gives access to more than one property, the connection will stop and point you to us. Group setup is something we do with you — write to support@hubamenity.com and we connect the properties together, in one session. It is not extra work for you and there is no extra charge for it.

Your rooms are imported automatically at this point. Nothing else is written to Apaleo.

Step 3 · Check your catalogue — and fill in what each item costs you

We start you with a suggested catalogue of common in-room items. Two fields matter:

The selling price is what the guest is charged. It comes from your catalogue, never from the phone in the housekeeper's hand — nobody on the floor can change a price, by design.

Your unit cost is what you pay for the item. This one is easy to skip and worth two minutes: it is what lets the report tell you what your complimentary items actually cost the hotel. Without it, that figure reads zero — which is not the same as free.

Mark as inactive anything you do not stock. Twelve to fifteen items is normal.

Step 4 · Add your housekeeping team

Add each person by the name you already call them. Each one receives a four-digit code.

There is no email address and no password for floor staff. This is deliberate: using HubAmenity should not make you collect more about your own employees than you already have.

Step 5 · Hand out the app

Send your team to app.hubamenity.com on any phone. They enter their code and see the floor. No installation, no app store, no device setup.

The flow is three taps: room, item, confirm. It works with no signal — entries are queued on the phone and posted when the connection returns. Restocking an empty room is a separate action that cannot become a charge.


What happens over the next 30 days

Your 30-Day Revenue Leakage Audit starts the moment your team records the first consumption. During those thirty days HubAmenity runs in shadow mode: it records everything exactly as it would in production and posts nothing to any folio. Your existing process keeps running, untouched.

Each night we compare what your team recorded against what actually reached the folio. At the end you get one figure in euros: the consumption nobody billed.

If that figure is small, do not subscribe. The audit exists to tell you whether you have a problem, not to sell you a product.

When the audit ends

Choose Activate HubAmenity and charges begin posting to folios. Pricing is €2.50 per room per month, with a €65 monthly minimum per property — twenty-six rooms. Annual billing is ten months for twelve. There is no setup fee, no training fee, no installation fee and no annual support fee.


Questions that come up

Can we run the audit on one property and live charging on another?

Yes. Each connected property is independent.

What happens when a consumption cannot be matched to a reservation?

It appears under Conflicts with the reason kept intact and three ways to resolve it. Nothing is discarded silently.

Does a charge ever get posted twice?

No. Each entry carries an identifier created on the phone that survives the offline queue and travels to Apaleo, so one consumption becomes exactly one charge.

Do you store anything about our guests?

No. There is no field for a guest name, email address or document anywhere in our database. Where a charge needs a destination, we hold the reservation identifier your PMS issued.

Where is our data?

In Frankfurt, Germany. Our privacy policy explains who can reach it and under what terms.

How do we disconnect?

From Apaleo, at any time. Ask us and we will delete or return your operational data.

Anything else: support@hubamenity.com