--- title: Add shuttle transfer bookings to WordPress description: "Amelia and Bookly handle everything except what you actually need: a form for fixed routes at set prices. This plugin closes that gap." source: https://steem.dev/blog/wordpress-shuttle-transfer-booking-plugin published: 2026-09-05 updated: 2026-10-31 alternative_to: Amelia site: Steem — AI WordPress plugin generator --- # Add shuttle transfer bookings to WordPress Amelia, Bookly and WP Appointment Booking are built for service businesses with variable staff availability, calendars across locations and pricing rules per service. Run airport transfers or city-to-city shuttles on a handful of fixed routes with set departure times and none of that applies, yet setup still takes hours before a visitor can choose anything. A transfer operator with four routes and two departures each needs three things: a place to define the routes, a form visitors can book with, and somewhere in the admin to see what came in. This plugin is those three things. ## What one build covers - Settings page to define routes with From, To, price, and departure times - Booking form shortcode with route selector, departure time dropdown, date, passengers, name, and email - Bookings saved as a custom post type and listed in an admin table - Admin email notification with full booking details on each submission - Confirmation message displayed to the visitor after a successful submission ## What it does not cover - Seat capacity limits: the plugin does not block a departure when it is fully booked - Payment at booking: no WooCommerce or payment gateway integration - Customer accounts or booking history for returning visitors - Variable pricing by date, season, or passenger count - Multi-vehicle or driver assignment ## The prompt ```text Build a WordPress plugin for fixed-route shuttle and transfer bookings. Add a top-level admin menu with the label 'Shuttle Bookings'. Under it add a Settings page and a Bookings page. On the Settings page, allow the admin to define routes using a repeatable set of fields saved with update_option: each route has a From location, a To location, a price, and a list of departure times stored as a comma-separated string. Provide an Add Route button that appends a new row of fields using JavaScript, and a Remove button on each row. Register a custom post type called shuttle_booking with the label Bookings, not publicly queryable, with show_in_menu set to the Shuttle Bookings menu slug. On the Bookings page, list all shuttle_booking posts in a table ordered by date descending, showing columns for Route, Departure Time, Travel Date, Passengers, Customer Name, Customer Email, and Date Submitted, with values pulled from post meta. Register a shortcode shuttle_booking_form that outputs a booking form. The form must include: a select element for route populated from saved settings with From and To as the label, a select element for departure time showing the times for the chosen route updated via JavaScript when the route changes, a date input, a number input for passenger count with a minimum of 1, a text input for customer name, and an email input. On POST submission, validate that all fields are present, create a shuttle_booking post with post_status publish, save all values as post meta using the keys route, departure_time, travel_date, passengers, customer_name, and customer_email, send a plain-text email to get_option admin_email with all booking details, and display a success message in place of the form. Register all hooks inside a function attached to plugins_loaded. ``` ## Why booking plugins are overkill for fixed routes General booking plugins assume availability depends on which staff member is free, which location is in use and how long each appointment runs. Before a visitor can pick a time, you configure services, staff profiles, working hours, buffers and often a payment gateway. A shuttle operator has none of those problems. Routes, prices and departure times are fixed; the only unknowns are whether someone wants to travel on a given date and how many seats they need. A form that captures that and emails you is the whole product. That mismatch is why so many operators end up with a contact form, a WhatsApp link or nothing at all. ## Routes in settings, a form in a shortcode, bookings in a table A Shuttle Bookings menu has a settings page for as many routes as you run, each with From, To, a price and its departure times as a comma-separated list, saved with `update_option` so they survive updates. `[shuttle_booking_form]` puts the form on any page: a route selector, a departure time dropdown that changes with the route, a date picker, a passenger count, and the customer's name and email, all required. Each submission is saved as a custom post type entry, the site admin email gets the full details, and the form is replaced by a confirmation message. A Bookings table in the admin lists every submission by date with route, departure, travel date, passengers, name and email; WP All Export will turn them into a spreadsheet. Notifications go to the address under Settings > General, or elsewhere through a `wp_mail` filter in your theme's functions.php. ## Airport runs and fixed-route transfers Airport transfer and shuttle operators with a defined set of pickup and destination pairs at fixed prices match this model exactly. So do tour operators offering transfers between a few fixed points as part of a package: the form sits on a page, visitors send a request, and you confirm by hand. Any service with fixed routes and prices that wants a booking form without signing up to a scheduling platform, or configuring staff calendars that do not exist, fits. ## Seat limits, payment and seasonal prices Capacity is not tracked. Every submission goes through however many have already booked the same departure; enforcing a limit would mean counting bookings per slot and removing a full departure from the form. Amelia's free tier handles capacity if that matters. Nobody pays at booking. You get the request and take payment separately, by invoice, bank transfer or a payment link in your confirmation. WooCommerce with a simple product per route is the alternative if you need payment up front. Each route has one fixed price, so pricing by date, season or passenger count means more logic than this build has. A follow-up message can add a special requests field saved with the booking and included in your email, or a confirmation email to the customer with the route, departure, date, passenger count and a booking reference. --- Source: https://steem.dev/blog/wordpress-shuttle-transfer-booking-plugin Build this plugin: https://steem.dev/app