Introducing Stores for Customers in Beta

You can now assign customer accounts to stores. This allows you to restrict a customer's login and associated carts to a specific store. This is useful for multi-store setups.

Introduced methods to the HTTP API that allow you to access customers belonging to a specific store. They can be used with an OAuth scope like manage_customers:acme-inc:luxury-brand.

When using stores, a customer can either register globally, or have a registration specific to a store. For more information, see Global versus store specific customers.

• [API] New store-based OAuth scopes manage_customers:{projectKey}:{storeKey} and view_customers:{projectKey}:{storeKey}.
• [API] Added the following methods to the HTTP API to access Customer in a specific Store:
  • Get a Customer in a Store by ID
  • Get a Customer in a Store by Key
  • Query Customer in a Store
  • Create Customer (Sign Up) in a Store
  • Update Customer in a Store by ID
  • Update Customer in a Store by Key
  • Set Stores
  • Add Store
  • Remove Store
  • Authenticate Customer (Sign In) in a Store
  • Create a Token for Resetting the Customer’s Password in a Store
  • Get Customer By Password Token in a Store
  • Reset Customer’s Password in a Store
  • Create a Token for verifying the Customer’s Email in a Store
  • Get Customer By Email Token in a Store
  • Verify Customer’s Email in a Store
  • Delete Customer by ID in a Store
  • Delete Customer by Key in a Store
• [API] Added the OAuth 2.0 Password Flow for Customer in a Store.
• [GraphQL API] Added the stores fields on the types Customer, CustomerDraft.
• [GraphQL API] The existing query fields inStore and inStores can be used to query customers.
• [GraphQL API] Added the storeKey argument to customer mutations customerSignUp, updateCustomer, deleteCustomer, customerChangePassword, customerCreatePasswordResetToken, customerResetPassword, customerCreateEmailVerificationToken, customerConfirmEmail