Owner Dashboard
Revenue, orders, AOV, customers and pending, preparing and completed counts in one adaptive workspace.
Adaptive to business sizebronze-buildfoodosfromscratchasaprofessionalproduction
by
Khristi Amit
Khristi AmitBUILDFOODOSFROMscratchasaprofessionalproductionreadyMULTITENANTSAASplatformforfoodbusinessesofalltypesincludingstreetstalls,foodcarts,foodtrucks,homefood,cafes,bakeries,QSRs,cloudkitchens,takeaways,restaurantsandmultibranchrestaurantgroups.Donotbuildasimpledemo,landingpageorbasicCRUDapp.BuildarealscalableFoodOperatingSystemwithauthentication,tenantisolation,subscriptions,RBAC,QRordering,onlineordering,POS,KDS,realtimeorders,CRM,menu,inventory,analytics,payments,notifications,branchesandplatformadministration. COREMODEL:PlatformAdmin→Plans→BusinessTenant→Branches→StaffRoles→Menu→QRTables→Orders→Payments→Customers→Analytics. MULTITENANCY:EverybusinessmusthaveanisolatedtenantworkspacewithtenantID,businessprofile,businessType,subscription,users,roles,branches,products,categories,addons,orders,customers,tables,QRcodes,payments,offers,inventory,notifications,settingsandanalytics.TenantAmustNEVERaccessTenantBdata.Enforceisolationatbackendanddatabaselevelusingauthorization,foreignkeys,indexesandtenantscopedqueries. BUSINESSTYPES:StreetStall,FoodCart,FoodTruck,HomeFood,Cafe,Bakery,FastFood,QSR,Restaurant,CloudKitchen,TakeawayandMultiBranchRestaurant.ThebusinessTypecontrolsthedefaultdashboardandvisiblemodules.Astreetstallshouldnotbeoverloadedwithrestaurantfeatures. ONBOARDING:CreatepremiummultiSteponboarding:Account→BusinessName→BusinessType→Location→Logo→Brand→OperatingHours→Menu→Payment→Plan→Complete.Allowskip/saveprogress. CUSTOMERAPP:Buildpremiumresponsivecustomerexperiencewithbusinesspage,digitalmenu,search,categories,productdetails,variants,addons,cart,checkout,payment,confirmation,livetracking,orderhistoryandprofile.Customerdoesnotneedanapp.Coreflow:QRorLink→Menu→Product→Customize→Cart→Checkout→Pay→Track. QR:GenerateuniqueQRcodesforbusiness,branch,table,counterandstall.QRautomaticallyidentifiesthecorrecttenantandbranchandoptionallytable.RestauranttableQRshouldattachordertotable.StallQRshouldopenstallmenuandordering. MENU:ProfessionalmenuCMS.Productsneedname,description,price,image,category,variants,addons,tax,availability,veg/nonveg,featured,bestseller,preparationtimeandnotes.Supportimageupload,bulkedit,duplicate,archiveandavailabilitytoggle. ORDERENGINE:UseDRAFT,PLACED,CONFIRMED,PREPARING,READY,OUT_FOR_DELIVERY,COMPLETED,CANCELLED,REFUNDED.PreventinvalidstatustransitionsserverSide.Storestatushistory,timestampsandactorinformation. DASHBOARD:Ownerdashboardwithrevenue,orders,AOV,customers,popularproducts,salescharts,recentorders,pendingorders,preparingorders,completedorders,lowstockalerts,subscriptionandquickactions.Createadaptivecomplexityforsmallandlargebusinesses. POS:BuildfastPOSforcashier/owner.SupportDineIn,Takeaway,Pickup,DeliveryandCounter.Productsearch,categoryshortcuts,quickadd,cartediting,discounts,coupons,notes,customerselection,paymentandreceipt. KDS:CreateprofessionalKitchenDisplaySystemwithNEW→CONFIRMED→PREPARING→READY→COMPLETED.Showordernumber,time,items,quantity,modifiers,notes,table/customer,priorityandtimer.OneTapstatuschangesandrealTimeupdates. TABLES:Forrestaurants/cafesprovidefloor/tablemanagement,number,capacity,status,QR,currentorder,merge,splitandtransfer.Streetstallsdonotneedthismodule. RBAC:SupportPlatformAdmin,Owner,Manager,Cashier,KitchenStaff,Waiter,DeliveryStaffandcustomroles.Permissionsfororders,products,customers,inventory,payments,analytics,staff,branches,settingsandsubscription.Enforcepermissionsbackend. SUBSCRIPTIONS:FoodOSisalsoaSaaSwithFREE,STARTER,GROWTH,PROandENTERPRISEplans.Supporttrial,monthly/yearlybilling,featurelimits,usagelimits,upgrade,downgrade,cancellation,renewal,paymentfailure,pastDueandgraceperiod.Createcentralfeatureentitlements:QR_MENU,ONLINE_ORDERING,POS,KDS,ANALYTICS,CRM,INVENTORY,OFFERS,MULTI_BRANCH,CUSTOM_BRANDING,CUSTOM_DOMAIN,API,ADVANCED_REPORTS.SubscriptionpermissionsmustbevalidatedserverSide. PLATFORMADMIN:CreateaseparateFoodOSsuperAdminpanel.Managetenants,users,plans,subscriptions,payments,trials,features,support,revenue,analyticsandsystemsettings.Addsearch,filters,tenantdetails,activitylogsandsubscriptionmanagement. PAYMENTS:CreateprovideragnosticpaymentlayerforUPI,onlinegateway,cardsandcash.States:PENDING,PROCESSING,SUCCESS,FAILED,REFUNDED,PARTIALLY_REFUNDED.Nevertrustfrontendpaymentstatus.Usewebhookverification,idempotencyandservervalidation. WHATSAPP:CreateintegrationReadyarchitecturefororderreceived,confirmed,preparing,ready,completedandpaymentnotifications.Useenvironmentvariablesforcredentials.Neverexposesecrets. REALTIME:UseWebSocketsorSupabaseRealtimeforneworders,statuschanges,KDSupdates,paymentupdatesanddashboardcounters.Handleduplicateeventsandconnectionrecovery. CRM:Customerprofileswithname,phone,orderhistory,totalspending,lastorder,favoritesandvisitfrequency.Useprivacyconsciousdatacollection. OFFERS:Supportpercentage,flat,productSpecific,firstOrder,minOrder,expiry,usageLimit,customerLimitandactivePeriodcoupons/promotions. INVENTORY:Optionalmodulewithingredients,units,stock,lowStockalerts,adjustments,purchases,suppliers,consumptionandinventoryhistory.Allowautomaticstockdeductionwhenconfigured. BRANCHES:Eligibleplanscancreatebranches.Eachbranchhasaddress,hours,staff,menu,tables,orders,inventory,QRs,settingsandanalytics.Supportbranchlevelandorganizationlevelreports. BRANDING:Tenantcanconfigurelogo,businessname,accentcolor,coverimage,menuappearanceanddescription.PreparewhiteLabel/customdomainarchitecture. ANALYTICS:Revenue,orders,AOV,newcustomers,repeatcustomers,popularproducts,categorysales,peakhours,paymentmethods,discountusage,branchperformanceandorderstatus.UseToday,7Days,30Days,90DaysandCustomRange.DoNotclaimprofitunlesscostdataexists. NOTIFICATIONS:CreateinAppnotificationcenterfororders,payments,inventory,subscription,systemandpromotions.Prepareemail,WhatsAppandSMSintegrationlayers. DESIGN:UsepremiumMidnightFoodOSdesign.DeepnearBlackbackground,glasssurfaces,subtleborders,ambientgradients,modernlargeTypography,highqualityfoodimages,elegantbuttons,softshadowsandclearstatusindicators.CustomerUIshouldfeel likepremiumfoodapp.AdminUIshouldfeel likeLinear+Stripe+modernPOS.KDSmustprioritizespeedandreadability.Donotoveruseglassmorphism. MOTION:UseFramerMotionorsimilarforpageTransitions,scrollReveal,hoverDepth,imageTransitions,orderstatusanimations,modals,toastsandmicroInteractions.UseGPUfriendlytransform/opacity.Respectreducedmotion. ACCESSIBILITY:SemanticHTML,keyboardnavigation,visiblefocus,properlabels,accessibleforms,contrastandreducedmotion. RESPONSIVE:Mobilefirst.CustomeroptimizedforAndroid/iPhone.Adminresponsivephone/tablet/desktop.KDSandPOSoptimizedtablet/desktop.NoHorizontalOverflow.Touchfriendlycontrols. PWA:MakecustomerorderinginstallableasPWAwhereappropriatewithmanifest,iconsandnetworkrecovery.Donotpretendofflineordersaresuccessful. TECHSTACK:FrontendReact+TypeScript+Vite+TailwindCSS+shadcn/ui+Lucide+FramerMotion.BackendNode.js+TypeScript+Express/NestJS.DatabasePostgreSQL+Prisma.RealtimeWebSockets/SupabaseRealtime.Storageobjectstorageforimages.Use.envforsecrets. ARCHITECTURE:Usecleanmodulararchitecturewithapps/web,apps/apiandsharedpackageswhereuseful.Domainmodules:auth,tenants,subscriptions,products,categories,orders,payments,customers,inventory,analytics,notifications,QR,branches,staffandsettings.KeepbusinesslogicoutofReactcomponents.Usevalidationservices,repositoriesandtypedAPIs. DATABASE:PostgreSQLwithUUIDs,foreignkeys,indexes,uniqueconstraints,timestamps,softDeletewhereappropriateandauditfields.Createproperrelationshipsforusers,tenants,plans,subscriptions,features,entitlements,branches,roles,permissions,products,categories,variants,addons,tables,QR,carts,orders,orderItems,payments,customers,coupons,offers,inventory,suppliers,notifications,auditLogsandsettings. SECURITY:Securepasswordhashing,secureauthentication,sessions/tokens,refreshrotationwhereappropriate,RBAC,tenantauthorization,inputvalidation,ratelimiting,secureheaders,CORS,CSRFprotectionwhereapplicable,SQLinjection/XSSprotection,auditlogs,secretmanagementandwebhookverification.Neverstoreplaintextpasswords.NeverexposeAPIsecrets. PERFORMANCE:CodeSplitting,lazyLoading,optimizedimages,caching,pagination,efficientqueries,debouncedsearch,virtualizationforlargeLists,compressedassetsandserverSidepagination. OBSERVABILITY:Structuredlogs,requestIDs,errorhandling,healthcheck,readinesscheckandbasicmetrics.Donotlogpasswords,tokensorfullpaymentdata. TESTING:Createunit,API,integration,database,RBAC,tenantIsolation,subscriptionEntitlement,orderLifecycle,paymentWebhookandcriticalE2Etests.Testsuccessandfailurepaths. DEMODATA:Seedmultiplebusinesstypes,branches,products,categories,tables,customers,orders,staffandplans.CreateclearlydocumenteddemoaccountsforPlatformAdmin,Owner,Manager,Cashier,KitchenStaffandCustomer. DOCUMENTATION:CreateREADME,.env.example,databaseSetup,migrations,seeding,APIdocumentation,architecture,roles,permissions,subscriptionfeatures,integrationsetup,testinganddeploymentinstructions. DEPLOYMENT:Productionreadyfrontend,backend,database,storageandrealtimeconfiguration.Addbuildscripts,migrationcommands,seedcommands,healthchecks,errorhandling,loggingandsecureconfiguration. IMPLEMENTATIONORDER:Architecture→Database→Authentication→RBAC→TenantIsolation→Onboarding→Subscriptions→Menu→Products→QR→CustomerOrdering→Cart→Checkout→Payments→POS→KDS→Realtime→CRM→Inventory→Offers→Branches→Analytics→PlatformAdmin→Notifications→PremiumUI→Testing→Security→Deployment. FINALVALIDATION:Runmigrations,seeds,testsandproductionbuild.FixallTypeScript,buildandruntimeerrors.TestQRflow,customerordering,checkout,paymentarchitecture,KDS,realtime,RBAC,subscriptionlimits,tenantisolation,mobile,tabletanddesktoplayouts.Verifythatstreetstallflowissimplewhileadvancedrestaurantfeaturesremainavailableforlargerbusinesses.BuildFoodOSasaseriouscommercialSaaSplatformcapableofservingthousandsoffoodbusinesseswithscalablearchitecture,security,premiumMidnightUIandexcellentUX.
Comments (0)
Sign in to leave a comment
System Requirements
Page 1 of 1
System Requirements Document for bronze-buildfoodosfromscratchasaprofessionalproduction
1. Introduction
FoodOS by TechCart is a professional, production-ready, multi-tenant SaaS Food Operating System for food businesses of all types — street stalls, food carts, food trucks, home food, cafes, bakeries, fast food, QSRs, restaurants, cloud kitchens, takeaways, and multi-branch restaurant groups.
This is explicitly not a simple demo, a landing page, or a basic CRUD application. It is a real, scalable operating system with authentication, tenant isolation, subscriptions, RBAC, QR ordering, online ordering, POS, KDS, realtime orders, CRM, menu, inventory, analytics, payments, notifications, branches, and platform administration.
The product intent is commercial scale: a serious SaaS platform capable of serving thousands of food businesses, where each business operates inside an isolated tenant workspace whose visible dashboard and modules adapt to its business type — a street stall is never overloaded with restaurant features, while advanced restaurant, cafe, and multi-branch capabilities remain available to larger operations.
Audience. The platform serves two macro-audiences under one system:
- Tenant-side food businesses and their staff — Business Owners, Managers, Cashiers, Kitchen Staff, Waiters, and Delivery Staff, each with
Preview dataChanges stay in this preview.
Food Operating System
Every food business.One operating system.
FoodOS by TechCart runs orders, menus, payments, kitchens and branches inside an isolated tenant workspace for each business — from a street stall with one counter to a restaurant group with branches across a city.
Default modules
- QR MENU
- ONLINE ORDERING
- CASH PAYMENTS
- ORDERS QUEUE
- BASIC ANALYTICS
- OFFERS
Not shown for this type
- TABLE FLOOR
- KDS TERMINAL
- WAITER APP
- MULTI BRANCH
- INVENTORY
Order #1042 · Table 72 items
DRAFT
PLACED
CONFIRMED
PREPARING
READY
COMPLETED
Tenant isolatedLive order queueStatus history kept
Adaptive by business type
The workspace opens to the job you actually do
Choose a business type to see the default dashboard and the modules that appear. A street stall never sees a floor plan it has no tables for; a restaurant group keeps every advanced control it needs.
Sell from a stall in minutes
One counter, one screen, one QR sign. Orders, payments and a live queue without a single restaurant control in the way.
Modules on by default
- QR MENU
- ONLINE ORDERING
- CASH PAYMENTS
- ORDERS QUEUE
- BASIC ANALYTICS
- OFFERS
Kept out of the way
- TABLE FLOOR
- KDS TERMINAL
- WAITER APP
- MULTI BRANCH
- INVENTORY
The operating system
Modules that cover a whole service day
Ordering, kitchen, counter, floor, stock, customers and reporting share one order record and one tenant, so nothing has to be re-entered between them.
QR Ordering
Unique codes for business, branch, table, counter and stall — each one resolving to the correct tenant and branch.
Code resolves the tenantOnline Ordering
Digital menu, categories, variants, add-ons, cart, checkout and payment without a customer app install.
No app install neededPOS Terminal
Dine in, takeaway, pickup, delivery and counter with product search, quick add, discounts and receipt.
Built for the counterKitchen Display
NEW through READY with order number, elapsed timer, modifiers, notes, table and one-tap status changes.
Readable at arm’s lengthTables & Floor
Table number, capacity, live status, current order, plus merge, split and transfer for full-service rooms.
Hidden for stalls by defaultMenu CMS
Variants, add-ons, tax, availability, featured and bestseller flags, bulk edit, duplicate and archive.
Bulk edit and archiveInventory
Ingredients, units, stock, low-stock alerts, adjustments, purchases, suppliers and consumption history.
Optional per tenantCustomers & CRM
Profiles with order history, total spend, last order, favourites and visit frequency, collected with care.
Privacy-conscious recordsOffers
Percentage, flat and product-specific coupons with first-order rules, minimums, expiry and usage limits.
Limits enforced server-sideBranches
Address, hours, staff, menu, tables, inventory and reports — scoped per branch and rolled up per organization.
Branch and org reportsAnalytics
Revenue, popular products, category sales, peak hours, payment mix and branch performance across any range.
No profit claim without cost dataRealtime Orders
Live new orders, status changes, kitchen updates, payment updates and dashboard counters over a resilient socket.
Recovers from dropsPayments
Provider-agnostic layer over UPI, online gateway, cards and cash with webhook verification and idempotency.
Never trusts the clientNotifications
In-app centre for orders, payments, inventory, subscription and system events, with message channels ready to plug in.
Per-tenant preferencesPlatform Admin
A separate FoodOS console for tenants, plans, subscriptions, trials, revenue and system settings.
Separate from tenant UIOrder engine
One status model, guarded on the server
Nine statuses, one history per order, and a validation layer that refuses impossible jumps. Pick a service mode to see where it starts, who acts on it, and how it ends.
Table order, from QR to settled bill
The table QR identifies tenant, branch and table, so the order is attached to the right seat and the waiter can merge or split it before service.
DRAFTPLACEDCONFIRMEDPREPARINGREADYCOMPLETEDCOMPLETED
Three surfaces, one platform
Built for the people standing in front of it
Tenant side
Business owners and their teams
One isolated workspace per business, with the dashboard and modules shaped by what that business actually does.
OwnerManagerCashierKitchen StaffWaiterDelivery Staff
Customer side
Guests who just want to order
Scan or open a link, browse the digital menu, customise the item, pay, and follow the order to collection.
MenuVariantsAdd-onsCartCheckoutLive trackingOrder history
Operator side
The platform team running FoodOS
Plans, entitlements, subscriptions, trials, support and revenue watched from a console that tenants never see.
TenantsPlansSubscriptionsPaymentsSupportSystem settings
Subscriptions & entitlements
Features unlock by plan, not by a hidden toggle
Each plan grants a set of feature entitlements, and those entitlements are checked on the server before any gated request is served.
Growth entitlements6 of 13 feature entitlements included
- QR MENU
- ONLINE ORDERING
- POS
- KDS
- ANALYTICS
- CRM
- INVENTORY
- OFFERS
- MULTI BRANCH
- CUSTOM BRANDING
- CUSTOM DOMAIN
- API
- ADVANCED REPORTS
Not included on Growth: inventory, offers, multi branch, custom branding, custom domain, api, advanced reports. Upgrading applies the new entitlements server-side, and downgrading only takes effect when it is safe.
Before you start
Common questions about running on FoodOS
Every record belongs to a tenant through a foreign key, every query is tenant-scoped, and authorization is enforced on the server before a response is built. One business can never read or write another business’s data, regardless of what the client asks for.
Yes. The business type selects the default dashboard and the visible modules, so a stall opens with a queue, a QR sign and payments, while a restaurant group gets floor plans, branch analytics and organization-level reporting.
No. The customer flow is a responsive web experience reached from a QR code or a link — menu, product customisation, cart, checkout, payment and live tracking all run in the browser.
Roles cover Platform Admin, Owner, Manager, Cashier, Kitchen Staff, Waiter and Delivery Staff, plus custom roles where the plan allows. Permissions for orders, products, customers, inventory, payments, analytics, staff, branches and settings are checked on the server.
Orders move through DRAFT, PLACED, CONFIRMED, PREPARING, READY, OUT_FOR_DELIVERY, COMPLETED, CANCELLED and REFUNDED. Invalid transitions are rejected server-side, and every change stores its timestamp, actor and history entry.
Branch creation is an entitlement, not a setting. Plans that include MULTI_BRANCH can create branches with their own address, hours, staff, menu, tables, orders, inventory, QRs, settings and analytics.
Start with one counter
Bring your menu, your orders and your kitchen onto one system
Create a workspace, pick your business type, and FoodOS shapes the dashboard around it. Add branches, staff roles and modules as the business grows.
Preview dataChanges stay in this preview.
Food Operating System
Every food business.One operating system.
FoodOS by TechCart runs orders, menus, payments, kitchens and branches inside an isolated tenant workspace for each business — from a street stall with one counter to a restaurant group with branches across a city.
Default modules
- QR MENU
- ONLINE ORDERING
- CASH PAYMENTS
- ORDERS QUEUE
- BASIC ANALYTICS
- OFFERS
Not shown for this type
- TABLE FLOOR
- KDS TERMINAL
- WAITER APP
- MULTI BRANCH
- INVENTORY
Order #1042 · Table 72 items
DRAFT
PLACED
CONFIRMED
PREPARING
READY
COMPLETED
Tenant isolatedLive order queueStatus history kept
Adaptive by business type
The workspace opens to the job you actually do
Choose a business type to see the default dashboard and the modules that appear. A street stall never sees a floor plan it has no tables for; a restaurant group keeps every advanced control it needs.
Sell from a stall in minutes
One counter, one screen, one QR sign. Orders, payments and a live queue without a single restaurant control in the way.
Modules on by default
- QR MENU
- ONLINE ORDERING
- CASH PAYMENTS
- ORDERS QUEUE
- BASIC ANALYTICS
- OFFERS
Kept out of the way
- TABLE FLOOR
- KDS TERMINAL
- WAITER APP
- MULTI BRANCH
- INVENTORY
The operating system
Modules that cover a whole service day
Ordering, kitchen, counter, floor, stock, customers and reporting share one order record and one tenant, so nothing has to be re-entered between them.
Owner Dashboard
Revenue, orders, AOV, customers and pending, preparing and completed counts in one adaptive workspace.
Adaptive to business sizeQR Ordering
Unique codes for business, branch, table, counter and stall — each one resolving to the correct tenant and branch.
Code resolves the tenantOnline Ordering
Digital menu, categories, variants, add-ons, cart, checkout and payment without a customer app install.
No app install neededPOS Terminal
Dine in, takeaway, pickup, delivery and counter with product search, quick add, discounts and receipt.
Built for the counterKitchen Display
NEW through READY with order number, elapsed timer, modifiers, notes, table and one-tap status changes.
Readable at arm’s lengthTables & Floor
Table number, capacity, live status, current order, plus merge, split and transfer for full-service rooms.
Hidden for stalls by defaultMenu CMS
Variants, add-ons, tax, availability, featured and bestseller flags, bulk edit, duplicate and archive.
Bulk edit and archiveInventory
Ingredients, units, stock, low-stock alerts, adjustments, purchases, suppliers and consumption history.
Optional per tenantCustomers & CRM
Profiles with order history, total spend, last order, favourites and visit frequency, collected with care.
Privacy-conscious recordsOffers
Percentage, flat and product-specific coupons with first-order rules, minimums, expiry and usage limits.
Limits enforced server-sideBranches
Address, hours, staff, menu, tables, inventory and reports — scoped per branch and rolled up per organization.
Branch and org reportsAnalytics
Revenue, popular products, category sales, peak hours, payment mix and branch performance across any range.
No profit claim without cost dataRealtime Orders
Live new orders, status changes, kitchen updates, payment updates and dashboard counters over a resilient socket.
Recovers from dropsPayments
Provider-agnostic layer over UPI, online gateway, cards and cash with webhook verification and idempotency.
Never trusts the clientNotifications
In-app centre for orders, payments, inventory, subscription and system events, with message channels ready to plug in.
Per-tenant preferencesPlatform Admin
A separate FoodOS console for tenants, plans, subscriptions, trials, revenue and system settings.
Separate from tenant UIOrder engine
One status model, guarded on the server
Nine statuses, one history per order, and a validation layer that refuses impossible jumps. Pick a service mode to see where it starts, who acts on it, and how it ends.
Table order, from QR to settled bill
The table QR identifies tenant, branch and table, so the order is attached to the right seat and the waiter can merge or split it before service.
DRAFTPLACEDCONFIRMEDPREPARINGREADYCOMPLETEDCOMPLETED
Three surfaces, one platform
Built for the people standing in front of it
Tenant side
Business owners and their teams
One isolated workspace per business, with the dashboard and modules shaped by what that business actually does.
OwnerManagerCashierKitchen StaffWaiterDelivery Staff
Customer side
Guests who just want to order
Scan or open a link, browse the digital menu, customise the item, pay, and follow the order to collection.
MenuVariantsAdd-onsCartCheckoutLive trackingOrder history
Operator side
The platform team running FoodOS
Plans, entitlements, subscriptions, trials, support and revenue watched from a console that tenants never see.
TenantsPlansSubscriptionsPaymentsSupportSystem settings
Subscriptions & entitlements
Features unlock by plan, not by a hidden toggle
Each plan grants a set of feature entitlements, and those entitlements are checked on the server before any gated request is served.
Growth entitlements6 of 13 feature entitlements included
- QR MENU
- ONLINE ORDERING
- POS
- KDS
- ANALYTICS
- CRM
- INVENTORY
- OFFERS
- MULTI BRANCH
- CUSTOM BRANDING
- CUSTOM DOMAIN
- API
- ADVANCED REPORTS
Not included on Growth: inventory, offers, multi branch, custom branding, custom domain, api, advanced reports. Upgrading applies the new entitlements server-side, and downgrading only takes effect when it is safe.
Before you start
Common questions about running on FoodOS
Every record belongs to a tenant through a foreign key, every query is tenant-scoped, and authorization is enforced on the server before a response is built. One business can never read or write another business’s data, regardless of what the client asks for.
Yes. The business type selects the default dashboard and the visible modules, so a stall opens with a queue, a QR sign and payments, while a restaurant group gets floor plans, branch analytics and organization-level reporting.
No. The customer flow is a responsive web experience reached from a QR code or a link — menu, product customisation, cart, checkout, payment and live tracking all run in the browser.
Roles cover Platform Admin, Owner, Manager, Cashier, Kitchen Staff, Waiter and Delivery Staff, plus custom roles where the plan allows. Permissions for orders, products, customers, inventory, payments, analytics, staff, branches and settings are checked on the server.
Orders move through DRAFT, PLACED, CONFIRMED, PREPARING, READY, OUT_FOR_DELIVERY, COMPLETED, CANCELLED and REFUNDED. Invalid transitions are rejected server-side, and every change stores its timestamp, actor and history entry.
Branch creation is an entitlement, not a setting. Plans that include MULTI_BRANCH can create branches with their own address, hours, staff, menu, tables, orders, inventory, QRs, settings and analytics.
Start with one counter
Bring your menu, your orders and your kitchen onto one system
Create a workspace, pick your business type, and FoodOS shapes the dashboard around it. Add branches, staff roles and modules as the business grows.
No comments yet. Be the first!