Skip to content

From your first site
to your next regular.

We configure your brand, menu and loyalty rules, then test the experience with your team. Start with an agreed first site and expand once it works for your operation.

From your brief to a working experience.

Our team turns your brief into working guest and operator journeys on the product. Your people validate the experience before launch.

Through a marketplace

Order DLV-7F2K19:42

Delivery · via a third-party app

  • Loaded Birria Street Tacos£11.29
  • Chili Cheese Fries£8.59
  • Paid to the platform£19.88
CustomerVisits — · Points — · Contact —

Commission on every orderGuest data stays with them

Directly from you

Spike’s Diner · Soho19:42

Table 12 · via the QR code at the table

  • Loaded Birria Street Tacos£11.29
  • Chili Cheese Fries£8.59
  • Paid£19.88
Alex M.3rd visit · +20 points · 30 to the next reward

Order 4821Same account on web and app

Same order. Only one of them starts a relationship.

Illustrative orders
  1. Discover

    Start with the service.

    Map the brands, sites, guest journeys and the jobs your team needs to do. Identify what stays and what needs to connect.

  2. Design

    Make your brand feel at home.

    Configure menus, navigation, rewards and operator workflows around your brief. Our delivery team reviews the work with you.

  3. Try and refine

    Put it in your team’s hands.

    Walk through real scenarios: ordering, payment, redemption, approvals and the things that can go wrong.

  4. Launch and operate

    Keep improving after opening day.

    Release the validated first scope. Agree support ownership, then use the same build-and-review loop as your operation evolves.

Book a demo

Start with one site. Know what comes next.

Your pilot has an agreed scope, a named owner and a clear checklist. Adding locations follows evidence from the first site.

From the demonstration to your first live site
StageWhat you can expectWhat we confirm together
Explore todayTry the demo restaurant’s menu, ordering and rewards on your phone, and explore its real back-office screens.Payments are simulated. The back office captures contain seeded demo data; Alex’s journey and the employee scenarios are worked examples. We confirm the modules and connector scope for your pilot.
Scope your pilotChoose the first site, the guest journey and the loyalty rules. Map the menu, brand and team roles.Delivery schedule, payment setup, messaging, guest consent and the modules included.
Connect and validateTest the agreed ordering, payment and loyalty journeys with your team before live use.POS vendor access and supported capabilities, automatic versus staff-assisted steps, refunds and failed handoffs.
Measure and expandReview identified orders, return visits, redemptions and operational issues at the pilot site.Available data, success measures, support ownership and readiness for the next location.

A POS connection is a defined scope.

Retter has integrated with all major POS providers in Turkey and the GCC. Previous restaurant projects include integrations with Oracle MICROS / Simphony and NCR / Aloha. Start without a POS link. Connect when you are ready. How deep the link goes depends on what your POS vendor opens up. We confirm it in writing before you commit. Day one works with no POS link at all. Book a demo

Follow a worked guest journeySee how orders and rewards connect across two sites.

From the first order to a reason to return.

Three purchases, two locations and one approved campaign. Follow Alex to see where the evidence comes from and how an action reaches a guest.

Illustrative scenario with fictional records and actual demo screens. The invitation and return steps show the intended campaign workflow; sending and campaign measurement are not yet available. Today you can build audiences, preview offers and export a customer list.

An order becomes the start of a guest record.

Day 1 · 12:18

Alex signs in and orders lunch for collection. The items, the payment and the points earned stay together. Marketing permission is a separate choice, not a condition of buying lunch.

Related product journey Real demo screens

Start with the burger menu.

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

What your team sees Example operator record

Alex MorganGuest AM-104 · one location
Recorded purchases
1 purchase · £14.50 paid
Loyalty balance
145 points
Contact choices
Email opted in · SMS off
Latest activity
Day 1 · 12:18

The receipt becomes useful context

Identity
Signed-in guest AM-104; no matching by name alone
Order
SD-1042 · collection · Riverside
Purchase history
Vegetable bowl and lemonade: recorded choices, not inferred dietary needs
Contact permission
Email opted in · SMS off
Connected history (1 event)
  1. First direct order · £14.50Day 1 · Riverside · +145 points
    New
How the first visit connects

The account identifies Alex. The confirmed purchase adds an order and a points entry to that account. In this example 10 points are earned per £1 paid; the programme and the currency are yours to configure.

Each connection has a job.

Ordering records the purchase. The guest account connects visits. Loyalty applies your rules. Marketing records the invitation and the response. Your POS connection decides which sales flow in automatically.

POS integrations
Inspect the team’s workspaceActual product screens from the demo restaurant.

Behind every visit, a team in control.

Take a look inside the real back office. Explore performance, menus, guest records, audiences, loyalty and the tools your people work with.

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.

Explore employee workflow examplesHow your team reviews and approves proposed work.

Your people set direction. Agents do the legwork.

Illustrative employee workflows. Audience building, offer previews and exports are available today; the campaign delivery and response steps describe planned capabilities, not a live sending service.

A return campaign, ready for your decision.

The employee’s request“Find lapsed lunch guests and prepare a return campaign.”

  1. Investigate

    Show who qualifies and why

    Review lunch purchases, the last group visit and contact permission. Surface missing data and exclude guests who do not meet the rules.

  2. Prepare

    Build the audience, offer and message

    Propose £2.50 off a £12 order at Riverside, one use per eligible guest. Show the audience criteria, expiry and message together.

  3. Approve

    Marketing reviews the proposed send

    A named approver checks eligibility, offer limits and wording. They can edit or reject the proposal before anything is delivered.

  4. Follow through

    Send approved work and inspect the response

    Record delivery status and link redemptions to orders. Failures stay visible; a redemption alone does not establish uplift.

What stays visible

An inspectable campaign: eligible audience, offer limits, message, approver, delivery status and linked redemptions.

Questions about
working with us.

Read all FAQs
Is Retter a software vendor or an agency?

Retter is the company that builds and runs the complete ordering, loyalty and app experience brands rely on. It designs and builds a brand's website, app, loyalty programme and back office, integrates them with the systems the brand already runs, and keeps operating them after launch. The brand gets the whole experience under its own name from one team, rather than a tool to set up alone or a one-off build handed over at launch.

Who runs it after launch?

Retter does. The team that builds a group's website, app, loyalty programme and back office keeps operating them after launch, so the engineers who built the platform are the engineers who run it. The group's own team manages the day-to-day content in the back office: menus, sites, rewards and audiences.

Where is Retter based?

Retter has offices in İstanbul, Düzce and Dubai. It builds and operates the apps, loyalty and ordering behind food and beverage brands in Türkiye and the Gulf, including Starbucks, Costa Coffee and PAUL, and now offers the same to UK food and beverage groups of 3 to 30 sites.

What happens in a demo?

A demo is a 30-minute walkthrough with the Retter team. You place an order as a guest, see the account and rewards behind it in the team's workspace, and agree what a first site would include. Before booking, anyone can open the guest demo on their own phone: it uses a fictional restaurant and payments are simulated.

Does Spike’s Diner demonstrate the complete offering?

No. Spike’s Diner is a fictional restaurant used to demonstrate selected experiences, with simulated payments. The website describes the complete offering. Product captures, conversation excerpts and illustrations are labelled separately. The waiter-app examples illustrate personalised service; a Spike’s Diner waiter app has not been confirmed.

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 ↗