Adobe Commerce B2B features run on Hyva, but with a catch that trips up most teams: the backend logic works untouched, while the storefront interfaces (company accounts, requisition lists, negotiable quotes, quick order) are KnockoutJS applications that do not render on Hyva’s Alpine.js and Tailwind stack. You get them back through Hyva Enterprise B2B or a custom rebuild.
The confusion is understandable. Ask “does Adobe Commerce B2B work with Hyva?” and you will get both “yes” and “no” as answers, because both are half right. The server-side B2B engine, company data, pricing rules, and quote workflow keep functioning. What breaks is the customer-facing UI, because Adobe built those screens on the exact frontend libraries Hyva removed. Below is the feature-by-feature reality, the install sequence that avoids a broken storefront, and how to scope the effort.
Bemeir is the USA’s first official Hyva Gold Partner and runs Adobe Commerce B2B on Hyva in production. This is the reference we wish existed when teams first ask us the question.
The core compatibility principle
Hyva does not modify Magento’s backend. It replaces the frontend rendering layer. So the rule for every B2B feature is the same: the PHP business logic, admin configuration, and data model are untouched, but any storefront screen that Adobe built as a KnockoutJS or RequireJS component needs a Hyva-native equivalent.
Adobe Commerce ships eight native B2B capabilities: company accounts, company management and hierarchies, shared catalogs with custom and tiered pricing, quick order by SKU, negotiable quotes, purchase order approvals, requisition lists, and Pay on Account (company credit). Each has a storefront footprint. That footprint is what determines your work.
The feature-by-feature compatibility matrix
The table below is the honest state of each Adobe Commerce B2B feature on a Hyva storefront. “Stock Hyva” means the free open-source theme with no enterprise add-on.
| Adobe Commerce B2B feature | Backend logic | Renders on stock Hyva? | Coverage path | Notes |
|---|---|---|---|---|
| Company accounts (registration, users, roles) | Works | No, Knockout UI | Hyva Enterprise B2B | The company registration and account management screens are a Knockout app that must be rebuilt |
| Company management and hierarchies | Works | Partial | Hyva Enterprise B2B | Admin-side hierarchy is fine; buyer-facing structure and role UI needs Hyva components |
| Shared catalogs and tiered/contract pricing | Works | Mostly | Stock Hyva plus checks | Pricing resolves server-side and displays; verify PLP/PDP price rendering per theme |
| Quick order by SKU | Works | No, Knockout UI | Hyva Enterprise B2B or rebuild | The SKU entry and autocomplete widget is a Knockout component |
| Negotiable quotes | Works | No, Knockout UI | Hyva Enterprise B2B | Request-a-quote, quote list, and negotiation screens all need Hyva templates |
| Purchase order approvals | Works | No, Knockout UI | Hyva Enterprise B2B | Approval rules and PO screens are storefront components |
| Requisition lists | Works | No, Knockout UI | Hyva Enterprise B2B or rebuild | The add-to-requisition-list widget on PDP/PLP is a Knockout component |
| Pay on Account (company credit) | Works | No, checkout UI | Hyva Enterprise checkout | Company credit at checkout needs Hyva Enterprise checkout compatibility |
The pattern is clear. Shared catalog pricing largely survives because it resolves on the server and renders through normal price blocks. Everything with an interactive buyer-facing screen needs a Hyva-native build, and the supported route for that is the paid Hyva Enterprise B2B layer.
Two paths: Hyva Enterprise B2B or a custom rebuild
You have two realistic ways to make these features render on Hyva. Choose deliberately, because the maintenance profile is very different.
| Dimension | Hyva Enterprise B2B | Custom rebuild (Magewire/Alpine) |
|---|---|---|
| What you get | Maintained templates for the full Adobe Commerce B2B suite | Bespoke components you own end to end |
| Upfront cost | Annual Hyva Enterprise license plus config and theming | Higher dev cost, 5 to 20+ days depending on features |
| Upgrade path | Vendor maintains compatibility as Adobe and Hyva release | You maintain compatibility on every Magento and Hyva upgrade |
| Time to live | Fastest | Slowest |
| Best for | Most B2B merchants who want supported, upgradeable UIs | Edge cases the Enterprise layer does not cover, or heavily customized flows |
For most merchants running the standard Adobe Commerce B2B feature set, Hyva Enterprise B2B is the correct answer. A full custom rebuild only earns its cost when you have deeply customized B2B screens that the Enterprise templates cannot express, and even then, a hybrid (Enterprise for the standard flows, custom for the exceptions) usually beats an all-custom build.
The install order that avoids a broken storefront
Sequence matters here more than in almost any other Magento task. Install these out of order and you will chase phantom rendering bugs.
- Confirm you are on Adobe Commerce 2.4.6 or higher and Hyva Themes 1.2.9 or higher. Hyva Enterprise B2B targets current releases; older 2.4.4/2.4.5 support is limited.
- Install and configure Adobe’s B2B extension first (
magento/extension-b2b1.4.0 or higher). Enable company accounts, which turns on shared catalogs and quotes by default. - Verify the B2B backend works on Luma or the default theme before touching Hyva. Prove the engine before you skin it.
- Install the Hyva Enterprise B2B metapackage (
hyva-themes/magento2-hyva-enterprise-b2b). It pulls in the base commerce compatibility package as a dependency, so you do not install that separately. - Add Hyva Enterprise checkout compatibility if you use Pay on Account, gift wrapping, reward points, or store credit at checkout. Company credit at checkout is an Enterprise checkout feature, not a base theme feature.
- Theme, test each B2B flow end to end, and gate the build on a company-user smoke test, not just a guest checkout.
Track feature status against Hyva’s public Enterprise Compatibility Tracker so you know exactly which components are covered in your target version before you commit a timeline.
Implementation notes that save you a sprint
Company accounts are the anchor. Enabling company accounts in Adobe Commerce also switches on shared catalogs and B2B quotes by default. Scope all three together; they are not independent line items.
Requisition lists and quick order live on product pages. Their add-to-list and SKU-entry widgets appear on PDP and PLP templates. If you rebuild category and product pages in Hyva (you will), make sure those B2B widgets are wired into the new templates, not left as orphaned Knockout that silently fails.
Negotiable quotes touch more screens than teams expect. A quote is not one page. It is a request action on cart and product, a buyer quote list, a negotiation thread, and admin-side seller screens. Budget for the whole flow.
Pay on Account is a checkout problem, not an account problem. Company credit shows up as a payment method at checkout, so it depends on Hyva Enterprise checkout compatibility rather than the account-page components. Teams often scope the account UI and forget the checkout payment method.
If you want the deeper frontend-behavior view of how account hierarchies and tiered pricing render, our companion piece on Hyva for B2B frontends walks through the rendering specifics. This guide stays on compatibility and sequencing.
Scoping the work honestly
Your cost is driven by how many of the interactive B2B features you actually use and how customized your existing B2B screens are. A merchant using company accounts, shared catalogs, and requisition lists on standard flows is a fast Hyva Enterprise configuration. A merchant with custom quote fields, bespoke approval logic, and a non-standard company registration form is a larger build.
The single most common scoping mistake is treating Adobe Commerce B2B on Hyva as a theme install. It is a compatibility project: you are aligning three moving parts (Adobe’s B2B extension, the Hyva Enterprise layer, and your customizations) across specific versions. Run the feature matrix above against your live store, mark which features you use, and the estimate writes itself.
When to bring in an agency
Do the feature inventory yourself. It costs an afternoon and makes every vendor conversation sharper. Bring in a partner when negotiable quotes or purchase order approvals are in scope, when you have customized B2B screens beyond Adobe’s defaults, or when the Pay on Account checkout path is business-critical and cannot break. Those are the flows where a team that has shipped Adobe Commerce B2B on Hyva before will save you weeks. You can see how Bemeir works as an extension of your team, the depth of our Magento and Adobe Commerce development practice, and the breadth of our technology partner ecosystem that keeps these integrations current.
If your evaluation is actually a platform decision rather than a frontend one, the honest framing is that Adobe Commerce still has the deepest native B2B feature set of any major platform. Shopify Plus, BigCommerce, and Shopware each cover a meaningful subset of these B2B capabilities, and Bemeir builds on all of them, so the right recommendation depends on which of the eight features above you truly need. The full picture of who we are and what we ship lives on the Bemeir homepage.
Frequently asked questions
Does Adobe Commerce B2B work with Hyva or not?
Both, depending on which layer you mean. The B2B backend (company data, pricing, quote and approval logic, admin configuration) works unchanged, because Hyva does not touch Magento’s backend. The storefront screens do not render on the stock Hyva theme, because Adobe built them in KnockoutJS. You restore those screens with Hyva Enterprise B2B or a custom Alpine/Magewire rebuild. So the accurate answer is: the logic works everywhere, the UI needs a compatibility layer.
Do I need Hyva Enterprise for B2B, or can I use the free theme?
For interactive B2B features (company accounts, requisition lists, quick order, negotiable quotes, purchase order approvals, company credit), you need Hyva Enterprise B2B or a custom rebuild. Shared catalog pricing largely works on the free theme because it resolves server-side. If your B2B usage is only tiered pricing on shared catalogs, you may avoid Enterprise; if buyers need account, quote, or requisition screens, you do not.
What is the correct install order for Adobe B2B and Hyva Enterprise?
Install and configure Adobe’s B2B extension first (magento/extension-b2b 1.4.0+), verify it on the default theme, then install the Hyva Enterprise B2B metapackage (hyva-themes/magento2-hyva-enterprise-b2b). Add Hyva Enterprise checkout compatibility if you use Pay on Account. Reversing this order produces rendering bugs that look like theme problems but are really sequencing problems.
Which Magento and Hyva versions do I need?
Plan for Adobe Commerce 2.4.6 or higher and Hyva Themes 1.2.9 or higher. Support for older 2.4.4 and 2.4.5 lines is limited and under review, so if you are on those, budget a platform upgrade before the B2B compatibility work.
How is this different from just skinning the B2B pages?
You cannot skin a KnockoutJS component into an Alpine one with CSS. The B2B storefront screens have to be reimplemented in Hyva’s rendering model, which is why Hyva Enterprise exists as a maintained set of those components rather than a stylesheet. Treating it as skinning is the mistake that turns a three-week configuration into a stalled project.
