jpiv_

[hollow thorn]

hello! I think what you would probably want to do is to implement a sign in process for your site. If the customer doesn't register on your site, then you would want to create a new Customer object for them instead. Does that make sense?

[noble sable]

Yes, that makes sense. The specific context here is that this is for a pre-order launch and we were hoping to not have to build out a signup/sign-in flow and could do something that is a bit lighter weight.

[hollow thorn]

it's not a good idea to pre-fill the customer id without some form of authentication prior. When you pre-fill the customer id, it also prefills the payment method info (depending on certain criteria)

n payment mode, the customer’s most recently saved card payment method will be used to prefill the email, name, card details, and billing address on the Checkout page. In subscription mode, the customer’s default payment method will be used if it’s a card, otherwise the most recently saved card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer’s card details.

[noble sable]

Ok, so it sounds like we will either need to add some form of authentication or create a new customer each time.

thank you!

[hollow thorn]

personally, i'd recommend doing authentication. You can't merge Customer objects just so you're aware, so you might end up with multiple of them

but if multiple Customer objects are not a concern, then totally fine to go down that route first too