> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/adobe-commerce-magento/additional-features/checkout-shopper-registration.md).

# Checkout Shopper Registration

Checkout Shopper Registration lets guest shoppers register for an Adobe Commerce account after checkout. This helps retailers convert guest orders into customer accounts without interrupting the purchase flow.

### Benefits

Checkout Shopper Registration helps you:

* build an international shopper database
* deliver targeted promotions based on purchase history
* let shoppers track orders from an account dashboard
* improve repeat purchase potential

### Checkout Shopper Registration configuration

To enable Checkout Shopper Registration:

1. Ask your ESW point of contact to enable checkout registration in ESW Checkout.
2. In Adobe Commerce, enable **Registration after Checkout** in the ESW extension feature flag configuration.

{% hint style="info" %}
The feature depends on both ESW Checkout and the Adobe Commerce extension being enabled.
{% endhint %}

### How the feature works

<div data-with-frame="true"><figure><img src="/files/xbOYacPNLf41TArwDA1k" alt=""><figcaption></figcaption></figure></div>

This feature applies to guest checkout only. The post-checkout flow depends on whether the shopper email already exists in Adobe Commerce.

There are two user flows:

* The shopper email does not exist in Adobe Commerce.
* The shopper email already exists in Adobe Commerce.

### Guest shopper flow for a new email address

If the guest shopper uses an email address that does not already exist in Adobe Commerce:

1. The shopper adds items to the cart as a guest.
2. The shopper completes ESW checkout with an email address that is not linked to an existing Adobe Commerce account.
3. On the order confirmation page, the shopper is shown a **Register** prompt.
4. The shopper clicks **REGISTER**.
5. The Adobe Commerce extension creates a customer account with the checkout email address.
6. The shopper receives an email with temporary password and account confirmation details.

### Guest shopper flow for an existing email address

If the guest shopper uses an email address that already exists in Adobe Commerce:

1. The shopper adds items to the cart as a guest.
2. The shopper completes ESW checkout with an email address that already belongs to an Adobe Commerce account.
3. On the order confirmation page, the shopper is shown a **Register** prompt.
4. The shopper clicks **REGISTER**.
5. The extension redirects the shopper to the native Adobe Commerce login page.
6. The shopper signs in to link the recent order to the existing account.
7. After sign-in, the shopper can view the linked order from the account order details page.

### Expected result

After registration completes:

* new guest shoppers can create an account from the confirmation flow
* existing customers can link the new order to their current account
* the retailer keeps a stronger record of international shopper activity


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/adobe-commerce-magento/additional-features/checkout-shopper-registration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.