Skip to content
Feature

One order list where nothing ever gets lost

Every order — scanned or waiter-taken — in a single filterable list, from placed to completed. Add rounds to an open order, cancel with a reason, and trust that yesterday's bills stay exactly as they were rung up.

All features

Orders that never get lost

Every order — QR or waiter-taken — in one filterable list, from placed all the way to completed.

Filter by status, table or source. Add items to an open order, or cancel with a reason before it is served. Order numbers run sequentially per day, and every line snapshots its name and price at order time, so editing tomorrow's menu never rewrites yesterday's bills.

  • Filter by status, table and QR vs waiter
  • Add to or cancel an open order
  • Daily sequential order numbers
  • Prices snapshot at order time
DinePilot orders list with status filters and orders marked preparing, completed, cancelled and ready
Why this matters

When orders live in three places, some of them fall through the cracks

QR orders on one screen, waiter orders on a pad, changes shouted to the kitchen — and no single list that shows what is actually happening right now. When a manager asks "where is table six's order?", finding the answer means asking three people.

Worse, editing the menu can quietly rewrite history: change a price today and yesterday's bill no longer matches what the guest was charged. Cancellations with no reason attached make it impossible to tell a mistake from a walkout when you look back.

  • No single source of truth for what is on right now
  • QR and waiter orders tracked separately and reconciled by hand
  • Menu edits silently altering the value of past orders
  • Cancellations with no reason, so patterns are impossible to spot
How DinePilot solves it

Every order, every source, in one honest list

DinePilot puts every order — QR or waiter-taken — into a single list you can filter by status, table or source, from the moment it is placed to the moment it is completed. Add items to an open order or cancel it with a reason before it is served, and the whole team sees the change at once.

Order numbers run sequentially per day, and every line snapshots its name and price at the time it was ordered. Edit tomorrow's menu all you like — yesterday's bills stay exactly as they were rung up.

How it works

Simple to set up, simple to run

No hardware to buy and no technical skills required — just a few steps to go live.

  1. 1

    Orders flow into one list

    QR and waiter orders both land in the same place, each stamped with its table, source and a daily sequential number.

  2. 2

    Filter to what you need

    Narrow by status, table, or whether it came from a QR scan or a waiter, to find any order in seconds.

  3. 3

    Adjust while it is open

    Add another round to an open order, or cancel it with a reason before it is served — the kitchen sees it immediately.

  4. 4

    It closes cleanly

    Completed orders keep their snapshotted prices, so the record of what was charged never changes under you.

Key benefits

What you get out of it

One source of truth

Every order, both sources, one list — so "where is table six's order?" is a glance, not an investigation.

Change orders safely

Add rounds or cancel with a reason before service, with the kitchen updated the instant you do.

History stays honest

Prices snapshot at order time, so editing today's menu never rewrites yesterday's bills.

Numbers you can audit

Daily sequential order numbers make the day's trade easy to count, reconcile and look back over.

Compared with the usual way

One order list against a pad, a rail and a memory

Not a competitor comparison — a comparison with the paper-and-shouting workflow most restaurants run today.

"Where is table six's order?"

Usually — Ask the waiter, then the kitchen, then look behind the counter.

With DinePilot — Filter the list by table. One tap, one answer.

QR and waiter orders

Usually — Tracked in two places and reconciled by hand at close.

With DinePilot — One list, with source as a filter when you need to tell them apart.

Adding a second round

Usually — A new ticket that may or may not get matched to the first one at billing.

With DinePilot — Added to the open order, and on the kitchen board immediately.

Cancelling an order

Usually — A ticket torn up, with no record that it ever existed.

With DinePilot — Cancelled with a reason, so a kitchen error and a change of mind stay distinguishable.

Editing the menu

Usually — Not applicable on paper — but in most software, yesterday's bill quietly changes value.

With DinePilot — Each line snapshots its name and price at order time. History does not move.

Counting the day

Usually — Add up the tickets and hope none went missing.

With DinePilot — Daily sequential numbers, so a gap is visible rather than invisible.

Who it's for

Who needs one order list most

It helps every dine-in restaurant, but these are the rooms where the difference is largest.

Restaurants running QR and waiter orders together

Two intake channels is exactly when a single list stops being a nicety. Reconciling them by hand at close is the work it removes.

Owners who are not on the floor every night

When you cannot see the room, the order list is the room. Status, table and source answer most questions without a phone call.

Bars and long-session venues

Where a table orders four or five times across an evening and every round has to end up on the same bill.

Anyone who has been burned by a menu edit

If you have ever changed a price and found last month's reports moved with it, price snapshotting is the reason this page exists.

Inside the app

See it in the product

Real screenshots from the DinePilot staff app — no mockups, no marketing renders.

  • DinePilot orders list with status filters showing preparing, completed, cancelled and ready orders

    Orders list

  • DinePilot order detail with itemised lines, quantities and the option to add items

    Order detail

  • DinePilot receipt showing an itemised, completed order with tax and total

    Completed bill

On a real service

What it looks like on the floor

Three moments from an ordinary week, and what happens differently in each.

A guest says they ordered twenty minutes ago

Filter to their table. The order is there, timestamped, sitting at accepted because the kitchen picked it up and the ticket is still working through the queue. You can tell the guest exactly where it is instead of promising to go and find out.

The kitchen drops a dish

The order is cancelled with the reason recorded before it is served, and the kitchen board updates the same moment. A month later, when you look at cancellations, "kitchen error" and "guest changed their mind" are still two different things.

You raise your prices in March

February's bills, February's revenue and February's top sellers all stay exactly as they were rung up, because every order line kept the name and price it was ordered at. The new price applies from the next order onward and nowhere else.

Getting it right

Best practices and common mistakes

What the restaurants who get the most out of this do — and what trips up the ones who don't.

What works

  • Cancel with an honest reason rather than the quickest one. The reason field is only worth having if the data in it is true.
  • Add second rounds to the open order rather than creating a new one, so the table bills as a single itemised total.
  • Use the source filter at close to see how much of your service is running through QR — it is the clearest measure of whether the codes are placed well.
  • Check the daily sequence at close. Sequential numbers make a missing order visible in a way a stack of tickets never does.
  • Let the order list, not the kitchen board, be where you answer questions about service — the board deliberately shows only what is active.

What to avoid

  • Cancelling and re-creating an order to change it. Adding to the open order keeps the table's history and its bill in one piece.
  • Using a generic reason for every cancellation, which makes the whole field useless six months later.
  • Expecting completed orders on the kitchen board. They are on the order list; the board stays clean on purpose.
  • Treating a cancelled order as a deleted one. It stays in the record, which is the point.

As volume grows

The filters are what make the list survive a busy service: status, table and source narrow a few hundred orders to the handful you actually want in one tap. Daily sequential numbering means the count resets with the trading day rather than growing into something unwieldy, and price snapshotting means your historical revenue stays comparable year on year no matter how many times the menu is revised in between — which is precisely what makes the analytics built on top of it worth trusting.

FAQ

Questions, answered

Ask us anything else — we reply to every message.

Are QR and waiter orders kept in the same place?

Yes. Every order lands in one list regardless of source, and you can filter by whether it came from a QR scan or a waiter whenever you need to tell them apart.

Can I add items to an order after it is placed?

Yes. An open order accepts more items — a second round, an extra side — and the additions flow to the kitchen board immediately.

How do cancellations work?

An order can be cancelled with a reason while it is still placed or accepted. Recording the reason means you can later tell a kitchen mistake from a guest who changed their mind.

Will editing my menu change past orders?

No. Every order line snapshots the item's name and price at the time it was ordered, so changing prices or dishes tomorrow never rewrites what a guest was charged today.

How are orders numbered?

Sequentially per day. Each day's orders count up from the start, which makes the day's trade simple to count and reconcile at close.

Can I filter orders by table?

Yes. Alongside status and source, you can filter the list by table, so pulling up everything happening on a particular table takes one tap.

What is restaurant order management software?

It is a single system that records every order from the moment it is placed to the moment it is completed. DinePilot keeps QR and waiter orders in one filterable list, lets you add to or cancel an open order, and snapshots each item's price at order time so past bills never change when you edit the menu.

Run your next service on autopilot

Set up your restaurant, print your QR codes and take your first order today. Starter is free.

See pricing

No card required · Nothing to install for your guests

Free walkthrough

Request a demo

See QR ordering, the kitchen board and tables — we will reply within one working day.

Email is optional — leave it blank if you prefer.