[tourist]

The new Cart looks good. It’s really great the customer can edit the PAX number in the Checkout.

One thing I have noticed is if you edit the number of PAX in the Checkout area then the Traveller Details section of the Checkout page doesn’t update to reflect the change e.g change PAX from 1 to 2 then you can still only enter the details for the Lead Traveller. Customers can check out like this which means we wouldn’t have the info for the 2nd Traveller.

If the page is refreshed the Traveller info area updates accordingly. Is there a simple fix for this? I guess so as the Total Trip Price further below in the Booking / Payments area updates accordingly with edits to the PAX.

I’ve got an unedited latest Wp Travel and WP Travel Pro extensions only on the latest WordPress, nothing else that could be causing any conflicts.

[tourist]

Hmm, I’ve also just found playing around with the checkout that if for instance the customer had 5 Pax in their cart arriving at checkout, and then used the edit button to reduce the PAX to 1 but didn’t hit the update button, that the Total Trip Price would reduce to the price for one PAX, but if they actually hit book it would be for the 5 PAX.

Surely there should be some kind of prevention of continuing with the booking when editing until edits are confirmed? Or if they are in the middle of edits and they haven’t confirmed yet a quick confirmation screen popup?

[tourist]

Another thing I’ve noticed playing around with the new checkout process, is if the customer books a trip without any trip extras, but then changes their mind at the checkout and clicks the edit button a heading for Trip Extras appears but nothing is actually displayed. It would be great for the trip extras that are linked to a pricing to appear here automatically with quantity 0 if they’re not selected on the trip page itself.

[wensolutions]

Hello,

Please find answers regarding your queries pointwise below:

Query1: One thing I have noticed is if you edit the number of PAX in the Checkout area then the Traveller Details section of the Checkout page doesn’t update to reflect the change

Response: Actually, when we inspected in our side everything is working fine as you can see in screen record given below:

https://www.loom.com/share/567a2fc0b4754e7e823f4c2c19ec18cf

So, please make sure that you have enabled ‘Enable multiple travelers’ option by going to Admin Panel > WP Travel > Settings > Trip

https://prnt.sc/t2kn5d

Query2: Surely there should be some kind of prevention of continuing with the booking when editing until edits are confirmed? Or if they are in the middle of edits and they haven’t confirmed yet a quick confirmation screen popup?

Response: Thank you for letting us know as well as for your suggestion.

Also, we will note it as feature request and will work on it.

Query3: Another thing I’ve noticed playing around with the new checkout process, is if the customer books a trip without any trip extras, but then changes their mind at the checkout and clicks the edit button a heading for Trip Extras appears but nothing is actually displayed. It would be great for the trip extras that are linked to a pricing to appear here automatically with quantity 0 if they’re not selected on the trip page itself.

Response: Thank you for letting us know. We will note it and will work on it.

If you have any queries further, let us know.

Thank you.

[tourist]

Hi,

in terms of Question 1. I have Multiple Travellers enabled. Your demonstration shows exactly the problem I was describing. How does the customer know that they need to refresh the page after hitting update on the minicart in checkout? Many non tech savvy customers are going to be confused when the extra traveller info doesn’t appear when they hit the update button. Either this should happen automatically (is it possible to force a page refresh) or there should be a prompt for the customer. It is pretty poor UX design if that is the intended functionality, especially given the customer can still checkout having only entered the traveller details for 2 Travellers and not the third at that point in your video. If you think that’s acceptable normal functionality I think I should consider asking for a refund on my WP Travel Pro!

[tourist]

Good to see the other bits will be worked on, I guess I’ll have to code my own workaround for the first issue. If anyone would like to see an improved functionality here please contact me and I’ll see what I can do to help.

[wensolutions]

Hello @stuartladehotmail-com,

The issue is noted on our side as well and has already been fixed. We will let you know as soon as the update is out after fixing the issue.

Hoping for your kind co-operations.

Thank you.

[tourist]

Hi,

that’s great it’s already fixed. Any idea on timeline for the next update?

A simple fix for point 2 would be to ditch having the Update mini-Cart Button at all, and just make the mini-cart button update on each click. Given that most trips I imagine are taking bookings for 1 – 5 people it wouldn’t be a big difference in speed for the customer as it’s only a small refresh each time rather than the entire page and might make the checkout process a little more Customer friendly.

[wensolutions]

Hello @stuartladehotmail-com,

As for now, we won’t be immediately incorporating this feature however as mentioned above we have already fixed the issue regarding the update of the mini cart.

We will note this feature as the requested feature and will work on it in future but will not be available as for now.

Hope you understand.

Let us know if you have any queries/confusion further.

Thank you.

[tourist]

Just updated to WP Travel 4.0.4 and surprised to see this hasn’t been fixed. I thought you said this had been addressed?

[wensolutions]

Hello @stuartladehotmail-com,

The issue has already been fixed as you can see in the screen record below:

https://www.loom.com/share/cdf01cbafca94c98833caa8d2c586cee

The automatic update is yet to include and has not been included in this version. We will discuss it further and will work on it.

Hope this clears the confusion.

Thank you.

[tourist]

You’ve fixed an issue but the problems with the cart still persist. The automatic update of the traveller details section isn’t an “upgrade” to be added on later, it’s a known flaw and issue potentially causing customer confusion and loss of sales, or potential aggrievements with customers after booking.

Simply put the minicart in the checkout area doesn’t work. If the customer edits the number of travellers and hits update the traveller details section remains as it was unless the customer knows to refresh the page. If they fail to do that it leads to one of 2 scenarios –

1. Decrease PAX number e.g added 3 PAX on booking page, reduces PAX to 2 in Checkout – booking payment is taken for 2 PAX but details for 3 PAX are submitted and the PAX number is set to 3 in the booking. The customer may think they’ve gotten away with getting 3 bookings for the price of 2 as all the details for all 3 travellers are present in their account area. Trip organiser now has to have a conversation with the client to figure out which 2 of the 3 entered travellers details are the ones relevant to the booking. Trip organiser then has to manually delete the details for the incorrect traveller, there’s no way to actually remove an entire traveller from the booking, so they can only delete the entries for the fields.

2. Increase PAX number e.g added just 1 PAX on booking page, increases PAX to 3 in Checkout – booking payment is taken for 3 bookings but customer has only entered details for lead traveller and PAX in booking is set to 1. Trip organiser now has to contact customer to get the remaining 2 travellers information for the booking. There is no way of manually adding extra traveller information to the booking in the backend. This is a massive issue which if the Checkout process didn’t have this flaw wouldn’t happen in the first place.

These 2 problems are caused by the poor checkout process design as it stands, and that’s assuming the customer doesn’t get confused by the inability to add the correct traveller details and you lose the booking entirely if the customer decides to go elsewhere.

[wensolutions]

Hello @stuartladehotmail-com,

Thank you for the detailed explanation of the issue. The issue does exist. We have already informed the developer team.

We will get back to you once the issue get fixed.

Thank you very much for your co-operations.

Regards!!

[tourist]

Thanks, look forward to seeing a usable working version.

As an aside, the ability to manually add and subtract the Pax number from the admin area and have the number of traveller details entries correspondingly update would be a super useful feature. For instance if somebody has booked a large group, and just one person needs to cancel. The ability to delete an entire traveller entry would be super useful, but potentially keep a record of the change for note-keeping in the booking. Similarly if a customer wants to add an extra person to their booking, it’s useful for everyone to add it to the same booking so you know the group are together. Being able to manually add extra travellers to bookings would be useful. Again, for note-keeping it would be useful to have an area where admins could make a note of extra payments taken, changes to bookings etc.

Manually adding bookings from the back end would also be a really useful feature come to think of it. Admins could then combine multiple bookings from different people within the same group to collate information as well as taking bookings over the phone/ in person where needed

But that’s getting ahead of fixing the main issue of having a working cart! Look forward to being able to start work developing the website once the basics all work.

[wensolutions]

Hello,

Thank you very much for your suggestion.

We will note the feature you have requested as feature request and will work on it in future.

If you have any queries further, let us know.

Thank you.

[Author]

Posts