About FoodPilot
FoodPilot is an AI-first restaurant operating system. Billing, kitchen, inventory, purchasing, customers and finance share one data platform, keep working offline, and are built for India first.
How it works
Every screen reads and writes the same data. When a bill is rung up, the rest of the restaurant follows without anyone re-entering it.
01
At the POS, a table QR, your online store or by voice.
02
Routed to the right station, with SLA timers.
03
Ingredients come off by recipe, variants and add-ons included.
04
Lower stock feeds the AI purchase plan and draft POs.
05
Points land on the guest's profile, reversed on refunds.
06
Sales, GST and profit reflect the bill the moment it closes.
One platform, every device
Six experiences, one login system and one set of permissions. Each person sees what their role needs, and nothing more.
Cashier · Captain
Touch, search or voice entry. Split bills, multi-tender and GST invoices, online or offline.
Chef · Kitchen
Station routing, SLA timers, allergens, bump-to-ready and bottleneck alerts.
Staff
PIN clock-in kiosk, weekly rosters, shift swaps, leave and payslips.
Owner · Manager
Today's sales, food cost and a daily briefing, with reports you can build, pin and schedule.
Customers
Order from a table QR or your own online store, follow live status, and get the bill by SMS or WhatsApp.
Chains · HQ
Consolidated KPIs, outlet ranking, master menu with local overrides and franchise royalties.
Runs in any modern browser and installs as an app. Native Android and iOS apps and a Windows desktop POS are next.
Works offline
Every change is saved on the device first, then synced in order the moment the connection returns.
Take orders, print KOTs and settle bills with no connection. The app itself opens offline too.
Every change waits in a local outbox on the device and is pushed in order when you reconnect.
Each event carries an idempotency key, so a retry never applies twice. Each device has its own invoice series, so numbers never collide.
Under
0.5s
Fire a KOT at the POS and it appears on the kitchen display in under half a second. Every device in the outlet receives a sync signal and pulls only the data it is allowed to see.
AI that works from your data
Briefings, forecasts and answers are calculated from your own transactions. AI drafts; a person confirms. Nothing reaches the books, stock or the kitchen until someone approves it.
Spoken
“dhai kilo pyaaz 400 rupaye Sharma se”
Purchase draft
Waiting for confirmationOn confirm: supplier bill, stock receipt and ingredient cost update.
Sales, stock risks, margins and anomalies, summarised for the owner every morning.
Ask about sales, top items, low stock, pending bills or cash. It answers from read-only tools over your data.
Speak orders, purchases and expenses in English, Hinglish or Hindi. Each one becomes an editable draft.
Weekday and hour patterns, the Indian festival calendar and live weather, back-tested for accuracy.
Built for India
Amounts are stored as whole paise, so totals, taxes and split bills always add up, to the paisa.
CGST and SGST or IGST, cess, inclusive or exclusive pricing. GST is configuration, never hardcoded per item.
Every device has its own GST invoice series, so numbers stay unique even offline. Credit notes on refunds, GSTR-1 B2CS and HSN exports, and Tally XML.
SPI3/26-27/00001
Show a UPI QR on the customer display. A dynamic QR confirms itself through a signed payment webhook, and is applied to the bill exactly once. A static UPI QR works with no gateway at all.
Navigation in eight languages. Voice entry and guest feedback understand English, Hindi and Hinglish.
Englishहिन्दीमराठीதமிழ்తెలుగుবাংলাગુજરાતીಕನ್ನಡ
Security & reliability
Sensitive rules are enforced on the server and in the database, not only in the app on the counter.
Each restaurant's data is separated by the database itself, so a bug in a query cannot read another restaurant's rows.
Every tenant table has a row-level security policy, and the API runs as a role that cannot bypass it.
Custom roles enforced by the server. Discounts, voids, refunds and complimentary bills can require a manager PIN.
Sensitive actions are recorded with the signed-in user. The app can add and read entries, never edit or delete them.
Two-factor login, refresh tokens that rotate on every use, and instant revocation of any session or device.
Webhooks are signed with HMAC-SHA256. Payment credentials are encrypted on the server and never sent to devices.
Yes. The POS keeps billing and printing KOTs offline. Every change is queued on the device and synced in order when the connection returns, and idempotency keys make sure nothing is applied twice.
Yes. The live demo runs in your browser with a demo restaurant and realistic history, no account needed. When you are ready, create your own restaurant from the sign-up page.
Any modern browser, and it installs as an app (PWA). Receipt and KOT printers, cash drawers, scales and barcode scanners connect from Chrome or Edge. Native Android and iOS apps and a Windows desktop POS are next on the roadmap.
No. Voice, chat and photo captures become drafts that a person reviews and confirms before anything reaches the books, stock or the kitchen. The assistant uses Claude when it is configured and a built-in rules engine otherwise.
Yes. Isolation is enforced by PostgreSQL row-level security on every tenant table, and the API connects with a role that cannot bypass it.
A static UPI QR works today, as do Tally XML and GST return exports, and a built-in simulator lets you try card machines and dynamic UPI in the demo. Real card machines, dynamic UPI, WhatsApp, SMS and Swiggy, Zomato or ONDC sync have adapters ready and go live once the provider accounts or partner approvals are in place.
Take an order, fire a KOT, settle a bill and watch stock, loyalty and the P&L follow. The demo runs in your browser, no account needed.