Hyvä Checkout for Romanian Stores

The final step is where orders get lost. The customer has chosen the product, reached the cart, and is then asked to work through a long, slow form full of fields they do not care about. Hyvä Checkout exists to shorten exactly that step. This article does not compare gateways, we did that separately in Romanian payments on Magento. This is about what you actually put into the final step for a Romanian store: payments, pickup points, lockers, and what still cannot be done.

What Hyvä Checkout actually changes

The standard Magento checkout is built on Knockout.js and loads as what amounts to a separate application on top of the rest of the store. Even on an otherwise fast store, the last step stays the slow one. Hyvä Checkout rewrites it on the same stack as the rest of the theme, which has two practical effects. The final page behaves like the rest of the store rather than like an island. And changing the checkout stops being the work nobody wants to touch.

The second effect matters more than it sounds. A checkout your team is afraid to edit is a checkout that never gets optimised again.

What it costs, briefly

Checked on 16 October 2026, Hyvä lists it at a one time fee of 1,000 EUR, which includes one year of support and updates and a Hyvä Theme licence, valid for one Magento 2 installation with unlimited domains and store views. From the second year it is 250 EUR per year, or 1,000 EUR once to cover five. If you want the argument about whether it is worth buying, we wrote that separately in what is worth buying from Hyvä. Here we take it as given and look at what you put inside it.

Payments: what goes into the final step

On the stores we run, Hyvä Checkout works with Mollie and with euPlatesc. The difference from an ordinary checkout is not the list of methods, it is where they appear: in the same step, with no intermediate page that looks nothing like the store, and no seconds lost to a redirect that sometimes fails.

The gateway comparison, Netopia and PayU included, and how cash on delivery behaves, are in the payments article. The only thing worth adding here is that a payment method being “supported” and one being tested in production on Hyvä Checkout are not the same claim, and the difference shows itself for the first time on a high traffic day.

Delivery: Cargus pickup points and Innoship lockers

This is where the Romanian difference is sharpest, because a meaningful share of customers do not want home delivery at all. They want a pickup point near the metro, or a locker that is open at ten in the evening. When those options are missing from the final step, the order does not switch to another delivery method. It leaves.

In our checkout setup, Hyvä Checkout shows Cargus pickup points and Innoship lockers inside the final step, as options the customer picks there, rather than as a text field where they type a locker address from memory. Innoship covers several locker networks through a single integration, which means fewer integrations to maintain as new networks appear.

The question worth asking anyone who proposes this: is the list of points updated live, or is it a file imported once? A pickup point that closed permanently and is still offered at checkout produces exactly the kind of order that ends up with support, and then with a return.

What is not there yet: in-store pickup

Worth saying plainly, because it is the gap we run into most often. In-store pickup is not available on Hyvä Checkout yet. If you have physical shops and a share of orders gets collected from the shelf, that is a conversation to have before you move the checkout rather than after. There are ways to work around it, but they are extra work and they get quoted separately rather than included.

The contracts are yours to sign

An administrative point that plenty of launch plans miss. The contracts with the payment provider and with the courier are signed between you and them, not between them and your agency. We integrate and we test, but the commercial approval, the company checks and the commission terms are between you and the provider.

The practical consequence: those approvals run on their own calendar and they will not hurry because you have a launch date. Start them in the first week of the project rather than the last. It is one of the most common reasons a finished store sits and waits.

The fields you ask for, and the ones you should not

Every extra field in the form costs orders, and for Romania the minimum list is shorter than most stores assume: name, phone, email, and a delivery address with county and locality. That is close to all of it. Everything else needs a justification rather than a habit behind it.

What usually gets added without needing to: separate fields for building, staircase and apartment when the address line can hold them anyway, an email confirmation field nobody reads twice, and a compulsory account. Each one looks small on its own. Together they turn a thirty second step into a two minute one, on a phone, on the metro.

What gets added for good reason, but conditionally: company invoicing details. A B2B buyer needs the company name, the VAT number, the registration number and the registered address. A consumer needs none of them. Ask everyone for all of it and your form is built for the business buyers and paid for by everybody else. A person or company toggle that reveals those fields only when they apply is one of the cheapest conversion improvements available in a checkout.

The account the customer never asked for

Compulsory registration is the oldest way to lose an order. The argument for it is that an account gives you a returning customer. In practice a customer who abandons at the registration step gives you nothing at all, and their email address never reaches your database either.

The version that works: guest checkout, with the account offered after the order is placed, when the customer finally has a reason to want one, which is to follow the delivery. Hyvä Checkout does not decide this for you. It is a setting and a business decision, but it is worth making deliberately rather than inheriting it from the old store's configuration.

The amounts that show up late

The second cause of abandonment, after the long form, is a number that changes. The customer sees a price in the cart, reaches the final step and finds a delivery cost they were not expecting. It does not matter that it is calculated correctly. What matters is that they learned it after doing the arithmetic in their head.

Hyvä Checkout does not fix this on its own, because it is a configuration problem rather than a theme one. What you can do concretely: show the delivery cost in the cart and not only in the final step, show the threshold at which delivery is covered while the customer can still add products, and if you charge a fee for cash on delivery, put it next to the payment method rather than at the end. The working rule is simple. Any amount a customer discovers after entering their details reads as a surprise.

How you will know whether it worked

Before you change the checkout, write down three numbers: cart abandonment rate, completion rate on phones kept separate from desktop, and median time from cart to confirmation. If you do not have them now, you will not be able to say afterwards whether the change helped or whether it was simply a better month.

Measure the same window before and after, and avoid comparing a campaign month against an ordinary one. Most of the disappointment people report with a new checkout comes from never having had a baseline, not from the checkout.

What to test before Black Friday

A real order, with a real card, on a phone, on every payment method you offer. A sandbox test does not prove the payment clears in production.
One order to a pickup point and one to a locker, then check that the right address reaches the waybill and not only the order.
A declined payment. What the customer sees when a card is refused decides whether they try again or leave.
The checkout on a slow connection. Throttle a phone to simulated 3G and walk the whole step, from cart to confirmation.
What happens when a pickup point stops being available between the moment of the order and the moment of dispatch.

The next step

If you already run Magento and the final step is where you lose orders, the first question is not which checkout to buy. It is where people are leaving right now. Book 30 minutes and we will look at your final step, the payment and delivery methods you offer, and what Hyvä Checkout would concretely change for your store.