Adobe Commerce now sends company emails from the correct from email address and scope. Previously, Adobe Commerce did not consider website scope when sending company credit assignment or update email.
Quick Order
Creating an order using Quick Order from a CSV file now works as expected with nonexistent SKUs.
Using Quick Order to search on multiple SKUs now works as expected. Previously, results included duplicate entries.
The Added Product list display now treats SKUs entered in lowercase and uppercase the same when you use SKUs to select multiple products during Quick Order.
Using Quick Order now adds products in the quantity specified by the shopper. Previously, Adobe Commerce added one product only even when shopper-specified quantities exceed one.
The Quick Order autocomplete feature now works with partial SKUs.
Adobe Commerce now displays products that have been configured as Not visible individually on the Quick Order page’s auto-suggest list and search results.
Shoppers can now use the Quick Order form to add multiple products by SKUs that include upper-case characters. Previously, only the first product was added.
Negotiable quote
Shoppers are now redirected to the negotiable quote page after pasting the link to a negotiable quote in the URL field and successfully logging in. Previously, shoppers were redirected to the My Account page.
Reordering now works as expected for orders that contain a product with a Date Customizable Option for a customer account that was created during checkout. Previously, Adobe Commerce did not process the reorder and displayed this error: The product has required options. Enter the options and try again.
The shipping address for a negotiable quote is no longer editable during checkout when the Purchase Order module is disabled. This behavior resulted from a previous fix in which isQuoteAddressLocked was removed from the negotiable quote checkout renderer.
Merchants can now add products to a negotiable quote from the Admin.
Purchase orders
Adobe Commerce now displays an informative error message as expected when you place a purchase order using PayPal Express Checkout when the Name Prefix attribute is set to required. Previously, Adobe Commerce did not place the order or display an error message.
The UI component for the billing address in the Purchase Order module now uses quote address correctly when Google Tag Manager is enabled. Previously, a JavaScript error occurred on the payment page.
Requisition lists
Merchants can now use the POST rest/all/V1/requisition_lists endpoint to create a requisition list for a customer. Previously, Adobe Commerce threw this 400 error when you tried to create a requisition list: Could not save Requisition List.
The Add to Requisition List button now appears for a shopping cart’s in-stock products when the cart also contains out-of-stock products. Previously, if a cart contained two products, one of which was out-of-stock, the Add to Requisition List button did not appear for either products.
You can now use the REST API to add a product to a requisition list.
Requisition list Latest Activity Date values now adhere to locale format.
Adobe Commerce no longer throws a fatal error when you edit a bundle product from a requisition list.
Adobe Commerce now displays the correct product price when you add a product with a customizable option (File) to a wish list from a requisition list. The link to the uploaded file is also visible as expected. Previously, Adobe Commerce displayed incorrect product prices and did not display the link to the file.
Products with a customizable option (File) can now be added to a shopping cart from a requisition list.
Shared catalog
An administrator with a role limited to a specific website can now create, view, and edit a shared catalog. Previously, Adobe Commerce threw a fatal error when an administrator with a limited role tried to create a shared catalog.
Layered navigation results now include an accurate count of products with filtered attributes, and shoppers can now apply multiple filters. Previously, only one filter could be applied, and Adobe Commerce displayed an inaccurate product count in layered navigation.
Adobe Commerce now correctly displays product counts in layered navigation filters in search results. Previously, a plugin for the Search Results page did not use ElasticSearch but issued a new query to the database.
Adobe Commerce no longer deletes tier prices when a merchant deletes all products from a default shared catalog.
Filters are now filtered by the current category and displayed correctly on all pages when shared catalogs are enabled. Previously, filters were wrongly calculated for the current page only and were not filtered by the current category.
The GraphQL products query no longer returns a product’s price range and category for products that are not assigned to a shared catalog when shared catalog is enabled. Previously, the query returned the product’s aggregations, even though the product itself was not returned in the items array.
B2B v1.3.1
February 9, 2021
[Supported]{class="badge informative" title="Supported"} Adobe Commerce 2.4.0 and newer versions
Added support for Adobe Commerce 2.4.2.
Online payment methods are now supported for purchase orders.
Adding a configurable product to the shopping cart directly from a requisition list when this product was used in a prior order no longer returns a system error.
Adobe Commerce now displays the Requires My Approval tab correctly for purchase orders when a split database configuration is deployed.
Adobe Commerce now displays details about bundle products and gift card when you view purchase orders.
Shoppers are now redirected as expected after logging into their account while browsing in a store where Website Restriction is enabled and Restriction Mode is set to Private Sales: Login Only. Previously, shoppers were redirected to the store home page.
Order history now loads as expected in a company administrator’s account dashboard page in deployments with a B2B company hierarchy that contains many customers (greater than 13000). Previously, order history loaded slowly or not at all, and Adobe Commerce displayed a 503 error.
Adobe Commerce no longer displays multiple identical warning messages when you add an unconfigured product with customizable options to a Requisition List from a Category page.
New and duplicated products are now visible as expected on the category page when B2B shared catalogs are enabled.
Adobe Commerce now maintains the correct store_id that is associated with a company administrator when the customer group for a company is updated. Previously, the store_id changed to the default store when the group was updated.
Adobe Commerce now saves a grouped product to a requisition list as a list of simple products in the same way as it adds a grouped product to a shopping cart. Previously, due to how Adobe Commerce saved grouped products, the link for a grouped product from the requisition list always redirected to simple products and not to the grouped product.
You can now filter orders by the Company Name field when exporting order information in CSV format. Previously, Adobe Commerce logged an error in var/export/{file-id}.
Adobe Commerce now displays the Create Requisition List popup as expected when you select the Create New Requisition List tab on the storefront.
Requisition lists now include 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.
The correct store view is now associated with the relevant website when you create a company in a multi-site deployment. Previously, you could not create a company, and Adobe Commerce displayed this error: The store view is not in the associated website.
Ordering products by SKU using Quick Order no longer results in duplicate product quantities in the CSV file.
The Add to Cart button is no longer blocked when the Enter Multiple SKUs section of the Quick Order page contains an empty value. Instead, Adobe Commerce now displays a message prompting you to enter valid SKUs.
Adobe Commerce now displays this message on the product page when you submit a product review from a requisition list: You submitted your review for moderation. The review also appears on the Pending Reviews page (Admin Marketing > Pending Reviews). Previously, although Adobe Commerce added the review to the list of pending reviews, it threw a 404 error on the product page.
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.
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.
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.
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.
Adobe Commerce now checks custom attributes for duplication of reserved company attribute names before permitting a merchant to save a new attribute.
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.
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. Work around: 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. Work around: None. See the Adobe Commerce 2.4.2 B2B known issue: discount remains for online Purchase Orders after payment method is changedKnowledge 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.
Added support for Adobe Commerce 2.4.1.
B2B order approvals have been enhanced to improve usability and to allow for bulk actions on purchase orders.
B2B merchants can now control shipping methods that are offered to each Company.
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
B2B buyers can now add individual items or the entire contents of their shopping cart directly to a requisition list.
B2B merchants can create orders from the Admin on behalf of customers using Payment on Account as the payment method.
Merchants can now directly view all quotes associated with a user from the customer’s detail page.
Merchants can now filter the Customers Now Online grid by Company.
Admins can now filter customers in the Admin by Sales Rep.
To reduce creation of fraudulent or spam accounts, merchants can now enable Google reCAPTCHA on the New Company Request form on the storefront.
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.
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.
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.
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.
Shared catalog category permissions are no longer overwritten when a product is edited from the product edit page.
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.
The HTML container that surrounds product price on requisition lists is now rendered correctly for the children of bundled products.
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 the enables merchants to select the appropriate store view and language was not displayed.
Custom customer address attributes fields are now displayed as expected in the storefront checkout workflow.
The B2B Features configuration tab now opens correctly. 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.
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.
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.
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.
Category permissions no longer change when a new product is assigned to a public shared catalog. Previously, category permissions were duplicated.
The REST API endpoint PUT rest/default/V1/company/{id}, which is used to update Company email, is no longer case-sensitive.
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.
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.
You can now successfully implement multishipping for orders that contain both physical and virtual products.
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.
Adobe Commerce no longer resets a customer’s customer group to the default when a customer saves their account information.
Adobe Commerce no longer throws a fatal error when an administrator assigns a customer who has an active shopping cart to a customer group.
Adobe Commerce now provides an addToCart DataLayer event for Quick Order and Requisition lists pages.
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.
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.
The products query now returns an accurate total_count field when shared catalog is enabled.
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.
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
Added support for Adobe Commerce 2.4.0.
Storefront Order Search, with added thanks for contribution by Marek Mularczyk from Divante and community members.
Purchase Orders are enhanced and rewritten. They are now included by default in Adobe Commerce.
Purchase Order Approval Rules have been implemented. These rules allow users to control the Purchase Order workflow by creating purchasing rules for orders.
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.
Attribute aggregations are now working correctly for Layered Navigation with Elasticsearch
Searching orders by special characters is now working properly.
Clicking the Clear All Button now expands all the filters, rather than collapsing them.
Product SKU/Name is now included in the Order History search filter summary.
Sorting Indicator is now displayed properly in the My Purchase Orders Grid.
Now, you can click the Approve, Cancel, Reject, and Purchase Order buttons only once. Previously, you could click the button multiple times.
