We're looking to add guest checkout to our TNEW site soon. Testing has gone pretty well, we like the overall ease of use. However, guest checkout is allowed when purchasing a membership, which we don't necessarily want. Does anyone know of a way to suppress this, or has anyone come up with a workaround? We need to have the information to send the member their cards and welcome packet.
Thanks for the advice,
Mike Dorsey
CRM Specialist - National WWI Museum and Memorial
mdorsey@theworldwar.org
Hi Mike and Anastassia,
The guest checkout currently is not managed at the product level so it's either available for all orders or not at all. We will be looking to enhance guest checkout to support being configurable at the product level but it was not included as a feature in the original release as we were primarily working toward parity with the existing guest checkout feature.
One way to help with this though would be to encourage/have a user log in first before adding anything to their cart. Guest checkout does not appear as an option on the log in page until they have added an item to their cart. I recognize it's not ideal adding messaging on the membership page to log in first or create an account first, but that's one option.
In addition, in order to gather information for where to send the membership cards and welcome packet, have you looked into requiring addresses for guest accounts?
This feedback is very helpful though so thank you!
I had considered that, yes. When we first set up guest checkout in Test, we had the address fields required. Then an update was applied to Test sites and the address fields went away. Interested parties at the museum were happy about those fields going away, because their main reason for wanting guest checkout was to speed up the user experience. But this might be a good argument for adding those fields back in while we wait for further developments around guest checkout.
And, worst-case scenario, we could also change the messaging.
Do you have a timeline for when guest checkout will be configurable at the product level?
Thanks,