Prices drift apart
The early-bird discount in the booking tool differs from the PMS. Reception quotes the wrong price.
Rooms, rates, policies, partners and suppliers. Maintained once, valid everywhere. Every price adjustment and every new partnership flows into reservations, offers and invoices.
Each system has its own property information. With every price change, the housekeeping list and the PMS have to be updated too. Much of it stays out of date.
The early-bird discount in the booking tool differs from the PMS. Reception quotes the wrong price.
The pet policy is on paper at reception, but not in the website booking.
The room was renovated, but the system still says "no balcony".
A delivery note arrives from the wine merchant, but nobody knows any more who holds the terms and conditions document.
Prices, policies, room attributes and partner data are held centrally in felixUnity. Every change appears immediately in booking, reception and housekeeping. History and approvals are carried along.
Property, room, rate and partner data in clean blocks. Every change is versioned and valid from a specific date.
Property, room, rate and policy master data, once and centrally.
Price changes from date X. Existing bookings keep their old terms.
Website, booking tool and accounting draw from the same source.
Who changed what and when. Every adjustment is traceable.
Using your room structure and rate logic, we show how the multi-system problem disappears.