Documentation update for SCP and SCP-B2B packages by deepak-soni1 · Pull Request #843 · commerce-docs/microsite-commerce-storefront

deepak-soni1 · 2026-04-20T10:52:41Z

Documentation update for SCP and SCP-B2B packages -

SCP-B2B-1.0.19
SCP-B2B-1.0.20

SCP-4.8.18
SCP-4.8.19
SCP-4.8.20

SCP-4.7.11
SCP-4.7.12
SCP-4.7.13

bdenham · 2026-04-20T15:58:46Z

+
+          - **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.
+          - **WishList Items**: Resolved an issue with wishlist items in multi-store view scenarios under the same website, wishlist items and items_count are now consistent and properly synchronized.
+          - **Cart Items**: Resolved an issue where cart item availability checks were failing for products with "Manage Stock" set to No.


Suggested change

- **Cart Items**: Resolved an issue where cart item availability checks were failing for products with "Manage Stock" set to No.

- **Cart Items**: Fixed cart availability checks for products where "Manage Stock" is disabled. Cart items now correctly display availability status.

change "display" to "return"

bdenham · 2026-04-20T15:59:36Z

+          The Storefront Compatibility Package has been updated to include the following changes:
+
+          - **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.
+          - **WishList Items**: Resolved an issue with wishlist items in multi-store view scenarios under the same website, wishlist items and items_count are now consistent and properly synchronized.


Suggested change

- **WishList Items**: Resolved an issue with wishlist items in multi-store view scenarios under the same website, wishlist items and items_count are now consistent and properly synchronized.

- **WishList Items**: Fixed inconsistencies in wishlist items and item count across multiple store views within the same website. Wishlist data is now properly synchronized.

No captial L in wishlist

bdenham · 2026-04-20T16:04:21Z

+      >
+          The Storefront Compatibility Package has been updated to include the following changes:
+
+          - **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.


Suggested change

- **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.

- **Login as Customer**: A new "Login as Customer" feature enables seller-assisted buying. Admins can now generate a one-time login code from the customer view page in the backend and use it to authenticate as the customer via GraphQL APIs. Two new fields have been added: `admin_assistance_actions` to the `Customer` type (to track admin activities) and `admin_assisted_order` to the `CustomerOrder` type (to mark orders placed by admins). The new `exchangeOtpForCustomerToken` mutation retrieves a customer token using the one-time code, complementing the existing `generateCustomerToken` mutation.

Add a link to https://experienceleague.adobe.com/en/docs/commerce-admin/customers/customer-accounts/manage/login-as-customer and to the new mutation.

Rewrite this to mention the new mutation before you list the changes to the Customer type.

Hello @keharper
As I shared, we moved the LAC code from ACCS to SCP because the feature overlapped.
Ref. -
https://git.corp.adobe.com/core-commerce-saas/commerce-core-saas-service/blob/main/application/modules/Magento/OtpGraphQl/etc/schema.graphqls

It was originally introduced in ACCS, but due to the code sync-up, we needed to move it to SCP. Later, the ACCS team will remove it from their codebase as per our earlier discussions.

On Friday, we have another call with the ACCS team regarding the RL sharing and LAC code merge. For more details, you can connect with Taras and Vinod.

bdenham · 2026-04-20T16:06:10Z

+      >
+          The Storefront Compatibility Package has been updated to include the following changes:
+
+          - **Order Cancellation**: Resolved issues in `requestGuestOrderCancel`, `cancelOrder`, and `confirmCancelOrder` mutations related to order comments in the response.


Suggested change

- **Order Cancellation**: Resolved issues in `requestGuestOrderCancel`, `cancelOrder`, and `confirmCancelOrder` mutations related to order comments in the response.

- **Order Cancellation**: Fixed issues with order comments in the response for the `requestGuestOrderCancel`, `cancelOrder`, and `confirmCancelOrder` mutations.

bdenham · 2026-04-20T16:39:08Z


 - [`updateCustomerAddressV2`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update-address-v2) mutation - Updates a customer’s billing or shipping address based on the provided customer UID.

+- [`exchangeOtpForCustomerToken`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/exchange-otp-customer-token/) mutation - Authenticates admin users for seller-assisted buying using a one-time code and email, and returns the customer token.


Suggested change

- [`exchangeOtpForCustomerToken`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/exchange-otp-customer-token/) mutation - Authenticates admin users for seller-assisted buying using a one-time code and email, and returns the customer token.

- [`exchangeOtpForCustomerToken`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/exchange-otp-customer-token/) mutation - Authenticates admins as customers for seller-assisted buying by exchanging a one-time code and email for a customer token.

@deepak-soni1, in addition to these changelog entries, make sure you submit a PR for the actual documentation.

Alphabetize the mutation. Also, add links to the *V2 documentation, as it now exists.

@bdenham Actually, for LAC, the Guardians team was working on B2B Phase 2 requirements, while the Nestle CDE team was also working on similar functionality. Since the feature overlapped, we decided to move the additional LAC-related code—such as the REST API and the exchangeOtpForCustomerToken mutation—from the ACCS codebase to SCP. As a result, we did not need to create a PR for the documentation, as it already exists.

Ref. -
https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/exchange-otp-customer-token/

@keharper We have alphabetized the mutation, but could you please share any reference or link for the V2 documentation? I wasn’t able to find any relevant reference.

keharper

I don't understand why thie exchangeOtpForCustomerToken mutation is being added here when it already exists in ACCS. Assuming the Login in Customer functionality will eventually be available on Adobe Commerce 2.4.9, the following work needs to be done.

Update the documentation for the exchangeOtpForCustomerToken so that it no longer has a SaaS-only badge. Also add a statement similar to the one in deleteCustomerAddressV2.
Explain how the merchant documentation needs to be updated.

Also, will the exchangeOtpForCustomerToken mutation appear twice in a GraphQL IDE (such as GraphQL Playground) when pointed to an ACCS instance?

keharper · 2026-04-20T17:54:00Z


 - [`updateCustomerAddressV2`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update-address-v2) mutation - Updates a customer’s billing or shipping address based on the provided customer UID.

+- [`exchangeOtpForCustomerToken`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/exchange-otp-customer-token/) mutation - Authenticates admin users for seller-assisted buying using a one-time code and email, and returns the customer token.


Alphabetize the mutation. Also, add links to the *V2 documentation, as it now exists.

keharper · 2026-04-20T18:07:14Z

+      >
+          The Storefront Compatibility Package has been updated to include the following changes:
+
+          - **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.


Add a link to https://experienceleague.adobe.com/en/docs/commerce-admin/customers/customer-accounts/manage/login-as-customer and to the new mutation.

Rewrite this to mention the new mutation before you list the changes to the Customer type.

keharper · 2026-04-20T18:07:55Z

+          The Storefront Compatibility Package has been updated to include the following changes:
+
+          - **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.
+          - **WishList Items**: Resolved an issue with wishlist items in multi-store view scenarios under the same website, wishlist items and items_count are now consistent and properly synchronized.


No captial L in wishlist

keharper · 2026-04-20T18:09:25Z

+
+          - **Login as Customer**: Introduced a “Login as Customer” feature to support seller-assisted buying. This allows admins to generate a one-time login code from the customer view page backend and authenticate as the customer via GraphQL APIs. Added `admin_assistance_actions` to the `Customer` type to track admin-specific activities or logs, and `admin_assisted_order` in the `CustomerOrder` type to indicate orders placed by an admin. Also introduced the `exchangeOtpForCustomerToken` mutation to retrieve a customer token using the one-time code, alongside the existing `generateCustomerToken` mutation.
+          - **WishList Items**: Resolved an issue with wishlist items in multi-store view scenarios under the same website, wishlist items and items_count are now consistent and properly synchronized.
+          - **Cart Items**: Resolved an issue where cart item availability checks were failing for products with "Manage Stock" set to No.


change "display" to "return"

deepak-soni1 · 2026-04-21T06:15:06Z

I don't understand why thie exchangeOtpForCustomerToken mutation is being added here when it already exists in ACCS. Assuming the Login in Customer functionality will eventually be available on Adobe Commerce 2.4.9, the following work needs to be done.

Update the documentation for the exchangeOtpForCustomerToken so that it no longer has a SaaS-only badge. Also add a statement similar to the one in deleteCustomerAddressV2.

Explain how the merchant documentation needs to be updated.

Also, will the exchangeOtpForCustomerToken mutation appear twice in a GraphQL IDE (such as GraphQL Playground) when pointed to an ACCS instance?

Actually, for LAC, the Guardians team was working on B2B Phase 2 requirements, while the Nestle CDE team was also working on similar functionality. Since the feature overlapped, we decided to move the additional LAC-related code—such as the REST API and the exchangeOtpForCustomerToken mutation—from the ACCS codebase to SCP.

Using SCP, it will not be available for PaaS-only users. However, as per the requirements, it will be available for both PaaS + ACO and ACCS, providing flexibility for customers to migrate smoothly from PaaS + ACO to ACCS.

Only users with either an internal (ACCS) or ACO (PaaS + ACO) license, or those with the appropriate availability group access, can download these SCP packages.

As this is not applicable for PaaS-only users, we can skip this -

Update the documentation for the exchangeOtpForCustomerToken so that it no longer has a SaaS-only badge. Also add a statement similar to the one in deleteCustomerAddressV2.

I think we only need to update the screenshots, since we have migrated the LAC code into SCP and already they have updated documentation.

Explain how the merchant documentation needs to be updated.

I believe it will be removed from the ACCS codebase by ACCS team.

Also, will the exchangeOtpForCustomerToken mutation appear twice in a GraphQL IDE (such as GraphQL Playground) when pointed to an ACCS instance?

I will share this PR link with Taras and Vinod to get their input on it.

…osite-commerce-storefront into SCP-4.8.19_SCP-4.7.12

…ite-commerce-storefront into SCP-4.8.19_SCP-4.7.12

Documentation update for SCP-4.8.19 and SCP-4.7.12

2decc65

cod40403 approved these changes Apr 20, 2026

View reviewed changes

Link updated

7b7c839

bdenham requested changes Apr 20, 2026

View reviewed changes

keharper requested changes Apr 20, 2026

View reviewed changes

PR feedback updated

0a2fc2c

deepak-soni1 added 2 commits April 27, 2026 13:15

Merge branch 'april-release' of https://github.com/commerce-docs/micr…

92d3481

…osite-commerce-storefront into SCP-4.8.19_SCP-4.7.12

Documentation update for SCP-4.8.20

0dd9d15

deepak-soni1 changed the title ~~Documentation update for SCP-4.8.19 and SCP-4.7.12~~ Documentation update for SCP-4.8.19, SCP-4.8.20 and SCP-4.7.12 Apr 27, 2026

Base automatically changed from april-release to release April 30, 2026 15:07

deepak-soni1 changed the title ~~Documentation update for SCP-4.8.19, SCP-4.8.20 and SCP-4.7.12~~ Documentation update for SCP-4.8.19, SCP-4.8.20, SCP-4.7.12 and SCP-4.7.13 May 4, 2026

SCP 4.7.13 Release related doc updated

d6512a6

bdenham changed the base branch from release to may-release May 4, 2026 14:21

bdenham added 2 commits May 4, 2026 10:01

Merge branch 'may-release' into SCP-4.8.19_SCP-4.7.12

796db3c

fix merge conflict

5055c1e

keharper approved these changes May 4, 2026

View reviewed changes

bdenham self-requested a review May 4, 2026 17:32

deepak-soni1 added 2 commits May 5, 2026 09:49

Merge branch 'may-release' of https://github.com/commerce-docs/micros…

bc3e8c8

…ite-commerce-storefront into SCP-4.8.19_SCP-4.7.12

Doc updated with missing changes

b506f8c

deepak-soni1 changed the title ~~Documentation update for SCP-4.8.19, SCP-4.8.20, SCP-4.7.12 and SCP-4.7.13~~ Documentation update for SCP and SCP-B2B packages May 5, 2026

deepak-soni1 added 3 commits May 5, 2026 11:08

Doc updated with missing changes

29cc57b

Doc updated with SCP-B2B-1.0.20

a7eafa7

Doc updated with SCP-B2B-1.0.20

f6d923c

	- Cart Items: Resolved an issue where cart item availability checks were failing for products with "Manage Stock" set to No.
	- Cart Items: Fixed cart availability checks for products where "Manage Stock" is disabled. Cart items now correctly display availability status.

	- WishList Items: Resolved an issue with wishlist items in multi-store view scenarios under the same website, wishlist items and items_count are now consistent and properly synchronized.
	- WishList Items: Fixed inconsistencies in wishlist items and item count across multiple store views within the same website. Wishlist data is now properly synchronized.

	- Order Cancellation: Resolved issues in `requestGuestOrderCancel`, `cancelOrder`, and `confirmCancelOrder` mutations related to order comments in the response.
	- Order Cancellation: Fixed issues with order comments in the response for the `requestGuestOrderCancel`, `cancelOrder`, and `confirmCancelOrder` mutations.


		- [`updateCustomerAddressV2`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/update-address-v2) mutation - Updates a customer’s billing or shipping address based on the provided customer UID.

		- [`exchangeOtpForCustomerToken`](https://developer.adobe.com/commerce/webapi/graphql/schema/customer/mutations/exchange-otp-customer-token/) mutation - Authenticates admin users for seller-assisted buying using a one-time code and email, and returns the customer token.

Conversation

deepak-soni1 commented Apr 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

keharper left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

deepak-soni1 commented Apr 21, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

deepak-soni1 commented Apr 20, 2026 •

edited

Loading

keharper left a comment •

edited

Loading