Skip to content

Operations management

Operations management is the back office where your team maintains menus, products, options and approved dietary details centrally, gives each site its own hours, availability and service controls, and sees who changed what. Named roles, approvals and an activity history keep a multi-site group organised.

Start with the burger menu.

One burger follows through this mobile web journey, from its choices to its populated checkout.

Mobile web ordering · Native app & kiosk payment examples · Spike’s Diner demo

From the catalogue to the channel

Four actual back-office screens from Spike’s Diner: the menu catalogue, the Smash Burger editor, its modifier groups and availability matrix, and the content blocks used across web, app and kiosk. Existing configuration, inspected without saving changes.

One catalogue. Clear channel availability.

Browse products by category, check prices and see availability for web, kiosk and app at the selected site.

Real Back office screens · Seeded demo data · Contact details hidden where shown
Select a stage to watch its steps. Pause to inspect a screen.

What your team
gets with it.

Menus kept organised
Products, options and approved dietary details maintained centrally.
Room for each site to operate
Local hours, availability and day-to-day service controls.
Who can change what
Named roles, approvals and an activity history.

Part of your complete setup.

Your website, customer app, waiter app and kiosk integration come together as standard. Retter builds and runs them under your brand, connected through the same menus, orders and guest records.

Web ordering
Mobile responsive web
Mobile customer app
Mobile waiter app
QR table ordering
Kiosk integration
Back office
Kitchen operations

Questions about
operations management.

Read all FAQs
What does reducing vendor inflation mean?

Vendor inflation is the growing number of overlapping software suppliers, disconnected guest records and support handoffs in your customer stack. Retter brings CRM, loyalty, promotions, product information, engagement, personalisation, ordering and apps together through the Retter AI Suite. We map what can be consolidated and connect the POS and payment systems you keep, with the scope agreed around your business.

Does the online menu show allergens and nutrition information?

Yes. Each item on the online menu Retter builds carries its photos, options, price, allergen and nutrition information. The team maintains an item once in the back office and the change shows everywhere guests order: the website, the app, the table QR and the kiosk.

How long does it take to go live?

The target is two weeks for an agreed first scope. In week one Retter loads the menu, brands, sites and tables and the operator approves the guest screens. In week two the staff get the waiter app and the back office and the first site takes a guest order. POS integration and app-store review run on their own agreed timelines.

Do we have to replace our POS?

No. Retter builds around the POS a group already uses. The first site can go live without a POS connection: guests order and pay through the group's own website and app, staff scan a guest's code to add points and reporting starts on day one. Retter then reviews the POS and agrees which menus, orders, payments and loyalty events can be connected. How deep the link goes depends on what your POS vendor opens up. We confirm it in writing before you commit.

Let’s put your restaurant in the picture.

Tell us about your sites and the systems you use. We’ll show you the guest experience, the team’s workspace and what a first rollout would include.

The guest demo uses a fictional restaurant. Payments are simulated.

In your walkthrough

  1. Place an order as a guest.
  2. See the account and rewards behind it.
  3. Agree the scope of your first site.
The regular, recognised.Every visit adds to the same account.
Product gallery
Open image ↗