Skip to content

Reporting & analytics

Reporting and analytics bring orders, sales, guest activity and rewards across your locations onto one consistent basis, with CSV export. An area manager compares sites and periods, then opens the orders, refunds and exceptions behind a change before choosing a response.

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 overview to one order

Three actual back-office screens from Spike’s Diner, with seeded reporting history: the overview, the branch view and an order record.

Start with the whole operation.

Choose a reporting period and see sales, order volume, average spend and preparation time together. This demo is showing London.

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.

Compare sites and periods
Recorded orders and sales, like for like.
Connect visits and rewards
Identified purchases, points earned and redemptions in one view.
Investigate the detail
Refunds, availability and missing data before you choose a response.

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
reporting & analytics.

Read all FAQs
Can we compare sites in one report?

Yes. The reporting Retter builds brings orders, sales, guest activity and rewards across a group's locations onto one consistent basis, with CSV export. An area manager compares sites and periods, then opens the orders, refunds and exceptions behind a change before choosing a response.

What is a restaurant CRM?

A restaurant CRM is one record per guest that holds their orders, visits, rewards and marketing permissions across every site and channel. Retter builds it as the guest account behind a group's website, app, table ordering and loyalty programme, so the team sees one history per guest instead of separate lists in separate tools.

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.

Who owns the guest data?

The operator does. The group is the data controller and Retter processes guest data under a data-processing agreement. Every guest record keeps its marketing permission per channel, guests can unsubscribe from any message, and the operator can export its data at any time.

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 ↗