Hospitality analytics for Dubai and the UAE
Hotels, serviced apartments, restaurant groups and caterers in the UAE share a problem: the property management system and the point of sale know what happened today, the finance system knows what happened last month, and the two are reconciled by a person with a spreadsheet. The daily flash and the month-end P&L disagree, and by the time they are reconciled the month is over.
A hospitality model puts the flash and the P&L on one set of definitions, so that occupancy, rate, covers and labour on Tuesday morning are the same measures that appear in the departmental P&L at month end. This page sets out those definitions for hotels and for F&B, the systems they come from, the seasonality the model has to understand, and a demo you can open.
Delivered remotely on GST hours, as a fixed price quoted before work starts, under the Power BI dashboards by industry UAE structure used across the site.
Hotels
A hotel dashboard has a well-established vocabulary, which helps; the difficulty is that each measure has two or three legitimate definitions and the PMS configuration silently picks one. The list below states the definition we start from and the choice that has to be made.
- Occupancy: rooms sold over rooms available, with out-of-order rooms removed from the denominator and complimentary rooms treated the way the PMS treats them, stated on the page.
- ADR and RevPAR: net of VAT, the tourism dirham and the municipality fee, with package components split out so a breakfast-inclusive rate does not inflate the room rate.
- TRevPAR and GOPPAR: total revenue and gross operating profit per available room, the second needing the month-end P&L and therefore the reconciliation this page is about.
- Channel mix and OTA commission: room nights and revenue by direct, OTA, wholesale and corporate, with commission attributed to the stay month at contract rates and trued up when the statement arrives.
- Pickup and pace: rooms on the books for a future period against the same lead time before the comparable period last year, event-aligned rather than calendar-aligned.
- Cancellation rate and length of stay: cancellations as a share of bookings by channel and lead time; nights per stay by segment.
- Guest nationality mix: from the PMS registration record, as a share of room nights, used for segment and channel planning.
- Tourism dirham and municipality fee reconciliation (explanatory): fees collected per room night by the PMS against the amounts remitted, by month, so the finance team can reconcile the two. The dashboard shows the position; the filing is the hotel’s responsibility.
- Service charge distribution: service charge collected against the amount distributed to staff under the hotel’s own policy, by month.
F&B and restaurant groups
For a restaurant group the unit of analysis is the outlet, and the outlets sit in malls, hotels and standalone sites across several emirates, often under different trading entities. The measures are simpler than a hotel’s; the reconciliation to delivery platforms and to payroll is where the work is.
- Covers, average cheque and table turns by outlet and meal period, with Ramadan iftar and suhoor services reported as their own meal periods rather than folded into dinner.
- Food cost percentage from stock counts and purchases, labelled as an estimate between counts.
- Menu engineering: contribution (price less recipe cost) and volume by item, in a two-by-two the chef can act on.
- Delivery platform share and commission: Talabat, Deliveroo, Careem and others as a share of outlet revenue, with the payout statements reconciled to POS orders.
- Labour cost percentage by outlet, including accommodation and end-of-service accruals, from the payroll ledger rather than the WPS transfer file.
- Outlet-level P&L by emirate and mall: revenue, cost of sales, labour, mall rent and marketing charges, so a busy outlet in an expensive mall is not mistaken for a profitable one.
- Ramadan performance versus standard service: iftar and suhoor covers, average cheque and food cost against the same outlet’s non-Ramadan weeks, and against last year’s Ramadan.
KPI definitions
Eleven definitions across rooms and F&B, written so the general manager, the F&B director and the financial controller can argue with them before the model is built. Each carries a formula and the trap that most often makes the number wrong.
| KPI | Definition | Formula | Watch out for |
|---|---|---|---|
| Occupancy | Rooms sold as a share of rooms available for sale, by night and by period. | Rooms sold ÷ (total rooms − out-of-order rooms) | Complimentary and house-use rooms are usually excluded from rooms sold; the PMS setting decides, and the page should say which. |
| ADR (average daily rate) | Room revenue divided by rooms sold, in AED, net of VAT, tourism dirham and municipality fee. | Net room revenue ÷ rooms sold | Package revenue (breakfast, transfers) must be split out before ADR is calculated, or ADR rises every time a package sells. |
| RevPAR | Room revenue per available room, combining occupancy and rate. | Net room revenue ÷ rooms available, or occupancy × ADR | Use the same rooms-available denominator as occupancy; rooms out of order for renovation should be excluded consistently. |
| TRevPAR | Total revenue per available room: rooms, F&B, spa, parking and other departments, in AED. | Total net revenue ÷ rooms available | F&B revenue from non-resident diners inflates TRevPAR; report it, but show F&B separately too. |
| GOPPAR | Gross operating profit per available room, after departmental and undistributed expenses, before fixed charges. | (Total revenue − departmental expenses − undistributed operating expenses) ÷ rooms available | Needs the month-end P&L, not the daily flash; the model reconciles the two so daily and monthly GOPPAR agree at month end. |
| Channel mix and OTA commission | Room nights and revenue by booking channel (direct, OTA, wholesale, corporate), with commission cost as a share of channel revenue. | Channel room revenue ÷ total room revenue; commission paid ÷ channel room revenue | OTA commission is invoiced monthly, not per booking; attribute it to the stay month, and take the rate from the contract rather than the invoice. |
| Pickup and pace | Room nights on the books for a future period compared with the same point before the comparable period last year. | Rooms booked for target period as at today − rooms booked for comparable period as at the same lead time last year | Comparable period must be event-aligned (same Ramadan, same exhibition week), not calendar-aligned. |
| Covers and average cheque | Guests served per outlet and meal period, and net F&B revenue per cover, in AED. | Net outlet revenue ÷ covers | Covers must be entered at the POS; a table of six rung up as one cover halves the average cheque and doubles the apparent spend per guest. |
| Food cost percentage | Cost of food consumed as a share of net food revenue, by outlet and period. | (Opening stock + purchases − closing stock) ÷ net food revenue | Depends on a physical stock count; between counts the figure is an estimate and should be labelled as one. |
| Delivery platform share and commission | Revenue through Talabat, Deliveroo, Careem and similar as a share of outlet revenue, with platform commission as a share of that revenue. | Platform order value ÷ outlet net revenue; platform commission ÷ platform order value | Platform payouts are net of commission and arrive weekly; reconcile payout statements to POS orders before trusting either the share or the commission. |
| Labour cost percentage | Total employment cost, including accommodation and end-of-service accruals, as a share of net revenue, by department and outlet. | Payroll cost from the payroll ledger ÷ net revenue | Outsourced staff sit in a different ledger line from payroll; include both or the figure is flattering. |
Systems we typically connect
The PMS and POS are the daily sources; finance and payroll are the monthly ones. STR data is listed because most hotels have it and it belongs in the model, under the hotel’s own licence.
| System | How it connects | Refresh | The catch |
|---|---|---|---|
| Opera PMS, IDS, Protel, Cloudbeds | Reporting database, scheduled exports or vendor API, depending on version and hosting | Daily flash at a fixed morning time; monthly close after night audit of the last day | Rate codes and market segments are configured per property; the mapping to channels and segments is agreed before the build. |
| Micros / Simphony, Foodics, Revel (POS) | Reporting database or API; Foodics and Revel are cloud APIs | Daily, with intraday where the API allows | Covers, voids and discounts are only as reliable as the cashier discipline; the model exposes anomalies rather than smoothing them. |
| Channel managers and OTA extranets | Channel manager API or scheduled export; extranet commission statements as files | Daily for bookings; monthly for commission statements | Commission statements arrive after the stay month; the model estimates from contract rates and trues up when the statement lands. |
| STR reports (client-licensed) | Read from files you receive under your own STR subscription | Weekly or monthly, as your subscription provides | Your licence, your data; we load it into your model and do not redistribute it. |
| Finance (Sun, SAP Business One, Odoo, Dynamics 365 Business Central) | Database, API or OData | Nightly; monthly close | Departmental P&L account mapping (USALI or your own chart) is agreed once and held in the model. |
| Payroll | Payroll system export or WPS SIF file | Monthly | Accommodation, flights and end-of-service accruals sit outside the SIF; labour cost needs the full ledger, not the transfer file. |
Seasonality that the model must understand
Hospitality in the UAE is seasonal in a way that makes naive comparisons useless. A model that compares this month with last month reports a boom every October and a collapse every June. The date table carries each of the following as an attribute, and every page has a comparable-period toggle that says which comparison is in force.
- The October-to-April peak and the summer trough: comparisons are made with the same period last year, and within-year trend is shown against a seasonal baseline rather than the previous month.
- Ramadan: rooms demand falls and F&B shifts into the evening; iftar and suhoor are meal periods in their own right. A Ramadan month is compared with the previous year’s Ramadan month, which is a different calendar month.
- Eid al-Fitr and Eid al-Adha: short, sharp peaks in rooms and F&B, compared with the same Eid last year rather than the surrounding weeks.
- Event-driven demand: GITEX, the Dubai Shopping Festival, the Abu Dhabi Formula 1 weekend and the exhibition calendar move rooms demand by the week. The model carries an event calendar so pace can be compared same-event to same-event.
- The working week: Saturday and Sunday are the weekend, with Friday a half day for federal government; F&B weekly patterns are reported against that week, not the older one.
Daily flash to monthly P&L, one model
The daily flash from the PMS and POS and the month-end P&L from finance are built from different systems with different cut-offs, and in most properties they are reconciled by hand. The model does the reconciliation instead: the flash measures are defined so they sum to the month, the month-end figures from finance are loaded when the close is done, and the difference between the two is shown as a variance with its cause — a late posting, a rebate, an allowance, a rate adjustment — rather than re-keyed into agreement.
The practical result is that the general manager’s Tuesday page and the financial controller’s month-end page use the same occupancy, the same ADR and the same covers, and when they differ the page says why. GOPPAR, which needs the P&L, appears on the same page as RevPAR, which does not, and the two are consistent at month end.
Open the hospitality demo
Demo built on synthetic data to show layout, KPI definitions and interaction. Not client data. Open the hospitality demo opens in this site; nothing to install and nothing to sign up for.
Interactive analytics and key metrics overview.
Hospitality Performance
Core metrics tracking
Regional Distribution
Click a bar to focus (Top 7)
Three things to look for while it is open:
- Switch the comparable-period toggle to Ramadan-adjusted and watch the RevPAR and covers comparisons change; the calendar month comparison is shown alongside so the difference is visible.
- Open the outlet page and filter to one outlet; the delivery-platform share, labour cost and outlet P&L all follow because they sit on one model.
- Look at the flash-to-P&L page: the daily figures sum to the month and the variance to the month-end P&L is itemised by cause.
Questions about hospitality analytics
Can Power BI connect to Opera and Micros?
Can we see RevPAR and GOPPAR daily?
How do you handle Ramadan and seasonal comparisons?
Can outlet managers see only their outlet?
Can we reconcile delivery-platform payouts?
What does it cost?
Fixed price for a hospitality dashboard
Quoted before work starts against a written scope. The quote is the price.
A hospitality build is quoted the same way as every other project on this site, following the sequence on the Power BI dashboard development Dubai page. Afterwards, the Power BI managed services UAE service keeps the PMS and POS feeds, the monthly commission statements and the payroll load running. Restaurant groups with a retail arm or a central kitchen selling wholesale will find the retail analytics Dubai page covers the stock and margin side.
It starts with a short discovery call, at no charge, and a look at your current reports and the systems behind them. From that we write a scope: the sources we will connect, the model we will build, the pages and visuals, the users and their security, the training and the handover.
We then quote a fixed price against that scope. The quote is the price. If we find something worse than expected inside the scope, that is our cost, not yours. If you want something outside the scope, we quote it separately before doing it, and you decide.
Payment is staged against the milestones written into the scope, so you are never paying ahead of what you have seen. Where a figure is published on this site it is a starting point rather than your quote, because the number depends on your systems; we would rather you knew how the price is built than read a "from" price as though it already applied to you.
The reporting diagnostic is a fixed AED 4,950. That is the whole amount. Nothing is added at checkout. A hospitality build is quoted rather than sold from a page: builds start at AED 15,500 and most land in the AED 15,500 to AED 62,000 range, depending on the systems joined, the state of the data and the number of entities, pages and trained users. Those figures anchor the conversation; the number in your written quote is the one you pay.
The written scope for a hospitality build itemises:
- Properties and outlets in scope, and the entities and emirates they trade under.
- Sources: PMS, POS, channel manager, commission statements, STR files, finance, payroll — and how each connects.
- Whether the flash-to-P&L reconciliation is in scope, and the chart of accounts mapping it needs.
- Pages and mobile layouts, including any outlet-manager view.
- Calendar logic: season, Ramadan, Eid and event-aligned comparisons.
Talk through your hospitality reporting
Get started — four quick questions takes about a minute and books a thirty-minute call at no charge, on GST hours.