← Integrations · Online ordering
Take orders on your own site, stop paying Just Eat 25%.
The ordering module plugs into your own site as native HTML, menu, basket, Stripe checkout, kitchen notifications, customer database. Built by the same person who builds your site. The customer types your URL, orders on your domain, and the customer is yours, not Just Eat's.
The maths
Why your own site beats the marketplace on every order.
Just Eat, Deliveroo and Uber Eats all run on roughly the same model: 20-30% of the order value, plus a small "service charge" the customer pays, and they own the customer relationship, so the people you feed are theirs, not yours. They justify the cut with marketing reach. For an established takeaway whose customers already know them, most local takeaways, that 20-30% is the dominant cost line, and the lost customer ownership costs you for years.
Here is what an average £20 order looks like on each option (UK averages; your numbers may vary slightly). On your own site there is a fair module fee instead of a marketplace cut, far smaller, and the customer stays yours:
| Option | Order | Marketplace cut | Who owns the customer |
|---|---|---|---|
| Just Eat (UK, indie tier) | £20.00 | ~£3.00 (15%) | Just Eat |
| Deliveroo Marketplace | £20.00 | ~£6.00 (30%) | Deliveroo |
| Uber Eats | £20.00 | ~£6.00 (30%) | Uber Eats |
| Your own site + ordering module | £20.00 | Fair module fee, far less than a marketplace cut | You |
A takeaway doing 30 orders a day at £20 average is handing roughly £100 a day to Deliveroo / Uber Eats, about £36,000 a year. On Just Eat it is closer to £55 a day, £20,000 a year. A fair module fee on your own orders is a fraction of that, and, unlike the marketplace, it leaves the customer with you.
The honest counter-argument: the marketplaces do bring you orders you would not otherwise get. If 100% of your Just Eat orders are brand-new customers you would never have reached, the maths is closer. In practice, for established takeaways, most marketplace orders are existing customers who simply default to the app, they would have ordered direct if direct was easy, and ordering direct keeps them yours. When you are ready, run a free audit at /audit and we will show you the numbers for your own shop.
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 own site loads in under a second (vs. 4 to 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 do not 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 is 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 are 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 do not 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 email us, or run a free audit at /audit to get started. Same-day acknowledgement.
- Day 1-2: We switch on your ordering module and send you a Google Form for the menu (or import a PDF / photo). It is all on your one bill, nothing separate to sign up for.
- Day 2-4: We enter your menu into the TicketWave HQ dashboard with you over email (or you do it yourself if you would rather). Configure opening hours, delivery zone, Stripe-Connect to your bank.
- Day 4-5: We 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. We are on email 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 to 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 does not have a delivery fleet and will not pretend to. If you want logistics, the simplest path is to plug a courier API into the module, ask us for a quote when you are ready.
How does Stripe Connect work for payments?
You connect your business bank account to Stripe (free, takes 10 minutes). Customers pay on your own site via Stripe. Stripe deposits the money in your account on the standard 2-business-day rolling settlement (UK default). TicketWave HQ never holds your funds, they go customer → Stripe → your bank. Stripe takes its standard card fee, and the ordering module takes a fair fee per order, far less than a marketplace's 20-30% cut, and the customer stays yours.
Can customers pay cash on delivery / pickup?
Yes, there is 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 should not carry cash). Configurable.
What about VAT?
If you are 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 am not sure I want to leave Just Eat yet?
You do not have to leave anything. The 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 channel for repeat customers (loyalty discounts, and you own the customer) and keep Just Eat for discovery. The maths works in your favour because a fair module fee is far less than Just Eat's 20-30% cut, and the customer stays yours.
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 are ready.
It starts with a free audit, then your website is built and run for you, cancel any time; bookings, ordering and payments run on a TicketWave HQ module, the same company that builds your site, for a fair fee, on the same one bill.