Insights
What should a hotel system alert you about before someone asks?
Most hotel systems answer questions. Few of them ask. The storeroom runs out because nobody looked at the stock report; the tentative group block expires because nobody checked the date; the purchase order sits unapproved because the approver did not know. This is how WinX turns those into alerts that arrive on their own, and what else the system does at night while nobody is watching.
The pain: the report existed, nobody opened it
Everything is visible, nothing is noticed. The low-stock report, the ageing report, the no-show list: all there, all accurate, all unread until the problem has already cost money.
The approver did not know. A purchase order waits two days for a signature from someone who never opened the purchasing screen. The delivery is late, then the stock-out, then the emergency buy at retail price.
Nobody watches the watchers. The nightly job that posts room charges failed on Tuesday. Everyone found out on Friday, from the accountant.
Why it happens: systems built to be queried, not to speak
Reporting is the easy part of software; deciding what matters is the hard part, so most systems leave it to the user. If the person whose job it is to check does not check, the system is silent. And the scheduled jobs that keep a hotel system honest, posting, rolling, snapshotting, are usually invisible until one of them stops.
How WinX does it: rules, audiences, and a watchdog
- A notification centre with rule types. Each property switches on the rules it wants: low stock, negative stock, purchase orders awaiting approval, purchase orders with overdue delivery, supplier payments due, unsettled POS bills, no-shows, tentative reservations about to expire, check-outs long past due, dirty rooms, and an email queue falling behind. Nothing is on until someone turns it on.
- The right audience, not everyone. A rule names who hears about it: the purchasing manager for approvals, front office for no-shows, housekeeping for dirty rooms, finance for payables. Alerts land in the WinX bell and by email.
- Tentative bookings count themselves down. A reminder, then a yellow flag two days before the option expires, then orange on the last day. The group block does not quietly lapse.
- A watchdog on the jobs. Every scheduled job reports a heartbeat. If a job that used to succeed goes quiet, WinX raises an alert about the silence, so a failed posting is known the same night, not on Friday.
- The database checks its own pulse. A ping every couple of minutes records latency and, if the primary stops answering, fails over to the backup host and clears the fault flags when it returns.
- Hardware tells you when it is down. Self-service kiosks send a heartbeat; a fleet monitor shows them live and emails on every state change, every minute if needed. Cash-machine refunds that nobody claims expire on their own.
What runs by itself every day
Alerts are the visible half. The other half is the list of jobs a WinX property never has to remember:
- Room charges and taxes posted to every in-house folio at the date roll, with no night-audit batch to run; no-shows processed with a deposit check; room statuses rolled.
- Abandoned booking-engine holds released after their timeout, so the room goes back on sale.
- A nightly on-the-books snapshot, 365 days ahead, which is what the booking pace and pickup reports compare against.
- Fixed-asset depreciation and other recurring journals posted; the consolidated ledger balanced for rounding; a monthly general-ledger snapshot rebuilt for the last thirteen months.
- Recurring invoices raised and emailed as PDF, with the e-invoice reference where the country requires it.
- A daily integrity check on paid ticket sales, so a sale that did not finish writing is found and reprinted rather than lost.
- Public holidays for the property's country loaded into the calendar; PABX extensions kept in sync; the email queue drained and retried.
- Very large reports built in the background month by month and delivered as a file, so a year of BIR forms does not freeze anyone's screen.
Where it earns its keep
At Manila Ocean Park and Hotel H2O, kiosks and cash machines on a park with thousands of guests a day are the front line; a kiosk that goes offline at 10 a.m. is a queue by 10:05, which is why the fleet reports every minute. At Petronas Pengerang, more than 1,000 rooms of charges post every night without a person pressing a button, and the watchdog is the person who would notice if they did not.
Common questions
- What can WinX alert me about automatically?
- Rule types include low and negative stock, purchase orders awaiting approval and purchase orders with overdue delivery, supplier payments due, unsettled POS bills, no-shows, tentative reservations about to expire, check-outs long past due, dirty rooms and an email queue backlog. Each property switches on the rules it wants and chooses who receives them, in the WinX bell and by email.
- Are the alerts on by default?
- No. A property starts with no notification rules active and enables the ones that matter to it, with an audience for each. That keeps the bell useful rather than noisy.
- What happens if a scheduled job fails overnight?
- Every job reports a heartbeat and a watchdog raises an alert when a job that used to succeed goes quiet, so a failed posting is known the same night rather than discovered days later from the accounts.
- Does WinX monitor its own database and hardware?
- Yes. A database ping every couple of minutes records latency and fails over to the backup host if the primary stops answering. Self-service kiosks send heartbeats to a fleet monitor that emails on every state change.
- What runs by itself every night?
- Room charge and tax posting at the date roll, no-show processing, room-status roll, release of abandoned web-booking holds, the on-the-books snapshot for pace reports, recurring journals and depreciation, the monthly GL snapshot, recurring invoices, the ticket-sale integrity check, holiday calendar updates and the email queue.
Tell us which three things you most often find out too late. We show the rules that would have told you.
Request a WinX demo