Release notes

Commerce Storefront on Edge Delivery Services now includes B2B drop-in components. The following B2B drop-ins are now available:

• Company management - Enables company profile management and role-based permissions for Adobe Commerce storefronts.

• Company switcher - Provides a UI component for users to switch between multiple companies they are associated with.

• Purchase orders - Manages purchase order workflows, approval rules, and purchase order history for B2B transactions.

• Quote management - Enables negotiable quotes for B2B customers with quote request, negotiation, and approval workflows.

• Requisition lists - Provides tools for creating and managing requisition lists for repeat purchases and bulk ordering.

  note note
  NOTE
  Detailed documentation for the B2B drop-in components will be available when this feature is promoted to Production.

Released the B2B Storefront Compatibility Package. This package enhances the Adobe Commerce B2B GraphQL schema to help improve development on B2B systems.

Resolved an error that could occur when uploading a file to S3.

Resolved a User is not entitled to access this instance error that could occur when logging into the Commerce Admin or accessing the REST API.

Corrected an error that occurred when previewing or queueing a newsletter from the Newsletter Template grid.

Fixed a 404 error that occurred when clicking the Reload Data button on the Admin dashboard.

Resolved an issue where product custom attributes could not be updated through the REST API when AEM Assets integration was enabled and the product had images.

Various performance and optimization improvements.

User management - Changed Product Admin role in the Admin Console to automatically update user access to the Commerce Admin.

Added the ability to upload and retrieve negotiable quote attachments as well as files and images associated with customers and customer addresses to Amazon S3 using presigned URLs in GraphQL and REST. With REST, you can also upload category images.

Added the POST /V1/customers and PUT /V1/customers/{customerId} endpoints to the REST API to create and update customers. These endpoints require admin authorization.

Added the exchangeOtpForCustomerToken mutation, which requires a shopper’s email address and one-time password (OTP), and receives a customer token in exchange. This mutation is typically used in scenarios where a customer needs to authenticate using an OTP sent to their email or phone.

If an address defined in the Store Email Addresses configuration screen in the Admin contains a value that ends with example.com, Commerce does not send emails to this address. Instead, the system logs that the email was not sent.