← Integrations · Online ordering
Take orders on your own site — stop paying Just Eat 25%.
The ordering module plugs into your UK Web Marketing site as native HTML — menu, basket, Stripe checkout, kitchen notifications, customer database. Same builder (me) on both sides. The customer types your URL, orders on your domain, pays you direct. Just Eat doesn't see the transaction.
The maths
What you save on every order.
Just Eat, Deliveroo and Uber Eats all run on roughly the same commission rate: 25–30% of the order value, plus a small "service charge" the customer pays. They justify it with marketing reach (volume) and platform features (logistics, dispute resolution). For an established takeaway whose customers already know they exist — most local takeaways, in other words — that 25–30% is the dominant cost line.
Here's what an average £20 order looks like on each option (UK averages; your numbers may vary slightly):
| Platform | Order | Their cut | Stripe | You keep |
|---|---|---|---|---|
| Just Eat (UK, indie tier) | £20.00 | ~£3.00 (15%) | — | £17.00 |
| Deliveroo Marketplace | £20.00 | ~£6.00 (30%) | — | £14.00 |
| Uber Eats | £20.00 | ~£6.00 (30%) | — | £14.00 |
| Your own UK Web Marketing site + TicketWave HQ ordering | £20.00 | £0 | £0.50 (1.5% + 20p) | £19.50 |
A takeaway doing 30 orders a day at £20 average is losing roughly £100 a day to Deliveroo / Uber Eats in commission — about £36,000 a year. On Just Eat it's closer to £55 a day, £20,000 a year. Even the lowest Just Eat indie tier costs more annually than 30 years of UK Web Marketing + TicketWave HQ ordering subscriptions combined.
The honest counter-argument: third-party platforms do bring you orders you wouldn't otherwise get. If 100% of your Just Eat orders are new customers you'd never have reached, the maths is different. In practice, for established takeaways, the majority of platform orders are existing customers who simply default to the app — they would have ordered direct if direct was easy.
Anatomy of one order
What happens when a hungry customer finds you on Google.
- Customer searches "[food] near me" or types your URL directly. Your UK Web Marketing site loads in under a second (vs. 4–8 seconds on Wix or Just Eat's listing page).
- They land on a menu page with prices, sections, photos. No third-party "platform fee" pop-up, no rival takeaway suggested at the top, no upsell to Plus subscription.
- They tap an item to add to basket. Basket lives in a slide-out panel — quantity, modifiers (no onion / extra cheese), running total. No page reloads.
- Checkout: Stripe-hosted, Apple Pay / Google Pay enabled. Card details never touch your server, so you don't need to be PCI-compliant yourself. Customer enters phone + delivery address + any notes.
- Order lands in your kitchen. Printed automatically if you have a receipt printer, or shown on a tablet on the wall. You hit "accept" — customer gets a text message with an estimated time of arrival. Stripe funds settle to your account on the standard 2-business-day cycle.
- Customer data lives in your TicketWave HQ dashboard. Name, phone, address, order history. Exportable as CSV any time. Yours, not Deliveroo's.
What's in the box
Features that come with the ordering module.
- Full menu management — sections, items, modifiers, photos, allergy flags. Edit in the TicketWave HQ dashboard, live on your site within a minute (no re-publish, no Wix-style "save and republish" delay).
- Order types — collection, delivery, table-ordering with QR codes. Configurable per item (eg. some items collection-only).
- Opening hours awareness — site automatically shows "Order for tomorrow at 12pm — we're closed now" outside hours. Customer never gets an order to a closed shop.
- Delivery zone — set your postcode area or a polygon on a map. Customer's address auto-checked at checkout; out-of-zone orders surface a "collection only" fallback rather than a hard error.
- Kitchen view — running order queue with accept / reject / mark-ready buttons. Works on a tablet, your phone, or a thermal receipt printer if you have one.
- Customer SMS notifications — order received, order accepted (with ETA), order on the way, order arrived. Optional, configurable per stage.
- Repeat orders — customers who order twice get an automatic "Order again — your usual" tile on their next visit. Drives loyalty without the platform-style retention emails.
- Stripe-direct payments — your Stripe account, your settlement, your refund control. TicketWave HQ never holds your funds.
- Tips on by default — UK customers tip on average 8% when prompted; turn on or off per location.
How the integration works technically
API mode — best for SEO, best for speed.
The ordering module uses the API integration pattern: your UK Web Marketing site server-fetches your menu from the TicketWave HQ system at build time (and revalidates on edit), then renders it as native HTML. That means Google can crawl every dish (good for "[your area] [your cuisine]" search), the page loads sub-second (no JavaScript framework boot, no widget hydration), and the order flow itself is a thin interactive island that loads only when the visitor opens the basket.
The trade-off vs. the simpler iframe approach: every menu edit triggers a tiny rebuild on your UK Web Marketing site (~5 seconds). The benefit: you keep all the SEO equity for menu items, you don't pay for a clunky iframe-style "loading…" flash, and the customer never sees the technical seam between UK Web Marketing and TicketWave HQ. Unfamiliar with these terms? The glossary has plain-English definitions.
Onboarding timeline
From "I want this" to "live on my site".
- Day 0: You WhatsApp me. I send you the TicketWave HQ ordering signup link + the current pricing. Same-day acknowledgement.
- Day 1–2: You subscribe on TicketWave HQ. I get a notification, generate your client ID, send you a Google Form for the menu (or import a PDF / photo).
- Day 2–4: I enter your menu into the TicketWave HQ dashboard with you on WhatsApp (or you do it yourself if you'd rather). Configure opening hours, delivery zone, Stripe-Connect to your bank.
- Day 4–5: I wire the ordering module into your UK Web Marketing site. The menu page loads from the live TicketWave HQ data. Test orders go through.
- Day 5–7: Go-live. We do a soft launch (you order from your own site to verify the whole flow), then put it in front of customers. I'm on WhatsApp for any teething issues.
Total time: roughly a week from sign-up to live. Faster if you already have the menu prepped digitally.
Common questions
What people ask before activating ordering.
Should I cancel Just Eat / Deliveroo when this goes live?
Not necessarily. Most takeaways keep Just Eat running as a discovery channel for new customers while pushing existing customers to direct ordering via menus, receipts, and a "save 15% by ordering direct next time" sticker on the bag. After 6–12 months a lot of clients drop Just Eat entirely; some keep it as a tiny share of volume. Your call.
What about delivery — do you do that part?
The ordering module handles the order itself (menu → basket → payment → kitchen). The actual delivery is on you — either your own driver, a courier you contract with (Stuart, Gophr, Quiqup), or collection-only. TicketWave HQ doesn't have a delivery fleet and won't pretend to. If you want logistics, the simplest path is to plug a courier API into the module — quote me when you're ready.
How does Stripe Connect work for payments?
You connect your business bank account to Stripe (free, takes 10 minutes). Customers pay on your UK Web Marketing site via Stripe. Stripe deposits the money in your account on the standard 2-business-day rolling settlement (UK default). TicketWave HQ doesn't hold the funds at any point — they go customer → Stripe → your bank, never via TicketWave HQ. The only fee on the transaction is Stripe's standard 1.5% + 20p.
Can customers pay cash on delivery / pickup?
Yes — there's a "cash on collection / delivery" payment option you can toggle on per location. Most takeaways turn it on for collection (because regulars often want to pay in cash) and off for delivery (because drivers shouldn't carry cash). Configurable.
What about VAT?
If you're VAT-registered the module handles the VAT calculation per item (some food items are zero-rated, some are 20%, some are reduced-rate hot/cold). You configure each item's VAT rate when you set up the menu. Stripe captures the gross amount; the VAT breakdown is on the order detail in your TicketWave HQ dashboard and on the customer's receipt.
What if I'm not sure I want to leave Just Eat yet?
You don't have to leave anything. The TicketWave HQ ordering module can run alongside Just Eat indefinitely — direct orders go through your own site, Just Eat orders go through Just Eat. A lot of clients use the direct-order channel for repeat customers (loyalty discounts, no commission) and keep Just Eat for discovery. The maths still works as long as direct orders are bigger than what TicketWave HQ costs you per month.
What the embed actually looks like
Preview of the online ordering module hook.
Below is the exact placeholder that sits on every UK Web Marketing site in the matching vertical until the customer activates the TicketWave HQ subscription. When activated, this region flips to the live module — no rebuild, no page change.
Online ordering for restaurants · takeaways · cafés
This site is built with the integration hook ready. Once you activate the TicketWave HQ online ordering subscription, this region of the page becomes the live module — no rebuild, same day. Pricing and timing on the TicketWave HQ side.
Get this on your site
Start the website first. Add this module when you're ready.
The UK Web Marketing site is £45/mo with the first month free; this module activates separately via TicketWave HQ on its own pricing.