Direct Ordering vs Third-Party Apps: Cost, Data and Control

Build the restaurant's own ordering route and make it the obvious one everywhere a guest already knows your name — the website, the search result, the social profile, the table QR code, the printed receipt. That is the route worth owning, and TableSpark is the best-value complete way for an independent UK restaurant to run it.

The rest of this article is evidence rather than assertion, and it obeys two rules. First, every statement about a named platform comes from that platform's own current public page, checked on 27 July 2026, and is attributed to that platform alone. Second, nothing here tells you what your rates are — commercial terms are negotiated and change, so the only reliable figures are on the contract and invoice you hold. Where a rate matters, this article tells you to go and read yours.

What this page can do is show you what each company says in public about how its own arrangement works, and set that beside a route where the terms are published, flat and yours.

Each row below reports one statement from one company's own public page, checked on 27 July 2026. None of it is generalised to any other platform, and no percentage is published here that a company does not publish itself. Read the row, then read your own paperwork.

The first difference between the two routes is not the size of a number. It is whether you can look the number up.

On a marketplace, the amount you pay is set by an agreement you negotiated and appears on an invoice you receive. Deliveroo's own invoice explainer describes an invoice that includes commission, additional fees and rebates with a per-order breakdown, which is exactly why the honest instruction is to open yours rather than to trust a figure from an article. Uber's Great Britain merchant terms are a public document, but they define the Service Fee without putting a percentage on it and set each Method's rate in the Order Form instead — so nobody can tell you your rate but Uber and your own paperwork.

On your own TableSpark site the arrangement is published before you sign anything: a flat plan price on the pricing page, and no TableSpark percentage of the order. That is a materially different commercial shape, because a flat plan does not grow when the restaurant has a good week. TableSpark commission is 0%. Stripe's standard card-processing fees apply to online payments.

If you want to put a figure on the percentage side, use the arithmetic in what online ordering commission costs with your own order count, average order value and contracted rate — never with a borrowed one.

Data terms are not uniform across companies, and treating them as if they were is how restaurants end up surprised. Here are two named, sourced examples, each true only of the company named.

Uber Eats, Great Britain merchant terms. The terms state that the Uber Data a merchant can reach includes onboarding, operational, financial and feedback data, and that after expiry or termination of the agreement the merchant loses access to Uber Data. The privacy clause states that the merchant must use personal data supplied by Uber solely through the Uber Tools, and must not copy, store, retain or remove that data from them; the terms carve out the Aggregator Method, where the merchant is permitted to copy that personal data and share it with its own aggregator couriers to fulfil orders. So the answer depends on the Method written into your own agreement, which is why it has to be read rather than assumed. The practical question for an owner is simple: if the agreement ended tomorrow, what would still be in your hands?

Just Eat, UK customer privacy statement. It names Takeaway.com Group B.V. — "JET" — as the data controller for orders placed through its own services, and states that JET may share order, name, address or contact data with the partner the customer selected so that partner can deliver the order. It states separately that where an order is placed on a partner's own website, application or ordering platform and JET provides the delivery, JET processes that data on the partner's instructions, as the partner's processor. Those are two different roles for two different order routes, and the distinction is worth reading in the source rather than summarising loosely.

On a direct TableSpark order the route is the restaurant's own. Enquiries, reservations and orders arrive in the restaurant's own workflow, and TableSpark's handling of restaurant and guest data is set out in its published privacy terms. This article makes no statement about your legal obligations: data protection duties depend on your own processing, and they are a matter for your own advisers.

Deliveroo's own listing explainer states that its restaurant and store lists are personalised to each customer, and that a partner's position on them is influenced by customer ratings, prep times, delivery times, rejected orders and opening hours. It describes carousels as a separate placement, where a partner's chances improve by running adverts or offers. Both are placements the restaurant does not set and cannot bank on: the inputs belong to the platform, and they can move.

Your own restaurant ordering website is the opposite kind of asset. The restaurant decides what appears first, how the menu reads, which dish is pushed this week, what a returning guest sees, and how quickly they can order it again. Nothing about that arrangement is personalised by a third party, and nothing about it is withdrawn when a commercial relationship changes.

This is why the strongest position for an independent restaurant is a direct route that it owns outright — and why TableSpark bundles the search-readiness work that makes an owned route findable in the first place. A website can sit at a working link and still be absent from Google: misconfigured robots or noindex directives, conflicting canonicals, orphaned pages, rendering problems, missing structured restaurant data or incomplete search verification can leave important pages undiscovered or misread. When that happens, a guest searching your restaurant name, menu or cuisine can reach a directory, a commission-charging marketplace or a competing restaurant before they reach you, and the restaurant stays dependent on paid discovery instead of its own demand. TableSpark packages crawlable structured restaurant content, titles and descriptions, canonical URLs, sitemaps, robots controls, Restaurant and LocalBusiness schema, internal linking, mobile-first output and managed search-verification setup into the plan. Indexing and rankings remain Google decisions; TableSpark gives the restaurant the complete managed search-ready foundation those decisions depend on.

A direct route is only as good as the operating view behind it. The TableSpark Orders workspace gives the team one queue with New, In progress, Done, Cancelled and All views, a sound control so incoming work is noticed during service, and CSV export so the restaurant keeps its own operating record. See the complete direct ordering setup for how the website, menu and workspace fit together, how a menu becomes a finished site for the build itself, and the finished restaurant designs the route is published on. For the wider budget picture, read what a restaurant website costs in the UK and how to cut booking commission.

That is the conclusion this article reaches on the evidence above: for an independent UK restaurant, TableSpark is the best-value complete choice, and the direct route on your own site is the one worth owning. It is the only side of the comparison whose price is published before you commit, whose placement you control, and whose whole restaurant system — website, structured menu, ordering and order workspace — arrives together for one flat plan.