Table QR ordering
Guests scan a table QR to open the current menu on their own phone. A scan alone does not occupy a table or create a visit session.
Explore the tools behind your guest experience, kitchen flow, payments and customer relationships—all in one restaurant workspace.
Bring guests from a table scan or online storefront into the same clear flow for your team.
Guests scan a table QR to open the current menu on their own phone. A scan alone does not occupy a table or create a visit session.
Take orders for the dining room and online storefront while keeping takeaway orders separate from dine-in tables.
Configure branch hours and pickup windows, prepare orders, and confirm handoff with a pickup code.
Set delivery coverage and fees, assign branch staff or riders, and track delivery status through OTP handoff.
Guests can request a waiter, water or the bill. A request by itself does not create an occupied-table session.
Keep guest-to-restaurant text conversations tied to the correct visit and branch. Attachments are not currently supported.
Signed-in customers can review their own orders and receipts. Reorders use current menu availability and prices.
Give kitchen and floor teams a shared view of orders, tables, people and branch operations.
Route new orders to kitchen workflows and track their validated preparation and service states.
View table and session activity while preserving separate visit identities for guests sharing a physical table.
Control team access by role, branch and the relevant operational permission.
Manage restaurant branches with branch-scoped operational data and access.
The current build includes ingredient, stock and recipe-costing workflows, but the inventory build is not ready for deployment.
In progress · not deployment-readyPurchase and receive stock, record counts and wastage, and transfer items between branches as the inventory rollout progresses.
In progress · not deployment-readyReview branch-scoped sales and operational summaries. Financial totals are calculated from server-side records.
Use server-calculated checkout and auditable payment records for customer and counter workflows.
Offer online payment methods supported by the restaurant’s own connected provider account.
Provider setup requiredRecord supported cash, UPI or card collections through authorized staff workflows.
Validate coupon eligibility and calculate discounts on the server before creating an order or payment.
Support shared Pay-Later tabs and staff-managed equal or custom counter splits. Online participant checkout and Pay-Later participant settlement are not included.
Counter split collectionInvestigate order and payment-record mismatches and verify linked Razorpay payments. This is not a bank-settlement feed or an automatic repair tool.
Keep service communication, feedback and review invitations transparent and separate from marketing.
Connect each restaurant’s official Meta WhatsApp Cloud API account. Approved templates, provider configuration and the correct customer consent are required.
Setup & consent requiredEligible paid orders can earn points after the customer explicitly opts in. Loyalty redemption is not enabled in checkout.
Consent & setup required · redemption offCollect private feedback from eligible customers and keep it separate from public reviews. Email and WhatsApp delivery require setup and separate consent.
Delivery setup may be requiredGive eligible customers the same voluntary review opportunity regardless of private feedback. TABLELY does not create, gate or incentivize reviews.
Manual review-link mode works without API access. Review sync requires approved Google API access and verified branch mapping; replies require owner approval.
Google setup requiredAI content needs review; online payments use each restaurant’s connected provider; customer messaging requires the right consent and provider setup; and inventory remains in progress. Group billing supports shared tabs and staff-managed counter splits, not shared online group checkout.