Hyvä quietly relaunched its enterprise tier last week, and the rebrand reshapes how a premium Adobe Commerce merchant should budget for a Magento Hyvä build in 2026. Hyvä Enterprise is now an All-Inclusive suite covering every Adobe Commerce surface the licence used to leave out: B2B, Adobe Sensei, content staging, loyalty, gift cards and an Adobe Edge Delivery Services bridge. For studios scoping enterprise-scale or mid-market B2B work on Adobe Commerce, the licence math just got a lot cleaner.
What changed
On 28 May 2026, Hyvä published a news and product post from Thien-Lan Weber, VP of Strategy and Marketing, repositioning Hyvä Enterprise as an "All-Inclusive Suite for Adobe Commerce." The Hyvä Enterprise product page spells out what is now in the box.
The Enterprise licence covers the Adobe Commerce features that Hyvä Theme and Hyvä Commerce historically did not handle out of the box. The B2B Suite is in: multiple wishlists, RMA, account hierarchies. Adobe Sensei is in: Live Search and Product Recommendations both work on the Hyvä storefront without a custom integration layer. Content staging and preview are in. Gift cards, loyalty points, Google Tag Manager and segmentation are in. The integration with Adobe Edge Delivery Services and AEM content management is in.
The pricing is the part that matters operationally. Hyvä Enterprise is €2,500 a year standalone, or €5,500 a year bundled with Hyvä Commerce, the all-in-one tier that pulls Theme, Checkout, UI, Admin Theme, CMS and Image Editor into a single SKU at €3,000. A five-year deal runs at €10,000 for Enterprise alone, €12,000 for Commerce. One Magento 2 installation per licence, unlimited domains and storeviews on the same business entity, non-production environments allowed.
Why this matters for premium studios in Asia
The Hyvä licence stack has been quietly fragmenting for two years. Hyvä Theme, Hyvä Checkout, Hyvä UI, Hyvä Commerce, Hyvä Enterprise, Hyvä Edge: every release added a SKU and another decision in the discovery call. For a Jakarta or Singapore based merchant on Adobe Commerce, the practical effect was a quote sheet that read like an à la carte menu, where procurement had to map their actual Magento usage against a six-line price list before signing anything.
Collapsing Enterprise into a single all-inclusive line removes most of that friction. A merchant who already uses Adobe Sensei Live Search and Product Recommendations no longer has to argue with engineering about whether the Hyvä storefront can integrate them. A merchant on the B2B Suite no longer needs a custom module pass to make wishlists work on Hyvä. A merchant routing AEM content through Adobe Edge Delivery Services no longer has to write the bridge themselves. The features that used to live as bespoke development now ship under the licence.
For our own e-commerce engineering work on Adobe Commerce platforms, this changes the discovery conversation in a useful way. The first question used to be which Adobe Commerce features the merchant actually uses, and which of those engineering will have to port onto Hyvä. The first question now is closer to whether the merchant needs the bundled features at all, and if yes whether they want them by the slice or All-Inclusive. That is a faster road to a number.
Three trade-offs to call out
First, the licence is still per Magento installation, not per merchant. A group with a consolidated Adobe Commerce platform serving multiple brands, several consumer labels sharing one backend, pays one Enterprise licence for the platform. A group with separate installations per brand pays per install. The math leans heavily toward consolidated platforms, which is the direction multi-brand groups have already chosen.
Second, All-Inclusive means everything Hyvä builds for Adobe Commerce, not everything Adobe Commerce ships. Adobe-licensed services outside the Hyvä surface, like Adobe Commerce Cloud hosting or Adobe IO Events, stay separate. So does Adobe's own AEM licence. The Hyvä Enterprise line is the integration layer, not the platform tax.
Third, the Adobe Edge Delivery Services capability is the new entry in the bundle, and it is the one most teams will underestimate. EDS is Adobe's headless content delivery layer, and it is a real piece of infrastructure to wire correctly. The Hyvä Enterprise integration makes it possible without a one-off project, but it does not make the editorial workflow trivial. Plan for an AEM side discovery sprint independently of the Hyvä side wiring.
What we would actually change this quarter
For studios with active Magento Hyvä engagements, three concrete moves.
First, re-quote any in-flight Adobe Commerce migration that was scoped before 28 May. If the proposal included custom work to wire Sensei, content staging or B2B onto Hyvä, that work is now bundled. The honest version of the new quote either removes the line items or repackages them as configuration time, not custom development. Merchants will notice if you do not.
Second, audit Hyvä licence allocation across multi-brand groups. If a large multi-brand group is paying per-brand because the original conversation predated Hyvä Commerce, the consolidation case writes itself: one licence, one Magento install, every brand's storeviews underneath. Most groups will save five-figure annual sums by moving the conversation.
Third, treat the Adobe EDS bridge as a discovery deliverable. Do not bury it in a generic CMS line. Editors who work in AEM, designers who write Hyvä templates, and merchants who decide which content lives where all need a one-page workflow diagram before the first sprint. The licence handles the plumbing. The shop's content operations team has to do the rest.
For Asia based merchants who have always treated Adobe Commerce as a European hand-me-down, this is also the moment to reconsider. The licence is now legible enough to scope cleanly, the storefront is fast enough to compete with Shopify Plus on Core Web Vitals, and the B2B and loyalty surfaces ship with the box. A Jakarta or Manila storefront that needs both a deep catalogue and a serious loyalty programme is no longer a build-it-yourself project. It is a licence call.