The same night, sold twice
Availability lives in one file, the channels hold their own copy, and the gap between them is a guest standing at your desk with a confirmation you cannot honour.
Property management system
Every room, every night,
in one place.
HotelForge runs the front desk, the rate calendar, the channels you sell on, housekeeping and the bill — for hotels small enough to know every guest by name and busy enough to lose track of them.
Built for UK hotels. Prices in GBP, VAT handled, dates in DD/MM/YYYY.
Why hotels change
The spreadsheet stops scaling at about thirty rooms.
Not because it breaks. Because the cost of keeping it honest starts to eat the evening.
Rates that nobody can explain
A price set in March for a bank holiday in August, changed twice, remembered by one person. When they are on leave, the room sells for the wrong number.
A bill assembled from memory
Bar tabs on a notepad, the late checkout agreed verbally, the parking that never got charged. Revenue leaves the building politely.
What is inside
Eight modules. One property, one login, one bill.
Nothing here is an add-on and nothing is priced separately. A twelve-room guest house gets the same system as a sixty-room hotel.
- 01
Reservations & calendar
The booking chart your team works from all day: drag to create, drag to move, and dates that cannot be double-sold.
Read more - 02
Rates & distribution
Set a price once and push it to every channel you sell on, with a limit on how many rooms each night may take.
Read more - 03
Direct booking & payments
Booking pages on your own domain, taking card payment into your own Stripe account, with no commission to us.
Read more - 04
Housekeeping
A daily board of what needs cleaning and why, assigned to named staff, showing them only what they need to know.
Read more - 05
Folio & payments
A running bill per stay: extras, charges, payments and balance, with VAT derived per line rather than guessed.
Read more - 06
Reporting
Sixteen reports covering occupancy, revenue, channels, cancellations and guests — each one downloadable as a spreadsheet or PDF.
Read more - 07
Guest email & alerts
Confirmations, reminders and thank-you emails sent once and only once, plus a notification bell for the things staff must not miss.
Read more - 08
Roles, audit & compliance
Who may do what, a permanent record of who did it, and the UK GDPR obligations handled as product features rather than promises.
Read more
A day on the desk
What the system does while you work.
Four moments from an ordinary Tuesday, in the order they happen.
- 07:40
The board is already set
Arrivals, departures and stayovers are counted before anyone clocks in. Rooms that were dirty last night are on the housekeeping board with a name against them.
- 11:15
A channel booking lands
A reservation arrives from an OTA, takes a confirmation code, drops the room out of inventory everywhere at once, and appears on the calendar. Nobody re-typed it.
- 16:00
A guest changes their mind
Two nights become four. The dates move, both the old and the new nights are locked while the change is written, and the confirmation code stays the same.
- 22:30
The day closes itself
Unpaid web bookings that never completed payment are released back into inventory. Tomorrow opens with availability that is true.
Built for one market
A UK system, not a translation of one.
We serve independent hotels in the United Kingdom. That decision shows up everywhere in the product.
- Pounds, VAT and DD/MM
- Money is stored VAT-inclusive because that is how a UK guest reads a price. The tax is derived per line, at the rate that line actually carries.
- Card payments through Stripe
- Each hotel connects its own Stripe account, so the money moves from the guest to you without passing through us. SCA and 3-D Secure are handled by the gateway.
- UK GDPR taken literally
- Guest data can be anonymised on request without shredding your accounts, and the audit trail records who changed what without ever storing the value they changed.
- Your own domain
- Your booking pages, your confirmation emails and your payment receipts carry your hotel name — not ours.
Underneath
The parts you only notice when they fail.
- 01A database of your own
- Your reservations, guests and rates sit in their own database. There is no shared table another hotel could be read out of.
- 02Permissions the server enforces
- The panel hides what a role may not do, and the server refuses it as well. A hidden button is never the thing keeping you safe.
- 03An audit trail without the values
- Every change records who, what and when — the field that moved, never the contents. A guest you erase cannot survive inside the log.
- 04Money that needs two roles
- Anyone may add a charge; only an owner or a manager may cancel one. The split is enforced in the route, not in a training day.
See it with your own rooms in it.
Send us a rate sheet and a room list. We will load them and walk you through a real Tuesday on your property, not a demo dataset.