These release notes for the B2B extension capture additions and fixes that Adobe has added during a release cycle, including:
New features Fixes and improvements Known issues
NOTE
See Product availability for information about versions of the B2B Commerce extension supported for available Adobe Commerce releases.
B2B v1.5.3-beta1
March 10, 2026
Compatible with Adobe Commerce version 2.4.9-beta1.
The B2B v1.5.3-beta1 release includes quality improvements and bug fixes. The release also includes the security fixes documented in Security Bulletin APSB26-05.
Negotiable quote
Negotiable quote checkout with Payflow Pro—Adobe Commerce now successfully places orders when checking out from a negotiable quote using the Payflow Pro credit card payment method. Previously, when B2B features were enabled and a buyer proceeded to checkout from a negotiable quote, selecting Payflow Pro and clicking Place Order caused the page to keep loading indefinitely with no error message, and the order was never created.
Success message after negotiable quote rename—Adobe Commerce now consistently displays a success message after a negotiable quote or quote template is renamed on the storefront. Previously, when a buyer renamed a negotiable quote, the success message would intermittently not appear (often clearing almost immediately), which also caused automated tests that wait for this message to fail even though the rename operation itself succeeded.
Shipping cost in PayPal Express negotiable quote checkout—Adobe Commerce now applies the correct shipping cost when completing a PayPal Express Checkout for an approved negotiable quote. Previously, shipping costs were incorrectly doubled, leading to inflated totals.
Purchase orders
Purchase Order totals with Cross Border Trade—An order now contains correct totals when placed from an existing Purchase Order with Cross Border Trade enabled.
Requisition list
Grouped products in requisition lists with category permissions—Fixed a TypeError that occurred when adding grouped products to a requisition list with category permissions enabled. After the fix, product options are handled safely as arrays, allowing all product types to be added without errors.
Add to Requisition List button on category page—The Add to Requisition List button is now visible on the category page. Previously, the button disappeared when users tried to add a product from the category page.
Requisition List page print option—The Print option on the Requisition List page now works correctly. Previously, clicking Print resulted in the error: An error has happened during application run. See exception log for details.
Requisition list creation with Add Store Code to URLs—Fixed an issue where requisition lists could not be created for products assigned to a new website and source when Add Store Code to URLs is enabled. The problem occurred because the store code was stripped from the API request, causing an unauthorized error. After the fix, the correct store context is preserved and requisition lists are created successfully.
Shared catalog
Shared catalog category unassignment performance—Performance is significantly improved when unassigning categories in a B2B shared catalog. Previously, it took a long time to unassign categories via the REST API.
Product unassignment from Shared Catalog—An Admin can now successfully unassign products from the Shared Catalog. Previously, unassigning products with a large number of long product SKUs from Shared Catalog resulted in an error.
Shared catalog company assignment for restricted admins—Fixed an issue where restricted Admin users encountered an exception when assigning a company to a shared catalog.
Cart and checkout
Checkout redirect after session expiry—Fixed an issue where users were redirected to the My Account login page instead of the checkout login after session expiry, ensuring they are correctly taken to checkout with the login form.
Checkout address validation for REST and GraphQL—Customer address data validation has been improved to be more consistent between REST and GraphQL for checkout.
Framework
Frontend 500 error from cached layout structure—Fixed an issue where a page would return a 500 error due to an incorrect layout structure being cached in the layout.
Commerce styling resources in Community themes—Removed Commerce-only styling resources from Community themes by relocating them to their respective module directories. This prevents unused CSS from being bundled in the Community Edition, which reduces unnecessary payload and eliminates dead style rules while ensuring proper styling when Commerce modules are enabled.
GraphQL
GraphQL error response format—Reverted a previous change that was returning errors in a different format. Now, potential errors are returned in a consistent manner that does not break the GraphQL schema.
B2B v1.5.2-p4
March 10, 2026
[Supported]{class="badge informative" title="Supported"} Adobe Commerce versions 2.4.8-p4, 2.4.7-p9, and 2.4.6-p14 security patch releases. Compatible with Adobe Commerce versions 2.4.7 to 2.4.7-p9, 2.4.6 to 2.4.6-p14.
[Supported]{class="badge informative" title="Supported"} Adobe Commerce versions 2.4.8, 2.4.7-p5 and 2.4.6-p10 security patch releases. Compatible with Adobe Commerce versions 2.4.7 to 2.4.7-p4, 2.4.6 to 2.4.6-p9.
The B2B v1.5.2 release includes quality improvements and bug fixes.
Company management
Administrators can now manage multiple companies from a single account using the storefront company switcher. Key benefits include:
Simplified multi-company management—Administrators can now oversee multiple companies from one user account, eliminating the need to create and manage separate logins for each company.
Efficient company switching—An intuitive interface allows administrators to quickly switch between companies and make updates, improving productivity when managing multiple entities.
Streamlined operations—Regional managers and business leaders can centrally manage all their companies, enabling faster decision-making and smoother business operations.
This enhancement builds on B2B 1.5.0’s multi-company membership capability, which allowed users to belong to multiple companies but did not support admin access across companies. The company switcher eliminates the need for separate admin accounts while maintaining proper access controls and company-specific views.
Company
Fixed an issue where guest customers would see a No such entity with cartId = ? error message when logging in as a company user with products in their shopping cart.
Negotiable quote
The B2B v1.5.2 release includes the following fixes for negotiable quotes:
The Line Item Discount Amount field now validates input to prevent entering negative discount values.
Fixed a user experience issue where long line item notes were truncated and difficult to read for B2B customers.
B2B customers can now specify product quantities using decimal values (such as 1.5 or 2.75) when creating quotes.
Quote template
New ability for B2B buyers and sellers to attach external document links to quote templates. This feature allows linking to documents hosted in services like DocuSign and Adobe Sign directly from quotes, complementing the existing file attachment capability. Key benefits include:
Streamlined collaboration through direct access to critical agreements and contracts
Enhanced transparency with instant access to the latest documentation
Faster quote negotiations by eliminating the need to download and upload files
Flexible document management using external document hosting services
B2B 1.5.1
February 11, 2025
[Supported]{class="badge informative" title="Supported"} Adobe Commerce versions 2.4.7-p4+ and 2.4.6-p9+ security patch releases. Compatible with Adobe Commerce versions 2.4.8-beta1 to 2.4.8-beta2, 2.4.7 to 2.4.7-p3, 2.4.6 to 2.4.6-p8.
The B2B v1.5.1 release includes quality improvements and bug fixes.
Company
If a customer tries to switch companies on the Quote Details page, the system now redirects the customer to an Access Denied page to ensure that a quote created for one company cannot be used to place an order with the prices of another company. Previously, a user could create a quote with the price for one company, and then switch to another company to place an order with different prices.
Line item discounts
Improved system efficiency by addressing a performance degradation observed in the quote recalculation scenario. Previously, two new entities were added to every cart line item which caused a noticeable increase in database requests, leading to slower performance.
Negotiable quote
The system now maintains the position of UI elements when JavaScript validation is applied to the min/max qty fields on the Luma Storefront Quote Template page. Previously, applying JavaScript validation to these fields caused other UI elements on the page to shift.
Shopping cart
Introduced a new shopping cart management system designed to streamline the shopping experience for users managing multiple company accounts. The new system associates shopping carts with individual companies rather than the customer account to streamline the shopping experience and improve the workflow by supporting the following capabilities.
Company-specific carts—Shopping carts are now linked to individual companies to support company-specific pricing and product options.
Seamless switching—Users can easily switch between different company accounts without affecting the contents of each company’s cart.
Contextual Integrity—All cart details remain within the context of the respective company, providing a consistent and reliable shopping experience.
B2B 1.5.0
October 30, 2024
[Supported]{class="badge informative" title="Supported"} Adobe Commerce versions 2.4.7-p3+ and 2.4.6-p8+ security patch releases. Compatible with Adobe Commerce versions 2.4.8-beta1, 2.4.7 to 2.4.7-p2, 2.4.6 to 2.4.6-p7.
Adobe Commerce B2B version 1.5.0 is also compatible with PHP 8.3 and supports the GraphQL Application Server.
The B2B v1.5.0 release includes new features, quality improvements, and bug fixes.
NOTE
Learn about backward-incompatible changes (BICs) introduced in the B2B 1.5.0 release by reviewing the highlights and reference information in the Backward Incompatible Changes topic.
Company management
Company Management—Merchants can now view and manage Adobe Commerce companies as hierarchical organizations by assigning companies to designated parent companies. After a company is assigned to a parent, the parent company administrator can manage the company account. Only authorized Admin users can add and manage company assignments. For details, see Manage company hierarchy.
Add and manage company assignments from the new Company Hierarchy section on the Company Account page in the Admin.
Sort and filter companies by the new Company Type setting. In the companies grid, the Company Type column indicates whether a company is an individual company or part of an organizational hierarchy (parent or child).
Manage company configuration at scale—Quickly change company configuration settings for selected companies using the Change company setting bulk action now available when managing companies from the Companies or Company Hierarchy grid. For example, if you create a new shared catalog for a group of companies, you can change the shared catalog configuration in a single action instead of editing each company individually.
API Developers can use the new Company Relations REST API endpoint /V1/company/{parentId}/relations to create, view, and remove company assignments. See Manage company objects in the Web API Developer Guide.
Company accounts
Multi-company assignment—Simplify company account access for company users by assigning a user to multiple companies. For example, if you have a buyer who orders from multiple company sites, create a single account and assign all companies the buyer works with to that account. Then, the buyer can log in one time, and switch between company accounts by choosing the company from the storefront.
NOTE
A company user can be assigned to multiple companies, but they can be the company administrator for only one company.
Company scope selector—Provides the ability for company users that are assigned to multiple companies to change companies on the storefront. When the scope is switched, the data updates to show the information based on the new company context. For example, if the new company uses a different shared catalog, the company user sees products, prices, and other information based on the new shared catalog. Content related to orders, quotes, quote templates also updates based on the context of the selected company.
NOTE
The shopping cart contents reflect items selected by the current customer. If the customer has an active shopping cart and selects a different company, they are prompted to update the cart to reflect the product assortment, pricing, and promotional discounts based on the new company context. Products that are not available in the catalog associated with the new company are removed from the cart. If the product has a different price or availability, the cart updates to reflect the data available in the context of the selected company.
Company administrators can now add company users from the storefront. Previously, Commerce logged an error when an Admin user tried to add a new user: CRITICAL: Error: Call to a member function __toArray() on null in app/code/Magento/LoginAsCustomerLogging/Observer/LogSaveCustomerObserver.php:123.
Quotes and quote templates
Improvements to quoting capabilities help buyers and sellers manage quotes and quote negotiation more effectively.
Quote templates—Buyers and sellers can now streamline the quote process by creating reusable and customizable quote templates. Using quote templates, the quote negotiation process can be completed once, and buyers can generate pre-approved linked quotes for recurring orders instead of going through the quote negotiation process for each order. Quote templates extend the existing quote functionality by adding the following advanced features:
Order thresholds allow sellers to set minimum and maximum order commitments, ensuring the buyer adheres to agreed-upon purchasing volumes.
Setting minimum and maximum item order quantities provides the buyer with the flexibility to adjust order quantities on the linked quote without requiring a new template or further negotiation.
Track the number of linked quotes generated and successfully completed orders to gain insights into the fulfillment of negotiated agreements.
Linked quotes are pre-approved quotes that the buyer generates from an active quote template to submit recurring orders based on the terms negotiated in the quote template.
Improvements to existing quote capabilities
Updated Commerce Access Control List (ACL) rules allow B2B managers and supervisors to manage quotes and quote templates of subordinate users. Separate rules support granular configuration for view, edit, and delete access.
Save Quote as Draft—When creating a quote request from the shopping cart, buyers can now save the quote as a draft so that they can review and update it before initiating the quote negotiation process with the seller. The draft quote does not have an expiration date. Buyers can review and update draft quotes from the My Quotes section of their account dashboard.
Rename Quote—Buyers can now change a quote name from the Quote detail page by selecting the Rename option. This option is available to authorized buyers when they are editing the quote. Name change events are recorded in the Quote History Log.
Duplicate Quote—Buyers and sellers can now create a new quote by copying an existing quote. A copy is created from the Quote detail view by selecting Create Copy on the Quote detail view in the Admin or the Storefront.
Move quote item to requisition list—Buyers now have the flexibility to remove products from a quote and save them to a requisition list if they decide not to include them in the quote negotiation process.
Remove multiple products from a quote—On quotes with a large number of products, buyers can now remove multiple products from the quote by selecting them one at a time and using the Remove option from the Actions control on the Quote detail page. In previous releases, a buyer had to delete products one at a time.
Line item discount locking—During quote negotiation, sellers can use line item discount locking for more flexibility when applying discounts during the quote negotiation process. For example, a Seller can apply a special line item discount to an item and lock the item to prevent further discounting. When an item is locked, the item price cannot be updated when a quote-level discount is applied. See Initiate quote for a buyer.
Fixes for existing quote capabilities
Merchants clicking the Print button in the Quote detail view in the Admin are now prompted to save the quote as a PDF. Previously, merchants were redirected to a page that contained quote details.
Previously, when sending a customer quote with 0 percentage and changing quantity, the Admin threw an exception but saved the quantity. After this fix, a proper exception with a message is thrown for the 0% case.
During quote negotiation, a seller can now specify a 0% discount in the Negotiated Quote quote discount field and send the quote back to the buyer. Previously, if the seller entered a 0% discount and sent the quote back to the buyer, the Admin returned an Exception occurred during quote sending error message.
ReCaptcha validation now works correctly during the checkout process for a B2B quote when ReCaptcha V3 is configured for storefront checkout. Previously, the validation failed with a recaptcha validation failed, please try again error message.
Purchase orders
Purchase orders can no longer be placed by a user associated with the company after the company has been blocked. Previously, a user associated with the company could place purchase orders when the company was blocked.
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Added compatibility with Adobe Commerce 2.4.7-p2+ and 2.4.6-p7+ security patch releases.
Includes the security fixes documented in Security Bulletin APSB24-73.
IMPORTANT
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
Added compatibility with Adobe Commerce 2.4.7-p1+ and 2.4.6-p6+ security patch releases.
IMPORTANT
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with the Adobe Commerce B2B release. Additionally, the B2B 1.4.2+ release does not support the GraphQL Application Server.
B2B v1.4.2
October 10, 2023
[Supported]{class="badge informative" title="Supported"} Adobe Commerce version 2.4.7 and version from 2.4.6 to 2.4.6-p5.
The B2B v1.4.2 release includes quality improvements and bug fixes.
If a Seller creates a buyer quote that includes a product SKU not available in the shared catalog associated with the buyer company, the system displays the error message The SKU you entered is not available in the shared catalog. Please check the SKU and try again. The Seller cannot save the quote until they remove the product that is not available. Previously, the quote was saved with the unavailable SKU included, and the quote failed to load on the storefront.
IMPORTANT
Adobe Commerce B2B version 1.4.2+ is compatible with PHP 8.2. If you upgrade the Commerce instance to version 2.4.7+, ensure that the instance uses PHP version 8.2 to maintain compatibility with Adobe Commerce B2B release. Additionally, B2B 1.4.2+ does not currently support the GraphQL Application Server.
The B2B v1.4.1 release includes quality improvements and bug fixes.
Purchase orders can no longer be placed by a user associated with the company after the company has been blocked. Previously, a user associated with the company could place purchase orders when the company was blocked.
Product backordered status is now displayed correctly on the storefront. Previously, products that were available for shipment were incorrectly identified as backordered.
If the company registration form includes a customer file type attribute, the file uploaded during the registration process is now included in the account information for the Company Administrator after the company is created. Previously, the attachment was missing.
The swatch selector for a configurable product is now displayed as expected in the requisition list item configuration page. Previously, the swatch selector was displayed as a dropdown field in the requisition list item configuration page.
When using the Company GraphQL query to return company details, results are now returned successfully without error.
This release includes new capabilities and enhancements for B2B negotiable quotes and multiple bug fixes.
Added compatibility with Adobe Commerce 2.4.7-beta1.
Seller initiated quotes—Sellers can now initiate a quote for a buyer directly from the Quote and Customer grids in the Admin. This capability streamlines the quote process and reduces complexity for customers. If a customer has not initiated an order, a seller can quickly create a quote on behalf of the customer and start the negotiation process. Previously, quotes could only be created from the storefront by the buyer, or by a seller logged in as the customer.
Line item discounts and negotiation— Within a quote, B2B buyers and sellers can now negotiate at the line item level, applying discounts and exchanging notes until an agreement is reached. Note creation and updates are included in the line item and quote history to track communication. Previously, buyers and sellers could only exchange notes and apply discounts at the quote level.
Adobe Commerce now displays correct details during payment when the Purchase Orders option is enabled and a virtual quote that was created with the PayPal payment option has been selected. Previously, totals were displayed as zero under these conditions.
Validation errors no longer occur when you try to save a company with a credit limit that exceeds 999. Previously, for company credit limits greater than 999, Adobe Commerce inserted a comma separator, which caused a validation error that prevented updates from being saved.
The selected shipping address now remains unchanged when you place an order with a negotiable quote. Previously, when you placed an order, the selected shipping address was changed to the default shipping address.
In the Store Configuration settings for B2B Features, the Enable Shared Catalog direct products price assigning field is now disabled automatically. On the storefront, it is hidden when the Enable Company setting or Enable Shared Catalog setting is set to No.
When creating a company account from the storefront, Commerce now validates the email address before processing the company registration. If the email address is invalid, the operation fails and no account updates are processed. Previously, a customer account was created even if the request to create a company account failed because of an invalid email address.
Product SKUs that include double quotation marks in the Shared Catalog and pricing structure no longer cause errors in the Admin.
Updated the Varnish configuration for the Commerce application to prevent Guest users from seeing data from other customer groups.
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires magento/extension-b2b 1.4.0 -> satisfiable by magento/extension-b2b[1.4.0].
- magento/extension-b2b 1.4.0 requires magento/security-package-b2b 1.0.4-beta1 -> found magento/security-package-b2b[1.0.4-beta1] but it does not match your minimum-stability.
Installation failed, reverting ./composer.json and ./composer.lock to their original content.
Released B2B version 1.3.5-p2 to support compatibility with Adobe Commerce 2.4.6-p2.
Released B2B version 1.3.5-p1 to support compatibility with Adobe Commerce 2.4.6-p1.
NOTE
After you upgrade Commerce from 2.4.6 to the latest release, make sure to update to the supported B2B 1.3.5 patch release. Or, upgrade the B2B extension from version 1.3.5 to version 1.4.0 or later to get the latest features.
Added support for Adobe Commerce 2.4.6.
Adobe Commerce now displays correct details during payment when the Purchase Orders option is enabled and a virtual quote that was created with the PayPal payment option has been selected. Previously, totals were displayed as zero under these conditions.
The list of customer groups for the Allow Browsing Category setting no longer contains customer groups that are related to shared catalogs.
The Tax/VAT Number customer attribute now works as expected with company admin accounts on both the Admin and storefront. Custom Tax/VAT attributes are no longer required to create a company account. Previously, when a merchant created a company account with a custom Tax/VAT attribute, Adobe Commerce threw a validation error on both the storefront and Admin.
Disabling the shared catalog feature on a specific scope now works correctly. Previously, Adobe Commerce set an invalid scope when a merchant saved shared catalog configuration.
Admin users can now save customer custom attribute values for company users. Previously, customer custom attributes for company users could not be saved.
Performance issues are resolved with the validation of company permissions provided through GraphQL when many company permissions are already assigned.
Adobe Commerce no longer throws an error on the cart page when Quick Order is used to add a product in a quantity that exceeds available inventory.
The performance of SELECT company permissions operations has improved.
Category queries now return product prices according to store configuration settings when there are no category permissions explicitly set on the category being queried.
The Place Order button now works as expected when completing a purchase with an approved quote request. Issues with the negotiable quote negotiableQuoteCheckoutSessionPlugin plugin have been resolved.
