Custom address fields at checkout have always been one of Magento's most frustrating contradictions. The platform's Entity-Attribute-Value (EAV) architecture is famously flexible: you can define virtually any attribute on a customer or address entity through the admin panel. But actually rendering those attributes in the checkout, validating them properly, and ensuring they survive upgrades? That is where most Magento merchants hit a wall.
On 3 August, Hyvä released Checkout 1.4.0-beta3, and among its changes is one that should matter to every Magento merchant running B2B, wholesale, or any operation that needs structured data collection at checkout: native support for rendering and validating custom EAV attributes in checkout address forms.
What actually changed
Hyvä Checkout now supports seven frontend input types for custom address attributes: Text Field, Text Area, Date, Dropdown, Yes/No (boolean), Multiple Select, and Multiline. Each field type ships with its own validation rules, and Dropdown and Multiple Select fields automatically preselect their configured default values.
The implementation is deliberately scoped. Only attributes associated with the customer_register_address form, as defined in Magento's customer_form_attribute table, are rendered on the storefront. Everything else stays hidden. This means merchants control visibility through Magento's existing attribute configuration, not through theme-level overrides that break on the next upgrade.
The release also includes two data patches that handle the migration from Hyvä Checkout's legacy address form configuration to the new structure. Each scope, default, website, and store, is migrated independently, so a failure in one does not cascade.
Why this matters more than it sounds
If you have worked with Magento checkout customisation, you know the pain this addresses. The standard approaches have historically involved writing JavaScript, layout XML, and PHP plugins to inject fields into the Knockout. js-based Luma checkout (fragile and upgrade-hostile), adding another third-party extension dependency, or moving custom data collection to order confirmation emails (which reduces completion rates). None of these are good options for B2B merchants who genuinely need to collect purchase order numbers, tax exemption IDs, delivery instructions, or custom identifiers at the point of sale.
Hyvä Checkout's approach is different because it treats Magento's own EAV system as the source of truth. You define the attribute in the Magento admin. You assign it to the right form. Hyvä Checkout renders it, validates it, and stores it, with no custom theme code required. If Magento adds a new frontend input type in a future release, Hyvä's architecture is positioned to support it without merchants rebuilding their checkout customisations.
The B2B implications
For B2B merchants on Magento, checkout customisation is a requirement, not a nice-to-have. B2B transactions routinely involve purchase order numbers that must appear on invoices, cost centre codes for internal allocation, VAT identifiers, delivery window preferences, and custom reference fields that map to buyer procurement systems.
Until now, collecting these at checkout on Hyvä required custom development work. That work created upgrade debt: every Hyvä Checkout update required testing and potentially reworking the customisation. For agencies managing multiple Magento builds, this upgrade friction multiplied across every client.
With native EAV support, the maintenance burden shifts to Hyvä. The attribute definition lives in Magento's database, the rendering logic lives in Hyvä's codebase, and the merchant's theme stays clean. That is a meaningful reduction in total cost of ownership.
The progress overlay is worth noting too
The same release introduces a reusable progress overlay for blocking checkout actions, a full-screen spinner with title and message that prevents user interaction during redirects such as SSO authentication or payment gateway handoffs. When a checkout redirect takes more than a couple of seconds, customers who do not see clear feedback often click away or try again. The fact that Hyvä has made this a reusable component means it is available to any payment integration or checkout extension built on Hyvä Checkout.
What merchants should do now?
This is a beta release, not a production recommendation. Hyvä released it across two lines, 1.4.0-beta3 for the current track and 1.3.1000-beta1 as a backport, which suggests they want broad testing before a stable release.
-
If you are planning a new Magento B2B build, this beta is worth evaluating in a development environment now. Understanding how it works before the stable release means you can architect your attribute definitions correctly from the start.
-
If you are running Hyvä Checkout in production with existing custom field implementations, do not rush to adopt the beta. But do start planning your migration path. When the stable release arrives, moving from custom checkout components to native EAV rendering will reduce your upgrade friction and simplify your codebase.
-
If you are evaluating Magento for a B2B project, this release strengthens the case for Hyvä Checkout specifically. The checkout customisation gap that previously pushed some B2B merchants towards custom or third-party solutions is closing.
The bigger picture
Hyvä's development trajectory has been consistent: take capabilities that Magento supports architecturally but that require custom development to use effectively, and make them native, upgrade-safe, and accessible through standard configuration. The AI module suite, the CMS Tailwind JIT improvements, and now checkout EAV support all follow this pattern. Each release reduces the total cost of running a Magento store and makes the platform more competitive against solutions where these capabilities are built in from the start.
About On Tap
On Tap is a growth-focused eCommerce consultancy and Hyvä partner, specialising in Magento and Adobe Commerce implementations for mid-market and enterprise merchants. From Hyvä Checkout configuration and B2B commerce architecture to custom EAV attribute design and upgrade planning, On Tap helps merchants get the most from Magento's flexibility without the maintenance overhead.
If you want to evaluate Hyvä Checkout's EAV support for your B2B build, get in touch.
