Implementing Hyvä for enterprise multi-warehouse Magento requires a structured approach: set up a Hyvä-capable environment, configure Adobe Commerce MSI (Multi-Source Inventory), customize theme templates per warehouse, and optimize performance through caching and lazy loading. The process takes 8-16 weeks depending on complexity, with careful attention to inventory synchronization and frontend performance.
The Core Challenge: Why Hyvä Changes the Game for Multi-Warehouse Retail
Multi-warehouse retailers live in a world of complexity. You’re managing inventory across multiple fulfillment centers, each with different shipping rules, pricing structures, and availability windows. The legacy Luma theme – or worse, a custom monolith – becomes a bottleneck. Hyvä, built on Vue 3 and PWA principles, gives you the architectural flexibility to handle that complexity while keeping your storefront snappy.
The real problem isn’t just “How do I install Hyvä?” It’s “How do I build Hyvä infrastructure that scales with my fulfillment operations?”
We’ve worked through this at Bemeir with mid-market retailers managing 3-8 regional warehouses. The teams that succeed share one trait: they treat the Hyvä implementation as a project delivery problem, not a theme reskin.
Prerequisites: What You Need Before Day One
Before you touch Hyvä code, nail these fundamentals:
Infrastructure Requirements:
– Adobe Commerce 2.4.4 or higher (2.4.6 recommended)
– Node.js 16.13+ and npm 8+
– Composer 2.x
– A staging environment that mirrors production
– Git version control
– Redis or Varnish for caching
Team Structure:
– At least one developer with Magento/Commerce experience
– A frontend engineer comfortable with Vue 3 and Tailwind CSS
– A DevOps engineer for environment management
– A QA specialist for inventory scenario testing
Inventory Maturity:
Your MSI setup should already be clean. If you’re still using Simple/Configurable products without proper source/stock mapping, pause here and fix that first. Hyvä won’t solve bad inventory data – it will just expose it faster.
Step 1: Environment Setup and Pre-Flight Checks
Start with a fresh staging environment. You’re not patching Luma here.
Verify MSI is active:
You should see these modules ENABLED:
– Magento_Inventory
– Magento_InventoryApi
– Magento_InventorySales
– Magento_InventorySalesApi
– Magento_InventoryAdminUi
Step 2: Installing and Configuring Hyvä
Hyvä comes as a premium theme from its creators. You’ll get access via composer.
At this stage, test the storefront. You should see the Hyvä interface with working product pages. Performance should feel noticeably faster than Luma – that’s your Vue 3 frontend doing its job.
Step 3: MSI Configuration for Multi-Warehouse Operations
This is where multi-warehouse becomes real. You need to map your actual warehouse locations into Magento’s MSI system.
Create Sources (Physical Warehouses):
Via Admin > Stores > Inventory > Sources, create each warehouse:
| Source Name | Code | Country | City | State | Contact Person |
|---|---|---|---|---|---|
| East Coast Fulfillment | us_east_fc | US | Newark | NJ | John Smith |
| West Coast Distribution | us_west_dc | US | Los Angeles | CA | Maria Garcia |
| Midwest Hub | us_midwest_hub | US | Chicago | IL | Robert Chen |
Or via CLI:
Create Stocks (Inventory Collections):
Stocks are logical groupings of sources. You might have a “Default Stock” for B2C and a “Wholesale Stock” for B2B channels.
Link Sources to Stocks:
Assign each source to its stock. A source can belong to multiple stocks.
Configure Sales Channels:
Associate each website/channel with a stock:
Stores > Inventory > Sales Channels > Default Web Site → Link to “Default Stock”
Step 4: Warehouse-Specific Pricing and Shipping Rules
This is where Hyvä’s flexibility shines. You can customize product pricing and shipping per warehouse without custom database extensions.
Pricing Rules by Warehouse:
Create catalog price rules that account for warehouse location. In Admin > Marketing > Catalog Price Rules:
- Create rule: “East Coast Fulfillment Markup”
– Condition: Product Attribute “Fulfillment Source” = “us_east_fc”
– Action: Apply discount/surcharge
For dynamic pricing based on inventory levels:
Shipping Rules by Warehouse:
Configure Table Rates or Flat Rate per source:
- Admin > Stores > Configuration > Sales > Shipping Methods
- Set different rates for each source’s origin location
- Use Magento’s native Shipping Module with warehouse-aware origin addresses
Or implement warehouse-specific shipping via GraphQL:
Step 5: Performance Tuning for Enterprise Scale
Hyvä is fast by default, but multi-warehouse complexity adds moving parts. Optimize aggressively.
Caching Strategy:
Varnish Configuration for Hyvä:
Hyvä plays well with Varnish. Configure cache headers:
Database Query Optimization:
Monitor slow queries during inventory updates:
Lazy Loading Product Data:
Hyvä supports lazy loading by default. Verify in your theme’s product-listing.html:
Step 6: Multi-Warehouse Testing Strategy
This is non-negotiable. One inventory synchronization bug in production costs real money.
Test Scenarios (Priority Order):
| Scenario | Steps | Success Criteria |
|---|---|---|
| Stock allocation with split sources | Order product in high demand. Verify system splits fulfillment across 2+ sources. | Cart shows correct allocation, each source reserves correct quantity. |
| Out-of-stock handling | Deplete all warehouse inventory of SKU. Order from front-end. | Product shows “Out of Stock”, cart prevents addition, accurate backorder option appears. |
| Price variance by source | Configure East Coast 5% markup. Order same product from different regions. | Price reflects source-based pricing correctly. |
| Shipping rate accuracy | Create 3 sources with different shipping origins. Check rates from checkout. | Shipping cost varies correctly by source. No duplicate/conflicting rates shown. |
| Low-stock threshold enforcement | Set threshold to 15 units across all sources. Reduce one source to 10 units. | Threshold only applies to that source, other sources unaffected. |
| Multi-currency by warehouse | Configure USD/EUR pricing by source. Switch currency in store. | Prices and shipping rates convert correctly per source. |
Automated Testing with Magento Functional Test Framework:
Step 7: Frontend Customization for Multi-Warehouse Context
Hyvä’s Vue 3 architecture makes it straightforward to display warehouse-specific information to customers.
Show Warehouse Availability on Product Pages:
Common Pitfalls and How Bemeir Avoids Them
Pitfall #1: Ignoring MSI Until Theme Launch
We’ve seen teams implement Hyvä first, then realize their inventory setup is a mess. Sources overlap, stock assignments contradict themselves, and suddenly your beautiful new theme is serving incorrect availability data.
Solution: Audit MSI completely before theme implementation. We typically spend weeks 1-2 just cleaning inventory structure.
Pitfall #2: Not Planning for Stock Reservation Delays
Multi-warehouse systems introduce latency. When a customer places an order, reservations propagate across sources asynchronously. If you don’t account for this, you get overselling.
Solution: Implement queue-based stock reservations. Use RabbitMQ or AWS SQS to handle async reservation with retry logic.
Pitfall #3: Inadequate Load Testing
You test with 100 products and 3 sources. Then you go live with 50,000 SKUs across 8 warehouses. Suddenly your GraphQL queries timeout.
Solution: Load test with production-scale data. Bemeir uses Apache JMeter with realistic product/warehouse ratios before launch.
Pitfall #4: Missing Source Selection in the Cart
Customers don’t care which warehouse ships their order – until they see a 7-day lead time from the West Coast when the East Coast had 1-day delivery.
Solution: Implement “Select Your Preferred Warehouse” option in checkout. Let them trade cost for speed.
