Supaorder, Recorded Live

0:00 Introduction

This is Olive and Ember, a demo restaurant running on Supaorder. Everything you are about to see is the live product on a demo tenant, with demo data, recorded in one session.

Over the next few minutes we follow orders through every role: the customer, the front of house, the kitchen, the driver, the counter, and the owner.

0:24 Customer orders

A customer lands on the restaurant's own web app. No marketplace in between, no app to install. They pick delivery, pickup or dine-in at a table.

The address check happens before the menu, so a customer outside the delivery zone finds out now, not at checkout. Downtown delivery is free over $50 here and $4 under it.

The menu is the restaurant's menu. A Margherita comes in two sizes, so the customer picks the 16 inch and adds extra toppings. The sold out olive oil cake is shown as sold out, not hidden.

Every item can carry a photo, a description, sizes and add-on groups, and the price updates as the customer chooses. Special instructions travel with the line all the way to the kitchen ticket.

At the cart, the welcome coupon takes 10% off. The customer pays with store credit they already hold, so the order total drops to zero and there is nothing to type.

Points, vouchers and store credit all live at the same checkout, so a regular sees every benefit they hold in one place.

The order is placed, and the customer sees its status move as the restaurant works it. Zero commission on this order, because this is the restaurant's own channel.

Pickup works the same way with a ready time, and an order can be scheduled days ahead for a Friday dinner or an office lunch.

Dine-in works from a QR code on the table. The guest scans it, orders from the same menu, and the ticket arrives tagged with the table number.

2:15 Front of house

The same order reaches the front of house in the partner app. Staff accept it, set a prep time, and the kitchen ticket goes to the printer or the kitchen display.

Auto-accept is a setting, so a busy kitchen can take orders the moment they land and only adjust the prep time when it needs to.

The register sees the same queue. Online, phone and walk-in orders land in one place, so nothing is re-keyed.

A walk-in wants an Ember Burger with fries. The cashier rings it on the register and takes cash at the counter. Card at the counter uses the same terminal the online orders settle through.

Split Tender is built-in. Part cash, part card, part store credit on one sale. Refunds need a manager's PIN and every movement lands in the till session.

Tables and tabs live on the register too. A table can carry a running tab across rounds and settle at the end.

Look the guest up by phone, and every register sale earns them points automatically. No separate loyalty app at the counter.

3:43 Kitchen

In the kitchen, the display shows two lanes on purpose: preparing and ready. Each item is checked off as it is plated, and the ticket moves to ready when the last one is done.

Each ticket shows the order type, the table or the pickup name, and the special instructions, so nobody reads a printout across the pass.

If a guest changes their mind, staff edit the order inside the edit window. The difference is charged or refunded, and the kitchen ticket updates in place instead of being re-sent.

Edits are bounded by a window the owner sets, and every change is logged with who made it.

4:28 Delivery

Delivery. The driver opens the partner app goes online and accepts the job. Drivers can be the restaurant's own, or a delivery network like DoorDash Drive, Uber Direct, Shipday, or Nash for overflow.

Delivery zones are drawn as shapes on a map, each with its own fee rule, so the fee the customer sees is the fee for their address.

The customer follows the driver on a live map, with the driver's name and vehicle. The same experience whether the driver is yours or a network's.

The driver app keeps the driver's location current in the background, and the restaurant sees the same map from its side.

Larger operations get a dispatcher panel in admin, with auto-dispatch by distance and load, send to all, or nearest first. This single-outlet demo lets the restaurant assign its own driver.

5:29 Loyalty in store

Loyalty in store. A walk-in guest enters their phone number on the counter tablet and sees their points.

The tablet faces the guest, so the guest types their own number and staff never need to read it out.

They redeem a reward, and the register approves it in one tap.

Marketing consent is captured on that same screen, so the guest who walked in today becomes a customer you can reach tomorrow.

Back in the customer's app, the balance is updated, the store credit wallet is there, and so is their referral code.

Store credit can be topped up in the app, and a refund can go straight back to it instead of waiting days for a card reversal.

6:22 Numbers and growth

Now the numbers. The dashboard shows sales by day and the top items, and the reports section holds 75-plus built-in reports, each with export.

Customers are sorted into nine automatic RFM segments: VIPs, regulars, at-risk, lapsed and the rest. These update by themselves from order history.

Each segment opens as its own customer list, from loyal regulars to customers who have quietly stopped coming.

Pick the at-risk segment and build a voucher campaign for it. Choose the offer, the channel and the window, then schedule it. This one goes out next Tuesday as a push notification in the app.

Autopilot campaigns run on their own once they are set up: a welcome for new customers, a nudge for lapsed ones, a birthday offer, each with a cooldown so nobody is messaged too often.

Each campaign reports what was sent, accepted and redeemed, with its conversion rate and the results per channel.

Reports filter by outlet, order type and date, and every table exports to CSV for the accountant.

7:44 Admin and control

Admin and control. The menu builder handles categories, variants, add-ons and availability, with a spreadsheet import for moving a menu in.

Customers rate dishes after the order, and reviews are moderated in admin before anything is shown.

Price books set different prices per order type and per outlet, and a kiosk price if you run one.

Staff accounts carry roles, from owner and manager to driver, and each role sees only what it needs.

Devices are enrolled with a code from admin. The register, the kitchen display, the kiosk and the counter tablet all register against the same outlet.

Brand and typography settings change the customer app's look without a release. Your brand, your domain, your customer data.

The native apps go out under the restaurant's own developer accounts, so the store listing carries the restaurant's name.

Everything shown today is documented step by step on the docs site, which is what a partner follows during onboarding.

That is one order through every role on Supaorder. Book a demo at supaorder.com, and we will run it on your menu.