Storage diagnostics
Help identify storage-access problems through protected support diagnostics.
Setup & scope details
Deployment permissions and any repair need authorised server review. A diagnostic result is not a recovery guarantee.
Modules extend the core restaurant workflow. Inclusion, configuration and release scope must be confirmed in your plan; this catalogue is not a promise of complete parity or live activation.
Help identify storage-access problems through protected support diagnostics.
Deployment permissions and any repair need authorised server review. A diagnostic result is not a recovery guarantee.
Station routing, ticket and item histories, printer profiles and managed browser print attempts.
Physical printing, device compatibility and broader event/API scope require confirmation.
Opening and closing counts, staff handovers, approvals, X/Z reports and supported cash refunds.
Cash/device acceptance and payment combinations remain specific to the configured workflow.
Connect branch terminals, control their access and see which terminal handled an activity.
Plan limits apply; real browsers, devices and concurrent operating load must be tested.
Ingredients, recipes, lots, counts, transfers, production, purchasing, suppliers and operational reports.
Contribution is not net profit. Future usage forecasting and complete financial-report parity are not promised.
Points, item stamps, tiers, expiry, eligible redemption, customer wallet and related reports.
Reward and discount combinations are restricted; unit totals do not promise monetary liability.
English, Hindi, Kannada and Thai presentation across many staff and customer workflows.
Coverage varies by screen. Review your team’s terminology and language requirements before rollout.
Choose supported fonts for public-menu presentation and branded QR labels.
Language styling and printed QR readability need review. Arbitrary font uploads and remote fonts are not promised.
Give your restaurant menu a managed address with a protected handover into customer ordering.
Domain and certificate setup require separate checks. Custom-domain and alias-management scope must be confirmed.
Controlled pairing, supported carts, pay-at-counter and private-phone payment/reward handoff.
Real-device and live-payment acceptance are separate; kiosk dine-in/table selection is outside accepted scope.
Connect authorised tools to selected branch data, ordering, kitchen and reservation actions.
Access uses scoped, expiring credentials. Only the documented endpoints are supported; cash-session actions are restricted.
Signed durable order, payment and selected dining-event deliveries with bounded retries.
Receiver operation and additional stock, print and platform events require separate scope confirmation.
Send supported event messages using your restaurant’s Twilio, Infobip or MSG91 account, with consent and template controls.
Provider fees, credentials, approved templates and supported delivery-status coverage apply; delivery is not guaranteed.
Use supported text templates through your restaurant’s Meta Cloud API, Infobip, Twilio or MSG91 account.
Consent and approved templates apply. Delivery-status, media/button and scheduled-report coverage varies.
Protected encrypted exports and isolated recovery tooling with reviewed policy information.
Scheduled creation/retention, offsite storage and actual server recovery acceptance remain separate work.
Rooms, stays, folios, room-service posting, accommodation documents, eligible settlement and venue workflows.
Extra-service catalogues, additional booking periods, broader credit/receivable combinations and outlet parity remain limited.
Bounded free-only menu-description drafts with staff review and retained application history.
No paid fallback. Free provider capacity is not guaranteed; analytical and conversational workflows are not promised.
Payment providers, printers, devices, messaging accounts and external integrations need separate configuration and acceptance. Automatic PromptPay is deferred. An extension listing does not include hardware, provider fees or a rollout date.
Explore the workflow, check the details and choose the setup that fits your restaurant.