Edit Booking / Checkout form

[J. Davis]

Hi Alberto,
Thanks for your feedback and questions.

Some of the elements can be hidden with custom CSS while others can be overridden with functions. You can find some examples here on the forum, for example:

Create custom CSS for Checkout form – [mphb_checkout]

Link to services on checkout form (or pop-up info window)

Check-in range Hours

When you override some checkout section within a function you can add code to the functions.php file of the child theme, to a third-party Snippets plugin, or create a custom plugin where you will add all your custom snippets.

[J. Davis]

Hi Robert, you can try this example https://motopress.com/forums/topic/full-guest-name/#post-657854

[Alberto]

About 6 years later. . .

Reading through this thread, it’s evident that many users share the same concerns about the checkout and booking confirmation process in MPHB. The current structure often feels redundant, inflexible, and not easily customizable without resorting to either CSS hacks (which are a “fix” but not ideal) or direct PHP edits (which are inaccessible to non-developers and break with updates).

If I were a developer working on MPHB, I would ask myself:

• Why are users forced to edit core PHP files for something as basic as removing unnecessary checkout elements?
• Why isn’t there a built-in toggle in settings to remove redundant fields like “Full Guest Name” for single accommodation sites?
• Why isn’t the checkout confirmation page more easily customizable, without requiring deep code modifications?
• Shouldn’t a premium plugin offer a better out-of-the-box user experience instead of making users struggle with workarounds?

MPHB is a great product, but a reservation system should focus on efficiency, clarity, and adaptability—not unnecessary complexity. As many have pointed out, the fewer steps, the better for a smooth booking process.

So the real question is: Will these concerns be officially addressed in a future update, or should we assume that customization will remain limited to code-level modifications?

For other users: the visibility of this thread might be low, as it tends to get lost in general support discussions rather than a dedicated section for feature improvements. To help bring more attention to this request, please leave a “+1” below. Thanks for your support!

[Pavel Lukáš]

+1
+1

[Author]

Posts