Hyvä for B2B ecommerce: What you need to know
Hyvä for B2B is the use case where the Hyvä Commerce + Adobe Commerce combination earns its premium. B2C Hyvä is straightforward — frontend swap, conversion lift, done. B2B Hyvä is materially more involved because of the company-account, shared-catalogue, quote-flow, and approval-workflow surfaces that don't exist in B2C.
This post is the B2B-specific guide: what features map cleanly to Hyvä, what needs custom work, the realistic timeline, and the cases where B2B Hyvä isn't worth the budget.
What "B2B Hyvä" actually means
There isn't a separate Hyvä product for B2B. The setup is:
- Adobe Commerce (paid Magento tier) with B2B Commerce features enabled
- Hyvä Commerce license (~£3,000–£5,000/year)
- Implementation work to re-template Adobe Commerce's B2B surfaces under Hyvä
For Magento Open Source B2B (no Adobe B2B Commerce features), you're limited to customer-group pricing and basic account features. The full B2B surface set requires Adobe Commerce.
The B2B-specific surfaces
Each of these is a separate Hyvä template + flow. None come for free with standard Hyvä Theme.
Company accounts
Customer signs up as part of a company. Company has multiple users with different roles (admin, buyer, viewer). Company admin manages users + permissions + billing.
Hyvä surfaces needed:
- Company self-registration flow
- Company dashboard for admins (users, settings, recent orders)
- User invite + role assignment UI
- User-level permissions enforcement (what each user can see / do)
Effort: 1–2 weeks.
Shared catalogues
Different customer segments see different products / categories / pricing. A wholesale customer sees commercial-grade products; a retail account sees consumer products. Both can be the same Magento install.
Hyvä surfaces needed:
- Category + product visibility per customer segment
- Catalogue assignment UI for admins
- Per-segment product detail pages (some merchandising blocks shown to some segments only)
Effort: 3–5 days.
Customer-specific pricing
Pricing tiers, contract pricing, negotiated pricing per customer. PDP shows the customer's price, not the list price.
Hyvä surfaces needed:
- PDP price block conditional on customer login
- PLP price rendering per customer tier
- Quantity-break tables (buy 10+ for £X each)
- Cart + checkout pricing carry-through
Effort: 3–5 days.
Negotiated quote workflow
Customer requests a quote from cart. Sales rep negotiates price + terms. Customer accepts, quote converts to order. This is the longest single B2B surface.
Hyvä surfaces needed:
- "Request quote" CTA in cart
- Quote-in-progress dashboard for customer
- Quote-acceptance UI
- Sales rep dashboard for active quotes
- Quote conversion to order flow
- Quote expiry handling
- Email notifications throughout
Effort: 1–2 weeks.
Requisition lists
Saved cart equivalents. Customer maintains a list of frequently-ordered products + quantities; quick-adds the whole list to cart for reorder.
Hyvä surfaces needed:
- "Save to requisition list" CTA on PDP + cart
- Requisition list management UI
- Quick-add-all to cart flow
- List sharing across company users
Effort: 3–5 days.
Approval workflows
Orders above a threshold require approver sign-off. Approver receives notification, reviews order, approves or rejects.
Hyvä surfaces needed:
- Pending-approval order list for approvers
- Approval / rejection UI with reason capture
- Notification email re-templating
- Requester-side approval-status UI
Effort: 1 week.
Multi-account ordering
Sales rep places an order on behalf of a company contact. Admin places an order on behalf of a junior user.
Hyvä surfaces needed:
- Account-switcher UI for sales reps
- "Placing order on behalf of X" indicator
- Audit trail (who placed, whose account)
Effort: 3–5 days.
B2B-specific PDP fields
Datasheets, technical specifications, certifications, lead times, bulk-pack pricing, trade-account status badges.
Hyvä surfaces needed:
- Extended PDP attribute display
- Document attachment rendering
- Trade-only badge / locked-content states
Effort: 2–4 days.
Combined B2B implementation effort
Full B2B Adobe Commerce Hyvä build adds 4–6 weeks to the standard Hyvä Theme + Checkout timeline. Total cost typically £50k–£90k for the complete Hyvä Enterprise build vs £35k–£60k for equivalent Hyvä Commerce B2C.
Where Adobe Commerce B2B + Hyvä shines
Three use cases where the combination is the clear right answer:
1. Trade-only ecommerce. Wholesale, trade aggregators, B2B-only platforms. The B2B feature set is core to the business model; Hyvä's performance gains compound with the B2B UX improvements.
2. Hybrid B2B + B2C. Manufacturers selling both direct-to-consumer and through trade partners. Different customer segments see different products, prices, and account UX — all on one Magento install.
3. Distributors with sales-rep-driven orders. Companies where the sales team places most orders on behalf of customers. The Hyvä-re-templated sales-rep UI is meaningfully better than classic Magento admin.
Where it doesn't make sense
1. Hybrid stores where B2B is <10% of revenue. If B2B is a side channel, the Hyvä B2B premium isn't justified. Run B2B through a simple customer-group-pricing setup on Hyvä Commerce B2C; skip the full B2B feature set.
2. Stores planning to move B2B to a separate platform. If B2B is heading to a dedicated B2B platform (Pepperi, OroCommerce, custom) within 12 months, don't invest in Adobe Commerce B2B + Hyvä for the interim.
3. Stores with very simple B2B needs. Just customer-group pricing and an account section? You don't need Adobe Commerce B2B at all. Magento Open Source B2B basics handle that, and Hyvä B2C Commerce + light customisation gets you 80% there.
The B2B Hyvä timeline
For a typical Adobe Commerce B2B Hyvä build:
- Weeks 1–2: Foundation + storefront templates (standard Hyvä Theme work)
- Weeks 3–4: B2B account surfaces (company accounts, shared catalogues, customer pricing)
- Weeks 5–6: Quote + approval flows
- Weeks 7–8: Hyvä Checkout integration with B2B fields (PO numbers, approval routing, multi-account)
- Weeks 9–10: Extension compatibility + performance tuning
- Weeks 11–12: UAT on staging with real B2B test scenarios
- Weeks 13–14: Cutover + post-launch monitoring + bug-fix sprint
Total: 14 weeks for a clean B2B build. Complex setups (multi-warehouse, custom approval routing, specific ERP integrations) push to 16 weeks.
The B2B UAT challenge
B2B UAT is harder than B2C UAT because the test scenarios are more complex:
- Multi-user company orders (User A places, User B approves, User C views)
- Quote-to-order conversion with edge cases (quote expires mid-conversion)
- Shared catalogue visibility per segment (Customer A sees product, Customer B doesn't)
- Approval routing with multiple approvers
- Multi-currency / multi-VAT-jurisdiction orders
Allow 2 weeks for B2B UAT vs 1 week for B2C. Recruit your actual sales reps and B2B customers to test — synthetic test scenarios miss the real-world friction points.
Integration considerations
B2B Hyvä commonly integrates with:
- ERP (SAP, NetSuite, Sage, Microsoft Dynamics) — for order sync, inventory, pricing
- CRM (Salesforce, HubSpot, Dynamics) — for customer + opportunity data
- PIM (Akeneo, inRiver, Salsify) — for product data
- Marketing automation (Klaviyo, Bloomreach, Marketo) — for nurture campaigns
Each integration touches Hyvä template surfaces. Pricing from ERP needs to render correctly. CRM customer data needs to display in the account section. PIM product data needs PDP rendering.
These integrations are usually backend-heavy and don't add much Hyvä-specific work — most of the integration is server-side. But each integration's frontend touch points need verifying during QA.
Custom B2B features we've built
A non-exhaustive list of B2B-specific work we've shipped under Hyvä:
- Customer-specific landing pages (URL like
/customer/acme-corpshows pricing + featured products for that customer) - Bulk-quote-upload (CSV upload of part numbers + quantities → quote request)
- Sales-rep dashboard with assigned customer accounts + open quotes + recent orders
- Customer-specific catalogue PDFs (downloadable price list specific to customer)
- Margin protection on negotiated quotes (alert sales rep if discount exceeds threshold)
- ERP-driven dynamic pricing (price calculated server-side from ERP API on each PDP load)
Each of these is custom work above the standard Adobe Commerce B2B + Hyvä baseline. Typical cost: £5k–£20k per feature depending on complexity.
The cost question, condensed
For B2B Hyvä on Adobe Commerce:
| Scenario | Cost | Timeline |
|---|---|---|
| Light B2B (customer pricing only, no company accounts) | £40k–£55k | 10–12 wks |
| Standard B2B (company accounts + shared catalogues + customer pricing) | £55k–£70k | 12–14 wks |
| Full B2B (above + quotes + approvals + multi-account) | £70k–£90k | 14–16 wks |
| Enterprise B2B (above + custom integrations + bespoke features) | £90k–£150k+ | 16–20 wks |
Add £3–5k/year for the Hyvä Commerce license, plus Adobe Commerce licensing (varies by GMV tier).
Next steps
- See the Hyvä Enterprise page for B2B + Adobe Commerce service detail
- Read Hyvä Enterprise for Adobe Commerce implementation guide for the full implementation walkthrough
- Read Hyvä for high-SKU catalogs if your B2B catalogue is large
- Book a scoping call for a fixed-price quote against your specific B2B feature set