Adobe Commerce B2B release notes

February 12, 2025

CREATED FOR:

  • Beginner
  • Intermediate
  • Admin
  • Leader
  • User

These release notes for the B2B extension capture additions and fixes that Adobe has added during a release cycle, including:

New New features
Fixed issue Fixes and improvements
Known issue Known issues

NOTE
See Product availability for information about versions of the B2B Commerce extension supported for available Adobe Commerce releases.

B2B 1.5.1

February 11, 2025

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.9-p8

The B2B v1.5.1 release includes quality improvements and bug fixes.

Company

Fixed issue 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

Fixed issue 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

Fixed issue 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

Fixed issue 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 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

New 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 organizational hierarchy (parent or child).

New 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.

New 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

New Multi-company assignment—Simplify company account access for company users by assigning a user to multiple companies. For example, if you have a buyer that 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.

New Company scope selector—Provides 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.

Fixed issue 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.

New 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 adhere 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.

New 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 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 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.

Fixed issue 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 throws an exception but saved the quantity. After this fix applies, for the 0 percentage proper exception with a message will be thrown.

  • 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

Fixed issue 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.

B2B v1.4.2-p4

February 11, 2025

Supported Adobe Commerce 2.4.7-p4+ and 2.4.6-p9+ security patch releases.

New Added compatibility with Adobe Commerce 2.4.7-p4+ and 2.4.6-p9+ security patch releases.

Fixed issue Includes the security fixes documented in Security Bulletin APSB25-08.

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-p3

October 8, 2024

Supported Adobe Commerce 2.4.7-p3+ and 2.4.6-p8+ security patch releases.

New Added compatibility with Adobe Commerce 2.4.7-p3+ and 2.4.6-p8+ security patch releases.

Fixed issue 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.

B2B v1.4.2-p2

Supported Adobe Commerce 2.4.7-p2+ and 2.4.6-p7+ security patch releases.

New Added compatibility with Adobe Commerce 2.4.7-p2+ and 2.4.6-p7+ security patch releases.

Fixed issue Includes the Security fixes documented in Security Bulletin xxxx.

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, the B2B 1.4.2+ release does not support the GraphQL Application Server.

B2B v1.4.2-p1

August 9, 2024

Supported Adobe Commerce 2.4.7-p1+ and 2.4.6-p6+ security patch releases.

New 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 Adobe Commerce B2B release. Additionally, B2B 1.4.2+ does not currently support the GraphQL Application Server.

B2B v1.4.2

October 10, 2023

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.

Fixed issue 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.

B2B v1.4.1

August 7, 2023

Supported Adobe Commerce 2.4.6-p2. Compatible with Adobe Commerce 2.4.7-beta1.

The B2B v1.4.1 release includes quality improvements and bug fixes.

Fixed issue 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.

Fixed issue Product backordered status is now displayed correctly on the storefront. Previously, products that were available for shipment were incorrectly identified as backordered.

Fixed issue 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.

Fixed issue 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.

Fixed issue When using the Company GraphQL query to return company details, results are now returned successfully without error.

B2B v1.4.0

June 13, 2023

Supported Adobe Commerce 2.4.6-p1. Compatible with Adobe Commerce 2.4.7-beta1

This release includes new capabilities and enhancements for B2B negotiable quotes and multiple bug fixes.

New Added compatibility with Adobe Commerce 2.4.7-beta1.

New 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.

New 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.

Fixed issue 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.

Fixed issue 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.

Fixed issue 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.

Fixed issue 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.

Fixed issue 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.

Fixed issue Product SKUs that include double quotation marks in the Shared Catalog and pricing structure no longer cause errors in the Admin.

Fixed issue Updated the Varnish configuration for the Commerce application to prevent Guest users from seeing data from other customer groups.