Restaurant owners & admins
Manage restaurant setup, branches, menus, staff, and operational settings according to assigned permissions.
Restaurant POS,|
FastAPI restaurant backend for menus, tables, orders, kitchen tickets, billing, payments, stock, staff, and devices.
From orderto the
kitchen.
kitchen.
THE SERVICE FLOWPOS / KOT
Connectedacross workflows
MENUS. ORDERS. KITCHEN. BILLING. OPERATIONS.SCROLL TO EXPLORE
One platform. Many connected modules.
Restaurant, tenant & branch admin
Documented operations include restaurant onboarding, tenant activation and suspension, plan migration, export, offboarding, and backups.
Restaurants · Tenants · Branches
Menus, zones & tables
Menu categories, items, variants, add-ons, area pricing, table records, zones, and clear-table operations are represented.
Catalogue · Pricing · Floor setup
Orders, KOT & kitchen
Order records, item add-ons, kitchen tickets, status handling, customer orders, and realtime order/kitchen channels are documented.
Orders · KOT · WebSockets
Bills, receipts & invoices
Billing models cover bill items, lifecycle status, PDF generation, receipt settings, refunds, and invoice delivery workflows.
Billing · PDFs · WhatsApp delivery
Payment gateways
Dedicated Razorpay and Cashfree integrations and adapters for Paytm, PhonePe, and Stripe are documented; provider readiness needs testing.
Payments · Webhooks · Reconciliation
Inventory & purchasing
Inventory structures include suppliers, recipe ingredients, stock logs, lots, purchases, purchase orders, and branch transfers.
Stock · Suppliers · Transfers
Customers & loyalty
Customer records and orders, loyalty transactions, tier/configuration endpoints, and customer-data synchronization are described.
Customers · Orders · Loyalty
Staff, roles & shifts
User administration, bulk import, role and permission assignment, shifts, clock-in/out, attendance, and staff activity are represented.
Users · RBAC · Attendance
Expenses, settings & integrations
Expense records and restaurant settings cover tax, payments, orders, notifications, security, backup, import/export, and integrations.
Settings · Expenses · Integrations
Delivery & public menu
Delivery slots, public-menu access, online-order settings, and order types are documented; capacity and availability need validation.
Delivery slots · Menu · Availability
Printers, devices & mobile
Printer configuration, print jobs, device registration and approval, token regeneration, licensing, and mobile authentication are described.
Printers · Devices · Mobile
Offline sync & realtime
Push/pull, acknowledgements, retry helpers, queue status, WebSockets, and Redis pub/sub are documented; conflict handling needs testing.
Sync · WebSockets · Redis
Plans, add-ons & billing
Plan lifecycle, trials, upgrades, renewals, billing previews, feature access, add-on purchases, and platform billing are represented.
Subscriptions · Features · Add-ons
Reports, exports & activity
Restaurant reports, analytics, platform reports, tenant/settings exports, global search, and activity-log structures are documented.
Reports · Exports · Audit activity
Security, support & platform admin
Authentication, RBAC, tenant context, security administration, support tickets/logs, and constrained impersonation have API structures.
Access · Support · Platform
01 / 04
From the first order to the final bill.
Every team has its own workflow.
Role names and permission assignments depend on the live configuration. Backend authorization and tenant/branch access must be validated independently of frontend visibility.
Managers & operational leads
Review assigned operations, reports, staff activity, and shifts where those capabilities are configured.
Cashiers & POS staff
Handle permitted table, order, customer, billing, payment, and receipt workflows.
Kitchen staff
View and update assigned kitchen tickets and order statuses through authorized workflows.
Inventory & purchase staff
Work with permitted stock items, suppliers, purchases, adjustments, and branch transfers.
Mobile & device users
Use configured mobile authentication, registered devices, branch context, and synchronization flows.
Platform admins & support
Oversee tenants, subscriptions, platform reports, support records, and security where authorized.
One backend for restaurant and platform operations.
The documented architecture separates API routers, data models, services, middleware, integrations, and database migrations. Tenant context, role controls, device sync, and realtime channels support connected workflows.
- Tenant and branch context in the application architecture
- Role and permission modules for access control
- Sync and WebSocket channels for connected clients
Let’s Talk Through Your Workflow.
Share The Restaurant, Branch, or Platform Workflow You Want To Discuss, From Order And Kitchen Operations To Billing, Inventory, Or Device Sync.
What the docs do and don’t confirm.
The archive describes backend modules and also calls out areas that need runtime, integration, security, and end-to-end verification.
Which restaurant workflows are documented?
The API areas include restaurant and tenant administration, menus, tables, orders, KOT and kitchen operations, billing, payments, inventory, customers, staff, shifts, settings, reports, devices, synchronization, and platform administration.
Does FoodKonnect include multi-restaurant and branch support?
Tenant onboarding and administration, tenant-aware database/request context, branch models, and branch-oriented endpoints are documented. Branch scope should still be verified for each read, write, export, and report path.
Which payment providers are represented?
Dedicated integration code is documented for Razorpay and Cashfree, alongside gateway adapters for Paytm, PhonePe, and Stripe. Provider configuration, webhook security, and payment-state handling require environment-specific testing.
Are all documented modules production-verified?
No. Source structures do not establish end-to-end readiness. Workflows, permissions, tenant isolation, integrations, UI connections, and production configuration must be validated before a capability is classified as live.
What is included for mobile sync and realtime updates?
The documentation describes push/pull and acknowledgement sync APIs, retry helpers, device status, and WebSocket channels for orders, kitchen updates, and notifications. Offline conflict handling and recovery behavior still require realistic testing.