How to Open a Restaurant in Saudi Arabia: The Complete Guide from Idea to Day 90

You can open a restaurant with genuinely great food and close it a year later. Food is one thing; the numbers are another. The lease you signed decides how many tickets you need every single day, the menu you wrote decides how much of each ticket you keep, and the system you installed decides whether you even know those two numbers. This is a guide to opening a restaurant in Saudi Arabia from the operations side: idea to day 90 of trading - the decisions that lock each other in, why the licensing order saves you months, how to turn rent into a daily ticket count, what to install before you open rather than after, and how to read your first three months in numbers you can actually act on.

Every step here ends in a number you can write into your own file or a decision you can make today. The figures you will see are worked examples with clean round numbers so you can redo the math with yours. The regulatory side is described in shape only, because it varies by municipality, activity, and area, and it changes. Rules move, so check the official source before you build a decision on any number here.

Before the first expense: the chain where each link locks the next

The concept decision is not a matter of taste, it is the first number in the equation. The concept sets your average ticket, and a fast burger counter and a full table-service dinner spot are not remotely the same number. The average ticket then decides how many sales you need to cover your rent, and that decides which locations can actually deliver that volume and which ones never will, no matter what you do to them.

The same chain keeps running. The average ticket sets the sensible menu size. A small ticket cannot carry 60 items, because every extra item drags in extra ingredients, more fridge space, another prep station, and waste on anything that does not turn over fast. Menu size then sets the number of kitchen stations and the kitchen footprint, the kitchen sets total floor area, and floor area sets the rent line. That is why changing the concept after you sign the lease costs you twice: once for the rework, and once for the months you paid rent while you did it.

Here is a worked example so you can watch the chain run. Say you set a target average ticket of 45 and you sign a lease at 20,000 a month. If you have decided rent should not exceed 10% of sales - and that is a ceiling you choose in your own plan, not an official rule - you need 200,000 a month in sales, which is 6,667 a day, which is roughly 148 tickets a day. On a 12 hour trading day, that is 12 tickets an hour, non-stop. Now go sit in the location for an hour at peak and count people yourself. Can this spot produce 12 tickets an hour? If the answer is no, the problem is not the marketing you will do later. The problem is a lease you have not signed yet.

Before you spend on design, fit-out, or a single piece of equipment, these need to be written down on one page and you need to believe them:

• The format: full dining room, takeaway and delivery, or a delivery-only kitchen with no seating. Each one has a completely different fit-out cost, licensing path, and daily operation.
• Your target average ticket, as one number and not a wide range. Every calculation after this hangs off it, and a wide range makes it very easy to lie to yourself.
• Your opening menu item count, plus a separate list of what you intend to add after three months. Do not launch that second list on day one.
• Your target food cost percentage of the selling price, written as a percentage and not as a general feeling that the margins look fine.
• Your rent ceiling as a percentage of expected sales, with the daily ticket count that ceiling produces written next to it.
• Your full monthly fixed costs: rent, payroll, utilities, subscriptions, maintenance, marketing. This one number is the basis of your break-even and every decision after it.

The format you pick changes which guide you even need. If the idea leans more coffee and pastry than food, the fit-out and daily operation are different and you will find them in the guide to opening a cafe in Saudi Arabia. If it is pure delivery with no dining room, the space, staffing, and channels change completely and that lives in the cloud kitchen guide. If it really is a full dining room, you are buying service, tables, and delivery at the same time, and that is what shapes the full restaurant system you need from day one. The difference between the three is not the food. It is what you buy, who you hire, and where you sell from.

Opening a restaurant in Saudi Arabia: from idea to the first invoice

The sequence below is ordered by dependency, not by importance: each step needs the output of the one before it, so running them in order saves you review cycles and rework. Timelines vary by city, municipality, site condition, and contractor, so do not take a duration estimate from any guide, including this one. Ask the authority and your contractor for real timelines for your case and plan on those.

1. 1
   Lock the concept and the number

   Write down the format, the target average ticket, and the opening menu item count. Do not move past this until all three are on paper, because every step after it branches off them and cannot be calculated without them.

2. 2
   Register the entity under the right activity

   A commercial registration with an activity that actually covers what you intend to do, plus the related registrations with the relevant authorities. The activity on the registration is the reference for everything you apply for afterwards, so a mistake there sends you back to the start after you have already spent.

3. 3
   Verify the site before you sign

   Before you sign the lease, confirm the location can be licensed for your activity in terms of permitted use, technical requirements, ventilation, and exits. Tie the large payment to the licence being issued, and put a clause in the lease that covers a refusal.

4. 4
   Run the licences in sequence

   The shop licence needs an attested lease and a site that meets the requirements, and the food safety and civil defence tracks have their own paths and inspection points. Requirements differ by municipality, activity, and area, so check the Balady platform for your specific case instead of relying on a summary.

5. 5
   Design the kitchen around the menu, not the reverse

   Map each item from fridge to station to pass and count its steps. Any item that needs a station of its own while you expect it to sell less than the rest is your first candidate for deletion, and the cheapest moment to delete it is before you buy its equipment.

6. 6
   Build the menu with its cost attached

   Every item enters with a recipe, quantities, and supplier prices, and from those you get its cost and its percentage of the selling price. Items whose cost you do not know should not be priced by guesswork and should not be on the opening menu.

7. 7
   Install the systems and run them in test mode

   POS, e-invoicing, inventory, permissions, and printers should be live and tested on the actual hardware in the actual location at least two weeks before opening, not on opening day and not the week before.

8. 8
   Open with a soft opening

   Run a limited invite-only service at half capacity with the full menu, and measure prep time per station and table turn time. Adjust the menu and the stations on what the test shows, then open properly.

Entity and licences: every document needs the one before it

The trouble with licensing is rarely complexity. It is almost always order. Each authority wants the output of another one: the activity on your commercial registration governs what you can even apply for, an attested lease is a condition inside the shop licence path, and the shop licence hangs on the site meeting technical and health requirements that get inspected on the ground after fit-out. Start from the wrong end, or spend on fit-out before confirming the site works, and you go two steps back while the rent keeps running.

The most expensive mistake at this stage is signing a long lease before confirming the site itself accepts your activity. A location can be commercially excellent and still be unusable as a restaurant because of permitted use, the extraction and ventilation route, the emergency exit, parking, or kitchen drainage. The landlord is not responsible for that and is not obliged to give anything back. You are. Verify first, then sign.

Site and rent: turn the lease into a ticket count

The lease you sign is not a monthly amount, it is a commitment to a daily ticket count you have to hit every day for the rest of the term. The only honest way to judge a location is to convert its rent into that number and compare it against the actual foot traffic you can see with your own eyes, on that street, at that hour.

Back to the worked example: 20,000 rent, a 10% ceiling, a 45 average ticket, and the answer was 148 tickets a day. Suppose you sit in the location and conclude that 90 tickets is the realistic maximum. You have exactly three ways out. Lower the rent, with a smaller unit, a different street, or a negotiation. Raise the average ticket, through a different menu, add-ons, and pricing structure, not just higher prices. Or open an additional channel that sells from the same kitchen without adding rent. If you pick none of those, you have automatically picked a fourth: opening 58 tickets short every day from day one.

The third option is the one most people forget. The same kitchen at the same rent can serve the dining room, delivery, and pre-orders at the same time. Extra channels do not raise your rent, but they do raise operational complexity if each one lives on its own tablet with its own menu. Bringing your sales channels onto one screen puts every order into the same kitchen in the same queue, instead of leaving you with three screens and three menus that never quite match and nobody knowing which one is right.

Startup cost: the two lines almost everyone forgets

Fit-out cost varies enormously by city, size, site condition, and whether you are starting from a shell or taking over a space that already has a kitchen, so no general figure you read anywhere is safe to budget against. What is useful is the structure of the budget: pull real quotes for every line from your own suppliers, then add two lines that never appear in a quote.

• Fit-out and utilities work: driven by the condition of the site, and the most volatile line in the whole project. Get at least two quotes against the same written specification so they are actually comparable.
• Kitchen equipment: bought against the opening menu only, not the menu you are dreaming about two years from now. A machine that runs twice a week costs you twice, in price and in floor space.
• Furniture, facade, and signage: driven by the seat count your table-turn math produced, not by the space available. Empty floor is cheaper than a seat nobody sits in.
• Systems and hardware: POS, printers, network, kitchen screen. You have a one-time hardware cost and a recurring monthly subscription, and they belong on separate budget lines because they behave differently.
• Licences, fees, and attestation: they vary by activity and municipality and they change, so ask what they currently are for your case instead of copying a figure from somewhere else.
• Opening inventory: the first fill of the store and the fridges, calculated from your recipes and expected sales, not from guesswork or from whatever the supplier is pushing.

The first forgotten line is the cost of the fit-out period itself. From the day rent starts accruing to the day you open, you are paying rent, paying a team you are training, paying utilities and permits, against zero sales. The second is operating reserve after opening. A restaurant rarely hits its target sales in month one, and the reserve is what lets you keep going without cutting ingredient quality or letting go of a team you just spent weeks training.

How much reserve? Tie it to your fixed costs, not to your capital. Worked example: fixed costs of 80,000 a month, made of 20,000 rent, 45,000 payroll, and 15,000 for everything else. A three month reserve is 240,000 set aside and not spent on fit-out no matter how tempting it gets. And if setting that aside forces you to cut the kitchen itself, the project is bigger than your budget, and the fix is to shrink the scope, not to shrink the reserve.

The menu: cost is calculated before the price, not after

Every menu item is a small equation: quantities times supplier prices gives you cost, and cost divided by price gives you food cost percentage. Without that equation for every item you do not have a menu, you have a list of names and prices. The nastiest scenario is that your best selling item is also your worst percentage, so sales climb while what you keep shrinks, and you go looking for the problem in the wrong place. The full calculation is in the recipe cost and food cost guide.

Opening menu size is a financial decision, not a hospitality one. Every extra item drags in an ingredient you can only buy by the case, fridge space, waste when that ingredient does not turn over, longer training, and slower prep at peak. Start with a menu you can execute under pressure, then after two months rank your items by sales and profitability and cut what does not earn its place. That is menu engineering, and it only works once you have real sales data from your own restaurant.

In Saudi Arabia menu prices are displayed inclusive of VAT, so the price the customer sees is the price they pay, and the tax is extracted from inside that amount when the invoice is issued. Keep that in mind while pricing, and keep something more important in mind too: the same item at the same price does not leave you the same amount on every channel.

This table is not telling you to drop the delivery apps. It is telling you to know the difference before you price. 45 from delivery beats zero when the kitchen is idle in a dead hour, and loses badly to 70 when it takes the place of a dining room order at peak. The right move is to know the number per channel and decide on it, and to separate channel pricing when the gap is wide. How to handle and improve those commissions is covered in managing delivery app commissions.

Systems get installed before opening, not after

The expensive idea is: let's open first and sort the system out later. The problem is that your first month is the most valuable data the business will ever produce. It tells you what actually sells, what your kitchen actually consumes, and what your real food cost percentage is rather than the assumed one. If the system was not set up during that month, the data is gone and does not come back, and nobody in practice goes back and reconstructs three months of invoices and stock movements.

E-invoicing is the clearest case. Every invoice you issue has to be compliant from day one, because there is no way to go back and fix invoices that were issued wrong. The requirements in Saudi Arabia run in two phases, a simplified invoice with a QR code for sales to individuals, and integration with the Fatoora platform. The covered groups, the timing, and the details are published by the Zakat, Tax and Customs Authority and they change, so check them for your own case rather than relying on a summary. What matters operationally is that the compliant invoice issues automatically with every paid sale, which is what Loqma does, with voids and returns automatically issuing credit notes, instead of leaving it as a manual step a cashier forgets in a rush.

The other things that need to be ready before the first invoice: recipes linked to menu items so stock deducts itself on every sale instead of you counting the fridge every night, permissions set so that voids, discounts, and refunds cannot happen without a logged reason and a named person, and a shift close from day one so you have a clear gap between expected and actual cash every single night. Whatever you do not measure from day one becomes a habit that is hard to change two months in. The shift close mechanics are in the X report and Z report guide, and the first count after opening is in the restaurant stock count guide.

And one test is worth running before you even choose a system: ask the vendor to unplug the internet in front of you and keep selling, print an invoice, and close a shift. If the system stops or the order disappears, that is your answer. The restaurant sells during the rush and the router does not ask permission. The rest of the selection criteria are in how to choose the right POS, and the difference between a system that takes a cut of your sales and one on a flat subscription is in commission versus flat subscription.

• The menu is built in the system with its prices, items, and modifiers, and at least one test invoice has been printed from it.
• Recipes are entered for every item that will sell, and supplier prices are current as of today, not as of the first quote.
• Printers are routed to the right stations, grill to grill and drinks to drinks, and tested with one order containing items from two stations.
• Every employee has permissions under their own name, and voids and discounts require a reason and an approval.
• Every cashier has run test invoices on both card and cash, and has personally completed a full shift close at least once.
• The internet cut test has been run on the actual hardware in the actual location, not on a demo device in an office.

The team: staff for the peak, not the average

Headcount is not calculated on the daily average, it is calculated on the single busiest hour. If your peak is two hours in the evening carrying half the day's sales, coverage is built around those two hours and the rest becomes shorter shifts or prep work. The common mistake is everyone arriving together and leaving together, so you pay wages during empty hours and then collapse during the rush, and both of those come out of your pocket.

Training before opening is not a luxury. Every cashier runs a set of test invoices across payment types, and every kitchen member walks each item's path against the clock. Hiring rules, contracts, and health certificates sit with their own authorities and those rules change, so go to the official source for each rather than trusting a summary. What belongs to us here is the operational translation: every employee gets an account in their own name with defined permissions, so any void, discount, or drawer open already tells you who did it and when, without anyone having to run an investigation.

Timing: open into a window where mistakes are cheap

The season you open in changes the size of your mistakes, not just the size of your opportunity. Open at the top of your strongest season with a brand new team and an unsettled kitchen, and the largest possible number of people form their first impression of you during your worst operational state, and a first impression costs more to repair than any campaign costs to run. The reverse also holds: open into a quieter stretch and the mistakes of the first fortnight land on fewer customers, and you go into the season steady with a kitchen that knows itself.

The seasonal patterns in Saudi Arabia are well known in shape. Ramadan inverts the restaurant day entirely, with compressed hours, a sharp evening peak, and different delivery behaviour. School holidays and summer shift traffic between residential neighbourhoods and destinations. Mild weather lifts demand for outdoor seating. But the size of each pattern differs by neighbourhood and by concept, so do not lean on general figures somebody published for somewhere else. Sit in the location across different days and hours and count the traffic yourself, and ask the neighbouring operators. After the first year, your own sales data becomes the most honest calendar you will ever plan against, and there is no substitute for it.

A soft opening before the real one is the cheapest test in the whole project: invite-only service, half capacity, full menu. Measure three things only: prep time per item under pressure, table turn time from seating to payment, and which station bottlenecks. You will usually walk out of it having decided to delete an item or two, and that decision alone justifies the exercise.

The first 90 days: from opening to a decision built on numbers

Opening is not the finish line, it is the first day your numbers become real instead of estimated. The first three months have exactly one job: find out whether the assumptions you built the project on were right, and if they were wrong, by how much and which lever you can pull. Anyone who coasts through this window without measuring discovers the problem in month seven, by which point the reserve is gone and the options have narrowed.

The first number to calculate after opening is break-even. Continuing the same worked example: 80,000 a month in fixed costs and a 30% food cost, which leaves you 70 out of every 100 in sales to cover the fixed side. Break-even is 80,000 divided by 0.70, which is 114,286, call it roughly 115,000 a month, which is 3,833 a day, which is about 85 tickets at an average of 45. Your plan called for 148. The gap between 85 and 148 is the gap between not losing money and making money, and that gap is what you work on every day instead of working on a general feeling that things seem fine.

Every profitability problem in a restaurant traces back to exactly three levers: ticket count, average ticket, and food cost percentage. Any fix you hear about is one of those three under a different name. Marketing moves ticket count. Add-ons, menu layout, and upselling training move the average ticket. Recipes, supplier prices, portioning, and waste move the cost percentage. The first thing you do at the end of month three is identify which lever holds your weakest number, and work on that one alone for a full month, instead of scattering effort across all three and moving none of them.

The most important comparison of your first month is theoretical stock against actual. The system knows you sold 400 burgers, the recipe says each burger takes 150 grams of beef, so you should have consumed 60 kilos. The count says 68. Those 8 kilos are not an accounting rounding you shrug at. They are either portions running heavier than the recipe, or prep waste, or short deliveries from the supplier, or issues going out unrecorded. Each cause has a completely different fix, and you cannot choose the fix until you can see the gap.

What things going well actually looks like at day 90 is not a feeling, it is four signals: sales above break-even by a margin that survives a weak month, actual food cost close to target with the difference explained rather than mysterious, a gap between expected and actual cash at shift close that is small and consistently the same size rather than random, and a menu that has had something removed from it - because anyone who has not cut a single item after three months almost certainly has not read their numbers.