docs: add section on customer account deletion (#13048)

www/apps/book/public/llms-full.txt

@@ -23274,9 +23274,39 @@ When this or another guest customer registers an account with the same email, a
 
 ## Email Uniqueness
 
-The above behavior means that two `Customer` records may exist with the same email. However, the main difference is the `has_account` property's value.
+The above behavior means that two `Customer` records may exist with the same email address. However, the main difference is the `has_account` property's value.
 
-So, there can only be one guest customer (having `has_account=false`) and one registered customer (having `has_account=true`) with the same email.
+So, there can only be one guest customer (having `has_account=false`) and one registered customer (having `has_account=true`) with the same email address.
+
+***
+
+## Customer Deletion and Email Reuse
+
+When a merchant deletes a customer, the `Customer` record is soft-deleted, meaning it is not permanently removed from the database.
+
+When using the Medusa Application with the [Auth Module](https://docs.medusajs.com/Users/shahednasser/medusa/www/apps/resources/app/commerce-modules/auth/index.html.md), possible confusion may arise in the following scenarios:
+
+1. An admin user is using the email address `john@example.com`, and a customer tries to register with the same email address.
+2. An admin user has deleted a customer with the email address `jane@example.com`, and another customer tries to register with the same email address.
+
+In these and similar scenarios, the customer trying to register will receive an error message indicating that the email address is already in use:
+
+```json
+{
+  "type": "unauthorized",
+  "message": "Identity with email already exists"
+}
+```
+
+To resolve this, you can amend the registration flow to:
+
+1. Retrieve the login token of the existing identity with the same email address.
+2. Use the login token when registering the new customer. This will not remove the existing identity but will allow the new customer to register with the same email address.
+
+You can learn more about how to implement this flow in the following guides:
+
+- [Conceptual guide on how to implement this flow with Medusa's authentication routes](https://docs.medusajs.com/Users/shahednasser/medusa/www/apps/resources/app/commerce-modules/auth/authentication-route#handling-existing-identities/index.html.md).
+- [How-to guide on how to implement this in a storefront](https://docs.medusajs.com/Users/shahednasser/medusa/www/apps/resources/app/storefront-development/customers/register/index.html.md).
 
 
 # Links between Customer Module and Other Modules

www/apps/resources/app/commerce-modules/customer/customer-accounts/page.mdx

@@ -24,6 +24,36 @@ When this or another guest customer registers an account with the same email, a
 
 ## Email Uniqueness
 
-The above behavior means that two `Customer` records may exist with the same email. However, the main difference is the `has_account` property's value.
+The above behavior means that two `Customer` records may exist with the same email address. However, the main difference is the `has_account` property's value.
 
-So, there can only be one guest customer (having `has_account=false`) and one registered customer (having `has_account=true`) with the same email.
+So, there can only be one guest customer (having `has_account=false`) and one registered customer (having `has_account=true`) with the same email address.
+
+---
+
+## Customer Deletion and Email Reuse
+
+When a merchant deletes a customer, the `Customer` record is soft-deleted, meaning it is not permanently removed from the database.
+
+When using the Medusa Application with the [Auth Module](../../auth/page.mdx), possible confusion may arise in the following scenarios:
+
+1. An admin user is using the email address `john@example.com`, and a customer tries to register with the same email address.
+2. An admin user has deleted a customer with the email address `jane@example.com`, and another customer tries to register with the same email address.
+
+In these and similar scenarios, the customer trying to register will receive an error message indicating that the email address is already in use:
+
+```json
+{
+  "type": "unauthorized",
+  "message": "Identity with email already exists"
+}
+```
+
+To resolve this, you can amend the registration flow to:
+
+1. Retrieve the login token of the existing identity with the same email address.
+2. Use the login token when registering the new customer. This will not remove the existing identity but will allow the new customer to register with the same email address.
+
+You can learn more about how to implement this flow in the following guides:
+
+- [Conceptual guide on how to implement this flow with Medusa's authentication routes](../../auth/authentication-route/page.mdx#handling-existing-identities).
+- [How-to guide on how to implement this in a storefront](../../../storefront-development/customers/register/page.mdx).

www/apps/resources/generated/edit-dates.mjs

@@ -16,7 +16,7 @@ export const generatedEditDates = {
   "app/commerce-modules/currency/page.mdx": "2025-04-17T08:48:30.550Z",
   "app/commerce-modules/customer/_events/_events-table/page.mdx": "2024-07-03T19:27:13+03:00",
   "app/commerce-modules/customer/_events/page.mdx": "2024-07-03T19:27:13+03:00",
-  "app/commerce-modules/customer/customer-accounts/page.mdx": "2025-02-26T11:17:42.327Z",
+  "app/commerce-modules/customer/customer-accounts/page.mdx": "2025-07-25T12:03:05.017Z",
   "app/commerce-modules/customer/page.mdx": "2025-04-17T08:48:31.918Z",
   "app/commerce-modules/fulfillment/_events/_events-table/page.mdx": "2024-07-03T19:27:13+03:00",
   "app/commerce-modules/fulfillment/_events/page.mdx": "2024-07-03T19:27:13+03:00",