A motorhome booking plugin powering two real campervan sites in Cumbria

Project · Motorhome Booking

Built originally as a bespoke solution for Wicham Parish Council's motorhome aire — a parish-managed pitch for campervans and motorhomes — then extended for Estuary View Escapes' commercial campervan site at Millom Pier. Two very different operational contexts, same plugin.

The architecture

Motorhome Booking is built as a pure PHP WordPress plugin — no React frontend. The reasoning: bookings need to be SEO-indexable (so search engines can find specific pitches), and the warden frontend needs to work on the patchiest 3G signal at a campervan gate.

The plugin is 12,000+ lines of PHP across fifteen admin pages — bookings, calendar, bays, season pricing, blackout dates, bay maintenance, warden view, users, settings, instructions, audit log, export. Each admin page handles a specific operational concern. The data model uses custom database tables with versioned migrations and full referential integrity.

Behind the scenes: WooCommerce integration for payments and refunds, DVLA API for vehicle reg lookup, Twilio API for SMS notifications, iCal export for channel manager sync (so Pitchup or Airbnb can read the calendar even when bookings are taken direct).

It is one of our older plugins and a demonstration that pure-PHP plugins remain a viable architecture when SEO, signal reliability or admin-heavy workflows favour it over a SPA approach.

Two deployments, one codebase

The plugin runs on two production sites with quite different operational profiles.

Wicham Parish Council runs a council-managed motorhome aire — a small pitch facility funded and operated by the parish. The pricing reflects parish-resident discounts. Bookings need full audit trails for council financial reporting. The warden frontend is operated by volunteer staff on rota. Compliance with public-sector accessibility standards mattered from the start.

Estuary View Escapes runs a commercial campervan site at Millom Pier. Higher booking volume, more bays, commercial pricing tiers, full marketing integration. The warden frontend is operated by paid staff. Direct bookings replace what would otherwise flow through Pitchup at 5-7% commission.

Same plugin, same codebase. The differences are configuration, not custom code. New deployments don't require new development — they require configuration of bays, pricing, and operational rules.

iCal sync and channel management

Both Wicham and Estuary View Escapes still maintain listings on third-party platforms — Pitchup, Booking.com, Airbnb — because some customers will only book through those platforms. The Motorhome Booking plugin keeps those calendars in sync with direct bookings via iCal export.

A direct booking comes in through the plugin. The iCal export immediately reflects that bay as unavailable for the booking dates. When Pitchup or another platform reads the iCal, it sees the bay as already booked and prevents double-booking automatically.

Conversely, the plugin can read iCal feeds from external platforms — so a booking taken on Pitchup blocks the same bay in the direct booking system. Bidirectional iCal sync works with any platform that supports the iCal standard, which is most of them.

This means clients can run the plugin alongside their existing channel listings without changing how they market — and gradually shift volume toward direct bookings as those become a bigger proportion of revenue.

Warden frontend in practice

The warden frontend is the part of the plugin that wardens actually use day-to-day. It is deliberately not a desktop admin panel — it is a mobile-first interface designed for use on a phone or tablet, at the gate, in any weather and on any signal.

Today's arrivals are listed by expected arrival time with the customer name, vehicle registration, expected vehicle make and model (from DVLA lookup), bay assignment, payment status and any customer notes. Wardens can mark check-in with a single tap. Late arrivals are flagged automatically. Departures are similarly tracked.

Quick actions handle the common exceptions — extending a stay, moving a customer to a different bay, applying a discount, recording a maintenance issue with the bay. Each action creates an audit log entry automatically.

The warden frontend works offline if the connection drops mid-shift — changes are queued and synced when signal returns. Critical when sites are remote or rural, which most campervan sites are.

DVLA integration — the small detail that makes a big difference

DVLA vehicle registration lookup at checkout is one of those small features that punches above its weight.

When a customer enters their vehicle registration at checkout, the plugin looks it up via DVLA's API and confirms the make, model, year and fuel type. The customer sees a confirmation message — 'Found: 2019 Ford Transit Custom' — and can correct if they entered a typo.

At the warden frontend, the expected vehicle make and model appear alongside the booking. When a vehicle arrives at the gate, the warden can quickly verify against the system. Mis-typed regs that would previously have caused a discussion at the gate are caught at checkout, not on arrival.

It is also useful for audit and compliance — vehicle records held are accurate, can be exported for reporting, and integrate cleanly with public-sector accessibility requirements where bay-allocation justification needs to be auditable.

What this proves

TP Food and the LMS use React-heavy architectures because their workflows are interactive and benefit from a SPA approach. Motorhome Booking uses pure PHP because its workflows are admin-heavy and its operational reality (poor signal at remote campervan sites, SEO matters, wardens need offline-capable interfaces) favours a server-rendered approach.

The point: we pick the right architecture for the project, not the flashiest one. Some clients want React because it sounds modern; sometimes that's the right call. Some clients are surprised when we recommend pure PHP for parts of their build; sometimes that is the right call too.

The Motorhome Booking plugin is a demonstration that traditional WordPress plugin architecture — done properly, with audit logs, security checks, versioned migrations, mobile-optimised admin frontends and external API integrations — is more than enough to deliver production-grade software for many real businesses.

The methodology behind it is the same as our React-heavy builds. The result looks different — but the discipline doesn't change.