• Resolved tufty

    (@tufty)


    Hi there, this looks like a great plugin. One thing I can’t see how to do… the Create shopping account checkbox is obviously really important, but it is far too aggressively persistent in putting the tick back in case of any interaction. Can we change that, so if it is unticked it stays unticked?
    I know shopify does similar and it is annoying as a user. Web sites need to take no for an answer and conversion evidence does not capture trust loss.
    Thanks

Viewing 3 replies - 1 through 3 (of 3 total)
  • ruelkestrel

    (@ruelkestrel)

    Hi there,

    Thank you for your feedback!

    I wanted to clarify how the “Create shopping account” checkbox works in CheckoutWC: it is unchecked by default. When a user starts filling in their email address, the checkbox will automatically check itself, which is intended to streamline account creation. However, if the user chooses to uncheck it, it should remain unchecked until the checkout is completed. I’ve attached a short video demonstrating this behavior.

    https://www.awesomescreenshot.com/video/46501184?key=21db81de7fab14d47224e64c19503b9c

    Could you please clarify in what way you’re seeing the checkbox being “too aggressive”? This will help us understand the issue better and see if there’s anything we can improve.

    Thread Starter tufty

    (@tufty)

    Hi there,

    Yes of course. If you type [email protected], then untick, and correct it to [email protected], the tick comes back. Any further interaction with the email field seems to reset the account tickbox.

    Plugin Support Ian Misner

    (@ianmisner)

    Hi there,

    I definitely see your points around trust-conscious merchants. It’s a fair UX consideration, especially if you’re particularly sensitive to trust signals and privacy. I’m not 100% sure this is a behavior we should change in the CheckoutWC plugin, however.

    We try to strike a balance here: we default to respecting your explicit uncheck, but we assume a change to the email could signal a different choice.

    Most merchants want the checkbox to re-enable if the email changes because different email = potentially different customer intent. It’s also the standard pattern in identity-first checkouts, as you’ve noted. This is generally because the data shows that this has no negative impact on checkout conversion but has a positive correlation with either identifying or generating repeat buyers on a store.

    We’re definitely open to continued UX refinements if we see a larger pattern of feedback around this.

    In the meantime, we do actually offer a code snippet in our documentation to solve for changing the checkbox behavior on email validation. It allows you to set the default state for that checkbox to unchecked.

    Please let me know if you had additional questions or feedback. We really appreciate it!

    Cheers,

    Ian

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.