How does a booking platform fit into a new business website?

Many small businesses already take bookings or orders through a specialist platform before they think about a new website. Appointment tools, table-booking systems, delivery marketplaces and calendar schedulers all do real jobs well: they hold availability, take payments or deposits, send reminders and keep a record.

A new website should not try to replace that work. It should make it easier for the right customer to reach the platform, with enough context that they arrive ready to book. This guide explains the practical choices and what to check before anything is connected.

What the platform does and what the website does

The two have different jobs.

The booking or ordering platform is usually the source of truth for live information: which slots are free, which services can be booked, what a deposit is and what the cancellation terms are. It also holds the customer record.

The website explains. It describes the services in plain language, shows genuine photography, sets out prices or ranges where the business publishes them, answers the questions people ask before booking and gives the business a stable address that it owns.

Problems appear when the website starts duplicating the platform’s live data. A price typed into two places will eventually disagree. An availability note on the website that is out of date sends customers to the wrong decision. The simplest way to avoid this is to decide, for each fact, which place is the master copy and to link to it rather than repeat it.

Three ways to connect: link, button or embed

There are three common routes, each with different trade-offs.

A plain link or button

A clear “Book now” or “Order online” button that opens the platform is the most robust option. It works on any device, does not depend on a third-party script loading, and keeps the platform’s own checkout, accessibility behaviour and security in the platform’s hands.

The cost is that the customer leaves the website. That is usually acceptable when the website has already done its explaining. Put the button where the decision is made: on the service page, in a prominent place on mobile and at the end of any page that answers a booking question.

A booking widget or embedded frame

Some platforms provide a widget or frame that shows availability inside a website page. This can feel smoother, because the customer does not appear to leave. It also adds dependencies.

An embed relies on the provider’s script, which can load slowly, fail to load or change its appearance without warning. It may behave differently with keyboard navigation and screen readers than the rest of the site, and it can be awkward on a small screen. If the platform supports an embed, test it on a phone, with the keyboard only and with scripts blocked before deciding to rely on it.

Whichever route is used, there should be an ordinary fallback link beside or below an embed, so that a failed frame never leaves a customer looking at a blank space.

A hand-off page that prepares the customer

A third option sits between the two: a short page on the website that explains what is being booked, how long it takes, what to prepare and what happens next, followed by a link to the live platform. It suits services where a customer benefits from understanding the process first.

Page & Place’s commissioned Emily’s Pet Services website takes this approach. It brings the price, appointment length and booking guidance together on the website before handing the customer to the client’s own booking account, so availability is not duplicated on the website.

Keep one source of truth

Before any connection is built, list the facts that appear on both the platform and the website. For most businesses that list includes:

• service names and descriptions;
• prices and deposits;
• opening hours and days off;
• cancellation and late-arrival terms;
• the address or service area, where it is published;
• contact details.

For each one, decide where the master copy lives. Live facts that change often, such as availability and slot lengths, belong on the platform. Descriptive facts that need explaining, such as what a service involves, belong on the website. Where a fact must appear in both places, agree who is responsible for updating each one when it changes.

When something changes, update the platform first, then the website, and check that the two still say the same thing.

What to check before connecting a platform

A short checklist saves awkward surprises after launch.

1. Who owns the account. The business should be the account owner, with any supplier given delegated access that can be removed later. A website should never depend on an account that belongs to someone else.
2. What the platform costs. Subscriptions, transaction fees and any charge for features such as custom branding are set by the provider and sit outside the website build. Page & Place identifies known third-party costs before setup and shows them separately unless a written scope says otherwise.
3. What the customer sees on a phone. Open the booking journey from the website on a mobile device and complete it from start to finish.
4. How it behaves without a mouse. Try the journey with the keyboard alone. Check that focus is visible and that nothing traps the cursor.
5. What happens when it fails. Is there a fallback link, a phone number or an enquiry form for someone who cannot use the platform?
6. Where confirmations go. Check which email address receives booking notifications and whether the business actually reads it.
7. What data is collected. A booking platform handles customer details under its own privacy terms. The website’s privacy information should not claim otherwise, and the business should know which party is responsible for what.

Measuring what happens next

It is useful to know whether people click through to book, and from which page. Where measurement is configured, clicks on booking buttons can be tracked as events so the business can see which pages lead to booking attempts. What happens inside the platform is usually reported by the platform itself.

Page & Place’s integration work includes analytics event planning where measurement is configured, and Cloudflare Web Analytics is the privacy-conscious default for basic measurement where it has been agreed. Treat early numbers cautiously: a handful of clicks says very little about what works.

When a platform is the wrong tool

An established booking platform is usually the sensible choice. Building a custom booking engine is a much larger project that brings its own security, testing and maintenance responsibilities. It is only worth considering when a business has a workflow that no established platform can serve.

How this fits a Page & Place website

Page & Place’s standard website package covers existing booking, ordering or social links. Established services such as OpenTable, Fresha, Booksy, Calendly, Deliveroo, Just Eat, WhatsApp and Google Maps can normally be linked or embedded where the platform supports it, and the business keeps control of the platform itself.

The integration work covers an audit of the existing customer journey, clear calls to book, order, call, message or enquire, links or supported embeds, accessible fallback routes when an embed is unavailable, and documentation of the third-party accounts and ongoing fees involved. Third-party fees remain separate from the website price.

Setting up a new booking platform, with deposits, cancellation policies and staff calendars, is a larger piece of work than linking to one that already exists, and it is scoped separately. See booking and enquiry integrations for what is included, or look at the pricing to see how scope and cost are set out.

If a business already uses a booking or ordering tool, the useful starting point is a description of the customer journey as it works today. From there, the website can be shaped around it. You can share that journey with Page & Place to discuss how a new site would fit.