# Cloud Kitchen Management in Saudi Arabia: Costs and Margins
*How to run a digital-only restaurant: ingredient inventory, meal costing and the real margin left after platform commissions*

> **In short:** Run a profitable cloud kitchen in Saudi Arabia: cost every meal, control ingredient inventory, reconcile delivery platform commissions and stay VAT compliant.

- **URL:** https://www.snad.io/en/blog/cloud-kitchens-management-finance-guide
- **Arabic original:** https://www.snad.io/blog/cloud-kitchens-management-finance-guide
- **Category:** Industry — Restaurants & Cafés
- **Tags:** Cloud Restaurant, Cloud Kitchen, Meal Costing, Inventory Management, Snad
- **Published:** 2026-05-10
- **Updated:** 2026-08-02
- **Publisher:** Snad (snad.io)

Saudi Arabia is in the middle of a shift toward the "cloud kitchen" model — restaurants that exist only as a kitchen and a delivery app listing. The appeal is obvious: no dining room, no waiters, far less capital to open the doors. What the model does not do is make management easier. Financially and operationally it is harder. Margins are squeezed by platform commissions, and ingredient tracking has to be near-perfect to stay profitable. This guide walks through how Snad turns a cloud kitchen into a precise, well-organised profit engine.

## The margin problem: accounting for delivery platform commissions

In a cloud kitchen, the delivery platforms (HungerStation, Jahez and the like) are your primary sales channel — and an expensive one, taking anywhere from 20-30% of the order value. If those commissions are not booked as a proper selling expense in your accounting system, you will believe you are profitable while you are quietly losing money. Snad lets you record sales and classify expenses and commissions precisely, so the net profit you see is the real one — after delivery and operating costs have come out.

## Menu engineering and getting ingredient costs under control

Every gram of sauce and every piece of packaging has a price. In a cloud kitchen, cost has to be tracked down to the halala. The inventory and purchasing modules in Snad give you the actual purchase cost of every raw ingredient and let you follow it over time. Link purchasing to sales and you will quickly see whether an item's price covers its variable cost. Menu engineering means pushing the items that combine low cost with high demand — and that decision is only possible with the accurate data an ERP system produces.

## Real-time inventory for raw materials (protein, produce, packaging)

Food spoilage is the fastest way to drain cash. Cloud kitchens move at high speed, and losing track of expiry dates or remaining quantities produces serious waste. Snad makes periodic stock counts quick and simple. You can see how much chicken or oil is left in the store at any moment, which lets you raise smart purchase orders — enough to avoid a stockout that halts production, not so much that stock piles up and spoils.

## Running multiple brands out of one kitchen

One of the advantages of the cloud kitchen model is running several brands from the same space — a burger brand and a shawarma brand sharing most of their ingredients, for example. Snad supports multiple cost centres, so you can see how each brand performs on its own: what it consumes and what it earns. That financial separation is essential for judging whether an experiment worked and for directing investment toward the brand that is actually growing.

## Snad: the accounting and inventory system built for digital kitchens

Snad was built to be simple and fast, which is exactly what a cloud kitchen environment demands. By bringing purchasing, inventory and accounting together in one cloud platform, it gives you full control from wherever you are. Track daily sales, monitor payroll spend through the HR module, and confirm that every SAR is going where it should. With Snad, your cloud kitchen stops being just a place where food is cooked and becomes a business run with real digital discipline.

## Tax compliance and e-invoicing in a cloud kitchen

Selling digitally does not change your tax obligations. First rule: VAT is calculated on the value of the supply to the customer, not on the net amount the platform transfers to you after deducting its commission. That confusion is the single most repeated error cloud kitchens make on their returns.

| Item | Official rule | What it means for your kitchen |
|---|---|---|
| Tax rate | 15% on most goods and services | Applied to the meal price shown to the customer |
| Mandatory registration | Revenue exceeding SAR 375,000 over 12 months | Add up sales across all platforms combined, not platform by platform |
| Voluntary registration | Revenue between SAR 187,500 and SAR 375,000 over 12 months | Worth weighing up when you are buying major kitchen equipment |
| Filing frequency | Monthly for revenue above SAR 40,000,000, quarterly below that | Most cloud kitchens sit in the quarterly bracket |
| Filing and payment deadline | Within the month following the end of the tax period | Schedule your internal close a week ahead of it |
| Late filing penalty | No less than 5% and no more than 25% of the tax that should have been declared | Delay costs more than any operating line item |
| E-invoicing — Wave 25 | Taxable revenue exceeding SAR 187,500 during 2022, 2023, 2024 or 2025 | Integration with the Fatoora platform by 1 February 2027 at the latest |

The Zakat, Tax and Customs Authority (ZATCA) also permits cash-basis accounting for businesses whose annual supplies — past or expected — do not exceed SAR 5 million. That is a practical option for a kitchen that receives platform transfers well after the sale date. Source: the official ZATCA pages, accessed 1 August 2026. Full preparation details in [the Wave 25 guide](/zatca/wave-25).

## Reconciling delivery platforms: from gross order value to the SAR that lands in the bank

A platform report is not a bank statement, and the amount deposited in your account is not your sales figure. The gap between them is made up of the commission agreed in your contract, additional service fees, cancelled orders, refunds, and the timing difference between the order date and the transfer date.

Adopt a fixed weekly reconciliation cycle:

- Record sales at the gross value the customer saw, and record the commission as a separate expense rather than a deduction from revenue.
- Match the **order count** first between the platform report and your system, then match the amounts. A count discrepancy surfaces missing orders faster than a SAR discrepancy.
- Open a clearing account for each platform within receivables, and close it when the transfer arrives. Whatever is left sitting in it is your uncollected balance.
- Request a tax invoice for the commission and file it with your purchase documents; the correct document is a precondition for any tax treatment later on.
- Treat an order cancelled after preparation as direct inventory waste, not as a shortfall in sales.

Recording sales net of commission looks easier, but it hides the true size of your business and distorts every ratio you rely on: food cost percentage rises artificially because the denominator is smaller than it really is.

## The standard recipe card: building an item's real cost

Cost estimated by feel loses money by accumulation. Every item on the menu needs a written recipe card specified in grams, updated whenever a supplier price moves.

| Cost component | Where the number comes from | Common mistake |
|---|---|---|
| Raw material | Weighted average purchase price from supplier invoices | Using a purchase price that is months out of date |
| Yield ratio | Ready-to-use weight ÷ raw weight | Ignoring trim loss on chicken and produce |
| Sauces and add-ons | A sub-recipe costed independently per 100 grams | Burying them in "general overheads" |
| Packaging | Container, lid, bag and label | Costing it per order instead of per item |
| Direct utilities | The item's share of the gas and electricity bill | Leaving it out of the meal price altogether |

Once the card exists, compare theoretical consumption (meals sold × recipe quantity) against actual consumption from the stock count. The variance is your read on discipline inside the kitchen: portions larger than the standard, preparation errors, or inventory walking out the door. Recording purchases and counts in the [inventory module](/inventory) turns that variance into a number you can measure every month instead of an impression you argue about.

## The operating metrics you review weekly, not annually

A cloud kitchen runs on a thin margin at high speed. Reviewing the numbers once a year means discovering the loss long after the window to correct it has closed.

| Metric | How it is calculated | Review cadence |
|---|---|---|
| Food cost percentage | Cost of ingredients consumed ÷ net sales | Weekly |
| Packaging cost per order | Total packaging expense ÷ number of orders | Weekly |
| Item contribution margin | Selling price − (ingredients + packaging + your contracted commission) | At every menu change |
| Prime cost | Food cost + labor cost | Monthly |
| Waste ratio | Value of spoilage and returns ÷ value of purchases | Weekly |
| Inventory turnover | Cost of goods sold ÷ average inventory | Monthly |
| Average order value per brand | Total sales ÷ number of orders | Weekly |

Start with two metrics and stay with them for eight weeks before adding any others; a dashboard nobody reads is worse than no dashboard. Work out your monthly break-even after loading in rent, payroll and subscriptions using the [break-even calculator](/tools/finance/break-even-calculator), and keep an eye on fast-spoiling ingredients through the [inventory turnover calculator](/tools/inventory/inventory-turnover-calculator).

## Closing the month in a cloud kitchen: the order of operations

A chaotic close turns the tax return into guesswork. Run the steps in this sequence, because each one feeds the next:

- Take a physical stock count on the last working day, covering packaging and not just food.
- Enter every supplier invoice under its correct date, including the ones that arrived late.
- Reconcile each delivery platform's reports and close its clearing account.
- Calculate actual consumption, compare it against theoretical, and document the waste variances.
- Book payroll, allowances, rent and subscription costs.
- Review total sales and output tax before preparing the return.

Separating brands inside a single kitchen starts at step one: one stock count, but consumption charged to each brand's cost centre according to its own recipes and sales. Without that, you will know the kitchen's total profit and never know which brand is drawing from the other.

## Labor cost in a cloud kitchen: from salary to the true hourly cost

Labor is the second largest line after food, yet most cloud kitchens manage it with a single number: total payroll. The useful number is the loaded hourly cost of each work station in the kitchen (prep, cooking, order assembly), and it is built on statutory rules rather than estimates.

| Item | Statutory rule | Impact on your cloud kitchen |
|---|---|---|
| Working hours | No more than eight hours a day or 48 hours a week | Build shifts around the demand peak, not around a fixed office day |
| Ramadan hours | Reduced for Muslim workers to six hours a day or 36 a week | Production capacity falls in the month when evening demand rises |
| Rest during the shift | A worker may not work more than five consecutive hours without a break for rest, prayer and meals | Fix the break periods into the written shift roster |
| Presence at the workplace | No more than twelve hours a day | A split shift counts toward this limit |
| Overtime rate | The hourly wage plus 50% of the basic wage | Price every extra peak hour before you approve it |
| Occupational hazards branch | 2% of the contributory wage, borne by the employer; the branch covers workers regardless of nationality | Added to the cost of every person in the kitchen |
| Unemployment insurance (Saned) | 1.5% split equally between employer and subscriber | Applies to Saudi employees |

Sources: the Ministry of Human Resources and Social Development and the General Organisation for Social Insurance (GOSI), accessed 2 August 2026. Before you approve any extended shift, cost it with the [overtime calculator](/tools/hr/overtime-calculator), and book salaries and allowances monthly in the [payroll module](/payroll) so they land inside your item cost rather than outside it.

## Channel pricing: why one price cannot work across every sales route

The same item does not carry the same cost in every channel. An order through an aggregator carries the fees agreed in your contract; an order through your own app carries payment gateway fees and customer acquisition cost; a pickup order carries lighter packaging. Set one price across all of them and you will be making money in one channel and losing it in another without knowing which is which.

Start from a target contribution margin per channel, then derive the price from it:

- Calculate each channel separately: selling price − (ingredients + packaging + that channel's contractual fees).
- Put your best price in the channel you own, not in the one that costs you the most.
- Revisit channel pricing every time supplier prices move materially, not once at signing.
- Before any promotion, establish who absorbs the discount — you or the channel — and take the contract text as the reference, not a phone call.
- Split sales reporting by channel inside your system so the difference shows up as a number rather than an impression.

The working rule: an item with a negative contribution margin in one channel drains the profit of every other channel, and the more of it you sell the wider the loss gets.

## Purchasing and receiving: setting the reorder point for perishables

A cloud kitchen buys more frequently than a traditional restaurant and in smaller quantities, which makes purchasing errors routine rather than exceptional.

- Calculate a reorder point for each item: (average daily consumption × lead time in days) + safety stock.
- Express safety stock for fresh items in days rather than quantities: one day for fast-spoiling fresh produce, a longer horizon for frozen, dry goods and packaging.
- Weigh what you receive and compare it against the invoice before signing; a weight shortfall at receiving is not recoverable afterwards.
- Match the invoice price against the price approved on the purchase order, and log any difference as a separate item to review with the supplier monthly.
- Approve a backup supplier for every critical item, and give them a small order each quarter so they stay ready when supply breaks.

Linking the purchase order to the goods receipt and then to the invoice in the [purchasing module](/purchases) turns these controls into a daily routine instead of an intention, and the [reorder point calculator](/tools/inventory/reorder-point-calculator) will set the order thresholds for each item.

## Working capital: the gap between the sale date and the collection date

A cloud kitchen appears to sell for cash while actually collecting on credit. The sale happens today; your transfer from the channel arrives according to the period stipulated in your agreement. Payroll and rent, meanwhile, fall due on fixed dates and do not wait.

| Item | Direction of cash impact | Practical action |
|---|---|---|
| Uncollected channel receivables | Ties up cash | Track the age of every clearing balance weekly |
| Supplier payment terms | Frees up cash | Negotiate them in writing and lock them into the purchase order |
| Excess dry goods and packaging inventory | Ties up cash | Tie purchasing to the reorder point, not to supplier offers |
| Payroll, rent and subscriptions | Fixed obligation | Include them in a three-month cash forecast |
| VAT payable | Recurring obligation | Separate it from the operating balance as soon as it is collected |
| In-channel promotion spend | Fast-moving variable | Tie the spend to order count, not to a flat monthly budget |

Update the cash forecast on the same day every week. Kitchens that get into trouble rarely do so because their margin is negative; they get into trouble because the cash arrived after the obligation was due.

## The expansion decision: another brand or a second location?

Adding a third brand inside the same kitchen costs less than opening a second location, but it is not always the more profitable move. Each option has its own precondition:

- **An additional brand in the same kitchen:** works when kitchen capacity at peak hours is still underused, and when the new brand shares most of its ingredients with your current menu. Otherwise you are adding items and waste without adding orders.
- **A second location:** works when the reason you are losing orders is distance or delivery time rather than pricing, and when your first location has been delivering stable operating profit over consecutive months rather than one good month.

Before deciding, rebuild your break-even on the full new picture: rent, payroll, equipment and subscriptions. Then answer a single question — how many additional daily orders are needed to reach it, and is there anything in your current sales data suggesting that demand exists? Expanding without that number is an emotional decision in an operational wrapper.

## Frequently asked questions

### Can I run payroll for my kitchen staff through Snad?

Yes. Snad includes a full HR module for managing employee files, salaries and allowances in line with the Saudi Labor Law.

### Is VAT calculated on the full order value or on the amount left after the platform's commission?

VAT is calculated on the value of the supply as displayed to the customer, at 15%, per the Zakat, Tax and Customs Authority (ZATCA). The platform commission is a separate expense line with its own supporting document. Recording sales net of commission understates your declared revenue and creates variances that are hard to explain later.

### When does my cloud kitchen have to register for VAT?

Registration is mandatory once revenue exceeds SAR 375,000 over twelve months, and voluntary between SAR 187,500 and SAR 375,000, per ZATCA (accessed August 2026). Measure the threshold against your combined sales across all platforms, not platform by platform.

### Does Fatoora integration apply to small kitchens?

ZATCA has announced that Wave 25 of the integration phase covers taxpayers whose taxable revenue exceeded SAR 187,500 during 2022, 2023, 2024 or 2025, with integration required by 1 February 2027 at the latest; the authority notifies targeted taxpayers in advance. That threshold puts a large share of cloud kitchens inside the scope.

### How often do I file the tax return, and when?

Filing is monthly for businesses with revenue above SAR 40,000,000 and quarterly below that, and the return is filed and paid within the month following the end of the tax period. The late filing penalty is no less than 5% and no more than 25% of the tax that should have been declared.

### Can I use cash-basis accounting for my cloud kitchen?

ZATCA permits cash-basis accounting for businesses whose annual supplies, past or expected, do not exceed SAR 5 million. It suits a kitchen that receives platform transfers weeks after the sale date, but it is a decision to review with your accountant before applying it.

### How do I split ingredient cost between two brands operating from the same kitchen?

Not by estimate, and not by sales share alone. Attach a recipe card to every item, calculate theoretical consumption for each brand from its actual sales, then charge the stock count variance to the brand that produced the waste wherever it can be traced. Where it cannot, charge it to a shared cost centre and review that centre monthly.

### What is a kitchen worker owed for an overtime hour?

The employer pays the hourly wage plus 50% of the basic wage for each overtime hour, per the labor law published on the Ministry of Human Resources and Social Development website (accessed August 2026). A worker may also not remain at the workplace for more than twelve hours a day — a constraint to keep in mind when designing evening peak shifts.

### How many working hours are permitted in Ramadan inside a cloud kitchen?

Actual working hours for Muslim workers are reduced in Ramadan to no more than six hours a day or 36 hours a week, per the Ministry of Human Resources and Social Development. In practice that means lower production capacity in a month when evening demand rises, so plan shift counts and available menu items before the month starts rather than after.

### Does a non-Saudi kitchen worker get registered with social insurance?

Yes, under the occupational hazards branch. The General Organisation for Social Insurance (GOSI) states that this branch applies to workers regardless of nationality, at a contribution rate of 2% of the contributory wage borne entirely by the employer. The pensions branch and the unemployment insurance branch (Saned) apply to Saudi employees.

### Should I sell the same item at one price across all channels?

Not necessarily. Each channel carries different fees, packaging costs and customer acquisition costs, so calculate contribution margin per channel: selling price minus (ingredients + packaging + that channel's contractual fees). Holding the price constant while costs differ means profit in one channel is covering a loss in another without you knowing which is which.

### How do I set the reorder point for fresh ingredients in the kitchen?

Use the formula: (average daily consumption × lead time in days) + safety stock. For perishables, express safety stock in days rather than quantities, and extend it for frozen goods, dry goods and packaging, because storing them costs less than halting preparation.

### When is opening a second kitchen the right call instead of adding a new brand?

A second location is worth considering when the reason you are losing orders is distance or delivery time rather than pricing, and when your first location has delivered stable operating profit over consecutive months. Adding a brand inside the same kitchen works when peak capacity is still underused and the new brand shares most of its ingredients with your current menu. In both cases, rebuild your break-even on the full new picture before committing.

---
## About the publisher
**Snad (سند)** — a private Saudi software company
based in Riyadh, founded 2025. Legal form: Sole proprietorship.
Commercial registration: 7038154642
VAT number: 310959226500003
Only official domain: snad.io
> Snad is a private commercial business-management platform. It is not a
> government body, not a bank, and not a government services portal, and it
> is not affiliated with any government entity. Any site or app with a
> similar name is unrelated to Snad.