Customers and customer groups

A customer holds buyer profile data and addresses. Customer groups express commercial segments that can affect prices and configured checkout rules. Creating a customer record is different from establishing an authenticated customer session.

Profile and identity

Use native fields for email, name, addresses, and supported consent data. Use metafields for typed extensions. A browser-submitted email or customer ID is not proof that a shopper owns the account. Use the authenticated customer response for protected profile and account workflows.

Groups and prices

A customer can belong to multiple groups. For example, a Wholesale group can have dedicated variant prices. Group membership must be managed through authorized operations, not trusted from a URL or form field. Groups are commerce data, not a replacement for application authorization.

Guest checkout

A cart can carry a guest email without a signed-in customer session. When a buyer signs in, deliberately reconcile the cart with that customer and refresh customer-sensitive prices. When they sign out, clear private account state and make sure it cannot appear for the next user of the browser.

Historical orders

An order retains its own commercial and address data. A later profile edit should not be used to rewrite what your order confirmation displays. Use the order response for historical purchases and the customer response for the current account.

For registration, activation, session handling, and password recovery, follow Add customer accounts.