The menu price is
what your customer pays.
TicketWave Food is the curated rail for independent restaurants in cities the 2026{city}.com network already covers. Zero markup, transparent 3% service fee, restaurant keeps every euro of the subtotal. Editorial selection is the moat — we don't take everyone who applies.
Stripe Connect direct charges — money lands in your account, never ours.
The conversation in your hero
Every Deliveroo competitor inflates your prices 20–30% silently. We don't touch them. That's the line on every /eat/your-slug page — and the reason customers come direct.
0% markup on menu prices
What you list is what your customer pays. Deliveroo and UberEats silently inflate prices 20–30% to absorb their cut; we don't touch the menu.
3% transparent service fee
Shown to the customer as a separate line at checkout, never hidden in inflated prices. The conversation in the hero on every /eat/[your-slug] page.
Restaurant keeps 97%
Subtotal + delivery fee + tip flow direct via Stripe Connect to your Stripe account. We never hold your funds.
You pay your own drivers
Drivers are your staff, not platform middlemen. Flat-fee or %-of-subtotal compensation configured per driver, snapshotted at delivery.
Demand from a curated network
Editorially-chosen restaurants appear on 2026{city}.com — our locals'-concierge city guides. Real intent-loaded traffic, not algorithm soup.
Your brand, end to end
Your name on the menu page, the confirmation email, the live tracking view. We're the rails, not the brand.
How it stacks up
Where the economics differ from Deliveroo, UberEats, and Just Eat. Margins below are typical for independent restaurants on each platform; check your own contract for the exact split.
| TicketWave | Deliveroo | UberEats | Just Eat | |
|---|---|---|---|---|
| Markup on menu prices | 0% | 20–30% | 20–30% | 13–25% |
| Service fee (transparent) | 3% | Hidden in markup | Hidden in markup | Hidden in markup |
| Restaurant keeps subtotal | 100% | 67–80% | 65–75% | 75–87% |
| Funds settle to | Your Stripe | Platform holds | Platform holds | Platform holds |
| Customer data ownership | Yours | Theirs | Theirs | Theirs |
| Driver employment | Your staff | Theirs | Theirs | Theirs |
| Editorial demand | 2026{city}.com network | Algorithm | Algorithm | Algorithm |
Industry-standard cuts published by each platform's merchant documentation. Effective rate varies by city + contract.
We choose, you don't apply
Selectivity is the product. The 2026{city}.com network only recommends restaurants we'd send our own friends to. That gatekeeping is what makes the rec lists worth reading — and the reason customers click through.
Apply
Fill the form at /eat/apply — restaurant name, city, your pitch, why TicketWave over Deliveroo. A real human reads every application.
We decide
Editorial curators review against the public rubric: provenance, kitchen care, locals' word-of-mouth, room for the network. Two weeks to respond.
Onboard
Accepted restaurants get a guided five-step setup — menu, photos, delivery zones, drivers. Live on /eat/your-slug in under an hour.
Earn demand
Your curator writes a personal intro for the 2026{city}.com /eat page. Customers arrive intent-loaded — they're not browsing categories.
Anyone can technically set up TicketWave Food. Only platform-curated tenants appear in the microsite recommendations. That's the moat.
Everything a takeaway operation needs
Eleven shipped phases of operational depth. No theoretical roadmap — every feature below runs in production.
Menu admin + photo-first
Categories, items, modifiers, combos, dietary + allergen tags. HTTPS image required on every item. CSV bulk import (Toast / Square / Deliveroo formats auto-detected).
Kitchen display + SSE
Wall-mounted KDS with live status flips, station-mode filter for individual cooks, prep-time learner that improves ETAs with every order.
Delivery zones + capacity
Postcode prefix + radius zones with per-zone fees + min order. Capacity throttling caps ASAP orders per 30-minute window when the kitchen's at full tilt.
Drivers + mobile-web app
Drivers get a phone-friendly /driver?token=… page with tap-to-call, address deep-links into maps, and Picked-up / Delivered buttons. Commission snapshotted at delivery.
Group ordering
Shared URL where everyone in the office adds their own line under their own name. One person pays at the end; kitchen sees every line tagged with its contributor.
Live tracking + email updates
Customers get a real-time SSE tracking page from the moment the kitchen confirms the order. Status emails at every meaningful transition.
Magic-link customer accounts
Customers see their order history + saved addresses + one-tap reorder. No password to remember; HMAC-signed link expires in 24h.
Ingredient BOM
Track stock per ingredient, define recipes per item, auto-decrement on every paid order. Low-stock alerts when a key ingredient drops below threshold.
Embed your menu anywhere
One iframe tag drops your live menu into your existing website. Order CTAs open the full TicketWave checkout in the parent frame.
Every euro lands in your Stripe account.
Customer pays subtotal + delivery fee + tip + a 3% TicketWave service fee. Stripe Connect routes everything except the 3% service fee directly to your Stripe account — we never hold your money. Withdrawals on Stripe's standard schedule.
No restaurant subscription required. The 3% is the only fee. You pay your own drivers (flat + % per delivery, configured per-driver; commission snapshotted at delivery so payroll is clean).
Apply to be featured.
Tell us about the restaurant. A real human reads every application; we aim to be in touch within two weeks.
Already onboarded? Skip to /dashboard/food-setup for the guided wizard.