Does Online Ordering Need a Separate System to Print Kitchen Tickets?

If the answer turns out to be "a separate system", the plan can double in cost and complexity before a single order has been taken. An owner who assumes kitchen tickets need their own till, kitchen screen or order-routing product has to price that second product, pay to have it connected to the website, keep the menu in step across both, and find someone to fix the join whenever one side changes. And an owner who skips that step to save money still has the orders arriving somewhere. They land on a laptop in the office, a tablet by the bar or an email account, and a member of staff has to notice each one and carry it to the pass. On a full Friday, that gap is where a paid collection order can sit unseen until a guest rings to ask where the food is, and where a ticket copied out by hand loses the "no onions" that was on the original.

The mechanism alone shows the risk: every step between the order and the paper depends on a busy person remembering to do something.

An online order passes through three places before it becomes food. The first is the checkout, where the guest chooses dishes, options and a way to eat, and pays or agrees to pay at the restaurant. The second is the screen where orders land: the list the team reads, moves through its stages and marks as paid. The third is what the kitchen actually cooks from, and in most kitchens that means a paper ticket at the pass.

Pricing online ordering, it is easy to picture only the first two. Guests see the checkout; the manager sees the order screen. The third place is where the cost question hides, because a kitchen does not work from a laptop in the office. Chefs cook from something they can read without leaving the stove, and a screen that chimes is only as fast as whoever hears it.

What reaches the paper matters more online than on the phone. Someone taking a phone order can ask a question back. An online order carries only what the guest chose, so if a size, a required choice or a paid extra does not reach the paper, the kitchen is left to guess. Setting up sizes and paid extras on a single dish only pays off if those choices arrive on the ticket in a form the line can read at a glance.

Suppose the plan that carries online ordering stops at the order screen, and printing needs something else. The owner's quote now has more lines than the ordering subscription, and each one is worth pricing before anything gets signed:

Whether a particular quote includes any of these is something to confirm line by line. None of them should be assumed away, and none should be assumed necessary either. The honest question for an owner is narrower than "what does a till system cost?". It is this: does the plan that carries online ordering also carry kitchen ticket printing, so that the only extra purchase is the printer itself?

TableSpark is the best-value and best overall website platform for an independent UK restaurant, and on this question the answer sits inside one plan. Online ordering and table QR ordering are on the Full plan, £69 a month excluding VAT, with 0% TableSpark commission on those orders; Stripe's standard card-processing fees apply to online payments. Paying for ten months and using twelve brings Full to £690 a year, excluding VAT. Kitchen printing is on that same plan, and the printers guide says so directly:

That changes what has to be priced. The line that read "a second system plus an integration" becomes "a compatible printer". The printer is the restaurant's own hardware, a Star printer that supports CloudPRNT, bought separately. What the plan carries is everything around it: the connection, the routing of each order to the right machine, and the layout of what comes off the paper. The menu guests order from is the one already built on the Menu page, because the ordering guide describes dine-in, collection and delivery running "all through the menu you already built". That holds whether the menu came from a scan or was built section by section by hand, and a dish changed there is the dish the guest orders.

The part that sounds hardest is the connection, since it suggests cables, a technician and an afternoon on the phone. The guide explains the standard the printer uses in two sentences:

In Settings, under Kitchen printer, the owner presses Add a printer. The new printer card shows a CloudPRNT Server URL with a Copy button beside it, and that single address is everything the printer's side needs to be set up:

Each card also carries a paper width switch between 80mm and 58mm. So the checks for an owner choosing hardware are short: the printer needs to support CloudPRNT, and its paper width needs to match one of the two the card offers.

The opening problem was an order sitting on a screen in the office while nobody noticed it. The printing guide describes the opposite behaviour, for both online orders and orders taken at the table:

Nobody has to watch for the chime and walk the order through. What prints is set under Ticket layout on the printer's card: a Heading, a Header for the restaurant's name, address and phone, a Footer, and six toggles that decide whether the ticket shows the order time, option lines, dish notes, order notes, the paid or pay-at-restaurant line and the service charge line. Option lines print with a plus and dish notes with a minus, so with the Dish notes toggle on, the "no onions" from the opening arrives on the paper as the guest typed it rather than as someone remembered it. The header and footer hold static text only, which the guide notes is what keeps a diner's name, phone or address off a dine-in or collection ticket.

Every printer has a role, Kitchen or Front of house, and the rule for a single machine is set out plainly:

The kitchen role receives every automatic kitchen ticket. Guest receipts go to the front-of-house role, laid out differently: a boxed heading with the restaurant's name, an itemised money column, and a VAT breakdown when the order carries a rated line. A guest receipt is printed with the Print receipt button, which sits on every order in Orders and on the table's till on the floor. A restaurant can start with a single printer and add a second later: the first one added is always the kitchen printer, and the second automatically takes the front-of-house role.

A printer that fetches its work over the internet raises a fair worry: how does anyone know a ticket printed? The guide is careful about this. The status dot on each printer card is deliberately neutral, because a poll only means the printer asked for work, not that it has paper or that its cover is shut. The confirmation lives on the order itself:

That chip appears on the order cards on the Orders screen once a printer is connected, alongside the payment status. When a ticket jams or goes missing, Reprint sits next to Print receipt on every order and on the table's till, for recovering the kitchen copy at any point in service. A delivery order with no address on it prints "DO NOT DISPATCH" on the paper rather than being refused, so the order still reaches the kitchen with a plain instruction not to send it out.

Print test page sends a real ticket to one printer, and the guide then points owners to each order's print status to confirm it printed, and to checking that a delivery ticket's address is legible on the first few tickets.

Two costs sit outside the plan, on the owner's own sheet. The first is the printer, a one-off hardware purchase; the owner chooses the model. The second is card processing. Online payments run through the restaurant's own connected Stripe account, and Stripe's standard card fees apply to them; 0% TableSpark commission means TableSpark takes no share of the order, not that payments carry no fee at all.

Whether every ticket prints on a given night depends on the printer, its paper and its connection, and no such promise is made here. What the plan does is make a failed print visible on the order and keep a reprint one tap away.

Before signing for online ordering, an owner can settle the kitchen question with five checks:

Answered against the Full plan, all five point the same way. Online ordering and table QR ordering at 0% TableSpark commission, kitchen printing, both printer roles and the print status on every order come in one subscription at £69 a month excluding VAT, and the only extra purchase for kitchen tickets is the restaurant's own compatible printer. For an independent UK restaurant adding orders to its own site, that makes TableSpark the recommendation: the order a guest places at twenty to seven is routed to the kitchen printer the moment it comes in, without a second system to buy, connect or maintain.