SINGAPORE · PRACTICAL RESTAURANT GUIDE

Singapore Food Shop and Food Stall Licences: A Beginner Guide

Choose the appropriate Singapore food-business route, prepare papers and kitchen drawings, avoid application mistakes and follow a practical readiness checklist.

Choose a section in this guide

Start by describing the business, not by choosing the cheapest form

If you are opening a restaurant, a takeaway kiosk or a stall in Singapore, the first useful question is what activity you will carry out and where. A small counter is not necessarily a Food Stall, and selling through an app does not decide the licensing route. Write down the place, operator, food preparation and service arrangement before choosing an application.

This guide helps a beginner organise those decisions and avoid common preparation mistakes. It is not a replacement for Singapore Food Agency instructions or a complete legal assessment of a particular premises. We have not signed into your application account or tested every current portal screen. The examples are invented learning cases, not accounts of businesses we helped obtain approval.

You can read the route summary, choose the case closest to your situation, then work through the preparation checklist. The long sections are practical exercises and explanations of what to ask, not additional official document requirements. Where a rule, deadline or document matters, follow the current instruction for your actual application rather than treating a general article as permission to open.

Describe the activity → Confirm the official route → Prepare current evidence → Check the actual outcome
Original learning diagram: follow the arrows through the checks. Not an official form, kitchen plan or dashboard screenshot.

Food Shop, Food Stall and home-based food business are different routes

SFA's retail requirements distinguish a Food Shop, including restaurants and standalone takeaway kiosks, from a Food Stall operating within a food shop. A stall responsible for its own refreshment area can need the Food Shop route. Hawker-centre arrangements have additional distinctions. Confirm the actual arrangement rather than judging the licence by the size of the counter.

SFA's home-business guidance currently exempts qualifying home-based food businesses from an SFA licence, but food laws and restrictions still apply. They cannot provide catering, supply SFA-licensed food retailers, or sell ready-to-eat raw seafood. Food prepared at home cannot be sold at temporary fairs or supplied to their stallholders, even if the seller has a temporary-fair stall licence. Home use and platform onboarding are separate matters; an exemption is not unrestricted permission to operate any food business.

Translate your idea into a short activity description

“I want to sell food” leaves too much for another person to guess. A better description says whether you cook, reheat, assemble or only sell packaged products; whether customers eat there; whether the kitchen is standalone or inside another establishment; and who will run the operation. You do not need fancy terms. You need enough detail for the responsible authority to understand the proposed activity.

For an invented takeaway business, the owner writes that meals will be prepared in a standalone unit and collected by customers or delivery riders, with no dining seats planned. The owner then asks which route fits that arrangement. They do not choose Food Stall merely because there is a short service counter. This small clarification can prevent a wrong application from consuming time and money.

Keep the operator and the trading name separate

A restaurant sign can have a different name from the entity applying for a licence. The application needs the appropriate operator details, not a guess based on the name on a menu. Identify who will legally operate the business and who is authorised to submit on its behalf. Confirm the applicable access arrangements through the current official process instead of borrowing a friend's account because it is convenient.

Imagine two friends developing a noodle concept. One signs the lease personally while the planned operating entity is different. Before submitting, they need to resolve which details the actual application and supporting records require. Changing a logo does not solve an inconsistent applicant. Keep the question visible and obtain the appropriate advice rather than editing documents to make unrelated names appear identical.

Do not confuse a platform listing with food-business permission

A delivery platform has its own onboarding and account requirements. A listing or partner conversation does not establish that the food-business route and premises conditions have been satisfied. Equally, a licence does not automatically connect you to GrabMerchant or guarantee delivery demand. Make two separate work lists: one for the lawful operation of the food business, and one for the commercial platform setup.

Food Data Extractor does not apply for SFA licences. Its currently released extraction workflows relate to authorised Zomato and Swiggy use, not a Singapore licensing portal or automatic GrabMerchant extraction. The checklist on this page is only a learning aid. Ticking every box records your preparation while the page is open; it does not send an application or certify that a kitchen is safe.

Understand the stages without assuming a fixed opening date

The SFA application page describes review, premises preparation, required checks and payment stages. Its published initial review target is not a guarantee that the whole business can open within that period. The standard listed annual fees are SGD one hundred and ninety-five for a Food Shop and thirty-two for a Food Stall. Eligible hawker stalls and canteen food stalls in primary schools, secondary schools or junior colleges have a listed reduced fee of thirteen dollars a year. Check the applicable category; these fees are not the full cost of opening a restaurant.

The same page warns against duplicate applications and incorrect applicant or licence choices that require a fresh correct submission. Read current messages for response and payment deadlines. A portal acknowledgement, pending review, inspection arrangement and issued licence are different stages. Do not treat any unfinished stage as approval to operate.

Build a stage board in everyday language

A simple board might have planning, preparing the correct application, waiting for a response, correcting a request, arranging required checks and confirming opening conditions. These are your own project labels, not asserted official portal statuses. Put the exact official wording and reference beside the relevant item. That helps the team understand the work while preserving what the authority actually said.

For each stage, record what is known, what is missing and who will act next. “Waiting” by itself is not very useful. “Waiting for the official response to the submitted layout; owner checks the account and email; builder must not use an unconfirmed revision” describes the dependency. A small business can use a page of notes rather than expensive project software.

Separate application cost from opening cost

An official fee can be a small part of the money needed for premises, equipment, advice, training, deposits and operating cash. Do not make a complete opening budget by copying a licence fee from an article. Obtain actual quotes and confirm which expenses fit your situation. Mark unknown amounts as unknown, not zero. A low form fee does not mean the business can open cheaply or immediately.

For a fictional budget, the owner has four quoted items: equipment, furniture, a design service and initial stock. They also have unresolved premises work. Adding the four known quotes produces a partial budget, not a final total. The useful action is to identify and price the unresolved work before making commitments. No amount in that teaching exercise is an official Singapore requirement or a normal market price.

Before committing to a place, test whether it fits the operation

A premises can look attractive while being unsuitable for the activity you plan. Describe the cooking method, storage, washing, delivery collection and customer service needs. Ask the landlord and relevant authorities what use and conditions apply. A food licence question can sit alongside premises-use, building or other approvals; do not assume one document answers every part of the opening plan.

This guide does not list a universal set of permissions for every Singapore property. The practical lesson is to check the proposed activity against the actual place early. A lease agreement is an important commercial commitment, not a technical assessment of food workflow. Where the risk is significant, use an appropriately qualified adviser and obtain specific answers before spending money on irreversible work.

Walk the proposed food journey

Imagine a delivery arriving, a worker storing ingredients, another preparing a meal and a rider collecting the finished order. Point to where each action would happen. Then imagine dirty equipment returning for cleaning. If you cannot explain the flow without several activities occupying the same space at the same time, you have a question for the design review. The exercise identifies uncertainty; it does not establish compliance.

Do the walk with the actual people who will use the kitchen. A drawing can look tidy while leaving a worker no practical place for a container during service. Record those observations and discuss them before finalising equipment positions. Do not invent minimum dimensions from a blog or use a generic diagram as the construction plan. Obtain the current relevant conditions and professional input.

Review collection and service arrangements

A dine-in restaurant, a takeaway unit and a stall within a larger food shop have different everyday interactions. Ask how customers, delivery riders and staff will move, where orders wait and who controls shared areas. An informal promise from another tenant may not settle responsibility. Write down the proposed arrangement and ask for clarification where the boundary affects the application or safe operation.

A fictional stall owner expects to use the main operator's washing area and storage. Before designing the business around that assumption, they confirm the arrangement with the main operator and the relevant authority. They do not infer that everything outside the counter belongs to them. Clear boundaries protect both businesses and make it easier to answer a request for an accurate plan.

Prepare a private document pack that is easy to check

Use the document list supplied for the correct current route. The following folder method is our practical suggestion, not an official mandatory list. Create sections for operator details, premises records, drawings, staff or training evidence where requested, correspondence and payment records. A file belongs in the pack because it answers a current requirement, not because another restaurant uploaded it several years ago.

Keep identity and business documents private. This website does not need them to explain the process, and a community post should not contain them. When the official application requires a document, use the official submission route. If a consultant is involved, agree secure access and responsibility. Sending every file to everyone working on the project is not a useful shortcut.

Use a document register

For each required item, record its purpose, current version, owner and status. Status can be available, being obtained, needs correction or not applicable with a reason to confirm. This avoids a common beginner mistake: assuming a document exists because someone said they would obtain it. The register should link to the actual complete readable file, not only to an email saying that it will arrive later.

Suppose a premises record has two pages and the owner saves only the signature page. The filename might look correct, but the application can still lack the relevant information. Open every file and check it against the request. If you are uncertain whether a document is sufficient, ask specifically about the missing detail rather than uploading several unrelated files in the hope that one will work.

Check consistency without altering evidence

Compare the operator name, address, unit details and any relevant references across the form and records. If they differ legitimately, explain or resolve the difference through the correct process. Do not alter an official record to conceal a mismatch. A trading-name difference may need explanation, while a wrong entity can require a more substantial correction. The facts determine the response.

An invented example involves a drawing labelled Unit A while the premises record describes Unit B. The owner first checks whether this is a labelling mistake or a different place. They do not simply replace the letter on the drawing without confirming the actual measurements and boundaries. A tidy-looking pack is useful only if it describes the real proposed business.

Preview files before submission

Check that text can be read, every required page is present and the orientation is sensible. Confirm the current allowed formats and sizes in the official process. A document that opens on your phone may still be incomplete. Conversely, do not compress a file so aggressively that its details become unreadable. Readability is more important than making every file extremely small.

Use meaningful private filenames so the team can distinguish the current plan from an earlier version. A name such as layout revision three is better than final final newest, but the drawing itself also needs its appropriate version information. Preserve a copy of what was actually submitted. Otherwise, a later response can become confusing because the team is reviewing a different file from the one the authority saw.

Make the kitchen drawing explain the proposed work

The official retail guidance describes layout information needed for the relevant route. Use that current instruction for the drawing you submit. Our teaching diagram is only a way to understand relationships: activity description leads to a suitable route, which leads to the correct document and layout preparation. It is not an official sample plan and does not specify compliant dimensions or construction details.

Start with a short operational brief

Tell the person preparing the drawing what the kitchen will actually do. A café reheating bought-in products and a restaurant cooking a broad menu may need different arrangements. Include the main equipment, storage and service pattern you intend to use. If the menu is not settled, identify the uncertainty before the drawing is treated as complete. A design based on the wrong activity can be expensive to revise.

For a fictional lunch kitchen, the owner plans two hot dishes and drinks but later adds a much wider menu. Rather than assuming the existing layout still fits, the owner asks the designer and relevant authority whether the change affects the arrangement. This is the moment to resolve the question. Waiting until equipment is installed can reduce the available options and make correction more disruptive.

Agree which revision is current

Keep one agreed working revision and a record of changes. When a new plan arrives, compare it with the operational brief and the relevant request. Tell contractors which version is authorised for their work; an informal message containing an old image can create confusion. Preserve earlier versions for reference, but keep them clearly marked so they are not mistaken for the current plan.

Imagine the owner approves a revised collection counter while a supplier quotes equipment against the earlier plan. Before accepting the quote, compare the layout and dimensions with the intended arrangement. The issue is not whether either file looks professional. It is whether the quote, construction and application describe the same business. Resolve differences before they turn into paid work.

Prepare questions instead of guessing technical requirements

Ask which boundary, equipment and service areas the plan needs to show for your route, which current checklist applies and whether a proposed revision must be submitted. Do not ask only “Is this fine?” A specific question gives the reviewer enough information to answer. Keep the answer with the plan so the team can understand what was confirmed and what remains unresolved.

When a requirement is technical, use an appropriate professional. This beginner guide does not prescribe ventilation capacity, drainage, materials or food-safety limits. It helps you recognise that those questions exist and organise the evidence. A website checklist cannot inspect a physical kitchen, and an attractive image cannot certify that the proposed arrangement satisfies the applicable conditions.

Choose one responsible submitter and track the actual application

Before anyone presses submit, agree who is responsible, who checks the information and where the reference will be kept. If an adviser or partner is submitting, confirm that the arrangement and account access are appropriate. Do not share personal credentials or OTPs. The responsible person should be able to see official messages and act on them, not merely create an application and disappear.

Review the route, operator details, premises and document pack together. Check whether a submission already exists before creating another. If a teammate says they applied but cannot provide a reference, investigate the existing account or official support route. Another submission is not a reliable way to find out what happened to the first one.

Record evidence of submission

Keep the acknowledgement, reference, submitted files and relevant date privately. These records help you ask a precise status question later. They do not themselves prove that the licence has been issued. A novice can avoid confusion by writing “application submitted; outcome pending” rather than “licence done” after the first acknowledgement arrives.

Make the monitoring plan practical. Decide who will check the official account and communication channels, and who takes over if that person is unavailable. An unread request can hold up work even when the original application was carefully prepared. Do not invent your own response deadline; record the actual deadline in the official message and allow time to obtain a missing document.

Pay through the correct route and preserve the receipt

When payment is required, follow the current official instructions and verify the reference. Keep the receipt connected to the application. A payment screenshot without a reference can be hard to match later. Do not pay an unsolicited request merely because it uses a familiar business name or arrives while you are expecting an official message.

Separate a consultant's invoice from an official fee. Ask what each payment covers and whether further work is included. A service provider can help prepare an application, but paying that provider does not mean the authority has approved it. In a budget or project note, label the type of payment clearly so a teammate does not mistake commercial work for a completed licensing stage.

Respond to a correction request without creating more confusion

Read the complete official message before editing files. Identify whether it concerns the chosen route, applicant, premises, drawing, missing evidence or another issue. Write down the exact request and deadline. If the meaning is unclear, use the official clarification channel with the application reference. A rushed guess can replace one problem with another.

Use a correction log

A useful log has the requested item, proposed response, evidence, owner and completion status. It need not be complicated. If the request asks for an updated drawing, record which revision will be sent and who checked it. If it asks for a missing record, record who is obtaining it. This helps the submitter confirm that every part of a multi-item request has been addressed.

For an invented case, an owner receives three requests: clarify the operating entity, supply a complete premises record and revise the layout label. They assign each item separately. The owner does not upload a revised drawing and assume the other two questions disappeared. After preparing the response, a second person compares it with the original request and checks that the files are the intended versions.

Do not repair a wrong route with unrelated attachments

If the underlying applicant or licence type is wrong, more documents may not solve it. Follow the current SFA instruction for that situation and ask how to handle the existing submission. Do not duplicate applications blindly or imply that all mistakes can be edited in place. The official process, not the convenience of your folder, decides the appropriate correction.

Keep any replacement submission connected in your private notes to the reason it was needed. Mark the status of the earlier one accurately. That avoids later confusion when a teammate sees two references and does not know which is active. A correction should make the story clearer, not leave several competing versions of the business in circulation.

Confirm that the response was received

After responding, save the relevant acknowledgement or visible confirmation through the official process. Do not assume that a file sitting in a local folder has been uploaded successfully. If the outcome is uncertain, check the actual account or ask support before repeating the action. Record what is known and what needs confirmation rather than declaring the issue resolved prematurely.

A missed deadline or lapsed application may need a different response from a minor correction still within time. Use the current message and official guidance. This article does not promise that an expired request can be reopened or that a payment will be refunded. Those are case-specific matters. Clear records help you ask for the correct next step without guessing.

Prepare for required checks, then confirm the conditions for opening

Use the inspection or other check arrangements instructed for your actual application. A photograph, virtual review or premises visit has a specific purpose and scope; do not assume they are interchangeable for every business. The current official process determines what is required. Prepare accurate evidence and make sure the premises shown matches the proposed operation and current plan.

Assign someone who understands the application and the kitchen to coordinate the required check. Keep relevant records accessible privately. If a reviewer identifies an issue, record the action and follow-up needed. Do not hide a discrepancy by photographing only the most attractive part of a room. The goal is a business that can operate appropriately, not a persuasive image.

Keep marketing separate from permission

An opening announcement can create pressure to rush unfinished work. Use a provisional internal schedule until the necessary conditions are confirmed. If a public date must change, communicate it honestly. A delivery listing, social media campaign or booked photographer does not settle the licensing position. Avoid taking commitments that depend on permission you do not yet have.

For a fictional café, the owner planned a launch before a required stage was complete. The useful response is to review the dependencies, contact the relevant official channel and revise the commercial plan where needed. The owner should not infer permission from silence or from the fact that equipment has been paid for. Money spent is not an approval signal.

Make an opening decision record

Before operating, record the licence or other applicable outcome, any conditions and unresolved issues, with the evidence used. The person responsible for the business should understand what has been confirmed. If another permission or premises issue remains, keep it separate and obtain the required answer. This record is a practical management aid, not a substitute for the actual licence or professional advice.

Check that the name, premises and activity covered match the intended operation. If a business has changed since the application, ask whether updates are required. Do not assume that the outcome for one unit or operator covers a different location or entity. A clear opening record is particularly useful when several people have handled different stages of preparation.

Case one: a standalone takeaway counter

A fictional owner wants to prepare lunch boxes in a small standalone unit. There are no dining seats, and most customers will order through an app. The owner initially calls the unit a stall in everyday conversation. After checking the official route summary, they recognise that the ordinary label does not decide the licence and ask about the Food Shop arrangement for the actual premises.

The owner prepares an activity description, checks the operator identity and obtains the applicable document list. They ask the designer to show the proposed preparation, equipment and collection arrangement using the required plan details. They separate the SFA work from platform onboarding. The example teaches a route decision; it does not promise that every similar unit will receive the same outcome.

Where the owner could go wrong

Choosing the smaller fee without checking the route would be one mistake. Submitting in a friend's name while planning a different operator would be another. Building around an unconfirmed layout and opening because a platform conversation went well would add further risks. Each mistake comes from treating a convenient signal as an answer to a different question.

A better sequence is describe, confirm, prepare, submit, respond and verify the outcome. The owner can work on a menu and cost model in parallel, but should keep unresolved premises or licensing issues visible. A commercial plan should allow for uncertainty without disguising it. The successful learning outcome is an organised set of questions and evidence, not a claim that this fictional café has been approved.

Case two: a stall inside a larger food shop

A fictional team plans to operate within an existing food shop. They need to understand the boundary between their operation and the main operator's shared areas. They ask who controls storage, washing and seating, and whether their proposed service arrangement affects the route. They do not assume that the main operator's licence automatically resolves every requirement for the new stall.

The team obtains the current route-specific instructions and checks which premises and layout records are needed. If a previous stall operator is involved, they clarify the change through the relevant official process. They keep the new operator details accurate. The purpose is to prevent ownership, shared-area and document assumptions from becoming an inconsistent application.

Use a shared-responsibility note

Write which tasks belong to the stall team, which belong to the main operator and which need official confirmation. A short note can cover access to shared records, layout preparation and communication with the authority. This is a management exercise, not a legal allocation of responsibility. Where an agreement or rule determines responsibility, use that evidence instead of the teaching note.

Before submitting, each responsible person checks the part they understand. The submitter then checks the complete pack against the current request. This avoids a common gap where every person assumes someone else supplied a shared document. If something cannot be obtained, identify it early and ask how the authority wants the issue addressed rather than silently leaving the field incomplete.

Case three: a home baker considering a larger business

A fictional home baker reads that qualifying home businesses currently do not need an SFA licence. They must still check the actual restrictions, food-safety duties and relevant home-use conditions. The exemption is not a general shortcut to catering or supplying shops. The baker should not expand into a prohibited activity because the original small operation did not require a licence.

When the baker considers a standalone retail unit, the decision changes. They describe the proposed new activity and premises and confirm the appropriate route rather than copying the home-business conclusion. They also check platform requirements separately. Growth can alter the questions that need answering, even when the products and trading name remain familiar.

Build an expansion question list

Ask what will change: the place, customer type, preparation scale, service method, staffing or supply channel. Then ask which authority and current guidance address each change. This is more useful than asking whether a home business can simply become a restaurant. The answer depends on the proposed operation, and a responsible guide should not hide that distinction.

Keep the existing activity within its applicable conditions while investigating the new model. Do not treat a future application as permission for a current expansion. Prepare cost and demand examples privately, but avoid public claims that the new operation is authorised before that is established. A careful transition protects the owner and the people who may rely on the business's statements.

After opening, keep the business record current

A licence is not the end of everyday responsibility. Keep official conditions, relevant records and contact details accessible to the people who need them. Assign someone to monitor renewal or other current obligations for the actual route. This guide does not invent a single calendar for every food business; use the terms and current guidance that apply to yours.

When the menu, operator, premises, layout or service arrangement changes, check whether the change requires action. A new sign is different from a new operating entity, and moving equipment can be different from changing a menu description. Describe the actual change and obtain the appropriate answer. Do not assume that a successful original application covers every future development.

Prepare a handover for staff changes

If the person managing the application leaves, hand over the reference, official correspondence, current licence record and pending actions securely. Do not hand over passwords through an informal chat. Use appropriate account-access arrangements and keep responsibility clear. A business can lose track of important messages if all knowledge sits with one person rather than in an organised private record.

A useful handover explains the current stage and unresolved questions in ordinary language. It distinguishes the current plan from older versions and states where the official evidence is stored. The new responsible person should not have to reconstruct the story from a pile of screenshots. This habit also helps when a consultant, partner or landlord joins the project later.

Practice reading an application problem

Imagine an invented project with a correct activity description, a readable plan and a submitted application reference. The owner's teammate says the licence is finished because the acknowledgement arrived. Ask what evidence would establish the actual outcome. The acknowledgement confirms submission; it does not by itself answer whether the required later stages are complete or whether the business may operate.

Next, imagine a correction request asking for two items. One is supplied and the other is still being obtained. What should the status note say? It should say that the response is incomplete and identify the remaining action and official deadline. It should not say “resolved” merely because one file was uploaded. This exercise teaches accurate status reporting rather than a particular portal button.

Finally, imagine that two people each submitted an application in different names. The next action is to identify the actual submissions and obtain official guidance on the correct applicant and handling of the duplicate. Another new application is not automatically the solution. Keep the references and explanation together so the issue can be resolved deliberately rather than creating an expanding trail of inconsistent forms.

Beginner questions

Can someone else apply for me?

Check the current official access and authorisation requirements for your route. Agree who submits, who checks and who responds to messages. A helper should not need your password or OTP in a public conversation. The operator still needs to understand the application and outcome. This website provides education, not an application service or account delegation.

What if I cannot identify the correct licence?

Send a clear description of the place, activity and service arrangement through the official enquiry channel. Include relevant facts, not private customer data. Ask about the specific route and any special arrangement. Do not choose the cheapest option or copy a neighbour's application just because the two businesses look similar from the street.

Does a complete checklist mean I can open?

No. The checklist records preparation only. Confirm the actual official outcome and all applicable opening conditions. An educational page cannot inspect your premises or grant permission. If a condition is unclear, ask the responsible authority before relying on an assumption. Keep the answer privately with the rest of the business record.

Sources, review date and scope

The three linked SFA pages were checked on twelve October twenty twenty-six. They support the limited route, home-business and application-process summaries above. The cases, folder method, question lists and practical exercises are original educational material. They are not official application forms, a complete technical design standard or proof of an authenticated portal test.

For a real application, use the current requirements and messages for your business. If a linked rule changes, follow the official update and tell us which passage needs review. Use the Singapore settlement guide for a separate money-review method once you have authorised business records; that guide does not replace food-business permissions.

Your preparation checklist

Tick only what you have checked. These boxes do not submit an application, inspect the kitchen or grant permission to open. Nothing is stored or sent.

Next: ask the responsible authority which route and opening conditions fit your business.

What our tools can and cannot do

The current extension and main settlement analyser support authorised Zomato and Swiggy workflows, not automatic DoorDash, Uber Eats, GrabMerchant, Deliveroo or Talabat extraction. The main margin tool uses INR. This page has a preparation checklist, not a financial model or application-portal connection. Licensing checklists cannot submit applications or grant approval.

Read the beginner tool manual or discuss an international extractor requirement. Do not send passwords, OTPs, tokens, identity documents, customer records or raw private exports.

Back to the organised guide library · How we prepare and correct guides