Saltar al contenido principal

Orders

The Orders page is where a manager watches a service: what is on the floor right now, what the day has sold, what is still owed, and every order behind those numbers. Open it from the sidebar under Service → Orders.

The Orders page on Today, with the summary strip

Online orders come first​

At the top of the page sits the Online orders queue. Orders placed on your website or through a delivery integration land here until someone accepts them; nothing reaches the kitchen before that. A sound alert can be turned on or off from the queue's header. When the queue is empty it says so, and new orders appear automatically.

The queue sits above the table on purpose: these are the only orders on the page that need an action rather than a look, and an order nobody answers is rejected when its acceptance window closes.

Each card shows the customer and the dishes, each with the options the guest chose (for example Sandwich club (Poutine régulière)). A website order also shows how it is being paid:

BadgeMeaning
Paid onlineThe guest paid on your website before the order was sent. See Website Ordering.
Awaiting paymentThe guest has not finished paying yet.
Pay at restaurantThe guest pays when they collect.
Partially refundedPart of the payment went back to the guest. The order still stands.
RefundedThe whole payment went back to the guest.

When the guest's ordering link carried a table and a source (a food court or another venue, for example), the card shows them beside the badge.

Source, in the queue's header, narrows the queue to one source: type the source name your venue's link uses. Orders from other sources are not lost: a line under the header says how many more are waiting, with Show all to clear the filter.

Pick a scope​

The bar under the queue decides which orders you are looking at:

ScopeWhat it shows
TodayOrders placed today. The default when the page opens.
YesterdayOrders placed yesterday.
OpenOrders still in service: not yet paid, cancelled or voided, whatever day they were placed.
DatesA range of days. Two date pickers appear; pick a first and a last day.
All timeEvery order the location has ever taken.

A caption beside the bar spells out the scope, for example Sat 12 Sep 2026 or 10 – 12 Sep 2026.

Days are the restaurant's days

"Today" is reckoned in the location's timezone, not the computer you are reading on. An order placed at 23:30 local time belongs to that day, even if it is already tomorrow somewhere else. Every time on the page — in the list and in an opened order — is shown on the location's clock too, so 17:43 means 17:43 in the restaurant wherever you are reading from.

Today and Open are live views: they re-read on their own every 30 seconds. The other scopes are history and load once.

The summary strip​

Five tiles above the list total the whole scope, not just the page of rows on screen:

TileMeaning
OrdersHow many orders are in scope, and how many of them are still open.
GuestsCovers: the sum of party sizes.
SalesThe order totals added up. Cancelled, voided, failed, abandoned and refunded orders never count.
OutstandingMoney still to collect on orders that can still be paid. Reads all settled when there is none.
Avg ticketSales divided by the orders that count toward sales.

Change the scope, the search or the status filter and the tiles follow.

The Open scope: only orders still in service

Find an order​

  • Search matches the order code, the daily number a guest reads out, the table name and the server's name. Partial text is enough: Patio finds every order on the patio tables, Sam finds Sam's orders.
  • Status opens a list of statuses to tick. Each one you pick shows as a chip under the toolbar so a filter can never be in effect silently; Clear removes them all. A table order that has been paid keeps its paid status while the kitchen finishes and serves its food: the kitchen's progress shows on its courses and dishes.
  • Source keeps only the online orders whose ordering link carried that source (for example mall-x). Use it to settle up with a venue.
  • The Balance column shows what is still owed on each order, or Paid. A cancelled, voided or refunded order shows —: nobody owes anything on it. Sort by it to bring the orders with the most outstanding to the top.
  • Sort by clicking a column header. Columns can be hidden or shown from the Columns button, and the page size can be 10, 25, 50 or 100 rows.

On a single-day scope the Placed column shows the time only; the date is in the caption.

Open an order​

Click anywhere on a row to open the order in a panel on the right, without leaving the list.

An order opened from the list, course by course

The panel shows:

  • The order number, its code, its status, the table, the server, the number of guests, the order type and where it came from.
  • When it was placed and, for online orders, the customer.
  • For a website order, a pickup box: how it is paid (the badges above), the table and source the guest's link carried, and the order's timeline. See The pickup box.
  • What was ordered, course by course. Each course carries its state (Held, Sent, Preparing, Ready, Ready to collect, Served) and how many of its plates are ready, and every line shows its own kitchen status. Each dish shows the options the guest chose, in brackets after its name.
  • Allergies — the allergies declared on the visit and how each conflict with a dish was decided. See The order's allergy record.
  • Subtotal, total and Balance: the amount still due, Paid once it is settled, or the order's status (Cancelled, Voided and so on) when it is an order nobody can pay any more.
  • Once money has gone back to the guest: Paid by card (what the card was charged, tip included), then each refund with what it was for (the dishes, or just an amount), its tax split, who made it and when, then Net paid. By the system marks a refund nobody made by hand, such as a paid order that was turned down.
  • Refund being recorded marks a refund the card processor has made that SSP hasn't finished recording. The money is back on the card, and Net paid already counts it. Its tax split and who made it appear once the processor confirms it. Don't refund it again.

The actions live at the bottom of the panel:

  • Take payment appears while there is money to collect on an order that can still be paid. It opens the virtual terminal with this order already loaded, so there is no code to copy across. It never appears on a cancelled, voided, refunded or abandoned order, even if a balance is left on it. It never appears on a website order the guest paid online either: a balance left on one is the guest's to pay on their own order page, and the panel says so.
  • Close appears for orders that never reached the kitchen and on which nothing was paid: still being built, or waiting to be accepted. Use it for an order that was opened by mistake or abandoned before anything was sent. You are asked to confirm and can add an optional reason, which is kept with the order. The order is marked Cancelled and leaves the kitchen board; nothing is refunded, because at that stage no payment was taken and no food was made. Closing needs the cancel orders permission. An order that is already cooking cannot be closed here — voiding it is a manager action with its own approval. An order with money paid on it is never closed: it is refunded instead (below).
  • Refund, Remove items and Cancel & refund appear on an order with money paid on it. See Refunds and changes to a paid order.

The Actions column of each row has View, Close where it applies, and Refund on an order with something left to refund. People without the cancel orders permission don't see Close anywhere; people without the refund orders permission don't see Refund, Remove items or Cancel & refund.

The pickup box​

A website order opens with a pickup box above its dishes.

The timeline lists each step the order has been through, with its time on the location's clock. Only the steps that happened are shown:

StepWhat happened
PlacedThe guest sent the order.
PaidThe guest paid online.
ConfirmedThe order was accepted, by someone or automatically.
Sent to the kitchenThe order reached the kitchen. A pre-order is sent at its start time.
ReadyThe kitchen finished it.
Picked upSomeone marked it handed over.
DeclinedIt was turned down, with the reason: closed, too busy, item unavailable or not answered in time.
Expired unpaidThe guest never paid, so it was cancelled. Nothing was charged.
RefundedMoney went back to the guest.

Under the timeline, a line sums it up when it can, for example 2 min to pay · 14 min in the kitchen.

Picked up marks the order handed over. It appears once the order has reached the kitchen and until it is picked up, and never on an order that was turned down, expired, cancelled or voided. It stays after a dish has been removed and refunded, since the guest still comes for the rest. If the guest still owes money on the order, Picked up is refused and the panel says how much: the guest pays it on their order page, then the order can be picked up.

The kitchen can mark the same order picked up from the kitchen screen; see Pickup orders: handing over in the Kitchen documentation.

Refunds and changes to a paid order​

A guest calls: they ordered by mistake, or they want to drop a dish from an order they already paid for. Open the order. These actions need the refund orders permission.

Refund gives money back without changing the order. The dialog shows what was Already Refunded and the Refundable Amount: what the guest paid and has not had back yet. Choose a Full Refund of that amount, or a Partial Refund of an amount you type, add an optional reason, and click Process Refund. A closed or completed order can be refunded too, as long as money is left on it; a cancelled or voided order can't.

Remove items takes dishes off a paid order and refunds the difference:

  1. Tick the dishes to remove.
  2. Pick a reason: Guest changed their mind, Wrong item, Kitchen error, Goodwill or Other (Other asks for a few words).
  3. Click Review refund. SSP works out the exact refund, tax included, and shows it. It never refunds more than is left on the order after earlier refunds. When what the guest still owes covers the removal, it says No refund needed: what is still owed covers it. When nothing is left to refund, it says No refund needed: nothing is left to refund for these items.
  4. Click Remove and refund to confirm, or Remove when no refund is needed. If the order changed in the meantime, the new amount is shown and you confirm again.

Nothing can be added to a website order the guest paid online. Ask the guest to place a new order, or take the extra dishes at the counter.

Cancel & refund is for a website order the guest paid online and has not picked up yet. Give a reason (it is kept with the order, never shown to the guest) and confirm. The order comes off the kitchen, the guest gets the whole payment back on their card and is told the order was cancelled. This cannot be undone. Once the guest has picked the order up, use Refund instead.

If the refund went through but the order was not marked cancelled, the button reads Finish cancelling: pressing it only cancels, it never refunds a second time.

Never refund twice

If a message says the refund was sent to the card but is not fully recorded yet, the guest has their money. Do not refund again: the refund appears on the order shortly. SSP Manager also holds off any other refund on that order for a few minutes, from every device.

If the message says No answer came back or Refund outcome unclear, the refund may or may not have gone through. Check the order first. Pressing again with the same amount is the same refund, never a second one. If it had already gone through, you'll see That refund had already gone through; nothing more is refunded.

A website order the guest paid online can't be merged with another order.

Looking back​

Use Dates for anything older than yesterday: pick a first and last day and the list, the tiles and the search all work over that range. All time is the ledger of everything the location has taken, newest first.

The Dates scope with a range picked