What Adobe Commerce’s Latest Release Means for B2B Sellers

TL;DR: Adobe Commerce’s June 2026 release targets common B2B friction points: AI-driven Live Search at no extra charge across PaaS, ACCS and Adobe Commerce Optimizer; four B2B drop-ins (requisition list sharing, seller-assisted buying, company hierarchies on ACCS, and quick and grid ordering); and an Advanced Security tier for PaaS. Together they fill gaps B2B teams used to pay for with custom development, which makes this a good time to audit which custom code can be retired.

Adobe Commerce’s June 2026 release continues a strong run of product investment, and this round lands squarely where B2B merchants feel the most friction: search relevance, purchasing efficiency, and platform security. None of these are flashy headline features on their own. But taken together, our read is that they add up to something bigger than a routine update: Adobe is closing gaps that B2B teams have historically paid custom development to solve. That’s worth unpacking feature by feature, and worth revisiting what custom-built B2B logic might now be safe to retire.

Search finally adapts to the buyer, not the other way around

B2B catalogs are brutal for keyword search. A buyer typing a part description, an internal nickname for a product line, or a spec that doesn’t match the exact attribute name in the PIM has historically landed on a blank results page, and a blank results page on a B2B site usually means a phone call to sales instead of a finished order. Adobe’s new AI-driven search is built to interpret what a buyer means instead of demanding they type it exactly right. It’s rolling into Live Search at no extra charge across Adobe Commerce PaaS, Adobe Commerce as a Cloud Service (ACCS), and Adobe Commerce Optimizer, the latest sign of the AI-native shift we flagged in Adobe Commerce Enters the Agentic Era.

For SaaS customers it arrives switched on for English catalogs by default; PaaS merchants get a single setting in the admin to turn it on themselves, no project or Adobe ticket required. That low-lift rollout matters almost as much as the capability itself: this is the rare AI feature a client can adopt without budgeting a discovery phase first.

Four B2B drop-ins that fix the workflows clients have been working around

B2B buying rarely looks like B2C buying, but Adobe Commerce’s B2B tools haven’t always reflected that. Most clients have either lived with the gap or paid to have it custom-built. This release closes four of the most common ones:

Feature	Why It Matters	How It Benefits B2B Customers
Requisition List Sharing	A purchasing list used to belong to whoever clicked save: useful for one person, useless for a department. The buyer who builds the cart and the buyer authorized to submit the PO are rarely the same person.	Anyone with access can view, add to, and check out from the list, so procurement teams can finally split sourcing and approval the way they actually work, without developers building that separation by hand.
Seller-Assisted Buying	When a rep places an order for a customer over the phone or by email, that interaction has always lived outside the platform: no record of what was approved, no easy way to prove it later if a dispute comes up.	Built-in consent and an audit trail make assisted orders both easier to place and easier to defend, cutting chargeback and compliance risk without adding process overhead for the sales team.
Company Hierarchies	Many B2B organizations are built around parent companies, regional divisions, or multiple subsidiaries and need their commerce platform to reflect that structure. PaaS has supported company hierarchies for a while; this drop-in brings that same capability to ACCS.	Multi-entity clients on ACCS can now mirror their actual org chart, with purchasing permissions and visibility that follow it, instead of commissioning custom development to model that structure.
Quick Ordering and Grid Ordering	A buyer reordering the same forty items every month shouldn’t have to click through product pages built for someone discovering what they want for the first time.	Repeat buyers can skip discovery entirely and enter what they already know (by SKU or grid), speeding up the highest-volume, most loyal order pattern a B2B site has and cutting down on abandoned reorders.

This is the pattern we flagged above: four of the stickiest gaps in Adobe Commerce’s B2B toolkit are now supported, upgrade-safe components instead of custom builds. For any client running bespoke logic to solve these same problems, this release is a legitimate reason to open the conversation about what can be decommissioned.

Security built for B2B’s bigger target

B2B storefronts are an unusually attractive target: order minimums are higher, account data is richer, and a competitor has more incentive to scrape a wholesale price list than a retail one. Until now, defending against that meant layering third-party tools on top of Adobe Commerce. The new Advanced Security tier for Adobe Commerce on Cloud (PaaS) folds that protection into the platform itself: edge-level defense against traffic floods, plus filtering aimed at the automated abuse B2B sites actually see, like stolen cards being tested in bulk, inventory tied up by bots, and pricing scraped wholesale. Today this tier is PaaS-specific, so the practical takeaway splits by platform: PaaS clients get a real option to consolidate bolt-on vendors, while ACCS clients should confirm with their Adobe or partner contact whether an equivalent protection layer is already built into the SaaS model.

Time to audit your custom B2B code

This is a genuinely useful release for B2B: search that adapts to the buyer, ordering workflows that match real procurement, and security options built for a higher-stakes storefront. All of it is available with minimal lift for clients already on Adobe Commerce Cloud. As we noted above, the common thread across this release is Adobe closing gaps that B2B teams have historically paid custom development to solve. For partners and in-house teams alike, that’s a good prompt to audit what custom B2B code could be retired, and to revisit the broader Adobe Commerce roadmap with that in mind. For more on where the platform itself is headed, see The Last Adobe Commerce Upgrade You’ll Ever Have to Run.

If you want to talk through what this release means for your specific setup (PaaS or ACCS), our Adobe PaaS to SaaS Accelerator page is a good starting point.

Frequently Asked Questions