#1 Platform

True multi-tenant restaurant SaaS model

Tenant-owned data, platform-owned reference data, and hybrid rows create a scalable SaaS base.

#2 Security

Tenant-scoped Prisma client extension

Automatic tenant filters reduce the chance of cross-tenant data leakage.

#3 Security

Default-private hybrid model handling

Credentials, sessions, jobs, and audit data stay private unless explicitly allow-listed.

#4 Platform

Platform versus tenant resource classification

Verified resource scopes keep superadmin and tenant operations separated.

#5 Product

Six-surface operating model

Storefront, POS, kitchen, delivery, admin, and superadmin map to real restaurant workflows.

#6 Platform

Headless API-first architecture

One backend can support websites, kiosks, apps, operators, and integrations.

#7 Engineering

Shared TypeScript and zod contracts

Shared schemas reduce drift between API and UI.

#8 Engineering

Monorepo with workspace packages

Shared packages for UI, SDK, DB, i18n, PSP, and catalog support coordinated releases.

#9 Governance

Feature catalog as source of truth

A registry-backed feature system makes product breadth visible and testable.

#10 Governance

Resource registry with generated API/page conventions

Every resource has predictable API and console routes.

#11 Quality

Catalog verification gate

Registry counts, resource references, and scope consistency are enforced by tests.

#12 Platform

187-resource operations model

Breadth covers restaurant, delivery, finance, HR, procurement, security, CMS, and SaaS operations.

#13 Product

1,457 feature definitions

Gives the product a broad enterprise roadmap and module taxonomy.

#14 Analytics

163-report catalog

Tenant and platform reporting are first-class rather than afterthoughts.

#15 Engineering

Generic CRUD/report controller layer

Broad management coverage can be expanded without hand-building every screen.

#16 Engineering

Bespoke controllers for critical workflows

Orders, payments, kitchen, delivery, sites, finance, and invoicing get domain-specific behavior.

#17 Data

Soft-delete/archive convention

Operational data can be restored and audited instead of casually destroyed.

#18 Integrations

API key support for headless integrations

Important for aggregator, kiosk, loyalty, accounting, and custom channels.

#19 Security

Role and permission model

Restaurant teams require location, role, and workflow-specific access control.

#20 SaaS

Superadmin operator console

Platform-level tenants, plans, backups, payments, reports, and support need a separate surface.

#21 Growth

Tenant cloning from site templates

Fast onboarding is a major SaaS differentiator for restaurant groups and agencies.

#22 Growth

Ten cuisine storefront templates

Template-led onboarding reduces time to first useful site.

#23 Growth

Multi-site tenant support

Restaurants can run multiple branded storefronts from one tenant.

#24 Operations

Multi-location operations

The schema supports restaurants, cloud kitchens, dark stores, central kitchens, food trucks, and kiosks.

#25 Operations

Virtual brand and cloud-kitchen model

Delivery-first restaurant groups need brand/location decoupling.

#26 Storefront

Rich menu catalog

Items, categories, modifiers, allergens, combos, tags, brands, units, and schedules map to modern menus.

#27 Storefront

Modifier groups and nested customization

Complex customization is essential for pizza, bowls, platters, beverages, and regional foods.

#28 Storefront

Allergen and dietary data

Consumer demand for allergen and dietary transparency is rising.

#29 Storefront

Search, filters, and merchandising rails

Fast discovery, facets, trending rails, and curated collections improve conversion.

#30 Storefront

Personalization and saved customizations

Repeat ordering improves when the platform remembers preferences and usual orders.

#31 Storefront

Group ordering

Office, family, and event ordering are high-value restaurant workflows.

#32 Storefront

Scheduled ordering

Capacity-aware future ordering protects kitchen flow and improves customer planning.

#33 Commerce

Dine-in, pickup, curbside, catering, B2B channels

The channel model is broad enough for modern omnichannel restaurant operations.

#34 Commerce

Server-owned checkout pricing

Prevents client-side price manipulation and centralizes tax, discount, and fee logic.

#35 Commerce

Inclusive and exclusive tax handling

Correct tax extraction and addition avoids overcharging and bad invoices.

#36 Growth

Coupon and promotion support

Promotions, coupons, stacking rules, thresholds, and budgets support acquisition and retention.

#37 Storefront

Cart persistence and recovery

Abandoned-cart recovery is standard in leading commerce products.

#38 Storefront

One-page and express checkout

Reduces friction for mobile guests and repeat customers.

#39 Reliability

Idempotent order placement

Prevents duplicate orders during retries, poor networks, and double taps.

#40 Operations

Order lifecycle state machine

A clear lifecycle keeps kitchen, delivery, customer tracking, and finance aligned.

#41 Operations

Order events timeline

Events enable audit, realtime updates, analytics, and support investigation.

#42 Kitchen

Kitchen ticket derivation per station

Station-based KDS is essential for scale and speed.

#43 Kitchen

Kitchen start, bump, ready, and recall flows

These are core KDS workflows for real restaurant prep.

#44 Kitchen

Cook-time profiles

Learned cook times support ETA accuracy and capacity management.

#45 Kitchen

Kitchen routing rules

Item, category, fulfilment, and daypart routing reduce operator work.

#46 Kitchen

Prep recipes and prep tasks

Recipe-driven prep improves consistency, inventory, and food-cost control.

#47 Kitchen

Packaging checklists

Reduces missing items, wrong packaging, and delivery complaints.

#48 Kitchen

Quality checks and HACCP logs

Quality and food-safety workflows are enterprise-grade differentiators.

#49 Operations

Kitchen capacity slots

Capacity-aware ordering helps protect service promises.

#50 Realtime

Realtime order/kitchen/delivery streams

Live operational boards are table stakes for serious restaurant systems.

#51 Reliability

Polling fallback for customer tracking

Keeps tracking usable when WebSockets are blocked.

#52 POS

POS cash checkout

Cash handling remains essential in many markets.

#53 POS

POS held carts

Staff need to suspend and resume transactions during rush periods.

#54 POS

POS local basket retention

Helps survive reloads and short connectivity dips.

#55 POS

Offline POS reconciliation

Best-in-class POS must safely sync offline orders, payments, inventory, and conflicts.

#56 POS

Payment terminal integration

Production POS needs terminal pairing, tap/chip flows, settlement, and reversals.

#57 Dine-in

Dynamic QR ordering and table barcodes

QR menus and table ordering reduce service friction.

#58 Dine-in

Reservations, tables, and waitlists

These workflows expand the product beyond delivery-only commerce.

#59 Dine-in/POS

Open tabs and split tender

Essential for dine-in hospitality and group settlement.

#60 Delivery

Driver dispatch model

Delivery assignment, partner profiles, shifts, offers, batches, zones, and proof are modeled.