diff --git a/_docs/_partners/ecommerce/shopify/shopify_custom_integration.md b/_docs/_partners/ecommerce/shopify/shopify_custom_integration.md
index 72cf79458a6..28525a3aa0d 100644
--- a/_docs/_partners/ecommerce/shopify/shopify_custom_integration.md
+++ b/_docs/_partners/ecommerce/shopify/shopify_custom_integration.md
@@ -682,41 +682,46 @@ After the metafield is created, populate it for your customers. We recommend the
 
 #### Step 6.2: Create an endpoint to retrieve your external ID
 
-You need to create a public endpoint that Braze can call to retrieve the external ID. This is necessary for scenarios where Shopify can't provide the `braze.external_id` metafield. 
+You must create a public endpoint that Braze can call to retrieve the external ID. This allows Braze to fetch the ID in scenarios where Shopify cannot provide the `braze.external_id` metafield directly.
 
 ##### Endpoint specifications
 
-**Method:** `GET`
+**Method:** GET
 
-| Parameters | Description |
-| --- | --- |
-| `shopify_customer_id` | The Shopify customer ID. |
-| `email_address` | The email address of the logged-in user. |
-| `shopify_storefront` | The storefront for the request. |
-{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+Braze sends the following parameters to your endpoint:
+
+| Parameter            | Required | Data Type | Description                                                      |
+|----------------------|----------|-----------|------------------------------------------------------------------|
+| shopify_customer_id  | Yes      | String    | The Shopify customer ID.                                         |
+| shopify_storefront   | Yes      | String    | The storefront name for the request. Ex: `<storefront_name>.myshopify.com` |
+| email_address        | No       | String    | The email address of the logged-in user. <br><br>This field may be missing in certain webhook scenarios. Your endpoint logic should account for null values here (for example, fetch the email using the shopify_customer_id if your internal logic requires it). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation"}
 
 ##### Example endpoint
 
-```
-GET 
-https://mystore.com/custom_id?shopify_customer_id=1234&email_address=bob@braze.com&shopify_storefront=dev-store.myshopify.com
+```http
+GET https://mystore.com/custom_id?shopify_customer_id=1234&email_address=bob@braze.com&shopify_storefront=dev-store.myshopify.com
 ```
 
-##### Expected response
-
-Braze expects a `200` status code. Any other code is considered a failure.
 
-{% raw %}
+##### Expected response
+Braze expects a `200` status code returning the external ID JSON:
 ```json
-{ 
-    "external_id": "my_external_id" 
+{
+  "external_id": "my_external_id"
 }
 ```
-{% endraw %}
 
-{% alert important %}
-It's important to validate that the `shopify_customer_id` and `email_address` match the customer values in Shopify. You can use the [Admin API](https://shopify.dev/docs/api/admin-graphql) or [Customer API](https://shopify.dev/docs/api/admin-rest/2025-04/resources/customer) to validate these parameters and retrieve the `braze.external_id` metafield.
-{% endalert %}
+##### Validation
+
+It is critical to validate that the `shopify_customer_id` and `email_address` (if present) match the customer values in Shopify. You can use the [Shopify Admin API](https://shopify.dev/docs/api/admin-graphql) or [Customer API](https://shopify.dev/docs/api/admin-rest/2025-04/resources/customer) to validate these parameters and retrieve the correct `braze.external_id` metafield.
+
+##### Failure behavior and merging
+Any status code other than `200` is considered a failure.
+
+- **Merge implications:** If the endpoint fails (returns non-`200` or times out), Braze cannot retrieve the external ID. Consequently, the merge between the Shopify user and the Braze user profile will not happen at that time.
+- **Retry logic:** Braze may attempt standard immediate network retries, but if the failure persists, the merge will be deferred until the next qualifying event (for example, the next time the user updates their profile or completes a checkout).
+- **Supportability:** To support timely user merging, ensure your endpoint is highly available and handles the optional `email_address` field gracefully.
 
 #### Step 6.3: Input your external ID
 
diff --git a/_docs/_partners/ecommerce/shopify/shopify_standard_integration.md b/_docs/_partners/ecommerce/shopify/shopify_standard_integration.md
index 510d293511b..7fc14dda31c 100644
--- a/_docs/_partners/ecommerce/shopify/shopify_standard_integration.md
+++ b/_docs/_partners/ecommerce/shopify/shopify_standard_integration.md
@@ -177,41 +177,44 @@ After the metafield is created, populate it for your customers. We recommend the
 
 ### Step 4.2: Create an endpoint to retrieve your external ID
 
-You need to create a public endpoint that Braze can call to retrieve the external ID. This is necessary for scenarios where Shopify can't provide the `braze.external_id` metafield. 
+You must create a public endpoint that Braze can call to retrieve the external ID. This allows Braze to fetch the ID in scenarios where Shopify cannot provide the `braze.external_id` metafield directly.
 
 #### Endpoint specifications
 
-**Method:** `GET`
+**Method:** GET
 
-| Parameters | Description |
-| --- | --- |
-| `shopify_customer_id` | The Shopify customer ID. |
-| `email_address` | The email address of the logged-in user. |
-| `shopify_storefront` | The storefront for the request. |
-{: .reset-td-br-1 .reset-td-br-2 role="presentation" }
+Braze sends the following parameters to your endpoint:
+
+| Parameter            | Required | Data Type | Description                                                      |
+|----------------------|----------|-----------|------------------------------------------------------------------|
+| shopify_customer_id  | Yes      | String    | The Shopify customer ID.                                         |
+| shopify_storefront   | Yes      | String    | The storefront name for the request. Ex: `<storefront_name>.myshopify.com` |
+| email_address        | No       | String    | The email address of the logged-in user. <br><br>This field may be missing in certain webhook scenarios. Your endpoint logic should account for null values here (for example, fetch the email using the shopify_customer_id if your internal logic requires it). |
+{: .reset-td-br-1 .reset-td-br-2 .reset-td-br-3 .reset-td-br-4 role="presentation"}
 
 #### Example endpoint
 
-```
-GET 
-https://mystore.com/custom_id?shopify_customer_id=1234&email_address=bob@braze.com&shopify_storefront=dev-store.myshopify.com
+```http
+GET https://mystore.com/custom_id?shopify_customer_id=1234&email_address=bob@braze.com&shopify_storefront=dev-store.myshopify.com
 ```
 
 #### Expected response
-
-Braze expects a `200` status code. Any other code is considered a failure.
-
-{% raw %}
+Braze expects a `200` status code returning the external ID JSON:
 ```json
-{ 
-    "external_id": "my_external_id" 
+{
+  "external_id": "my_external_id"
 }
 ```
-{% endraw %}
 
-{% alert important %}
-It's important to validate that the `shopify_customer_id` and `email_address` match the customer values in Shopify. You can use the [Admin API](https://shopify.dev/docs/api/admin-graphql) or [Customer API](https://shopify.dev/docs/api/admin-rest/2025-04/resources/customer) to validate these parameters and retrieve the `braze.external_id` metafield.
-{% endalert %}
+#### Validation
+It is critical to validate that the `shopify_customer_id` and `email_address` (if present) match the customer values in Shopify. You can use the [Shopify Admin API](https://shopify.dev/docs/api/admin-graphql) or [Customer API](https://shopify.dev/docs/api/admin-rest/2025-04/resources/customer) to validate these parameters and retrieve the correct `braze.external_id` metafield.
+
+#### Failure behavior and merging
+Any status code other than `200` is considered a failure.
+
+- **Merge implications:** If the endpoint fails (returns non-`200` or times out), Braze cannot retrieve the external ID. Consequently, the merge between the Shopify user and the Braze user profile will not happen at that time.
+- **Retry logic:** Braze may attempt standard immediate network retries, but if the failure persists, the merge will be deferred until the next qualifying event (for example, the next time the user updates their profile or completes a checkout).
+- **Supportability:** To support timely user merging, ensure your endpoint is highly available and handles the optional `email_address` field gracefully.
 
 ### Step 4.3: Input your external ID