Skip to content

USF-3795: Seller assisted buying#922

Merged
bdenham merged 6 commits into
may-releasefrom
seller-assisted-buying
Jun 8, 2026
Merged

USF-3795: Seller assisted buying#922
bdenham merged 6 commits into
may-releasefrom
seller-assisted-buying

Conversation

@bdenham
Copy link
Copy Markdown
Collaborator

@bdenham bdenham commented Jun 6, 2026

Purpose of this pull request

This pull request adds documentation for the seller-assisted buying feature, which lets a store administrator log in as a customer and act on their behalf (browse, build a cart, and place orders). Because the feature spans several drop-ins rather than belonging to one, it adds a new Storefront Features overview page that explains the end-to-end flow and links to where each part is documented. Naming follows Adobe's sentence-case capitalization rule (seller-assisted buying), with the hyphenated compound modifier.

Associated JIRA ticket

USF-3795

Staging preview

https://commerce-docs.github.io/microsite-commerce-storefront/dropins/user-account/containers/seller-assisted-buying/

Affected pages

  • Storefront Features > Seller-assisted buying (new): /storefront-features/seller-assisted-buying/
  • User Account > Containers > SellerAssistedBuyingSettings (new)
  • User Account > Containers > SellerAssistedBuyingActivity (new)
  • User Account > Containers (index), Orders list, Dictionary, Functions, Styles, Index
  • User Auth > Containers > SignUp, Slots
  • Order > Containers > OrderStatus, Dictionary, Index

Links to source code

  • adobe-commerce/storefront-auth (admin session cookie + JWT handling)
  • hlxsites/aem-boilerplate-commerce PR #1283 (session banner and account blocks)

@bdenham bdenham self-assigned this Jun 6, 2026
@bdenham bdenham added major-update Significant original updates to existing content new-topic A major update published as an entirely new document labels Jun 6, 2026
@bdenham bdenham changed the base branch from release to may-release June 6, 2026 22:46
Comment on lines +42 to +50
Once you have generated a one-time code (OTC) from the customer's edit page in the Admin:

<Steps>

1. Go to your storefront sign-in page.

1. Enter the customer's email address and paste the OTC as the password, then sign in.

The session banner appears at the top of every page. You are now browsing as the customer.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation - storefront-features/seller-assisted-buying.mdx uses OTP (one-time password) while merchants/blocks/seller-assisted-buying.mdx uses OTC (one-time code). For consistency, it would be better to standardize on OTP throughout, as that's what appears in the technical flow description and is more commonly used in authentication contexts.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops. Yeah, I missed that one. Thanks.

Copy link
Copy Markdown
Contributor

@KostiantynFandeliuk KostiantynFandeliuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thank you.

@bdenham bdenham merged commit 972559e into may-release Jun 8, 2026
5 checks passed
@bdenham bdenham deleted the seller-assisted-buying branch June 8, 2026 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

major-update Significant original updates to existing content new-topic A major update published as an entirely new document

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants