The problem isn't missing data, it's that it doesn't reconcile
The POS shows one figure, the payment gateway another, the OTA settles at thirty days and the partner hotel sends its own count at the end of the month. Consolidating that by hand eats hours and produces a number nobody fully trusts — the worst possible combination when deciding on pricing or fleet investment.
What the dashboard shows
- Revenue by source: front desk, website, WhatsApp, OTAs and partners
- Bookings recovered by chase mode, kept separate from the rest
- Revenue by product and by time slot, so you can see which hour and which activity actually pay
- Base-to-base comparison on the same metrics over the same period
- Fleet utilisation and underused craft
The closing that does itself
- Official register filled in from the contract and boarding data
- Review request sent automatically after the activity
- Customer base with full history, for retention and seasonal campaigns
- Accounting export of revenue by base and period
These are the tasks always left for the end of the season and, precisely because of that, almost never done.
Frequently asked questions
Can I migrate my booking history?+
Yes. Customers, historical bookings and configuration are migrated from Excel, Google Calendar or other software as part of the implementation.
Can I see each base's data separately?+
Yes. Every metric can be viewed grouped or filtered by base, and bases can be compared against each other over the same period.
Is the official register it produces valid for an inspection?+
It is filled in from the contract and boarding data, in the format the applicable regulation requires, and it stays archived and exportable.
Can I export it for my accountant?+
Yes. Revenue exports by base and period in standard accounting formats.