Cloud Kitchen Agreement (UAE)

A Cloud Kitchen Agreement in the UAE is a licence to occupy contract under which a cloud kitchen provider grants a food brand the right to use a defined kitchen unit at a shared commercial food preparation facility, exclusively for the production of food for delivery and takeaway orders. The agreement is governed by the UAE Civil Code (Federal Law No. 5 of 1985) and the Commercial Transactions Law (Federal Decree-Law No. 50 of 2022), and the food operations conducted from the kitchen unit must comply with the Food Safety Federal Law No. 10 of 2015 as implemented by Dubai Municipality's Food Safety Department, the Abu Dhabi Agriculture and Food Safety Authority (ADAFSA), and the Emirates Authority for Standardisation and Metrology (ESMA).

Cloud kitchens — also known as ghost kitchens, dark kitchens, or virtual kitchens — emerged as a dominant food and beverage format in the UAE during and after 2020, driven by the rapid expansion of delivery aggregator platforms including Talabat, Deliveroo UAE, Noon Food, and Careem Now. Dubai's dense urban population, high smartphone penetration, and demand for convenience created the conditions for a delivery-first restaurant model that generates significant order volumes without requiring a customer-facing dining room, mall space, or prime street-level location. A cloud kitchen facility in Al Quoz, Dubai Investment Park, or Mussafah in Abu Dhabi can host dozens of independent food brands simultaneously, each operating from its own dedicated kitchen unit.

The legal structure of a cloud kitchen agreement is a licence rather than a tenancy. The provider retains exclusive possession of the facility and grants the food brand only a personal, non-exclusive right to use the kitchen unit for its defined food concept during agreed operating hours. The Dubai Tenancy Law — Law No. 26 of 2007 as amended by Law No. 33 of 2008 — and the Real Estate Regulatory Agency (RERA) registration requirement do not apply to a licence, giving the provider flexibility to manage the facility occupancy and exit non-performing brands quickly.

Food safety compliance is the defining operational obligation. The cloud kitchen provider holds the facility-level food establishment licence from Dubai Municipality's Food Safety Department and is responsible for the shared infrastructure — cold storage, ventilation, waste disposal, and pest control — meeting the mandatory hygiene standards under the Food Safety Federal Law No. 10 of 2015. Each food brand bears responsibility for food safety within its own kitchen unit, including HACCP implementation, staff food safety cards, Halal certification for meat and poultry from a Ministry of Climate Change and Environment-approved body, and product-level traceability records.

The fee structure typically combines a fixed monthly kitchen fee covering the unit and shared services, a one-time setup fee, and a security deposit. Some providers charge a commission on delivery revenue as an alternative or supplement to the fixed fee. All payments are subject to Value Added Tax at 5% under Federal Decree-Law No. 8 of 2017, administered by the Federal Tax Authority (FTA).

Delivery aggregator relationships are a practical commercial element unique to the cloud kitchen model. The food brand typically registers its virtual storefront on Talabat, Deliveroo UAE, or Noon Food independently, bears the aggregator commission costs — typically 25% to 35% of order value — and is responsible for meeting the aggregator's quality and compliance requirements. Some cloud kitchen providers offer aggregator registration support as part of their onboarding service.

A Cloud Kitchen Agreement in the UAE is needed whenever a food brand, entrepreneur, or restaurant operator wishes to establish a delivery-only food business from a shared professional kitchen facility without the capital commitment of a traditional restaurant fit-out, and the cloud kitchen provider requires a written agreement governing the licence to occupy, the fees, the food safety obligations, and the exit terms.

Entrepreneurs testing a new food concept in the UAE rely on the cloud kitchen model and the associated agreement to access a licensed, fully equipped kitchen at a fraction of the cost of a traditional restaurant. A delivery-only food brand can launch on Talabat or Deliveroo UAE with a kitchen setup cost of AED 5,000 to AED 20,000, compared to AED 300,000 to AED 1,000,000 or more for a traditional dine-in restaurant. The Cloud Kitchen Agreement formalises the right to use the unit, specifies the permitted cuisine, and defines the commercial terms before the brand commits any capital to food procurement or aggregator onboarding.

Established restaurant operators expanding into delivery without adding physical outlets use the cloud kitchen agreement to access kitchen capacity in delivery-dense neighbourhoods. A restaurant in Downtown Dubai may open a cloud kitchen unit in Deira or Barsha to serve a delivery zone that its central location cannot serve within acceptable delivery time windows.

Food businesses scaling from a home kitchen or a catering operation into a licensed commercial format require the cloud kitchen agreement to establish legal food preparation premises. Operating a food business from a residential kitchen without a valid food establishment licence violates the Food Safety Federal Law No. 10 of 2015 and the relevant DED trade licence conditions. A cloud kitchen unit provides the licensed commercial premises required for regulatory compliance.

Restaurant groups operating multiple virtual brands — for example, a Mexican brand, a Japanese brand, and a health food brand operated by the same team from a single kitchen unit — use the agreement to secure the kitchen capacity for their multi-brand delivery strategy and to clarify the permitted cuisine scope that covers all their virtual storefronts.

The agreement is also needed at the point of expansion or relocation. A food brand that has tested a concept successfully from one cloud kitchen unit and wishes to add units in other locations requires a separate Cloud Kitchen Agreement for each new unit, establishing the commercial terms, the security deposit, and the food safety compliance framework for each facility.

A UAE Cloud Kitchen Agreement must contain a defined set of elements to create a workable licence arrangement, comply with the Food Safety Federal Law No. 10 of 2015, and protect both the provider's facility and the brand's commercial interests.

Party identification requires the full legal names, DED or free zone trade licence numbers, and registered addresses of both the cloud kitchen provider and the food brand. The provider's licence must cover food service and catering facility activities; the brand's licence must cover restaurant or food service activities. The forms-legal.com UAE Cloud Kitchen Agreement template captures all the party, unit, fee, and compliance fields that a UAE regulatory authority or court expects.

The kitchen unit description must specify the unit reference number, the precise location within the facility building, and the approximate area in square metres. An attached floor plan showing the licensed unit boundary eliminates disputes with adjacent brand operators about equipment placement and storage allocation.

The permitted cuisine clause defines the specific food concept the brand may prepare from the unit. The clause must be specific enough to prevent the brand from expanding to an incompatible food format — for example, adding a fish and chips brand to a declared biryani brand — without the provider's consent, which would affect the facility's smell, waste profile, and HACCP requirements.

The operating hours clause specifies the hours during which the brand may access and use the Kitchen Unit. Many cloud kitchen facilities operate 24 hours but individual brands may agree to time-slotted hours, particularly in multi-brand facilities where kitchen equipment is shared.

The facilities and services clause must specify exactly what the provider includes: the kitchen equipment in the unit, access to shared cold and dry storage, waste disposal, utilities, wi-fi, and packaging storage. Shared equipment such as blast chillers or proofers that multiple brands use must be scheduled to avoid conflicts.

The fee clause must set out the monthly kitchen fee and its payment due date, the commission rate if applicable, the one-time setup fee, and the security deposit amount and refund conditions. All amounts must be stated exclusive of VAT at 5% under Federal Decree-Law No. 8 of 2017. The food safety obligations clause must allocate HACCP implementation, staff food safety card maintenance, Halal certification requirements, and traceability record-keeping between the provider and the brand as described in the agreement. Termination provisions must specify immediate termination events and the 30-day notice right. The agreement should also address the delivery aggregator platform rules: which platforms are approved, whether the provider imposes any exclusivity or commission-sharing requirement, and how disputes with aggregators are handled.

Completing a UAE Cloud Kitchen Agreement requires the parties to work through the fields in the order the commercial relationship was negotiated, starting with the parties' identities and ending with the fee and governance structure.

Begin with the agreement date and kitchen licence term. Enter the execution date in DD/MM/YYYY format and state the term clearly, for example twelve months from 01 July 2026, automatically renewable for successive six-month periods on 30 days' notice before each expiry. Enter the commencement date on which the brand gains access to the kitchen unit and begins paying the monthly fee.

Enter the provider's details: the full legal name of the cloud kitchen operating entity, the DED trade licence number, and the full address of the facility. Then enter the brand's details: the full registered legal name, the DED trade licence number, and the brand's registered business address.

Describe the kitchen unit precisely: the unit reference number, the block or zone within the facility, and the approximate area. Describe the permitted cuisine with enough specificity to anchor the operational scope — for example, authentic Hyderabadi biryani, kebabs, and Indian sweets for delivery and takeaway only. Enter the permitted operating hours.

Complete the fee fields: the monthly kitchen fee and payment due date, the commission rate on delivery revenue if applicable or none if not, the one-time setup fee, and the security deposit amount. Confirm that all amounts are exclusive of VAT.

Fill in the brand's obligations field, specifying food establishment licence maintenance, HACCP implementation, staff food safety card requirements, approved aggregator platform usage, and monthly sales reporting if a commission structure applies. Select the governing law forum — the Dubai Courts for a Dubai facility or the Abu Dhabi Judicial Department for an Abu Dhabi location. Execute the agreement with the authorised signatory of each entity providing name, designation, and date.

Legal requirements for a UAE Cloud Kitchen Agreement arise from the food safety regulatory framework, trade licensing rules, and the commercial law principles that govern the licence to occupy arrangement.

The cloud kitchen provider must hold a valid food establishment licence from Dubai Municipality's Food Safety Department or the Abu Dhabi Agriculture and Food Safety Authority (ADAFSA) covering the entire facility. This licence requires the facility to meet mandatory hygiene, equipment, ventilation, waste disposal, and pest control standards under the Food Safety Federal Law No. 10 of 2015. Each food brand operating in the facility must either be covered as a sub-operator under the facility licence or hold its own food establishment licence for its specific unit, depending on the arrangement agreed with the relevant municipal authority.

Food safety compliance obligations under the Food Safety Federal Law No. 10 of 2015 require every food preparation operation to implement HACCP, maintain traceability records, ensure all food-handling staff hold current food safety cards after completing municipally approved training, and source Halal-certified meat and poultry from approved suppliers with valid certificates from a Ministry of Climate Change and Environment-approved body. Product standards must comply with Emirates Authority for Standardisation and Metrology (ESMA) requirements.

Trade licensing requires the provider's DED trade licence to cover cloud kitchen and food service facility activities. The brand's DED trade licence must cover restaurant or food service activities at the cloud kitchen address. Delivery operations are subject to the aggregator platform's terms and the relevant consumer protection requirements under the Consumer Protection Law (Federal Law No. 15 of 2020) administered by the Ministry of Economy.

Tax compliance requires VAT registration with the Federal Tax Authority (FTA) if the brand's taxable food and beverage sales exceed AED 375,000 per rolling twelve months, with VAT at 5% under Federal Decree-Law No. 8 of 2017 charged on sales and on the kitchen licence fees. The UAE Civil Code (Federal Law No. 5 of 1985) and the Commercial Transactions Law (Federal Decree-Law No. 50 of 2022) govern the agreement and the licence to occupy relationship.

Common mistakes in UAE Cloud Kitchen Agreements cluster around food safety allocation, the licence versus tenancy distinction, permitted cuisine scope, and fee structure ambiguity.

Failing to clearly allocate food safety responsibility between the provider and the brand is the most consequential structural gap. When Dubai Municipality's Food Safety Department issues a closure notice to a cloud kitchen facility, both the provider as facility licence holder and the individual brand as the operator of the offending kitchen unit may be affected. Without a precise allocation in the agreement specifying which party is responsible for the shared infrastructure and which party is responsible for the individual kitchen unit, the fine and remediation cost allocation becomes a secondary dispute that compounds the primary food safety crisis. The indemnity clause must mirror the operational responsibility allocation precisely.

Treating a cloud kitchen agreement as equivalent to a commercial lease is a misunderstanding of the legal framework that can mislead a brand into over-investing in fit-out improvements to the kitchen unit. Because the agreement is a licence to occupy rather than a tenancy, the brand has no right to remain after the provider exercises its no-fault termination right on 30 days' notice. A brand that spends AED 50,000 or more on custom kitchen equipment that cannot be removed without destroying the unit has made an investment that will not be recoverable on a short-notice exit.

Defining the permitted cuisine too narrowly creates a practical problem for a food brand that wants to evolve its menu. An agreement that specifies only biryani and kebabs prevents the brand from adding curries or fusion dishes without a formal contract amendment. Menu evolution is a normal part of a food brand's development, and the permitted cuisine clause should be written broadly enough to accommodate natural menu expansion while still preventing the brand from switching to a completely incompatible food format.

Omitting the approved aggregator list or failing to specify whether the provider imposes any platform exclusivity creates a dispute when the brand wants to list on a new platform. Some cloud kitchen providers have commercial arrangements with specific aggregators; others are platform-agnostic. The agreement should state the approved platforms clearly.

Leaving the VAT treatment ambiguous on the monthly fee invoice is an avoidable compliance error. The agreement should state that all fees are exclusive of VAT at 5% under Federal Decree-Law No. 8 of 2017, and that the provider issues a compliant tax invoice. A brand that has not recovered input VAT on kitchen fees due to an unclear invoicing arrangement is losing a refundable tax credit every month.