Fixed issue The performance of the sharedCatalogUpdateCategoryPermissions consumer has been improved. After creating a shared catalog, the catalog permission indexer now uses only the customer group ID from the shared catalog, not all customer groups.

Fixed issue Custom customer address attribute fields that are associated with a shopper’s non-default address are now saved as expected in the storefront checkout workflow.

Fixed issue Orders for products that belong to a store’s default shared catalog can now be placed for shoppers through the Admin REST API (rest/V1/carts/{<CART_ID>/items) as expected. Adobe Commerce now checks if the product was assigned to a public catalog before shared catalog permissions validation in \Magento\SharedCatalog\Plugin\Quote\Api\ValidateAddProductToCartPlugin::beforeSave. Previously, Adobe Commerce did not add the product to the shopper’s cart and threw this error: No such shared catalog entity.

Fixed issue Adobe Commerce now sends new company user registration emails from the Adobe Commerce store’s address. Previously, this email was sent from the company administrator’s address.

Fixed issue Adobe Commerce now checks custom attributes for duplication of reserved company attribute names before permitting a merchant to save a new attribute.

Fixed issue The credit_history query now returns the specified company’s credit history for both the originally allocated amount and the purchased amount. Previously, this query returned an error.

Fixed issue The Company and Job Title fields on the Edit Account Information page are no longer editable.

Known issues

  • B2B buyers can use online payment methods to bypass the usual purchase order flow. This scenario can occur if the buyer can reduce their entire checkout total to a 0 — for example, by a promo code or gift card — and then remove the code or gift card. Even under those conditions, Adobe Commerce still places the order for the correct amount based on the prices of the items in their assigned catalog. Workaround: Disable gift cards and coupon codes when online payment methods are enabled for purchase order approval.

  • Buyers are redirected to the shopping cart when trying to place an order from a purchase order using PayPal Express Checkout when In-Context Mode is disabled.

  • Adobe Commerce sometimes displays a 404 error when a buyer creates a purchase order and then navigates to the checkout page. This error occurs when a buyer has previously created a different purchase order with an online payment method before navigating to the checkout page without completing the previous purchase. The buyer can still place the purchase order. Workaround: None.

  • Discounts for a specific payment method persist during checkout for a purchase order even when the buyer changes their payment method during final checkout. As a result, customers can receive a discount that they are not entitled to. This issue occurs because a cart rule for the original payment method is still applied despite the change in payment method. Workaround: None. See the Adobe Commerce 2.4.2 B2B known issue: discount remains for online Purchase Orders after payment method is changed Knowledge Base article.

  • The deleteRequisitionListOutput query returns details about the deleted requisition list instead of the remaining requisition lists.

B2B v1.3.0

October 15, 2020

[Supported]{class="badge informative" title="Supported"} Adobe Commerce 2.4.0 and newer versions

This release includes improvements to order approvals, shipping methods, shopping cart, and logging of Admin actions.

New Added support for Adobe Commerce 2.4.1.

New B2B order approvals have been enhanced to improve usability and to allow for bulk actions on purchase orders.

New B2B merchants can now control shipping methods that are offered to each Company.

New Merchants can now allow users to clear the contents of their shopping cart in a single action and can configure this ability independently on each website.

New B2B buyers can now add individual items or the entire contents of their shopping cart directly to a requisition list.

New B2B merchants can create orders from the Admin on behalf of customers using Payment on Account as the payment method.

New Merchants can now directly view all quotes associated with a user from the customer’s detail page.

New Merchants can now filter the Customers Now Online grid by Company.

New Admins can now filter customers in the Admin by Sales Rep.

New To reduce creation of fraudulent or spam accounts, merchants can now enable Google reCAPTCHA on the New Company Request form on the storefront.

New Admin actions taken in the Company modules are now logged in the Admin Actions Log. Actions are logged from all relevant company modules: Company, NegotiableQuote, CompanyCredit, SharedCatalog.

Fixed issue Adobe Commerce no longer displays the Delete customer button on the Customers page when the logged-in administrator does not have rights to delete customers in deployments where B2B is installed.

Fixed issue Customer group is no longer changed automatically for a customer who is assigned to a Company when you edit the customer on the Customer grid.

Fixed issue When a merchant creates a shared catalog, permissions are now automatically set to Allow for the Display Product Prices and Add to Cart features in categories when the customer group is assigned this access in catalog permission settings. Previously, these settings were automatically set to Deny even when catalog permissions were set to Allow.

Fixed issue Shared catalog category permissions are no longer overwritten when a product is edited from the product edit page.

Fixed issue Adobe Commerce now sends an email notification confirming that a customer has permission to exceed the designated credit limit when a merchant enables the Allow To Exceed Credit Limit setting. Previously, the notification email sent by Adobe Commerce indicated that the customer did not have permission to exceed the limit.

Fixed issue The HTML container that surrounds product price on requisition lists is now rendered correctly for the children of bundled products.

Fixed issue Merchants can now designate the language in which company user email is sent when creating a company in multi-language deployments. Previously, the drop-down menu that enables merchants to select the appropriate store view and language was not displayed.

Fixed issue Custom customer address attributes fields are now displayed as expected in the storefront checkout workflow.

Fixed issue The B2B Features configuration tab now opens correctly.

Fixed issue Guests can now use QuickOrder to add products to their cart and then successfully remove items. Previously, when a shopper used QuickOrder to add multiple products to their cart, and then removed a product, the product was not removed.

Fixed issue A company can now be updated using the REST API PUT /V1/company/:companyId request without specifying the region_id when state is configured as not required. Previously, even though region_id was not required, Adobe Commerce threw an error if it was not specified.

Fixed issue When you create or update a B2B Company using the REST API (http://magento.local/rest/V1/company/2, where 2 represents the company ID), the response now includes the settings for applicable_payment_method or available_payment_methods as expected.

Fixed issue Adobe Commerce no longer displays a 404 page when a merchant uses the Enter button instead of clicking the Save button when creating a requisition list on the storefront.

Fixed issue Category permissions no longer change when a new product is assigned to a public shared catalog. Previously, category permissions were duplicated.

Fixed issue The REST API endpoint PUT rest/default/V1/company/{id}, which is used to update Company email, is no longer case-sensitive.

Fixed issue Disabling reward modules no longer affects B2B features on customer accounts. Previously, when reward modules were disabled, the following B2B-related tabs were not displayed: Company Profile, Company Users, and Roles and Permissions.

Fixed issue Adobe Commerce now uses the correct sender name on email notifications when changes are made to company accounts. Previously, Adobe Commerce used the general contact sender name defined in the default scope for all emails.

Fixed issue You can now successfully implement multishipping for orders that contain both physical and virtual products.

Fixed issue Merchants can now create company users from the Company Users section in My Account and Company Structure pages when Access Restriction is enabled and Restriction Mode is set to Sales: Login Only. Previously, Adobe Commerce threw this error when a merchant tried to create a user: Can not register new customer due to restrictions are enabled.

Fixed issue Adobe Commerce no longer resets a customer’s customer group to the default when a customer saves their account information.

Fixed issue Adobe Commerce no longer throws a fatal error when an administrator assigns a customer who has an active shopping cart to a customer group.

Fixed issue Adobe Commerce now provides an addToCart DataLayer event for Quick Order and Requisition lists pages.

Fixed issue Notification emails that are sent to sales representatives assigned to a company now include the assigned corporate logo. Previously, the notification email included the default LUMA logo, not the uploaded corporate logo.

Fixed issue A requisition list now includes all grouped products and quantities that have been added to the list. Previously, when a merchant navigated to a requisition list after adding products to it from a product detail page, Adobe Commerce displayed this error: 1 product(s) require your attention - Options were updated. Please review available configurations.

Fixed issue The products query now returns an accurate total_count field when shared catalog is enabled.

Fixed issue The Company Configuration and Create Company pages now work as expected after you disable an online shipping method. Verification has been added to prevent the attempted processing of disabled Shipping modules. Previously, Adobe Commerce displayed this error: Type Error occurred when creating object: Magento\CompanyShipping\Model\Source\ShippingMethod, Too few arguments to function Magento\CompanyShipping\Model\Source\ShippingMethod::__construct(), 1 passed in /var/www/html/elmtup/vendor/magento/framework/ObjectManager/Factory/AbstractFactory.php on line 121 and exactly 2 expected.

Fixed issue Integration test memory consumption has been reduced, which improves test performance and reduces the time required for test completion.

B2B v1.2.0

July 28, 2020

[Supported]{class="badge informative" title="Supported"} Adobe Commerce 2.4.0 and newer versions

New Added support for Adobe Commerce 2.4.0.

New Storefront Order Search, with thanks for the contribution by Marek Mularczyk from Divante and community members.

New Purchase Orders are enhanced and rewritten. They are now included by default in Adobe Commerce.

New Purchase Order Approval Rules have been implemented. These rules allow users to control the Purchase Order workflow by creating purchasing rules for orders.

New Login as Customer is now included by default in Adobe Commerce. This feature allows site employees to assist customers by logging in as the customer to see what they see.

Fixed issue Attribute aggregations are now working correctly for Layered Navigation with Elasticsearch

Fixed issue Searching orders by special characters is now working properly.

Fixed issue Clicking the Clear All Button now expands all the filters, rather than collapsing them.

Fixed issue Product SKU/Name is now included in the Order History search filter summary.

Fixed issue Sorting Indicator is now displayed properly in the My Purchase Orders Grid.

Fixed issue Now, you can click the Approve, Cancel, Reject, and Purchase Order buttons only once. Previously, you could click the button multiple times.

Fixed issue The Purchase Order Approve, Reject, Cancel, and Validate buttons now render correctly on mobile devices.

Fixed issue Previously, approving a Purchase Order with a discount that has expired placed the order at the full amount and did not update the Purchase Order total. Now, the Purchase Order total is updated to show the correct total.

Fixed issue An issue was introduced in 2.3.4 where custom extension attributes would not be copied from the Customer Address to the Quote Address. This issue has been fixed.

Fixed issue With B2B installed, a SQL error would appear when assigning categories to shared catalogs. This issue has been fixed.

Fixed issue Due to an incorrect variable type value, admins could not add configurable products to an order. The option dropdowns would not populate. This feature now works properly.

Fixed issue Previously, when editing Category Permissions for the Not Logged In group, an error would occur when saving the changes. This issue has been fixed.

Fixed issue A fix is added to allow store administrators to add products to an order that are not in the shared catalog. Previously, an error message would appear when adding an item not in the catalog.

Fixed issue [PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."} Previously, after running the command php bin/magento indexer:set-dimensions-mode catalog_product_price website and then trying to create a shared catalog, an error would occur. This issue has been fixed.

Fixed issue When adding a company and assigning the company administrator to a non-default website, the wrong site ID was sent, causing an error. This issue has been fixed.

Fixed issue Previously, after a customer was moved to another customer group, adding a product to an order using Quick Order would fail with an error. This issue has been fixed.

Fixed issue Previously, when attempting to check out using the WebAPI with a B2B quote, an incorrect value was sent to the API, causing an error to occur. This issue has been fixed.

Fixed issue Previously, when setting a company to “Active” via the API, an error would occur. This issue has now been fixed.

Fixed issue Due to an unneeded form tag, the order page automatically refreshed when you pressed Enter after changing a proposed shipping charge. This issue has been fixed.

Fixed issue Previously, when setting a product display limit on a catalog page and that limit was less than the number of total products, an error occurred. That feature now works as expected.

Fixed issue Previously, when changing the admin of a company, the original admin address would be copied to the new admin, giving them two addresses. Now, only the correct address is added.

Fixed issue Previously, using the API to save a quote item when backorder is set to “Allowed and Notify Customer” would fail. “Allowed and Notify Customer” would fail. This API call now works as expected.

Fixed issue The Fixed Product Tax is now displayed on the Quotes detail page.

Fixed issue Previously, clicking an attachment in the Comments tab of the My Quotes page would fail to download the file. This behavior now works as expected.

Known issues

  • Adobe Commerce throws an exception during upgrade to B2B 1.2.0 in a multi-website deployment. When setup:upgrade runs, this error occurs on the PurchaseOrder module: Module Magento_PurchaseOrder: Unable to apply data patch Magento\PurchaseOrder\Setup\Patch\Data\InitPurchaseOrderSalesSequence for moduleMagento_PurchaseOrder. Workaround: Install the B2B-716 Add NonTransactionableInterface interface to the InitPurchaseOrderSalesSequence data patch hotfix, which is now available from the My Account > Downloads section of magento.com.
  • If a discount code expires before a Purchase Order (PO) is approved, the PO continues to display the discounted amount, but once the PO is approved, the order is placed at the non-discounted total. Workaround: Install the B2B-709 Purchase Order Discount patch hotfix for this issue, which is now available from the My Account > Downloads section of magento.com.
  • If items in a purchase order are out of stock, or of insufficient quantity when the purchase order is converted into an actual order, an error occurs. If backorders are enabled, the order is processed normally.
recommendation-more-help