Hyvä Enterprise for Adobe Commerce: The full implementation guide
Hyvä Enterprise, Hyvä Theme + Hyvä Commerce running on Adobe Commerce, is the same product as Hyvä on Magento Open Source. The complexity multiplier comes from Adobe Commerce's B2B feature set, which has surfaces (company accounts, shared catalogs, customer-specific pricing, quote flows, requisition lists, approval workflows) that Magento Open Source doesn't have.
This post is the full implementation guide for Hyvä on Adobe Commerce, with specific attention to the B2B surfaces and the Cloud deployment model.
What "Hyvä Enterprise" actually means
There isn't a separate "Hyvä Enterprise" product. The terminology refers to Hyvä Theme + Hyvä Commerce running on Adobe Commerce (the paid Magento tier), with the Adobe-specific features re-templated under the Hyvä render layer.
The license is Hyvä Commerce, ~$3,000–$5,000 per year, billed by Hyvä Themes, and the implementation work covers the Adobe-specific surfaces on top of standard Hyvä Commerce.
Adobe Commerce features re-templated under Hyvä
Each of these is a separate Hyvä template surface. Each is implementation work beyond standard Hyvä Theme.
1. Company-account self-service
- Company structure (parent + child accounts)
- User invites and role permissions
- User management dashboard for company admins
- Company-level settings (billing address, default approver, etc.)
Typical effort: 1–2 weeks of Hyvä template work.
2. Shared catalogs
- Customer-segment-specific catalog visibility
- Hidden products / categories per customer segment
- Catalog assignment UI for admins
Typical effort: 3–5 days.
3. Customer-specific pricing
- Contract pricing display per customer
- Tiered pricing rendering on PDP
- Quantity break visualization
Typical effort: 3–5 days.
4. Negotiated quote workflow
- Request a quote from cart
- Quote-in-progress view for customers
- Quote-acceptance and conversion-to-order flow
- Quote rejection / counter-quote handling
Typical effort: 1–2 weeks. This is the longest single B2B surface.
5. Requisition lists
- Saved cart equivalents for B2B customers
- Quick-add from requisition list to cart
- Sharing requisition lists across company users
Typical effort: 3–5 days.
6. Approval workflows
- Order above threshold requires manager sign-off
- Approver-side dashboard for pending approvals
- Notification flow for approver and requester
- Approval history per order
Typical effort: 1 week.
7. Multi-account ordering
- Place an order on behalf of a different company contact
- Account-impersonation UI for sales reps
- Audit trail for who placed the order vs whose account it's against
Typical effort: 3–5 days.
8. B2B-specific PDP fields
- Datasheets / certifications / lead times
- Bulk-pack pricing
- Trade account status / membership
Typical effort: 2–4 days.
Combined B2B surface effort
A full B2B Adobe Commerce Hyvä build adds 4–6 weeks to the standard Hyvä Theme timeline. Total cost typically $50k–$90k for the complete Hyvä Enterprise build vs $35k–$60k for equivalent Hyvä Commerce on Magento Open Source.
Adobe Commerce Cloud, the deployment model
Most of our Hyvä Enterprise clients are on Adobe Commerce Cloud (the managed-hosting tier from Adobe). The Cloud deployment model is materially different from self-hosted Magento and affects how Hyvä work ships:
The Cloud branch / environment promotion flow
Code moves: Integration → Staging → Production
- Integration: feature branches deploy here. Use for active dev.
- Staging: pre-production environment matching prod data. Use for UAT.
- Production: live customer environment. Cloud CI deploys here.
You can't bypass this. There's no direct deploy to production; every change moves through Integration first.
Cloud CI pipeline
Code lives in a Git repository managed by Adobe. Pushing to a Cloud branch triggers a build + deploy via the Cloud CI pipeline. The pipeline:
- Pulls code from Git
- Runs
composer install - Runs
bin/magento setup:upgrade - Runs
bin/magento setup:di:compile - Runs
bin/magento setup:static-content:deploy - Deploys to the target environment
This is automated; you don't run these commands by hand on prod. Hyvä's composer require hyva-themes/* packages slot into this pipeline normally.
What we can't do on Cloud
- Direct SSH access to production (limited; available for diagnostics not changes)
- Manual file uploads to production
- Override the
composer.jsonoutside the managed model - Install custom Linux packages outside the Cloud-supported set
In practice, Hyvä fits inside the Cloud model without issue. The constraints are real but don't affect Hyvä-specific work.
The Hyvä Enterprise implementation timeline
A typical Hyvä Enterprise build with full B2B feature scope:
Weeks 1–2: Foundation
- Hyvä Theme install + brand-system Tailwind config
- Header / footer / navigation
- Component library
- Cloud Integration environment ready
Weeks 3–5: Storefront templates
- PDP, PLP, search, cart, customer account (B2C surfaces)
- CMS blocks and content pages
Weeks 6–7: B2B surfaces
- Company accounts, shared catalogs, customer pricing
- Requisition lists, multi-account ordering
Weeks 8–9: Quote + approval flows
- Negotiated quote workflow end-to-end
- Approval routing + dashboards
- B2B-specific PDP fields
Weeks 10–11: Hyvä Checkout (if licensed)
- One-page checkout integration
- B2B fields (PO number, approval routing)
- Payment + shipping integration
Weeks 12–13: Extension compatibility + performance
- Hyvä compat for each paid extension
- Lighthouse mobile 90+ on storefront and checkout
- Cross-browser QA
Weeks 14–15: UAT + cutover
- Pre-launch UAT on Staging environment with real B2B test scenarios
- Off-peak DNS cutover via Cloud production promote
- 72-hour post-launch monitoring
Week 16: Post-launch sprint
- Bug-fix sprint for any production issues
- Handover doc + deploy runbook
- Team training on Hyvä admin patterns
Total: ~16 weeks, $50k–$90k.
The Adobe Commerce B2B-specific edge cases
A few things that trip up first-time Hyvä-Adobe Commerce implementers:
1. Customer-segmented product visibility
Adobe Commerce supports hiding entire products / categories from specific customer segments. The Hyvä-rendered PLP needs to respect this dynamically, if Customer A logs in, they see different products than Customer B. This affects search, navigation, sitemap, and PDP availability.
Implementation: standard Magento backend logic + Hyvä template conditional rendering. Not hard, but easy to forget until UAT.
2. Negotiated quote in-flight states
A quote can be in several states (requested, in negotiation, accepted, rejected, expired, converted-to-order). The customer-facing UI needs to handle all of these cleanly, including edge cases like "quote expired while customer was viewing it."
Implementation: Hyvä template + Alpine.js state management. ~3 days of work for the customer-facing surfaces.
3. Multi-warehouse stock visibility per customer
Some Adobe Commerce B2B configurations show different stock availability per customer (e.g. customer A has access to UK warehouse, customer B has access to EU warehouse). The PDP needs to render this per logged-in customer.
Implementation: standard Magento inventory backend + Hyvä template per-customer rendering.
4. Approval thresholds and notification routing
Orders above a customer-defined threshold require approver sign-off. The approver receives a notification, reviews the order, approves or rejects. The requester sees the approval status update.
Implementation: standard Adobe Commerce approval engine + Hyvä-rendered approver dashboard + notification email re-templating. ~1 week.
5. Saved-card / saved-address per company contact
In B2B, a saved card might belong to a company rather than a contact. The Hyvä Checkout needs to handle "use company card" vs "use my card" cleanly.
Implementation: payment-method integration with Hyvä Checkout + B2B-specific UI. ~3 days.
Hyvä Admin + Insights for B2B
Hyvä Admin is more useful for B2B than B2C, the admin workload on a B2B store is heavier (customer management, quote handling, approval oversight) and the modernized admin UX matters more.
Hyvä Insights is less differentiated, most B2B merchants already have BI tools (Tableau, Power BI, Looker) for B2B analytics. Hyvä Insights duplicates capability you probably already have.
Recommendation: include Hyvä Admin in scope for B2B builds. Skip Hyvä Insights unless your team specifically wants the unified Hyvä experience.
What it costs, real numbers
| Scenario | Cost | Timeline |
|---|---|---|
| Hyvä Theme only on Adobe Commerce (B2C) | $30k–$45k | 8–10 weeks |
| Hyvä Theme + Hyvä Checkout on Adobe Commerce (B2C) | $40k–$60k | 10–12 weeks |
| Hyvä Theme + selected B2B features (company accounts + shared catalogs) | $50k–$70k | 12–14 weeks |
| Full Hyvä Enterprise (Theme + Checkout + full B2B + Admin) | $60k–$90k | 14–16 weeks |
These are typical price bands. Your number depends on extension count, custom checkout fields, multi-store complexity, and B2B feature scope.
Pre-flight: things to confirm before starting
For Adobe Commerce specifically, confirm:
- Adobe Commerce version is Hyvä-supported. Check hyva.io for current compatibility.
- Cloud project access for our engineers. Read-only or environment-specific is fine; we don't need prod-write.
- Composer auth for Adobe + private vendor registries. Cloud manages this normally; verify it's working before kickoff.
- B2B feature list locked. Which B2B features in scope (company accounts, shared catalogs, quotes, approvals, etc.) and which are out.
- Integration list locked. ERP, CRM, marketing automation, PIM, all integrations we need to test against.
Pre-flight is a 1-week exercise before the engagement officially starts.
Next steps
- See the Hyvä Enterprise page for service detail
- Read Hyvä for B2B Ecommerce for B2B-specific considerations
- Read Hyvä Commerce cost breakdown 2026 for general Hyvä Commerce pricing
- Book a scoping call for a fixed-price quote against your Adobe Commerce environment