Book a table
A clearer route from interest to reservation.
Explore the diary pilot
A collection of practical systems for the work around your service. Menus, bookings, orders, gifts and reasons to come back—built around your venue.
Explore existing pilots, assisted tools and the connected hospitality roadmap. Features and provider connections are agreed before launch.Bring bookings, gifts and loyalty closer together as connections are completed.
Give customers the right next step. A café may need two of these; a restaurant or venue may use all four.
A clearer route from interest to reservation.
Explore the diary pilotDirect collection and delivery ordering in development.
See Takeaway OSGive a meal, an experience or a reason to return.
Try the voucher demoPrivate parties, celebrations and group occasions.
Plan the enquiry journeyA proper local, a late-night bar or a special occasion. Choose a starting point and shape it around your venue, with your own content, colours and photography.
A dramatic invitation panel, fine serif headlines and celebration-led sections.
Explore this design →Choose your venue type for a suggested starting shortlist. Add or remove tools below; this does not create a subscription.
7 tools in your planning shortlist. Each has its own readiness and setup needs.
Explore what exists, what you can try and what is planned. A pilot can demonstrate a useful workflow without being a complete connected service.
Private manager-scoped visit closing retains served orders and bills. Manual external receipt entries, partial balances and reasoned corrections preserve the original history. Earlier authenticated pilot checks covered role privacy and simultaneous writes. These records do not charge cards, verify bank receipts, reconcile booking deposits or issue provider refunds; device and venue acceptance remain open.
Optional compatible iPad/tablet routes for a staff till, customer kiosk and kitchen display. Existing venue screens are demonstrations. Production guest isolation, provider payments, hardware, printers and outage handling require implementation and validation.
Pocket HR & Operations private pilot: separate manager and staff areas, saved draft/published shifts, personal clock-in/out and breaks, manager-assigned tasks, versioned policy acknowledgements and site-scoped access. Staff see their own permitted shifts and tasks. Onboarding, leave, advanced rota, approved timesheets and payroll remain development work; venue rollout is not yet approved.
Fictional venue demo with opening, service and closing checks, temperature readings, corrective actions and a printable log. Venue-specific controls and durable live records require completion.
Saved venue-scoped campaign drafts, staff review, expiry, communication preferences and activity history. Automatic recipient matching and delivery are not connected.
Your brand, photographs, menus and prominent booking, voucher and enquiry links. Keep your existing website or plan a new one.
Create sections, descriptions and prices; review content, share a hosted menu and QR link, and print through the browser. Seasonal design and richer marketing connections are a later step.
Private saved table diary with opening hours, party size, seat-capacity and overlap checks, cancellations and atomic changes with retained history. The staff service workspace uses named role grants and stale-save protection. Waiting-list automation, public self-booking, deposits and reminders are not released.
Private ordering work covers menus, extras, availability, collection slots and an order board. Public release, merchant payments and supported delivery rules still need completion.
Public table-specific QR ordering and bill splitting remain planned. A separate private service pilot already supports table-linked held orders, protected QR arrival and staff-controlled kitchen release. This does not establish public self-ordering, card payments or automatic bill settlement.
A private saved pilot for held orders, slot limits, staff acceptance and separate kitchen release. Protected guest claims and table QR arrival have role, expiry, table and venue checks; a reservation diary connects permitted table visits. Guest self-ordering, physical-device acceptance, merchant payments and live rollout still need completion.
Voucher codes, balance checks and partial redemption. Online purchases and delivery methods are confirmed with the venue’s merchant setup.
Event listings, capacity and admission records for music, tastings and ticketed evenings. Confirm buyer-facing tickets, delivery and payments for the chosen rollout.
Private grouped-table bookings validate every allocation before saving, support whole-group cancellation and atomic date/time moves, and retain terms and change history. Dedicated function-room capacity, group deposits, quotes and buffet service sheets remain planned. A group of tables is not a confirmed function-room booking.
Reward rules, customer records, qualifying activity and redemption history. Programme membership and permission to send marketing remain separate.
Joining links, counter QR codes, staff stamps and reward redemption. Configure a practical programme around your café.
Planned reminders, newsletters and return-visit offers through approved email, SMS and WhatsApp connections, with channel-specific permission and opt-outs.
Newsletter drafts, seasonal campaigns and promotional content concepts. Design-tool connections, generated video and scheduled social publishing remain planned; Marketing OS prospecting is a separate product.
Bring relevant booking, voucher, order and loyalty activity into a business-scoped customer history as connections are completed. Buying never automatically means marketing consent.
Planned combined sales, payments, refunds and repeat-visit reporting, with invoice workflows. Current separate records do not yet form a single hospitality ledger.
A separate private accommodation pilot for stay records, guests and maintenance. Booking-channel connections and live guest payments are not confirmed for release.
Planned question banks, host packs and team scoring. The production quiz engine and live phone participation are not yet released.
Private course outlines, lesson resources and assessment plans. Learner accounts, marking and certificates remain future work; the system does not provide professional accreditation.
The private testing pilot saves held orders, staff-confirmed arrival and kitchen release with owner and staff permissions. Protected guest/table QR arrival and a saved reservation diary are available for fictional testing. Live payments are not enabled.
Open the private testing office → · Read the testing guide →
Staff enable pre-orders for selected service periods, limit orders per arrival slot and pause new orders when busy. A pause does not silently cancel orders already accepted.
The guest selects an enabled arrival time and available dishes.
The venue confirms the pre-order and any payment or deposit terms.
The kitchen receives the agreed order in its held-for-arrival queue.
At the table, the guest uses the QR link and confirms their own order.
Arrival links the order to the table; the team controls release to preparation.
Planned Table OS covers QR menus, table-linked ordering and kitchen/bar routing. Table management covers reservations, covers, availability and seating separately.
Proposed options: equal shares, selected items or a chosen amount. Paid and outstanding amounts must stay clear so the same bill cannot be charged twice.
Agree advance-order cut-offs, item changes, late arrivals, no-shows, cancellations and staff-assisted check-in. A guest without a phone can be checked in by the team.
This is a proposed service journey, not live kitchen software. QR arrival confirmation, staff controls, reservation checks and preparation handoff have testing implementations. Physical-device acceptance, merchant payments and refunds still need completion. A table QR alone must not reveal or activate another guest’s order.
Functions and buffets deserve their own journey. Plan for small private parties, funeral gatherings, christenings, work events and celebrations.
The private testing diary now records table-based parties and functions, event names, required deposit amounts and a snapshot of the venue cancellation policy. Whole-room or multi-table allocation, quotes and live deposit collection remain to be connected.
Private testing available · deposits are recorded as outstandingCapture the occasion and requirements.
Check the date, room and service capacity.
Confirm the quote, terms and payment arrangements.
Create the agreed menu and internal service plan.
STAFF MANAGEMENT & HR · POCKET HR PRIVATE PILOT
Managers coordinate their site. Staff use their own account to see permitted shifts, assigned tasks and policies, with private records restricted by role.
Create draft and published shifts, record online clock-in/out and breaks, and review recent attendance summaries. Approved timesheets and payroll export are still in development.
Assign instructions, priorities and due dates to each person. Staff update their task status and acknowledge the relevant version of a published policy.
Explore Staff Management & HR in the App Store → · Management pilot → · Staff sign-in →
Saved private pilot, not a released HR or payroll service. Staff onboarding, leave, advanced rota, timesheet approvals and jurisdiction-specific rollout remain to complete. Shared kiosk/PIN and badge hardware require separate validation. Existing venue-demo staff screens remain illustrative.
KITCHEN · FOOD SAFETY
Make daily checks easier to record and review. The current fictional venue demo connects food-safety screens with the kitchen, table and staff demonstration.
Opening, during-service and closing checklists, temperature readings and recorded corrective actions for out-of-range results.
Named demo staff, timestamps and a printable food-safety log. Demo sessions are temporary and must contain fictional records only.
Before live use, complete the venue’s hazard analysis, approved critical controls and limits, monitoring, corrective actions, verification and retention arrangements.
Allergen information is also shown in the menu and kitchen demo. This is not a complete live HACCP system or certification.Try the kitchen and food-safety demo → · Read the food-safety guide →
GIVE YOUR NEXT SERVICE A HEAD START
Your customer relationship should continue after the bill. Plan useful communications around your tables, your menu and the reasons people love visiting.
Prepare availability and cancellation notices, with current capacity and offer expiry reviewed by staff.
Plan priority booking windows and relevant invitations for eligible customers.
Draft menu changes, specials, seasonal offers and event announcements.
Prepare after-visit and win-back messages with a clear booking or ordering link.
Save channel choices, planned frequency and quiet hours. Buying or booking never automatically supplies marketing permission.
Save drafts, record review, pause a campaign and keep an activity trail within the venue’s pilot workspace.
Try the fictional growth demo → · Open saved pilot workspace →
Saved planning pilot available. Audience descriptions are briefs, not matched recipient lists. Sending, automatic scheduling, live availability triggers, frequency enforcement and unsubscribe delivery still need integration.
CHOOSE YOUR STARTING POINT
A branded design with your photographs, menus and clear booking, ordering and voucher journeys. Review the saved design before release.
See website designs →Choose the operational tools your venue needs and agree the package, provider setup and launch checks.
Compare starting packages →Add selected website widgets through the Hospitality OS widget store within our App Store. Use supported links or embeds without taking the full system.
Browse website widgets →YOUR TILL IS YOUR CHOICE
Pubs and venues can keep their existing system. Optional till integration is being evaluated, with Square the first proposed sandbox candidate.
Record your current provider and model in the growth workspace. Compatibility and access must be checked before quoting any connection.
Start with verified sales and refunds, business and location matching, and reconciliation. Table availability and marketing permission need their own reliable sources.
No till provider is connected. Hardware, processing, provider plans and integration support are separately scoped.An optional staff-circle connection to Gizalift is planned alongside the operational tools. Participation and private wellbeing records need a separate, reviewed setup.
Explore the App Store →COUNTER · FLOOR · KITCHEN
Choose the screens your team needs: a counter till, a handheld staff device, a kitchen display or a customer self-service kiosk. Keep your existing till where that is the right fit.
Explore a compatible tablet POS route for counter or table service. Staff accounts and permissions must protect orders, refunds, takings and customer records.
Our venue till screen is a demonstration. Live payments need a supported provider app, approved hardware and a tested connection.Planned customer-only ordering on a secured countertop or freestanding tablet. Keep the journey simple: menu, options, basket, payment route and order confirmation.
A kiosk needs its own guest mode, basket/session clearing, accessible interaction and help route. It must never expose the staff office. Our production kiosk is not built.Use a tablet-sized screen to demonstrate kitchen/bar queues and staff tasks. Agree locations, charging, network, printers and who can see each screen.
The shared venue demo uses fictional data. Reliable live routing, printer support, device security and outage handling still require validation.Add a menu, booking, voucher or other supported journey to your existing website through the Hospitality OS widget store. That does not require a new till or the full system.
Browse website widgets → · Try the venue screens → · Read the iPad and kiosk setup guide →
Tablet and hardware setup is optional. Confirm the exact iPad model, operating system, provider, country, stand, reader, printer, network and software charges before purchasing. No universal hardware compatibility, offline operation or completed provider integration is claimed.
Someone books a table, receives a voucher, joins a rewards programme or comes to an event. The connected hospitality plan brings the relevant history into a clearer view for that business.
Know the visit.
Know the occasion.
Recognise the regular.
Follow up with permission.
Step through the concept, then explore the relevant existing sample tools. This is a guided concept, not a video or a connected venue dashboard.
A clear menu, a useful offer and the right button. Your website should help a guest decide what to do next.
Explore website designsA narrated introduction and task-training clips can follow the same reusable demo framework as Your Club OS. Audio has not been generated yet.
Keep your website and add a useful tool, or plan the website and relevant systems together. Final module scope and provider costs are agreed before activation.
ONE CLEAR ONGOING SERVICE
Your website package covers website hosting, your hospitality hub and the back-office tools included in your plan, together with the maintenance, monitoring and support defined in your plan. The fee funds the ongoing service around your business, including the agreed review of tool performance and integration.
Shown separately: any one-off setup, design or migration fee, optional development and provider usage such as card processing, SMS or WhatsApp. Included allowances, monitoring frequency and response targets are confirmed before you subscribe. Widget-only plans cover the selected tool and its hub; hosting for an existing third-party website stays with its provider unless a website package is agreed.
Current restaurant catalogue starting point, including website hosting.
A focused website and core venue-tool discussion.
Review the existing packageCurrent restaurant catalogue starting point, including website hosting.
Review the wider events, marketing and customer-growth requirements.
Review the existing packageExplore separate app listings and discuss the one workflow that would help first. A website button, hosted page or supported embed may be enough.
Explore the OS App StoreThese are existing catalogue proposals, not a new all-inclusive hospitality tariff. The tools on this page are not all included in either price. Optional modules, imports and specialist integrations are scoped separately. DIY website setup is £0; assisted website setup is £179 once for the defined up-to-five-page scope. Prices are GBP, excluding VAT where applicable. Domains, mailboxes, merchant processing, SMS and WhatsApp are separate. Euro pricing is agreed before an Irish rollout. No billing starts here.
Food-safety checks have a fictional venue demo. Venue-specific HACCP controls, durable records, recipe costing and margin analysis need further work.
Optional iPad/tablet till and self-service kiosk routes, printers, delivery and booking-channel connections need device-specific compatibility, provider agreements and rollout checks.
Staff documents, resources, invoices and tasks can be scoped around existing shared tools. Payroll, inventory and universal accountancy sync are not included by assumption.
No. Start by reviewing a tool link, hosted page or supported embed. A full website move is a separate choice.
No. Reservations organise the visit and table capacity. Table OS is the planned QR ordering and service workflow after guests arrive.
That optional journey is now available for fictional testing. The team controls availability and arrival-slot limits. Advance orders stay held until the guest confirms arrival at their table, then the kitchen controls preparation. It is separate from takeaway ordering.
Payment readiness is checked for each venue and module. Buying an OS subscription does not itself activate merchant checkout. Connections, refunds and customer journeys must be confirmed before taking live sales.
No. Menu OS is the Sector OS widget/workspace product. Nice One Menus is a separate standalone brand and licence.
No. The current Marketing OS listing concerns prospecting. Hospitality promotion, newsletter drafts and future design or social-publishing connections are described separately here.
A CLEAR ROUTE INTO YOUR VENUE
Choose a new website, selected website widgets or a wider back office. Keep your existing till where it suits your service. We agree the scope and show the relevant workflow before switching anything on.
Walk through a fictional demo. Agree the tools, price, responsibilities and support your team needs.
Review existing records and permissions. Test imports, access and exports, then reconcile the result.
Run a sample service, booking and order. Test selected devices and connections, then train your team.
Approve the working scope, cutover and recovery plan. Use Ask Dougie, task guides and private support, with diagnostics and development agreed in your package.
The venue demonstration, website-widget catalogue and saved customer-growth planning can be explored. Public demos use fictional records.
Live marketing delivery, connected pre-arrival ordering, production staff operations, till payments and our own kiosk remain to finish. Stronger login, remaining privacy checks, full migration and account-wide exports are also launch work. Your agreed pilot scope determines what must be completed before use.
Explore website widgets → · Arrange a scoped demonstration →
TRUST & DATA PROTECTION
Your takings, customer list and staff records are your business. Knowing the software owner should never mean giving them routine access.
The shared business-workspace checks now require actual ownership. A platform admin title alone no longer opens another customer’s workspace. Club Office uses ownership or an active scoped membership.
Other module access paths still need the complete release audit.Passwords are hashed. Repeated failed logins trigger a lockout. Session cookies use Secure and HttpOnly protection, and password reset invalidates existing sessions.
Multi-factor authentication, passkeys and a customer session-management screen are not yet implemented.Required launch policy: the venue or club approves any support access to private operational records, with a defined purpose, limited duration and a visible access log.
The dedicated grant, expiry and audit workflow is still to build. Information you submit in a support ticket is intentionally shared with the support team.Use available module exports and agree a complete exit pack before account closure. Downloading records does not delete them or end your subscription.
Understand exports →Connections must identify what data a payment, messaging or hosting provider receives and why. A sale or booking does not automatically grant marketing permission.
Provider agreements, data locations and retention schedules need confirmation before live rollout.Preventing infrastructure administrators from reading stored data requires an additional encryption and key-custody design. That protection is not currently implemented.
We do not claim that nobody, including the software owner, can technically access all stored data today.These remain pilots. Full access testing, stronger authentication, customer-approved support access, retention and recovery checks, and independent security review must be completed before confidential live operations. Use fictional records in public demonstrations.
Read the Trust & Data Protection guide →MOVING FROM ANOTHER SYSTEM?
Start with a migration assessment. Agree the scope, cost and cutover before moving your records or changing the way your team works.
List the systems, contracts, website, domain, provider accounts and records you want to keep. Confirm export access and what can legally and technically be transferred.
Menus, customers, future bookings, orders, vouchers, loyalty balances, staff and website content. Keep allergen information and food-safety history explicitly reviewed. Agree the enabled modules, responsible people, timeline and any manual work.
Use an agreed secure transfer route. Match source fields, identifiers, dates, currencies and statuses. Deduplicate carefully; preserve consent source, purpose, time and withdrawals where available. Unknown consent stays unknown.
Import a small reviewed batch into an isolated test workspace once the required importer is built and approved. Check rejected rows, ownership, counts, totals and representative records with your team.
Practise daily tasks using guides and Ask Dougie. Reconcile future bookings, active orders, voucher or loyalty liabilities and any collected money. Avoid two systems accepting the same booking or payment.
Agree a change freeze, final export and delta reconciliation. Keep a recoverable backup and an agreed rollback window. Obtain customer sign-off before changing links, domains or intake.
Check the first live journeys, staff access and support issues. Keep the old system accessible for an agreed retention period, then close or remove access only with approval.
Keep your existing website and till where that is the right fit. Payment credentials, card details, subscriptions and provider tokens are not assumed transferable; the relevant provider must confirm the route.
Current stage: guided migration planning. A universal importer, automatic provider transfers and zero-downtime switching are not available. Each source system needs a verified mapping, test run and agreed price.
Use the exports available within each enabled tool, then request a scoped exit pack for the remaining records. Agree machine-readable CSV/JSON, document originals, identifiers, timestamps, consent evidence, financial balances and an exceptions list. Verify the files before closing the account.
Available now: the saved Club Office task/news working report has a CSV export; Hospitality Growth Office exports its saved planning data as JSON and campaign rows as CSV. These are partial module exports. A whole-account archive, bulk document bundle and full-suite extraction are still to build.
Read the export and exit guide →
Read the migration guide → · Start your migration brief → · Ask Dougie for help →
YOUR TEAM HAS BACKUP
Your own brand, useful tools and ongoing help to get more from every service.
Plan a fresh branded website or keep your existing site and add selected website widgets. Start small and expand when it helps.
Explore website widgets →Choose your system, describe the task and find checked answers with source guides and clear next steps. If you still need help, Sid prepares a ticket for you to review.
Ask Dougie →Search setup, daily tasks, team access, website updates and troubleshooting. Each guide explains the steps, what to check and which features are ready or still in development.
Open your user guide →Sign in to raise a private ticket, add a screenshot and follow replies in your support history. The team can connect relevant diagnostic evidence to the investigation.
My support tickets →Existing operator tools record diagnostic runs, test evidence and launch blockers. This helps the team investigate problems and review readiness before a tool is released.
Continuous monitoring and independent alerts are not configured. Response hours and service targets must be agreed.Build requests, revisions and review history support improvements to websites and apps. Scope, testing, release readiness and any additional costs are reviewed before rollout.
My system build →Ask Dougie · Searchable guides · Getting started · Private tickets and replies · Screenshot support · Build reviews · Diagnostic evidence · Training resources
Written help is available now. Training currently provides lesson storyboards and companion guides; recorded lessons, live AI conversation and support email notifications are still to be connected.