Guides · Aus der Werkstatt · 2 min

When the booking shows the wrong amount: why booking systems need end-to-end testing

Maria Ducos · updated October 2026
In short

When testing a booking store, everything looked fine on desktop. Only when we ran through real bookings did the bugs surface: wrong totals in the cart, shipping copy for a product that never ships, cut-off buttons on mobile and mixed languages in the foreign-language versions. We traced every bug individually and fixed it where it originated. Some were in the theme, some in the booking app. The lesson: a booking system is only tested once every combination has been booked all the way through.

The case

With a booking product, the price depends on many factors at once: date, rate, season, extras, deposit. An error in that calculation doesn’t stand out at a quick glance. It stands out when a guest sees a different amount than expected, and then the trust is gone.

Our test matrix

Instead of clicking through once, we combined systematically:

  • Language: every language version separately
  • Device: desktop and mobile
  • Date and rate: high and low season, different start times
  • Extras: none, one, several
  • Path: product page, cart, checkout, confirmation email

Every combination was run through to confirmation. Only then do the bugs show up that only occur in one specific combination.

Questions about your store?
Audit in 3 business days. For €490.
To the audit

Theme or app?

A big part of the work was figuring out where each bug belonged. A cut-off button is usually a theme issue, a wrong total often an app issue. Bugs that sat in the app we passed to the provider with a precise description, instead of patching around them in the theme. That fixes the problem in the right place.

One more detail: standard copy from regular e-commerce, such as shipping and delivery times, has no place in a booking store. It has to be deliberately removed or adapted.

Your takeaways

  • A desktop check isn’t a test. With bookings, every combination counts, all the way to confirmation.
  • Build yourself a test matrix. Language, device, date, rate and extras, combined systematically.
  • Separate app bugs from theme bugs. That’s the only way the fix lands in the right place.
  • Remove copy that doesn’t fit. Shipping notes on an experience confuse more than they explain.

Do you sell bookings or appointments through Shopify? We test them the way your guests book, before a guest does.

Rather talk than read?

20 minutes, honest and no strings attached. Afterwards you know what your store needs.