Hyva replaces Magento’s Luma frontend, but it does not automatically render Adobe Commerce B2B storefront features. Company accounts, tiered pricing, shared catalogs, negotiable quotes, and requisition lists live in the backend and need Hyva-native components, from Hyva Enterprise or a custom build, to appear correctly. Skip that step and the logic works while the storefront does not.
This is the part most Hyva B2B content skips. Introductory guides confirm Hyva “supports B2B” and mention the Hyva Enterprise add-on, then move on. For a B2B merchant with account hierarchies and customer-specific pricing, that is exactly where the real questions start. This guide walks through what actually changes in the frontend, feature by feature, and where a Hyva B2B build succeeds or quietly breaks.
As the first US-based Hyva Gold Partner, Bemeir has shipped these builds, so this reflects what happens in production rather than what a datasheet promises. You can read more about that background on About Bemeir.
The core distinction: backend logic versus frontend rendering
Adobe Commerce B2B features are backend capabilities. Hyva is a frontend theme. Those are two different layers, and understanding the seam between them is the whole game.
When you migrate from Luma to Hyva, you are replacing the presentation layer. The B2B business logic, company accounts, permissions, shared catalog pricing, quote workflows, stays in Adobe Commerce. What changes is how, and whether, that logic gets drawn on the page. Luma ships with the templates and JavaScript that render every native B2B screen. Hyva does not inherit those templates. It is a lean rebuild of the frontend, which is exactly why it is fast, and exactly why B2B screens need to be rebuilt in the Hyva way rather than assumed to carry over.
The Adobe Commerce B2B feature set includes company accounts, hierarchical company management, shared catalogs, quick order, negotiable quotes, purchase orders with approval, and requisition lists. Every one of those has a storefront surface that must exist in Hyva.
Where B2B logic lives, and what Hyva needs to render it
Before the feature walkthrough, this table is the mental model. The failure mode is always the same: the logic is present, the frontend is not.
| B2B feature | Where the logic lives | What Hyva needs to render it | What breaks if you skip it |
|---|---|---|---|
| Company account and users | Adobe Commerce B2B | Hyva company dashboard and user-management components | Company admins cannot manage sub-users from the storefront |
| Account hierarchy and roles | Adobe Commerce B2B | Role and permission UI in Hyva | Permissions apply in backend but are invisible to buyers |
| Tiered and customer-specific pricing | Catalog price rules, shared catalog | Price rendering wired to private content | Wrong or generic prices shown, or prices cached across companies |
| Shared or custom catalogs | Adobe Commerce B2B | Catalog visibility logic in Hyva templates | Buyers see products or prices meant for another company |
| Negotiable quotes | Adobe Commerce B2B | Hyva quote cart and negotiation UI | Request-for-quote button leads nowhere |
| Requisition lists | Adobe Commerce B2B | Add-to-requisition and reorder components | Fast reorder workflow disappears |
| Purchase order and approval | Adobe Commerce B2B | Approval and PO screens in Hyva | Approvers cannot act from the storefront |
Account hierarchies: the company dashboard has to be rebuilt
A B2B company account is a tree: a company admin, sub-users, and roles that decide who can order, who can approve, and who can see pricing. In the frontend, that tree shows up as a company dashboard where the admin adds users and assigns roles.
Under Hyva, that dashboard is a set of components that has to exist and be wired to the B2B backend. Adobe describes the company account as the entity “on which all other features are in some way dependent,” which is why getting it right in Hyva matters so much. If the company management screens are not rebuilt, the hierarchy still functions in the admin, but your buyers lose the self-service that makes B2B accounts worth having. A well-executed Hyva build reproduces the full company account experience, and because Hyva is lean, those data-heavy account pages often load faster than they did on Luma.
Tiered and customer-specific pricing: the caching trap
Pricing is where Hyva B2B builds most often go wrong, and the culprit is caching. B2B prices are personal: company A and company B can see different prices for the same SKU. The frontend has to render each buyer’s price without ever caching one company’s price for another.
Magento solves this by treating prices as private content pulled in per session rather than baked into the cached page. Hyva handles private content differently from Luma, using its own approach to the customer-data and sections mechanism. If a Hyva B2B build renders tier prices as static page content instead of private content, two things break: the full-page cache can serve the wrong company’s price, and price updates may not appear until the cache clears. Done correctly, the product and category pages stay fully cached and fast while each company still sees its own shared catalog pricing. This is a detail no introductory Hyva B2B article covers, and it is the one most likely to cause a support ticket after launch.
Shared and custom catalogs: visibility follows the buyer
Shared catalogs control which products and prices each company can see. In the storefront, that means category and product visibility, and the price shown, both depend on who is logged in.
In a Hyva build, catalog visibility logic has to be respected in the templates that list and filter products, so a buyer never sees a SKU or a price outside their assigned catalog. This interacts with layered navigation and search, which also have to filter to the buyer’s catalog. When this is handled correctly, a guest and two different companies can hit the same category URL and each get a correct, cache-safe result. When it is not, buyers see products they cannot purchase or prices that are not theirs.
Quotes, requisition lists, and quick order: the daily B2B workflows
The features B2B buyers touch every day are negotiable quotes, requisition lists, and quick order. Each has a distinct frontend surface that Hyva must provide.
Negotiable quotes need a quote cart, a submit-for-quote action, and a negotiation view where buyer and seller adjust quantities and pricing. Requisition lists need an add-to-requisition control on product pages and a reorder view built for frequent restocking. Quick order needs a fast SKU-and-quantity or CSV entry screen. On Luma these ship as templates; on Hyva they are Hyva components. Requisition and quick-order screens are exactly the data-heavy, interaction-heavy pages where Hyva’s lighter JavaScript pays off, so buyers get the workflow back and a faster one. These frontend workflows also have to line up with your back-office systems, which is where our Adobe Commerce B2B and ERP integration guide picks up.
How to get B2B onto Hyva: three paths
There is more than one way to render B2B in Hyva, and the right one depends on your edition and your appetite for maintenance.
| Path | Best for | Trade-off |
|---|---|---|
| Hyva Enterprise add-on | Adobe Commerce merchants wanting native B2B UI, maintained | Annual license cost, tied to the add-on roadmap |
| Custom Hyva components | Teams with specific B2B UX or non-standard workflows | More build effort, you own the maintenance |
| Third-party B2B extension with Hyva compatibility | Open Source merchants using an extension for B2B | Depends on that vendor shipping a Hyva-ready frontend |
Hyva Commerce and Hyva Enterprise provide Hyva-native components for the Adobe Commerce B2B suite, which is the fastest path for most Adobe Commerce merchants. It matters which edition you run: Adobe Commerce ships the native B2B suite, while Magento Open Source has no native company accounts or shared catalogs, so Open Source merchants reach B2B through a third-party extension, and that extension must have its own Hyva-compatible frontend. Choosing among these paths is where a partner who has built Hyva for B2B before saves you from an expensive wrong turn. Our technology partner ecosystem also matters when a third-party B2B extension is in the mix.
Performance still has to hold under B2B load
The reason to be on Hyva at all is speed, and B2B pages are the heaviest pages you run: large account dashboards, big requisition lists, and personalized pricing everywhere. A B2B Hyva build has to hold its Core Web Vitals under that weight.
The targets do not change for B2B: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1, per the Core Web Vitals thresholds. What changes is the difficulty, because personalization and private content add moving parts. This is why the caching approach described earlier is not a nicety. It is what lets a heavily personalized B2B storefront stay both correct and fast. If your B2B needs are lighter, narrower platforms such as Shopify Plus, BigCommerce, or Shopware cover a smaller band of B2B, but for deep account hierarchies and per-company catalogs, Adobe Commerce on Hyva remains the stronger fit.
Getting all of this right, correct pricing, cache-safe personalization, rebuilt workflows, and held performance, is the difference between a Hyva B2B build that works and one that looks fine until a buyer logs in. If you want that built by a team that has shipped it, start at Bemeir.
Frequently asked questions
Does Hyva support Adobe Commerce B2B out of the box?
Not automatically. Hyva replaces the Luma frontend, and the native B2B storefront screens do not carry over on their own. You render them through Hyva Enterprise, custom Hyva components, or a Hyva-compatible B2B extension. The backend B2B logic keeps working the whole time; what needs building is the frontend.
Do I need Hyva Enterprise for a B2B store?
If you run Adobe Commerce and want the native B2B suite rendered in Hyva with ongoing maintenance, Hyva Enterprise is usually the most efficient path. If you have unusual B2B workflows or run Magento Open Source with a third-party B2B extension, custom components or that extension’s own Hyva frontend may fit better. The right answer depends on your edition and how standard your B2B flows are.
Why do my B2B prices show up wrong or stale on Hyva?
Almost always a caching mistake. B2B prices are per-company private content, and if a build renders them as static page content the full-page cache can serve the wrong price or fail to refresh it. The fix is to render prices through Hyva’s private-content mechanism so pages stay cached and fast while each buyer still sees their own price.
Will Hyva make my B2B account pages faster?
Usually yes. B2B account dashboards, requisition lists, and quick-order screens are data-heavy and interaction-heavy, which is where Hyva’s lighter JavaScript helps most. The catch is that the speed only holds if personalization and caching are implemented correctly, so the build quality matters more on B2B than on a simple catalog.
Can I migrate a B2B store to Hyva without losing functionality?
Yes, when the migration plan explicitly accounts for every B2B screen. The failure mode is treating a B2B store like a standard catalog and discovering after launch that quotes, requisition lists, or company management were never rebuilt. A migration scoped feature by feature, with the pricing and caching handled deliberately, keeps full functionality and gains the performance.
