A self-service dealer portal on Adobe Commerce is built from four native B2B pieces: company accounts for the buyer hierarchy, shared catalogs for account-specific products and pricing, negotiable quotes for custom deals, and purchase-order approvals. On a Hyva storefront those screens need Hyva Enterprise or a custom rebuild, because the defaults use the frontend Hyva removed.
If you run a distribution business with a few hundred dealer accounts, your portal is not a nice-to-have. It is the order desk. Around 86 percent of B2B buyers now prefer to place orders themselves rather than call a rep, and every quote request that stalls on a slow page is an order a competitor’s portal captures. This guide lays out how to structure a portal for 500-plus wholesale accounts on Adobe Commerce, what changes when the storefront runs Hyva, and where the revenue actually comes from.
Bemeir builds these portals as core Magento development work, and the architecture below is the one we scope against real dealer networks.
What a self-service dealer portal actually is
Strip away the marketing and a dealer portal is four capabilities working together:
- A buyer hierarchy so a dealership’s head office, its branches, and individual buyers all sit under one account with the right roles and spending limits.
- Account-specific catalogs and pricing so each dealer sees only the products they are contracted to buy, at their negotiated price, not your public list price.
- A quote and approval workflow for the deals that fall outside standard pricing.
- Frictionless reordering so the 30 to 40 percent of portal revenue that comes from repeat orders takes three clicks, not a phone call.
Adobe Commerce ships native modules for all four. Magento Open Source does not include the B2B module, so an Open Source store needs extensions or a custom build to reach the same feature set. That edition decision is the first fork in the road, and we cover it in depth in our comparison of Adobe Commerce B2B on Hyva.
The four native building blocks
Here is what each Adobe Commerce B2B module does and which edition you need for it.
| Portal capability | Native module | What it controls | Edition needed |
|---|---|---|---|
| Buyer hierarchy | Company Accounts | Parent and child companies, buyer roles, permissions, spending limits | Adobe Commerce B2B |
| Account catalogs and pricing | Shared Catalogs | Which products and prices each company sees, tiered and contract pricing | Adobe Commerce B2B |
| Custom deals | Negotiable Quotes | Request for quote, back-and-forth pricing, quote-to-order | Adobe Commerce B2B |
| Procurement controls | Purchase Orders and Approvals | PO checkout, multi-step approval rules by amount or role | Adobe Commerce B2B |
| Fast reordering | Requisition Lists, Quick Order | Saved order templates, SKU and CSV bulk entry, reorder from history | Adobe Commerce B2B |
Company management lets you build a hierarchy that mirrors a dealer’s org chart. A head office can oversee several branch accounts, and you set pricing, roles, and approval rules once at the parent level so they cascade to every location beneath it. That parent-child structure is what makes 500 accounts manageable instead of 500 separate configurations.
Shared catalogs are the pricing engine. As Adobe’s own shared catalog overview explains, you create multiple catalogs, assign each to one or more companies, and set both product visibility and custom prices per catalog. A distributor typically runs a handful of catalog tiers (for example national dealers, regional dealers, and buying groups) rather than one catalog per account, which keeps the model maintainable at scale. Scandiweb’s rundown of Adobe Commerce B2B features is a useful second reference on how these pieces fit together.
Why the default B2B storefront breaks on Hyva
This is the part most merchants discover too late. Adobe built the customer-facing B2B screens, company account management, requisition lists, negotiable quotes, and quick order, as Knockout.js applications running on RequireJS. Those are exactly the legacy libraries a Hyva development frontend removes in favor of Alpine.js, Tailwind CSS, and native JavaScript.
The result: on a stock Hyva theme, the B2B backend, its GraphQL and REST APIs, the data models, the admin, and all the pricing logic keep working untouched, but the default B2B storefront screens render blank or throw errors, because the JavaScript they depend on is not loaded. You get the speed of Hyva and a broken dealer portal.
There are two ways to fix it. The first is Hyva Enterprise, the paid bundle that ships Hyva-native versions of company accounts, requisition lists, quick order, and negotiable quotes, built and supported by the Hyva team. The Hyva Enterprise B2B modules are documented in the Hyva Enterprise getting-started docs, and for most portals it is the sensible default. We break down what the bundle includes and when you need it in Hyva Enterprise vs the Free Hyva Core. The second path is a custom Hyva rebuild of the specific screens you need, which makes sense when your workflow diverges from the native one. Either way, budgeting a Hyva B2B build without accounting for these screens is the single most common way a dealer-portal project blows its timeline.
Architecture for 500-plus dealer accounts
At a few hundred accounts, three design decisions decide whether the portal stays fast and maintainable.
Catalog tiering, not per-account catalogs. Model your dealer types into a small set of shared catalogs. Assign companies to a tier, and handle the exceptions with negotiable quotes or customer-specific pricing rather than spinning up a new catalog per dealer. This keeps reindex times and admin overhead sane.
Hierarchy that matches the real org chart. Map parent companies to buying groups or head offices and child accounts to branches. Push roles and spending limits down from the parent. A 500-account network is usually far fewer than 500 top-level companies once you group branches correctly.
Data that lives in the right system. Decide, per data type, whether Adobe Commerce or your ERP is the source of truth. The table below is the pattern we use.
| Portal data | Source of truth | How it renders on Hyva |
|---|---|---|
| Contract and tier pricing | ERP, synced to shared catalogs | Cached with the catalog, served from full page cache |
| Real-time stock | ERP or Multi-Source Inventory | Fetched client-side via GraphQL as private content |
| Credit limit and balance | ERP | Fetched per session, never cached publicly |
| Order and invoice history | Adobe Commerce plus ERP | Account section, private content |
| Saved reorder templates | Adobe Commerce (Requisition Lists) | Hyva Enterprise or custom screen |
The rule that keeps a Hyva portal fast is simple: anything account-specific (a dealer’s price, their credit, their stock view) must be served as private content fetched after the cacheable shell loads, never baked into a cached page. Get that boundary wrong and you either leak one dealer’s pricing into another’s cache or you disable caching and lose the speed you migrated to Hyva for. Our guide to Hyva for B2B frontends walks through this rendering split in detail.
The reorder engine is where the revenue is
For an established dealer network, most orders are repeat orders. Industry data on mid-market B2B portals puts quick-order, CSV-upload, and reorder-from-history workflows at roughly 30 to 40 percent of total portal revenue within the first year. That means the reorder experience deserves more design attention than the marketing homepage.
Three workflows carry that load:
- Reorder from history. One click to rebuild a past order into the cart. This is the highest-frequency action in the portal.
- Requisition lists. Saved templates a buyer maintains for recurring orders, editable quantities, add-all-to-cart.
- Quick order and CSV upload. SKU-and-quantity entry and spreadsheet upload for buyers who already know what they want.
All three are native Adobe Commerce B2B features, and all three are Knockout screens that need Hyva Enterprise or a rebuild on a Hyva storefront. We cover the reorder patterns specifically in Magento B2B requisition lists and quick order on Hyva. If dealers are abandoning orders today because your Luma portal is slow, this is the layer that recovers them.
ERP integration: real-time pricing, stock, and credit
A dealer portal that shows stale pricing or lets a dealer over-order against a maxed credit line creates more work than it saves. The three data points dealers care about most, their price, whether it is in stock, and how much credit they have left, usually live in your ERP, not in Magento.
The integration pattern that scales: sync contract and tier pricing into shared catalogs on a schedule so it serves from cache, and fetch the volatile values (live stock, credit balance) in real time as private content when the dealer views the page. Net terms and company credit are their own subsystem, and real net-terms enforcement almost always ties back to the ERP; we cover that in Magento B2B payment on account and company credit. For NetSuite specifically, the object mapping and sync cadence are in our NetSuite and Adobe Commerce integration blueprint.
This integration depth is where the platform’s ecosystem matters. Bemeir’s technology partner network spans the ERP connectors, payment gateways, and fraud tools a distributor portal leans on, so the integration is assembled from proven parts rather than built from zero.
A phased build plan
A 500-account portal does not have to launch all at once. The sequence that keeps a dealer network selling through the transition:
- Foundation. Stand up company accounts and the hierarchy, migrate dealers, and set roles and spending limits.
- Catalogs and pricing. Build the shared catalog tiers and wire the ERP price sync. This is the core of the portal’s value.
- Storefront on Hyva. Deploy Hyva with Hyva Enterprise B2B screens, or the custom rebuild, and validate that private content renders correctly per account.
- Reorder and ERP live data. Turn on requisition lists, quick order, reorder-from-history, and the real-time stock and credit feeds.
- Quotes and approvals. Add negotiable quotes and PO approval rules for the deals that need them.
Running the build this way means each phase ships something dealers can use, and the risky storefront cutover happens after the data model is proven.
Bemeir has a decade-plus of B2B Magento work behind this sequence, and as the first US-based Hyva Gold Partner the team scopes the Hyva rendering boundary correctly from the start, which is the part that most often goes wrong.
Frequently asked questions
Do I need Adobe Commerce, or can I build a dealer portal on Magento Open Source?
The native company accounts, shared catalogs, negotiable quotes, and requisition list features are part of the Adobe Commerce B2B module, which Open Source does not include. You can approximate a portal on Open Source with B2B extensions or a custom build, but for a 500-account network the native B2B feature set on Adobe Commerce is usually the lower-risk foundation, especially where custom pricing and approvals are involved.
Will a Hyva migration break my existing B2B dealer portal?
The backend, APIs, pricing, and admin keep working, but the default customer-facing B2B screens (company account management, requisition lists, quotes, quick order) render blank on a stock Hyva theme, because they were built on the Knockout.js stack Hyva removes. You resolve this with Hyva Enterprise, which ships Hyva-native versions of those screens, or with a custom rebuild of the screens you use.
How do I keep dealer-specific pricing from leaking through full page cache?
Serve anything account-specific as private content fetched after the cacheable page shell loads, rather than rendering a dealer’s price into a cached page. Shared catalog tier pricing can be cached with the catalog, but a specific dealer’s negotiated price, credit balance, and live stock view should be fetched per session. This is the core rendering discipline of a fast Hyva B2B storefront.
Can I run a dealer portal on Shopify, Shopware, or BigCommerce instead?
Yes, and the right platform depends on how complex your pricing, hierarchy, and ERP needs are. Simpler dealer programs can fit well on Shopify B2B, and both Shopware and BigCommerce support B2B portals with their own tradeoffs. Adobe Commerce tends to win when you need deep company hierarchies, many pricing tiers, and tight ERP integration at scale. Bemeir builds on all of these, so the recommendation follows your requirements rather than a single platform.
How long does a 500-account dealer portal take to build?
There is no single figure, because timeline scales with catalog complexity, the number of pricing tiers, and ERP integration depth. Phasing the build (hierarchy first, then catalogs and pricing, then the Hyva storefront, then reorder and live data, then quotes) lets dealers start using each stage as it ships, rather than waiting for a single big-bang launch, which is the safer path for a network that cannot go dark.
