Fewer steps and fewer fields between the basket and the order.
Hyvä Checkout is Hyvä's own checkout for Magento Open Source, Adobe Commerce and Mage-OS stores on the Hyvä theme, fitted in place of Magento's default. For merchants who see shoppers leave at the checkout and want fewer steps, address lookup and a page that responds as it is filled. It is the best checkout Magento has had, and we fit it as a Hyvä Silver Partner.
What merchants see in their analytics before they ask us about the checkout.
People get as far as the checkout and then just leave.
The Baymard Institute puts the documented average at 70.22%. Some of it is browsing; some is the checkout itself, and that part can be fixed.
Our checkout asks for an account before people can pay.
In Baymard's survey, 18% of US shoppers who abandoned an order said the site wanted them to create an account. Guest checkout first.
On a phone, typing the address seems to take forever.
Seven fields, each a chance to give up. Postcode lookup fills them from one, and only the fields your couriers need remain.
Six parts, each in the written plan, from reading your funnel to measuring the result.
Where shoppers leave now, on which device and at which field, read before anything is designed.
One page or a short sequence, only the fields your rules need, styled to your Hyvä theme.
Your providers connected and every method, rule and tax case exercised on staging.
Postcode lookup, sensible defaults, inline validation and errors a shopper can act on.
An account offered after the order, not demanded before it, configured to your policy.
The same funnel read again after the deployment, in writing. No figure promised in advance.
The live store stays untouched until you have tested every payment method yourself.
Send us the store address. A senior engineer reads its release, support status, PHP, headers, hosting and any sign of a hijack.
Within two working daysPayment and shipping providers, tax rules, account policy, B2B modules and where shoppers leave today.
First findings within two working daysHyvä Checkout installed on a copy of your store, laid out to the agreed steps and fields, styled to your theme.
ThroughoutEach payment method, shipping rule, discount, tax case and account flow, on every device size. You place test orders too.
Before the deploymentSwitched live at a quiet hour with the default checkout ready to switch back to; the funnel read again once there is enough data.
A quiet hour agreed with youThe reasons US online shoppers gave for abandoning an order, setting aside the 42% who were only browsing. The ones marked are the ones a checkout can do something about.
Source: Baymard Institute, cart abandonment rate statistics, list last updated 22nd September 2025, read 31st October 2026. Survey of US online shoppers; reasons can overlap.
We price the work, not the clock.
The payment and shipping providers, tax and account rules and any B2B modules decide the work, so we examine the store first and then give you a written plan and estimate. Hyvä Checkout itself is licensed from Hyvä; we arrange the licence for you and show it separately. Later changes can be ad hoc, itemised on a monthly invoice, or part of a retainer.
Hyvä build for dormeo.co.uk and dormeo.ie, with a continuing programme of consent, tracking and security work.
Core Web Vitals, real-user data (Chrome UX Report), mobile, 28 days to 31st October 2026. Marks show Google's thresholds.
We adopted Hyvä when it launched and have built on it ever since. It is now the only frontend we build new Magento stores on.
Recognised by Hyvä for the stores we have delivered, with direct access to Hyvä's own team when a project needs it.
The main content of a Hyvä store on our case pages loads in 1.1 seconds on a phone, measured by Google on real visits.
Yes. Hyvä Checkout is built for stores using the Hyvä theme and shares its stack. If you are on Luma, the migration comes first, and Hyvä keeps Magento's default checkout working in the meantime through a compatibility layer, so the two can be done together or in sequence.
Hyvä Checkout has compatibility modules for many payment and shipping providers, some from Hyvä and some from the providers. We check yours before we estimate. Where a provider has no module, we write the integration or, if the provider is the problem, say so. Every payment method is tested end to end on staging before anything is deployed.
That is the aim, and the honest answer is that we measure rather than promise. Fewer steps, fewer fields, address lookup and a page that responds instantly remove reasons shoppers give for leaving, but the size of the effect depends on where your shoppers leave now. We read your funnel before and after, and will not give you a figure we have not measured on your store.
Yes. Hyvä includes a compatibility layer that keeps the default checkout working on a Hyvä store, and some merchants stay on it. It is slower and harder to change than the rest of a Hyvä store, which is why most move eventually, but there is no obligation and we will tell you if the default is good enough.
Either, and the choice is yours after we have looked at your funnel. Hyvä Checkout can be laid out as a single page or as a short sequence of steps, with fields, order and layout configured rather than hard-coded. We usually recommend the fewest steps your shipping and payment rules allow.
Guest checkout, account creation and logged-in checkout are all supported and configured to your policy. Company accounts, purchase orders and other B2B flows depend on the modules your store uses, so we check each one for Hyvä Checkout compatibility and list it in the plan.
Give us the address and we will read what the store already shows the world: release, support status, PHP, headers, hosting and any sign of a hijack. One page, by email, within two working days. Nothing is accessed or tested.
What we would do first. Apply the outstanding security fixes, then plan the upgrade to a supported release.