Integrations
Your site, plus the tools that run your business.
Your build covers the website. The tools that run the day-to-day, ordering for a takeaway, bookings for a salon or clinic, stock for a car dealer, ticketing for an event, add on for a fair fee and run on your own site, under your own brand. They are built by the same person who builds your site and run on a TicketWave HQ module, so it is all one bill. The big difference: the customer is yours, not a marketplace's.
The model
One point of contact, one bill, zero rebuild.
- You start with a free audit at /audit. It scores your current site and shows what is worth building. From there we quote your build and monthly retainer, and we set up your website with the tools' hook ready in advance, even if you do not switch them on day one. No lock-in, cancel any time.
- The website is yours, on your domain, from day one. It works as your shop window, lead-magnet and Google surface even with no booking module switched on. Most people run this way for a few weeks before deciding which tools they actually want.
- When you are ready for bookings, ordering, stock or ticketing, the module adds on for a fair fee and wires straight into your site, on your domain, under your brand, with payments settling straight to your own account. We switch it on for you; nothing to rebuild.
- One clean monthly bill. Your build covers the website and the modules add on for a fair fee, all on one bill. The booking and ordering module is run by TicketWave HQ, the same company that builds your site, and takes a fair fee per transaction, on that same one bill. One accountable point of contact behind all of it.
The modules
Four tools that run on your own site.
Each one replaces a marketplace that takes 20-30% of every transaction AND owns your customer. Run it on your own site instead and the customer stays yours. Click through for what each one does, what it replaces, and how it works.
- Module 01
Online ordering
Restaurants · takeaways · cafés
Take orders on your own site, under your own brand, so the customer is yours, not Just Eat's. A fair fee, from the same people who built your site, on one bill.
Replaces: Just Eat / Deliveroo / Uber Eats (20–30% AND they own your customer)
See how it plugs in → - Module 02
Appointment bookings
Salons · clinics · service businesses
Bookings on your own site, under your own brand, your customer list stays yours, not the platform's. A fair fee, from the same people who built your site, on one bill.
Replaces: Fresha / Booksy (20–30% AND they own your customer, then market your rivals to them)
See how it plugs in → - Module 03
Vehicle / inventory stock
Car dealers · garages · traders
Your stock, displayed on your own site, not someone else's.
Replaces: AutoTrader-only visibility (£300–1,500/month for the dealer packages)
See how it plugs in → - Module 04
Event ticketing
Events · clubs · classes · workshops
Sell tickets on your own site, under your own brand, your attendee list stays yours. A fair fee, from the same people who built your site, on one bill.
Replaces: Eventbrite / DICE (commission AND they own your attendee list)
See how it plugs in →
Anatomy of a typical transaction
What happens when a customer orders / books / buys.
The honest summary of every module's transaction: customer interacts with your UK Web Marketing site → Stripe takes payment → money lands in your account → email + (optional) SMS confirmation to both sides → fulfilment. No marketplace sits in the middle, and no marketplace owns the customer, they are yours. The TicketWave HQ module takes a fair fee per transaction (the same company that builds your site, on one bill), and Stripe takes its standard card fee, the same as any modern checkout.
- 1 Customer lands on your own site, your domain, your branding, your URL in their address bar. The booking or ordering looks like part of your site, because it is.
- 2 Customer interacts with the module, adds items to a basket, picks a booking slot, configures a finance enquiry, buys a ticket.
- 3 Stripe Checkout (or embedded card flow) takes the card. Your business is the merchant of record, funds land in your Stripe account, not the platform's.
- 4 Confirmation email to the customer + notification to you (email, SMS or both, depending on the module). The customer's contact details land in your CRM (also yours, exportable any time).
- 5 You fulfil it, cook the order, host the appointment, sell the car, scan the ticket at the door. The platform's job is done.
Data ownership, non-negotiable
Your customer list is yours. Your reviews are yours. Your transactions are yours.
- Customers belong to you, not a marketplace. Every name, email, phone number and order history lives in your own account, fully exportable as CSV any time. If you ever leave, you take them with you.
- Reviews live on your domain. Not on a marketplace that can de-platform you or market your rivals to your customers. The SEO benefit goes to your site, not Just Eat's.
- Stripe funds settle to your account. No marketplace ever holds your money. No 7-day "platform settlement", no rolling reserve, no "we are holding £X for risk".
- A fair fee, not a marketplace cut. Fresha, Booksy and Just Eat take 20-30% of every transaction AND own the customer. Here the customer is yours, and the TicketWave HQ module takes a fair fee per transaction, from the same person who builds your site, on one bill.
- You are not locked in. Cancel any time and the module goes offline; your customer list comes with you as an export. Your website keeps running, just without the booking button.
Who builds and runs the tools
Same person, same company, one bill.
Your website and the tools that run your business are built by the same person, me. There is no agency to chase, no separate booking app to log into, no third party in the middle of your customer relationship.
The bookings, ordering, stock and ticketing run on a TicketWave HQ module, that is the same company that operates UK Web Marketing, so it all comes to you on one monthly bill. The module takes a fair fee per transaction, and that is the trade you are making: a fair fee for tools that keep the customer yours, instead of 20-30% to Fresha, Booksy or Just Eat who take the cut and own the customer.
The way in is a free audit at /audit: it scores your current site and shows what is worth building, then we quote your build and retainer. If you want the tools now, say so and we will scope them into the quote. If you want the website first and the tools later, that is the default path, we set up the website with the hook ready, and you switch the tools on when you want them, anything from week 1 to year 3.
Questions people actually ask
FAQ.
Do I have to take a bookings or ordering module to get a UK Web Marketing site?
No. Your build covers the website, and it stands on its own as a complete done-for-you site. Many people run for months with just the site and add bookings or ordering later (or never). The integration hook is built in either way, so there is nothing to rebuild if you decide to switch one on. Start with a free audit at /audit to see what you actually need.
How much does the bookings or ordering module cost?
Your build covers the website, and the modules add on for a fair fee, all on one bill. Bookings and ordering wire into your own site and are run by TicketWave HQ (the same company that builds your site), which takes a fair fee per transaction. There are no separate apps and no separate logins, just one monthly bill from one supplier. The exact figure is quoted to your business, there are no off-the-shelf prices. Run a free audit at /audit and we will scope it.
Can I use a third-party platform (Fresha, Booksy, Just Eat) instead?
Yes, and a lot of people do, especially when they are starting out. Your UK Web Marketing site can link to any external booking or ordering platform you already use; we will wire the buttons. But those platforms take 20-30% of every transaction AND own the customer, your customer list is theirs, and they will market your rivals to the people you brought them. Running bookings on your own site keeps the customer yours.
What if I want to leave?
You can cancel any time. On cancel: the module goes offline; you keep your customer list (export it before you cancel, or we will do it for you); your website keeps running with the booking button hidden. The same rules apply as in the refund policy.
How does the integration actually work technically?
Three patterns depending on the module: API (your UK Web Marketing site server-fetches data from TicketWave HQ and renders it as native HTML, best for SEO, used for ordering and stock), web component (a small bit of JavaScript loads inside the page, used for bookings, where the calendar interface is interactive), iframe (sandboxed embed of the TicketWave HQ module, used for ticketing where the interface iterates fastest). In all three, the customer never leaves your domain. If any of those terms are new, the glossary has plain-English definitions.
Is this stable? Some of those modules sound new.
The ticketing module is the longest-lived, TicketWave the platform has been running Dubai Events 2026 and live UK events for some time. Ordering, bookings and stock are newer and rolling out to existing clients in stages. If you are an early adopter you will get the founder-pricing on TicketWave HQ's side; I will be straight about what is production-ready vs. what is in beta.
Get started
Start with the website. Add the tools when you are ready.
Begin with a free audit; we quote your build and the modules stay dormant until you say go.