Restaurant ERP Consultant, UAE

Aggregator settlements and cash at the door

Delivery in the UAE comes through several routes at once. Aggregator apps send orders to a tablet or straight into the POS, the group's own app or website takes orders that its own riders or a fleet company deliver, and some customers still pay cash when the food arrives. Each route settles differently, and each creates its own reconciliation gap.

Aggregators typically pay on a cycle, net of commission, restaurant-funded discounts, cancellations and any penalties for late or incorrect orders. I design a matching process that imports each settlement report, links it to POS orders by reference, books gross sales and each deduction separately, and leaves only real differences for review. Where an aggregator issues its own tax invoice for commission, that invoice is captured as a supplier bill with its VAT.

Cash on delivery needs a different control. The POS knows how much cash each rider should hold at the end of a shift; the ERP should know how much was handed over and banked. I define the handover record, the tolerance and the follow-up, whether riders are employees or provided by a fleet partner. The resulting reports show net margin by channel and brand, which is often the first time owners see what delivery actually earns. The interface work is scoped through my ERP integration service.

Master franchisees and reporting to brand owners abroad

Many restaurant brands trading in the UAE belong to franchisors based elsewhere, with a local company holding the rights for one emirate, the whole country or the wider region. The franchise agreement sets the royalty and marketing contribution, the sales definition they are calculated on, the currency of payment and the reports the brand owner receives. It often also dictates recipes, approved suppliers and product specifications.

Those terms belong in the ERP rather than in a finance manager's spreadsheet. I translate them into calculation rules per brand, decide how exchange rates are applied when fees are due in dollars or euros, and design the monthly pack the franchisor expects. Withholding or other tax questions on cross-border fees are confirmed with your tax advisor before anything is configured.

Approved supplier lists and brand specifications shape purchasing. Items can be restricted to listed suppliers, and specifications held against the item, so an outlet cannot quietly substitute a cheaper product. Where the franchisor supplies proprietary ingredients from abroad, those purchases carry their full landed cost into recipes. A multi-brand operator then sees each brand's food cost, royalty burden and outlet profit side by side, which helps when renewing or renegotiating rights. This is restaurant-level detail; group structures spanning hotels and leisure are covered on my UAE hospitality ERP page.

Cloud kitchens and delivery-only brands

Shared kitchen facilities, where operators rent a fitted kitchen unit with delivery logistics nearby, make it practical to launch a brand without a dining room. Some UAE groups use them to test a concept before opening an outlet; others run several delivery-only menus from one unit, cooked by the same team from the same stock.

In the ERP, stock belongs to the kitchen unit, while every sale and every recipe depletion is tagged with the brand that generated it. Packaging is part of each recipe, because a rice bowl brand and a burger brand use very different containers and the cost is not trivial. Kitchen rental, facility service fees and shared staff are allocated to brands by a rule the owners agree, so brand profit is calculated the same way every month.

Speed of change is the main challenge. Delivery-only menus are adjusted often, items are renamed for promotions and new brands appear quickly. I set a rule that no menu item can be activated in the POS or on an aggregator without a linked recipe, otherwise theoretical food cost silently loses accuracy. When a brand is retired, its recipes and items are closed rather than deleted, keeping history for comparison. The general approach to recipes and theoretical cost is set out on ERP for restaurants.

Ramadan menus, iftar orders and production planning

For restaurants, Ramadan changes what is cooked as much as when. Daytime dine-in trade typically slows, while iftar set menus, family boxes, corporate iftar orders and late-evening delivery climb. Suhoor service adds a second peak for some concepts. The menu often changes for the month, and the products in demand shift with it.

From an ERP standpoint, each iftar box or set menu needs its own recipe, built from existing sub-recipes, with packaging and portioning defined before the month starts. Pre-orders and bulk corporate orders should flow into the central kitchen's production plan, so prep for dates, soups, rice dishes and desserts is scheduled from real demand rather than memory. I also suggest a Ramadan-specific par level for each outlet, since normal pars no longer fit.

Timing matters for the project too. I avoid go-live during Ramadan, but I do use the previous year's Ramadan sales, where available, to test that recipes, aggregator promotions and production planning hold up under that pattern. After Eid, a variance review compares theoretical and actual usage for the month, which is often when portion drift on set menus becomes visible. Restaurants producing packaged sweets or retail products for the season can see related guidance on my UAE food and beverage ERP page.

Outlet permits, VAT, e-invoicing and a remote rollout

Each UAE outlet and kitchen operates under licenses and food safety approvals from the relevant emirate's authorities, and requirements differ between emirates. I record license details, expiry dates and responsible persons on each location's record, so renewals are visible across a growing estate. The interpretation of those requirements stays with your licensing and food safety teams.

Restaurant sales are subject to VAT, and bills may also carry emirate-level charges. Tax codes must be set at the POS and received intact by the ERP. The UAE has also announced a national e-invoicing program, and restaurant groups should ask every POS and ERP vendor how they plan to support it for the transactions that will fall within scope, rather than assuming readiness. Your tax advisor confirms what applies to you; the wider context is on my UAE ERP consultant page.

For platform selection, Zoho, Odoo, ERPNext and Microsoft Dynamics 365 each run the same four restaurant cases drawn from your business: an aggregator settlement, a rider cash handover, a royalty calculation in foreign currency and a cloud kitchen with three brands. The rollout then runs remotely, pilot kitchen first, with live sessions inside UAE working hours and short recordings for chefs and outlet managers on split shifts. Visiting a kitchen in person is possible by arrangement. More UAE material is on the UAE hub.