Summary
Key takeaways
- Hyvä’s Linked Products feature lets a color swatch take shoppers to a separate product page. Each color can keep its own photography, stock, reviews and URL.
- Linked Products went into beta on July 28, 2026 and reached general availability 76 days later in Hyvä Commerce 1.4. Follow-up releases on November 2 and 3 refined group behavior and permissions.
- A feature that looks simple in a demo still has consequences for catalog operations, accessibility and what search engines can discover.
- Before adopting a feature, read its history from first release to the current patch, then test the workflow with the people and data that will actually use it.
- Merchant needs reach the Hyvä team through public GitHub repositories, partner requests and upvotes in GitLab, and the public roadmap. Each release changelog shows what actually shipped.
- The general availability release added bulk transfer tools, a storefront switch, warnings for products shoppers cannot reach and safer group saves.
- Retailers need three decisions: which products deserve separate pages, who owns group membership, and how each page behaves for shoppers, catalog editors and search crawlers.
- When variants live on separate URLs, review product group identifiers, variant URLs, structured data and the product feed as part of the release.
- A useful feature request is reproducible. It names the SKUs, the store view, the expected swatch destination, what should happen when stock or visibility changes, and the edition and versions in scope.
- Separate what belongs to the shared Hyvä product from what belongs to the merchant’s own integration, such as stock and image data from internal systems.
When this applies
This guidance is for Magento merchants and implementation teams on Hyvä who are evaluating new Hyvä Commerce features such as Linked Products, or who want to raise their own needs with the Hyvä team. It is most relevant for catalogs where colors or other variants work better as separate product pages with their own images, inventory, pricing or campaigns, and where several people or integrations maintain the same product records. Merchandising, catalog, SEO and engineering teams can use it to decide when a roadmap item is ready to budget, how to test it under production roles and data, and how to write a feature request the maintainers can reproduce.
When this does not apply
Linked Products adds little for stores where variants are better served as options on one configurable product page, for example when colors share photography, stock and reviews. The guidance is also less relevant for merchants that are not on Hyvä Commerce or do not plan to use its paid features. A roadmap entry on its own is not a basis for a budget or a launch date. Teams should wait for a generally available release and check the current patch before committing. Store-specific needs, such as moving stock or images from internal systems, also belong in the merchant’s implementation scope rather than in a shared product request.
Checklist
- Identify which product variants have their own photography, inventory, pricing or campaigns and genuinely need separate pages.
- Confirm the Hyvä Commerce edition and the first generally available version that includes the feature.
- Read the changelog from the beta through the latest patch, paying attention to permission and group behavior changes.
- Assign an owner for group membership and decide which system supplies stock and price.
- Set up the editor, reviewer and administrator roles you plan to use in production.
- Create a product group on staging and confirm that the swatch leads to the correct page in the same store view.
- Test bulk transfer of groups and check that the intended relationships are kept.
- Make one linked product unavailable and check that the storefront follows your agreed policy.
- Test the case where a product becomes the only remaining member of a group.
- Check the swatch and both product pages for keyboard access and screen reader labels.
- Review product group identifiers, variant URLs and structured data on each separate page.
- Align product feed attributes with the page data for the same product records.
- Crawl the linked pages to confirm search engines can discover them as intended.
- Separate the shared feature need from store-specific integration work and assign each to the right owner.
- Write any feature request as a reproducible scenario with SKUs, store views, expected results and versions in scope.
Common pitfalls
- Judging a feature from a demo without reading how it changed between beta and the current patch.
- Budgeting or setting a launch date from a roadmap entry instead of a generally available release.
- Splitting every variant into a separate page when the colors share images, stock and reviews.
- Leaving group membership without a clear owner, so editors and integrations overwrite each other.
- Testing with an admin account instead of the roles the catalog team will use.
- Forgetting to define what shoppers see when one linked product goes out of stock or is hidden.
- Assuming bulk data transfers keep product group relationships without checking them.
- Skipping structured data and feed checks for variants that live on separate URLs.
- Submitting vague feature requests without SKUs, store views, expected outcomes or versions.
- Asking the shared product to solve store-specific integration needs that belong in the implementation.
A retailer wants its navy jacket and red jacket to have their own pages. Each color has its own photography, stock and reviews. A shopper who arrives on the navy page still expects to select red without starting a new search. Hyvä’s Linked Products feature answers that request with a swatch that links to a separate eligible product page. It is a small piece of interface with consequences for catalog operations, storefront accessibility and what a search engine can discover. Hyvä Linked Products documentation
The Hyvä team released Linked Products in beta on July 28, 2026. It reached general availability 76 days later in Hyvä Commerce 1.4. Two follow-up releases arrived on consecutive days in November, refining group behavior and permissions. The product looked simple in a demo. The changelog gives merchants a view of the work needed to make it dependable when several people and integrations maintain the same catalog. Linked Products changelog · Hyvä Equinox
Elogic Commerce recommends following a Magento feature from its first release to the current patch, then trying the workflow with the people and data that will use it. The case for adoption becomes stronger when the swatch works for the shopper and the catalog team can keep every linked item correct.
The people and the channels behind Hyvä
Willem Wigman created Hyvä Theme. Hyvä lists Vinai Kopp as technical director and partner with a focus on developer experience, tooling and education. Thien-Lan Weber leads strategy and marketing. Sanne Bolkenstein leads sales and partnerships. Those roles have visible points of contact with merchant needs. In the Magento Association’s 2026 interviews with Matt Harris, Wigman describes starting Hyvä and discusses the decision to release the theme as open source. Hyvä had announced that change on November 6, 2025, and made the source freely available starting November 10. Hyvä team · Founder interview · Open-source strategy interview · Hyvä announcement
Merchant input has several routes. Hyvä documents public GitHub repositories for the open-source theme and explains how contributors can bring confirmed issues and code changes to the team. Official agency partners can also raise requests and collect upvotes on issues in the relevant GitLab repositories. Public roadmap entries describe direction. Each release changelog tells the merchant what actually shipped. Source code and contributions · How partners can influence the roadmap · Hyvä roadmap
In a July 2026 LinkedIn digest, Hyvä credited Andreas von Studnitz and Willem Poortman with contributions to Magento Bricklayer. That post identifies contributors to one project. The public changelog for Linked Products documents the dates and changes in another. Its initial request and internal prioritization remain unreported in that record. Hyvä’s July community digest
Hyvä said in its 2025 business review that more than 6,400 websites across 81 countries were selling with Hyvä as of January 2026. That is a dated company figure. It gives some scale to the audience behind apparently narrow requests. A choice about product-group imports, for instance, has to work for stores that manage their assortment by hand and teams that regularly transfer catalog records between systems. Hyvä business review
What changed between a swatch demo and a release
The October version added bulk transfer tools, a storefront switch and warnings for products shoppers cannot reach. It also made group saves safer. The early November versions refined what happens when a product is the sole remaining member of a group and updated the permissions around managing or transferring groups. For a catalog lead, those details dictate who can change a group and whether a data transfer preserves the intended relationships. 1.0.0 and maintenance release notes · Hyvä Commerce 1.4.1 upgrade notes
That leaves three practical decisions for a retailer. First, decide which products genuinely merit separate pages. A color with its own photography, inventory and pricing can be a meaningful destination. Second, assign an owner for group membership. A merchandising team may set it in the admin while the catalog integration supplies stock and price. Third, test both pages as a shopper, a catalog editor and a search crawler. When one item becomes unavailable, the storefront should follow the merchant’s policy for showing or removing its path.
Google documents variant structured data for both single-page and multi-page configurations. When the business uses separate URLs, review product group identifiers, eligible variant URLs and the pages’ product data as an explicit part of the release. Align the feed and page attributes to the same product records. A native storefront control and a healthy product feed are two checks the catalog owner can sign off. Google product variant guidance
The work can be more specific than any shared module. Elogic Commerce moved FlexShopper’s US electronics marketplace from Luma to Hyvä in about three months ahead of Black Friday, with project work spanning dynamic vendor pricing and Best Buy pickup as well as the storefront and checkout. That case shows why a release decision starts with the catalog and operating model of the merchant in front of you. Elogic Commerce FlexShopper case
Turn a roadmap request into something engineers can test
A useful feature request starts with a transaction or a workday. Give the maintainers a precise example of a shopper going wrong or an editor doing repeated work. For separate color pages, show two or three SKUs, the storefront each should appear in, the place the swatch should lead and the expected outcome when stock or visibility changes. Identify which edition and versions are in scope. The request is easier to evaluate when the product team can rerun it.
| What a merchant can provide | A useful example |
|---|---|
| A repeatable buyer task | A shopper arriving on the navy SKU switches to red and reaches the correct product page in the same store view. |
| The commercial reason | The colors have independent photos, inventory and merchandising. A campaign links directly to the featured color. |
| The operating context | The editor groups products. The catalog integration owns price and stock. Only the catalog team maintains group membership. |
| The expected result when data changes | A discontinued item follows the retailer’s agreed storefront policy and the remaining items still behave correctly. |
| The decision a release must support | The team can create, review and transfer the group under its production roles, and the shopper journey passes on staging. |
What can merchants ask their implementation team to do?
Ask which parts of the request concern the shared Hyvä product and which belong to the merchant’s integration. For Linked Products, group behavior belongs in the product evaluation. Moving stock and image data from a retailer’s own systems belongs in the implementation. A partner can submit the shared need with a reproducible scenario while preparing the store-specific work in parallel. Elogic Commerce Hyvä development
When should an ecommerce team act on a roadmap item?
A roadmap can tell the team what to follow. For budgeting and a committed date, identify the product edition, the first generally available version and any dependency in the current patch. Linked Products moved from beta to a production release, then adjusted permissions and group behavior soon afterward. Read all three stages when the feature touches a catalog several teams update. The same discipline is useful when reviewing an Adobe Commerce implementation.