Food Safety Compliance Software in Dubai (2026): DMChecked Ended the Paper Logbook
DMChecked became mandatory on 12 November 2025 and paper temperature logs no longer count. Dubai has 29,303 food establishments and ran 31,563 inspections in H1 2026. What the software has to do.
- PUBLISHED
- 18 SEPT 2026
- READ TIME
- 10 MIN
- AUTHOR
- AQUARIUS · DUBAI
- UNIT
- REV 2026.09
Short answer: Dubai Municipality replaced FoodWatch Connect with DMChecked in November 2025, and since 12 November 2025 it is the mandatory channel for every DM-licensed food establishment — restaurants, cafes, caterers, central kitchens, factories, delivery vehicles and every licensed Person in Charge. The Dubai Food Code is explicit that paper logs no longer satisfy compliance. That turns a clipboard problem into a software problem: temperature records, pest reports, staff illness exclusions and corrective actions now have to be captured digitally, by the right certified person, at the time they happen. Fines for food safety offences reach AED 100,000, and a Grade D or F can close the door entirely.
Key takeaways
- Dubai now has 29,303 food establishments. 1,898 opened in the first half of 2026 alone — about 316 a month, or 10.5 new food businesses every day.
- Inspection volume matches it. Dubai Municipality carried out 31,563 food inspections in H1 2026. Roughly one inspection per establishment, per half-year, before you count re-visits and complaint-driven calls.
- Paper is now a finding, not a record. DMChecked has been mandatory since 12 November 2025. The PIC must record pest reports, employee illness exclusions, delivery incidents, vehicle issues, equipment failures and process deviations in the platform (Food Code §3.1.2.e).
- Most Dubai operators get this wrong: they register on DMChecked, then keep running the kitchen on a laminated sheet and back-fill the app on Thursday. An inspector reading identical handwriting for fourteen days of fridge checks knows exactly what happened, and back-filled entries are worse than missing ones.
- The compliance cost is already being paid. HACCP plan development runs AED 5,000–20,000, a PIC certificate AED 1,000–2,000, and each food handler AED 393–593 in year one. What is usually missing is the AED 0 spent on making the daily records actually happen.
Why this landed on 29,303 businesses at once
Dubai’s food sector is close to 30,000 establishments and still compounding. 1,898 new food businesses opened in the first half of 2026 — an average of 316 per month and 10.5 per day — bringing the total to 29,303. Over the same six months the Food Safety Department ran 31,563 inspections and processed 144,063 food consignments covering 193,955 containers and roughly 840,400 individual imported products.
No inspectorate scales linearly with a market growing at ten openings a day. It scales by pushing the record-keeping onto the operator and auditing the data instead of the paperwork. That is what DMChecked is. Launched in November 2025 as the next-generation replacement for FoodWatch Connect, it gives the Municipality real-time inspection recording, mobile dashboards, follow-up reminders and corrective-action tracking, with data shared between business and regulator as it is entered. Existing FoodWatch registrations were migrated automatically; registration itself is free and mandatory.
The commercial stakes are not small. The UAE food service market was valued at about USD 18.6 billion in 2025 and is forecast to reach USD 56.09 billion by 2034 (roughly 11.7% CAGR), while UAE full-service restaurants alone are put at USD 11.26 billion in 2026 growing toward USD 25.97 billion by 2031. Cloud kitchens — the format with the least floor space and the most compliance surface per dirham of revenue — went from about USD 430 million in 2025 toward a projected USD 1.08 billion by 2032.
What the Food Code actually asks you to record
Strip out the consultancy language and the daily obligations are measurable, timed and repetitive — which is precisely why they belong in software rather than a binder.
| Control | Dubai Food Code requirement | What the system must capture |
|---|---|---|
| Cold storage | High-risk foods at 5°C or below; frozen at −18°C (§3.4.2.a) | Per-unit readings, timestamp, who took them, exception flagged on breach |
| Hot holding | 60°C or above, maximum 4 hours (§3.2.11) | Countdown from batch start, discard prompt at the limit |
| Cooking | 70°C for 2 minutes or an equivalent time/temperature combination (§3.2.7.b) | Probe reading tied to a named dish and batch |
| Two-stage cooling | 60°C to 20°C within 2 hours, then to 5°C within a further 4 hours — 6 hours total (§3.2.12.a) | Two timed checkpoints, not one signature at the end of the shift |
| Reheating | Above 75°C within 1 hour (§3.2.14) | Single reading, hard pass or fail |
| Thermometers | Calibrated, with calibration evidence retained (§2.7.4) | Device register, calibration due dates, automatic reminders |
| Person in Charge | Full-time, on site, certified; active PIC every shift in high-risk operations; registered in DMChecked; credentials never shared (§3.1.1) | Per-user login, shift rota, no generic “manager” account |
| Incidents | Pest reports, staff illness exclusions, delivery and vehicle incidents, equipment failure, process deviations (§3.1.2.e) | Structured event log with corrective action and closure |
| Training | Every employee trained before starting work; refresher every 2 years (§6.4.b) | Certificate expiry tracking per staff member |
Two rules deserve special attention because they are the ones that fail silently. First, if your PIC resigns you have 30 days to designate a successor and that person must be certified within 45 days (§3.1.1.e) — a clock that starts the day a resignation letter lands, not the day someone remembers. Second, PIC credentials cannot be shared. A kitchen where four people log temperatures under one borrowed account has no valid records at all, however neat the numbers look.
The grade is the business risk, not the fine
Dubai Municipality grades establishments A through F with a visual card: Gold for consistent Grade A, Green for B, Orange for D, Red for F. Grade A means impeccable standards, B commendable with room to improve, C acceptable. D is substandard and demands immediate corrective action; F means hygiene and food safety are severely compromised.
Fines get the headlines — food safety offences can attract up to AED 100,000, inaccurate platform records are penalised in the AED 50,000–100,000 band, and misleading labels or false descriptions run AED 10,000–100,000 — but the real loss is downstream. Enforcement escalates from warnings and mandatory corrective actions to temporary closure, permit withdrawal, product recall and public notification. In a market with 29,303 competitors and delivery apps that rank by rating, a public grade downgrade costs more than the penalty notice attached to it.
Buy, configure or build
Three routes work in Dubai, and the right one is decided by branch count and how much of your kitchen data already lives in other systems.
| Route | Best for | Typical 2026 investment (AED) | Trade-off |
|---|---|---|---|
| Off-the-shelf checklist SaaS, configured | 1–5 outlets, standard menu | 15,000–35,000 setup, then subscription per site | Fast, but generic templates rarely match Food Code clause numbering or your Arabic-speaking staff |
| Custom compliance app | 6–40 outlets, central kitchen, mixed brands | 60,000–150,000 | Bilingual, offline-first, role separation by PIC — but it is a build, not a download |
| Custom plus IoT temperature monitoring | Multi-site groups, cold chain, distribution | 180,000–400,000+ | Sensors remove the single biggest source of falsified records; hardware, gateways and site survey are separate line items |
Budget 15–20% of build cost annually for maintenance in every case. Regulatory platforms change, device fleets churn, and staff turnover in Dubai F&B means the onboarding flow gets more use than any other screen. For adjacent budgets, see our POS and inventory software cost guide, the cloud kitchen management breakdown and the QR menu and table ordering system guide.
What separates a system that survives an inspection
The failure modes are consistent across every Dubai kitchen we have looked at, and none of them are about features.
Capture at the point of work. A phone in a chef’s pocket with a Bluetooth probe records at 11:04 because the check happened at 11:04. A form filled in the office records the story someone remembers. Timestamps that cluster at the end of a shift are the first thing an experienced inspector looks for.
Named users, always. Because the Food Code forbids shared PIC credentials, a single tablet on the wall with one login is a compliance liability. PIN-per-user on a shared device is the practical answer for a kitchen where phones are not allowed on the line.
Offline-first. Walk-in freezers, basement prep rooms and delivery vehicles have no signal. If the app cannot queue readings and sync later, staff will stop using it in exactly the locations where the readings matter most.
Arabic and English from the wireframe. Dubai kitchens run on multilingual teams, and a compliance app only works if the person holding the probe understands the prompt. Retrofitting right-to-left layout after launch is a rebuild, not a translation — the same lesson covered in our Arabic localisation guide.
Expiry as a first-class object. Occupational Health Cards are valid for 1 year with renewal due 30 days before expiry and a AED 310 late penalty; basic food hygiene training refreshes on roughly a two-year cycle; the PIC certificate runs 5 years. Three different clocks per employee, multiplied by your headcount, is a spreadsheet nobody maintains and a query any database answers in a second.
Corrective actions that close. Recording a fridge at 9°C is half the obligation. The system has to demand what was done, by whom, and whether the product was discarded — then keep the evidence retrievable months later.
What it costs to stay compliant anyway
Before any software spend, a Dubai food business is already paying for compliance. Basic food hygiene training is AED 100–300 per handler, the Occupational Health Card AED 290 plus a AED 3 service fee, and the first-year total per food handler lands at AED 393–593. A PIC certificate is AED 1,000–2,000, with accredited PIC courses commonly quoted at AED 450–950, and a documented HACCP plan — mandatory for commercial food establishments and submitted with the food establishment permit — runs AED 5,000–20,000 depending on menu complexity and risk level.
Run the arithmetic for a 40-staff restaurant group and the annual people-side compliance cost alone clears AED 20,000 before a single sensor is bought. The software question is not whether to spend money on compliance. It is whether the money already being spent produces records that hold up on the day an inspector opens DMChecked next to your logbook.
How Aquarius approaches it
We start with the clause list, not the screens. First sprint maps every Food Code obligation that applies to your operation — and only those — to a record, a frequency, an owner and a corrective action path. Second sprint is capture: offline-first mobile, PIN-per-user, probe integration where the cold chain justifies it, Arabic and English in the same build. Reporting comes last, because a dashboard over incomplete data is decoration.
If you already run a decent checklist tool, the faster fix is usually an integration and data-quality layer rather than a replacement. If you run multiple brands across multiple DED licences with a central kitchen in between, a purpose-built system pays for itself in avoided re-inspections and staff hours long before it pays for itself in avoided fines. See our development services and pricing for how engagements are structured.
Frequently asked questions
Is DMChecked mandatory for all food businesses in Dubai?
Yes. DMChecked replaced FoodWatch Connect and has been mandatory since 12 November 2025 for all Dubai Municipality-licensed establishments — restaurants, cafes, catering companies, central kitchens, food factories, food transport vehicles and licensed Persons in Charge. Registration is free, and businesses already on FoodWatch were migrated automatically without data loss.
Can we still keep paper temperature logs?
You can keep them as a backup, but they do not satisfy compliance on their own. The Food Code requires the PIC to record incidents and checks through the platform, and paper logs alone are treated as a gap. The practical answer is digital capture at the point of work with the paper retired, not run in parallel.
What happens if our Person in Charge resigns?
You have 30 days to designate a successor, and that successor must complete training and be certified within 45 days. High-risk operations need an active certified PIC on every shift, so a single-PIC site is a scheduling risk as much as a compliance one.
What are the fines for food safety violations in Dubai?
Food safety offences can attract fines of up to AED 100,000, with inaccurate platform records penalised in the AED 50,000–100,000 band and misleading labelling in the AED 10,000–100,000 band. Beyond fines, enforcement includes mandatory corrective action, temporary closure, product withdrawal, licence suspension and public notification.
Do we need IoT temperature sensors, or is manual logging enough?
Manual logging is compliant if it is genuinely done at the required frequency and recorded by the certified person. Sensors earn their place where the failure is expensive or invisible: walk-in freezers, overnight periods, delivery vehicles and multi-site cold chain. They also remove the audit concern about back-filled records, because the data arrives whether anyone remembers or not.
How long does a food safety compliance app take to build?
An integration or data-quality layer over an existing tool is typically 4 to 6 weeks. A custom multi-branch compliance app with offline capture, bilingual UI and role separation runs 10 to 16 weeks, with the first stage spent mapping Food Code clauses to records rather than writing code.
Does the same system work in Abu Dhabi or Sharjah?
The control logic transfers — temperatures, cooling curves, training expiry — but the regulator and submission channel do not. Abu Dhabi operates under ADAFSA with its own permits, record retention expectations and training scheme. Build the record model once and keep the regulator adapter separate if you plan to expand across emirates.
Records are the product
Dubai did not just digitise a form in November 2025. It changed what counts as proof. In a sector adding 10.5 new businesses a day and absorbing 31,563 inspections in six months, the operators who sail through are not the ones with the cleanest kitchens on inspection day — they are the ones whose records were already true on the other 180 days. That is a software outcome, and it is a cheaper one than a closure.
Talk to Aquarius about DMChecked and food safety compliance software →