Platform features

Guests browse your menu on your own website, build a basket, and check out online. You set minimum orders, fees, time slots, and how payment works so the flow matches how you already trade.

• Discounts, tax, and service charges as you configure them
• Order confirmation and operational notifications
• Works alongside card and cash at the till where you use both
• Orders carry source attribution (e.g. website, at-table QR, waiter, voice) where recorded—for reporting and the operations activity log

Online card payments run through your chosen payment provider (for example Stripe or Revolut) so funds settle with you. VoiceMenu configures the checkout experience; you maintain the relationship with your processor.

Customers interact with your website—not a generic marketplace app. The same menu, prices, and rules they see online are what staff fulfil in the back end, so you are not reconciling two systems.

Operator staff use authenticated routes under /staff—separate from Filament /admin for managers. Each user has an assigned primary interface and is steered to that surface after login (they cannot open another staff app in the same session). Views use live polling so queues update without manual refresh.

Optional when enabled: branch IP allowlisting, staff PIN, scheduled-shift checks tied to rotas, and QR login for fast device sign-in. Waiter may call a small set of cashier actions (accept order, mark served / serve later) without switching apps. See Staff interfaces below for each screen.

Owners and managers use Filament /admin for users and roles, menu and branches, clients, orders and discounts, table layout and booking settings, events, posts, memberships, module toggles, SEO, media, FAQs, sliders, alerts, staff security, reporting, and Orders → Staff activity log for an audit-style operations timeline. Changes flow through to the public site and /staff interfaces.

The public experience is built for food businesses: clear menu navigation, allergens and modifiers where you use them, and a smooth path into cart and checkout. Content blocks, FAQs, and alerts help you explain how you operate.

SEO-oriented fields and patterns help you publish pages and menu content in a way search engines can understand. Treat this as a strong baseline—your rankings still depend on competition, locality, and ongoing content.

Share openings, specials, or announcements on your own site instead of sending visitors only to social channels. Availability depends on your instance configuration.

Registered customers get a client dashboard: profile and saved addresses, order history and downloadable invoices where exposed, table bookings (adjust, cancel, pre-order, pay deposits) when you use that module, event bookings, and marketing subscription preferences.

Offer membership schemes that tie into ordering and customer records. Rules and pricing are yours to define in the product limits of your plan.

Define delivery by postcode bands, distance, or your own rules, and offer collection or delivery windows that match kitchen capacity. Fees can reflect distance or order value.

Where configured, customers see sensible progress for their slot or delivery—so the team spends less time on ad-hoc “where is my order?” calls. Driver and dispatch still work from the delivery driver staff interface.

At /staff/cashier: create and work till orders, look up clients, and quote totals before committing. Accept inbound orders (e.g. web), take payment, and mark orders complete. Per-line serve control: mark items served or serve later so kitchen, bar, and front-of-house stay aligned. Live polling keeps the view current.

Receipts: ESC/POS-style output from the browser; optional QZ Tray (certificate/sign routes) when local printing is set up. Printers and cash drawers depend on your hardware and OS. Cashier is the usual entry to the operations activity log during service.

At /staff/kitchen: a production queue for kitchen-routed items—mark orders preparing / ready, bump line items to ready in line with your flow. Live polling for queue updates.

At /staff/bar: the same operational pattern as kitchen—a separate surface so drinks (and bar-routed items) are not mixed with food tickets on one screen. Routing depends on your menu and item configuration.

At /staff/driver: a delivery queue for runs in your operational model—progress stages and mark delivered when the drop is complete. Separately, public token links (no guest login) can support delivery confirmation where your deployment exposes them.

At /staff/waiter—Professional when table service is in use: claim and release table sessions, create waiter-originated orders with table context, and send payment links for guests. Live polling and access to the same operations activity log pattern for floor awareness.

A single timeline of meaningful order and service events: new and progressing orders, status moves (including ready for collection or service), channel context (web, QR, waiter, till, voice, etc.) where recorded, plus kitchen, bar, till, driver, and waiter milestones—so you can answer what just happened without opening five screens.

• Cashier: in-venue activity experience from /staff/activity-log for fast glance and search during service (branch scope follows your deployment rules).
• Waiter: the same style of feed for floor awareness.
• Admin: Orders → Staff activity log in Filament for the full list, filters, and audit-style review.

Lines are persisted with event type, message, order link, branch, acting user where applicable, and metadata (e.g. status transitions). The staff UI uses category grouping (e.g. kitchen, bar, cashier, driver, website/QR/voice) for easier scanning. The log reflects what the application records; authorisation follows staff routing and order permissions.

Guests book tables against your rules: party size, sitting length, deposits or prepayment where you want them, and email-style confirmations aligned with your brand voice.

Professional tier.

Customers scan, order, and add to a tab in a controlled way—ideal for busy dining rooms. Bill requests and handoff to staff stay in one operational picture.

Professional tier.

Run tastings, supper clubs, or one-off seatings with their own pricing and capacity—alongside your day-to-day menu and booking setup.

Professional tier.

Plan who is on and when, handle simple swap flows, and export or summarise hours for payroll prep where the product supports it.

Professional tier.

Slice orders, revenue, and operational data for the periods and sites you care about. Use exports for accounting partners or internal review—without maintaining a separate reporting stack.

Central /admin configuration: users and roles, menu, branches and company, clients, orders and discounts, table booking resources and settings, events, posts and categories, memberships, module settings, SEO, media, layout and marketing blocks, FAQs, sliders, alerts, staff security lists, delivery tools (including map views where used), rotas (shifts, holidays, swaps, hours reporting), reporting backed by daily reporting models, and Orders → Staff activity log for operators who need filters and audit-style review.

Lite and Professional include one trading site in the base licence. Additional locations are added commercially per branch (see current add-on pricing). Enterprise-style group deals are quoted separately.

Optional AI phone agent: HTTP webhooks under /voiceai/* for your provider, menu data for agents, and related flows. Twilio SMS can support follow-up (e.g. delivery address or completing a voice-initiated checkout). When Voice AI is off, the rest of the platform runs as a full web, till, and booking stack. Priced separately from the base subscription; ask for current platform and usage rates.