How an Italian Tour Company Stopped Losing Booking Details Between Reservation and Order
Staff could see a booking existed, just not what the customer asked for.
In the transfer business, the details are the service.
Sorrento Transfer, an excursion booking company in Italy.
Customers reserve tours online through YITH WooCommerce Booking, with Extra Product Options & Add-Ons collecting the additional information each reservation needs. The site’s job is simple to state: let customers submit required details during reservation, and carry those details through checkout, emails, and order records without losing a single field.
They arrived with a one-sentence definition of done.
One clear brief. Every field, everywhere it belonged.
Where do the pickup details go when confirmation is on?
Customers filled in every field at reservation. Confirmation erased them all.
With Require confirmation enabled, Extra Product Options data disappeared: gone from New Booking and Confirmed Booking emails for admin and customer alike, and absent from the WooCommerce order even after payment. Staff chased customers to re-ask for details already given.
- Complete booking emails
- Data in the backend
- No chase-up calls
- Fields survive confirmation
- Checkout shows the inputs
- Orders carry every field
The real question
YITH Booking and Extra Product Options each did their job. The failure lived between them, at the moment YITH rebuilds the cart for confirm-and-pay and the extra fields lose their home. The question was how to make two plugins hand data across that gap.
All in all, it came down to these 5 non-negotiables.
Extra Product Options data had to survive with Require confirmation switched on.
New Booking and Confirmed Booking emails had to carry the details, for customer and admin.
Confirmed-and-paid bookings had to pass every extra field into the WooCommerce order.
The two plugins had to cooperate at the exact moment YITH rebuilds the cart.
Admins needed the stored details visible directly inside the booking record.
The fix followed the data through every hand-off.
Capture it, restore it, then show it everywhere it counts.
01 · Capture & Restore
Data that survives the confirmation rebuild.
The selected extra-field data is now captured and stored the moment booking confirmation is requested, preserving customer inputs before payment happens. When YITH recreates the cart for confirm-and-pay, the stored data returns as cart_item_data, so Extra Product Options renders it properly at checkout.
-
Stored at request Inputs preserved before payment even starts.
-
Restored on rebuild cart_item_data carries fields into checkout.
-
Rendered correctly Customers see exactly what they submitted.
02 · Backend Visibility
Every booking record tells the full story.
The booking post type backend view was modified to display the stored additional data, so admins see extra details directly in the booking record. Verification that once meant contacting the customer again now takes a glance, which is where the 40% faster verification figure comes from.
-
Backend display Stored fields shown inside the booking itself.
-
One-glance checks No cross-referencing, no customer callbacks.
-
Operational chain intact Booking to fulfillment, fully informed.
03 · Email Placeholders
Reservation details, delivered to both inboxes.
Additional placeholders built for New Booking and Confirmed Booking emails let the extra fields slot into email templates. Both customer and admin emails now include the required reservation details, closing the loop that once forced staff into manual follow-ups on every affected booking.
-
Custom placeholders Extra fields insertable in both email types.
-
Both sides informed Customer and admin copies carry the details.
-
Follow-ups cut 70% The chase-up burden measurably gone.
From vanishing fields to a booking chain that never drops data.
Follow-ups no longer needed
Quicker verification for admins
Fewer checkout booking errors
Fewer checkouts abandoned
When the flow was sealed, the numbers followed.
Reliability restored across the full confirmation flow.
details lost at confirmation
Extra fields wiped when confirmation was required
Booking emails silent on customer requirements
Paid orders arriving without their add-on data
preserved end to end
Data fully carried, even with Require confirmation on
Emails include every detail via placeholders
Confirmed payments land in orders complete
Orders coming through with details missing?
Don’t chase customers for information they already gave you. Get your WooCommerce checkout & booking flow fixed so every order arrives complete.
- See what custom WooCommerce can handle
- Explore builds shaped to niche bookings
- Learn how complex stores stay easy to run
Tech Partners Driving Business Outcomes
For 14+ years, we’ve partnered with ambitious businesses across industries that are investing seriously in growth and need websites built for what comes next.