Summary
Key takeaways
- To judge Hyvä Commerce, time the whole campaign job: ordering products, building the landing page, testing the form and handing shoppers a working storefront. Editing speed alone is not enough.
- Hyvä Commerce 1.4, released as Equinox in October 2026, made Category Merchandiser, Form Builder, advanced admin permissions and visual email tools generally available. The suite also includes Hyvä CMS, Checkout and UI.
- Hyvä listed the yearly Commerce subscription at €3,000 on November 20. At a loaded rate of €60 an hour, a team needs to save 50 hours a year to cover it in labor capacity alone.
- The Category Merchandiser grid can show status, visibility and price for a selected store view, but product inclusion and manual sort order are global. A different order per market has to be tested explicitly.
- Compare both environments on equal terms: the same catalog snapshot, copy, assets, market and definition of done, done by a merchandiser with the permissions they will have after launch.
- Record active editing time, elapsed time to publication and any time engineers or administrators contribute, so you can tell a fast editor from a slow approval or a development dependency.
- Annual capacity value equals campaigns per week, times campaign weeks, times hours saved per campaign, times the loaded hourly rate. Compare it with the incremental subscription, support and setup costs.
- At four campaigns a week for 48 weeks, a team needs about 16 minutes saved per campaign to cover the €3,000 subscription and about 22 minutes to cover an illustrative €4,200 first year.
- Case studies such as a 75-day storefront launch describe whole projects. They do not measure minutes saved on recurring campaign work, which you need to measure in your own store.
- The best candidates publish campaigns every week, reuse campaign patterns and can give editors the right role. Regional retailers should test category scope and language output before applying the same estimate to every market.
When this applies
This guidance is for Magento merchants on Hyvä, or moving to Hyvä, who are deciding whether to pay for Hyvä Commerce to speed up campaign work. It fits ecommerce and marketing teams that publish campaigns weekly or more often, reuse landing page and category patterns, collect leads through forms and need clear editor, reviewer and administrator roles. It also helps teams build a finance case, because it turns a timed staging test into an annual capacity value that can be compared with the subscription, support and setup costs. Multi-store and multilingual merchants can use the scope checks to find out early whether global category ordering fits their regional promotions.
When this does not apply
The investment is harder to justify for merchants that run only occasional campaigns, because even large time savings per campaign may not cover the license. It is also a poor fit when campaigns need different category orders in each market and global sorting cannot meet that requirement without workarounds. Stores whose pages depend on custom Page Builder elements or forms that feed a CRM should not assume those carry over, since recreating components and integrating lead handoffs can add one-time costs. The pricing, release features and example figures reflect the article’s date and assumptions. Confirm current terms with Hyvä and use your own campaign volumes, hourly rates and timing data.
Checklist
- Set up two staging environments with the same catalog snapshot, approved copy, assets and target market.
- Write a definition of done that covers category order, the landing page, the form and storefront verification.
- Assign a merchandiser with the exact permissions they will have after launch.
- Give each tool the same short practice run, and have a second operator repeat the task in reverse order if possible.
- Time ordering 12 products to match the campaign brief, and check adjacent storefronts that share the category.
- Time publishing the landing page with approved structure, copy, links and images on desktop and mobile.
- Add a lead form and confirm that a test entry reaches the right destination and the shopper gets the correct acknowledgment.
- Have a second reviewer verify the storefront and practice restoring the previous content or category order.
- Record active editing minutes, elapsed time to publication, approval waits, rework and engineering or admin help.
- Test category scope for multi-store setups, keeping in mind that inclusion and manual order are global.
- List which existing Page Builder elements and templates can be reused and which need one-time rebuilding.
- Test editor, reviewer and administrator roles, including the permission changes in the 1.4.1 release.
- Calculate annual capacity value from campaign volume, minutes saved and loaded hourly rates for each contributor.
- Compare that value with the incremental subscription, support and setup costs, taking existing entitlements and renewal dates into account.
- Agree on a target in minutes saved per campaign, have ecommerce operations and engineering approve it, and decide what the recovered time will be used for.
Common pitfalls
- Timing only the editing step and ignoring approvals, verification and dependencies on developers.
- Running the test with an admin account instead of the role the merchandiser will actually use.
- Assuming a store-view price preview means category order can differ by market, when sorting is global.
- Comparing environments that use different catalogs, assets or definitions of done.
- Expecting existing Page Builder components and custom forms to work without rebuilding or integration work.
- Building the case on case-study launch timelines instead of measured minutes saved per campaign.
- Comparing the value against the full suite price when part of the bundle is already licensed.
- Leaving one-time setup out of the first-year cost.
- Claiming revenue gains from faster content without logging missed email or inventory windows.
- Applying one savings estimate to every market without testing regional category and language output.
A campaign deadline exposes where a commerce platform slows down the people who run it. Somebody has to put the right products first, build the landing page, test the form and hand the customer a working storefront. When a team compares Hyvä Commerce 1.4 with its current Magento workflow, Elogic Commerce recommends timing that entire job. The value includes what the editor can publish and how quickly someone else can resolve a dependency.
Hyvä’s October 2026 Equinox release made Category Merchandiser, Form Builder, advanced admin permissions and visual email tooling generally available in Hyvä Commerce 1.4. The suite also includes Hyvä CMS, Checkout and UI. The theme itself is available separately. Hyvä listed the yearly Commerce subscription at €3,000 when we checked on November 20. At a loaded €60 an hour, a team would need to save 50 hours a year to cover that subscription in labor capacity alone. Hyvä Equinox release · Hyvä Commerce pricing
One workflow detail can change the purchase decision. The Category Merchandiser’s grid can show status, visibility and price for a selected store view. Product inclusion and manual ordering are managed at global scope. A business that needs the same category in different orders across markets should test its category structure and workflow explicitly. The ability to see local prices in the editor tells you something useful about the preview. The global sort tells you what publishing will do. Category Merchandiser scope
Make the campaign realistic enough to price
Set both staging environments up with the same catalog snapshot, approved copy, assets, shopper market and definition of done. Ask a merchandiser to run the workflow using the permissions they will have after launch. Give each tool the same short practice run. Have a second operator repeat the task in the reverse order if staffing allows. Record active editing, elapsed time to publication, and time contributed by engineers or administrators. Those measures help identify a fast editor, a slow approval or a dependency on development.
| Task | Standard to meet | What to record |
|---|---|---|
| Put 12 products in order | The first 12 items match the campaign brief for the intended market. Check adjacent storefronts when they share the category. | Active edit minutes, time to verify storefront output and any unintended market change. |
| Publish the campaign page | Landing page uses the approved structure and shows the correct copy, links and imagery at desktop and mobile widths. | Active edit minutes, assistance required and time from brief to approved page. |
| Add a lead form | Test entry reaches the destination the business uses and the shopper gets the correct acknowledgment. | Setup and verification minutes, any integration work and access needed to inspect the entry. |
| Rehearse release and recovery | A second reviewer verifies storefront output. The operator can restore the agreed previous content or category order. | Approval wait, defects, rework and recovery steps. |
The standard Magento workflow should use the retailer’s normal CMS, Page Builder and installed extensions where appropriate. Hyvä CMS can coexist with Page Builder and Magento’s editor. Verify which existing page elements can be reused and identify one-time work for recreating approved components. The Form Builder can handle forms inside Hyvä CMS. A lead handoff into a CRM deserves its own end-to-end test and any implementation cost that applies. Hyvä CMS guidance · Form Builder configuration
Verify permissions on the editor roles you actually intend to grant. Hyvä Commerce 1.4 introduced scope restrictions and more precise administration permissions. Its 1.4.1 release includes changes across seven modules, with explicit guidance for checking role access. Put an editor, a reviewer and an administrator through the applicable scenarios so the workflow works on a normal trading day. Advanced Admin Permissions · Hyvä Commerce 1.4.1 upgrade notes
Calculate the number that matters for the budget
Estimate annual capacity value by multiplying campaigns per week by campaign weeks, then by minutes saved per campaign divided by 60 and your loaded hourly rate. Where people with different hourly rates contribute, calculate their time separately and add the amounts. Compare the annual value with the incremental subscription, ongoing support and relevant setup. A merchant already paying for parts of the bundle should use the change in cost after reviewing entitlement and renewal dates.
| Campaign load | Time saved | Annual capacity value at €60 an hour |
|---|---|---|
| 2 per week for 48 weeks | 12 minutes per campaign | 19.2 hours and €1,152 |
| 4 per week for 48 weeks | 20 minutes per campaign | 64 hours and €3,840 |
| 8 per week for 48 weeks | 20 minutes per campaign | 128 hours and €7,680 |
Four campaigns per week at 20 minutes saved would clear the €3,000 annual license by €840 in modeled capacity value. Against the illustrative €4,200 first-year total it would fall short by €360. At that volume, set a target of at least 16 minutes per campaign for the subscription and at least 22 minutes for year one. A team that publishes several campaigns a week can use recovered time on creative work, more tests or fewer externally billed interventions. The finance case should specify which it expects.
Keep revenue sensitivity grounded in the retailer’s own data. If a one-day approval delay repeatedly sends a launch past an email or inventory window, put that timing into the campaign log. A documented missed trading window is a better starting point than a generic claim about faster content increasing sales.
Read the case studies at the scale they measure
Scandiweb used Hyvä Commerce and Hyvä CMS for ATX Fitness’s first US direct-to-consumer store. The agency describes easier content editing and more flexibility for marketing pages. In a public LinkedIn post, scandiweb said the storefront went from zero to launch in 75 days. That number describes a full project with design, extensions and checkout work. It is useful evidence that the software shipped with a real merchant. Minutes saved on recurring campaign tasks are best measured directly in your store. ATX Fitness case study · Scandiweb LinkedIn project post
The product announcements and practitioner coverage make a good test inventory. Foundation Commerce highlights category sorting, scoped roles and visual email tools. Ecomwise details how a merchandiser can change a product position in the admin and preview the grid. Simon Sprankel’s LinkedIn recap of an earlier release flagged CMS templates and snippets and the growing role of admin tooling. The useful extension for a buyer is a controlled comparison on a live-shaped catalog. Foundation Commerce Equinox recap · Ecomwise release analysis · Simon Sprankel’s release notes
Who is most likely to recover the cost
Start with a merchant that publishes weekly, maintains reusable campaign patterns and can give editors the right role. It has enough work to measure and a chance to turn saved minutes into capacity. A retailer with separate regional promotions needs to test category scope and language outputs before using the same value estimate in every market. Elogic Commerce suggests setting a target in minutes per campaign and asking both ecommerce operations and engineering to approve it. Elogic Commerce ecommerce consulting
Can Hyvä Commerce replace our current page editing workflow
It can change the day-to-day workflow where its components cover the store’s pages and forms. Inventory the existing templates, parts of Page Builder you depend on and any custom data destinations. Rebuild a representative campaign on staging and export the content or retain the revision your team needs for recovery. A Magento build or retrofit can incorporate that acceptance work in the Hyvä development scope and test it in the multi-store ecommerce setup.