One-page or multi-step checkout in PrestaShop: which fields to drop and when to use 1-click

Every so often someone suggests switching the checkout to «a single page» because it converts better. Sometimes it improves, sometimes nothing changes and sometimes it gets worse. What decides whether a customer completes the purchase is not so much the number of screens as the number of decisions, fields and surprises they find along the way.

What the PrestaShop checkout looks like

Since 1.7, the PrestaShop checkout has been a single page divided into blocks that open in order: personal information, addresses, shipping method and payment. It is a hybrid: it does not reload the page between steps, but it requires each block to be completed before the next one. Themes and third-party checkout modules change that structure, for better or worse.

One page or steps: what really changes

With few fields, a single page works well. With many, steps bring order. Before changing the structure, it is more worthwhile to reduce what you ask for.

The fields that are usually unnecessary

• Title (Mr/Mrs) and date of birth. If you do not use them for anything specific, remove them. In PrestaShop, the date of birth is disabled in the customer settings, and address fields are adjusted per country in its address format.
• Mandatory password. Allowing guest checkout and offering to create the account at the end keeps first-time buyers on board.
• Repeating the email. Better to validate the format and display it clearly in the confirmation.
• Company and tax ID for everyone. They are only needed if the customer wants an invoice in a company's name. Show them when the customer asks for it.
• Mandatory second address line. Always optional.
• Separate billing address without a «use the same address» checkbox.

Some fields look unnecessary but are not: almost every carrier requires the phone number, and removing it is paid for in delivery incidents. The postcode needs to come before the city if you want to calculate shipping early.

The surprises that make people abandon

The most frequent cause of checkout abandonment is discovering an unexpected cost, usually shipping. Show it as early as possible, ideally in the cart with an estimate.

And there are also rules to follow here. Spanish consumer law (Royal Legislative Decree 1/2007, the consolidated General Law for the Defence of Consumers and Users, article 60 bis) requires the customer's express consent for any payment in addition to the main one: no pre-ticked boxes that add insurance, a warranty or a donation. And article 98.2 requires the final button to make clear that the order involves paying, with wording such as «Order with obligation to pay» or an equally unambiguous equivalent. A «Continue» on the last step is not enough.

Errors that show up too late

• Validations that only fire when the final button is pressed.
• Messages in English or generic ones («Invalid field») that do not say what is wrong.
• Rigid phone or postcode formats that reject what the customer types with spaces.
• Payment methods that fail on mobile because the module was not updated along with the theme.

That last one is more common than it seems. A checkout that mixes a new theme, old payment modules and a PHP version they were never tested on breaks in the worst place, and does so without warning. Keeping PrestaShop and the payment modules up to date, and testing a complete purchase after every update, is part of looking after conversion.

When one-click buying makes sense

One-click buying lets the customer pay without going through the whole checkout. It works well when:

• The product sells itself, without much configuration.
• A large share of visits come from mobile.
• There is impulse buying or the customer already knows the product.
• The customer is a repeat buyer and does not want to fill in their details again.

It is a worse fit for B2B orders with many lines, for customisable products or when shipping depends heavily on the address. In that case there is a useful variant: asking for the address after payment. It works as long as shipping is recalculated when the address arrives, and the store does not use an existing customer's account without them logging in.

Offering something extra without getting in the way

The checkout is also a good moment to offer an add-on: the customer has already decided to buy. The condition is that it does not get in the way: a single offer related to what is in the cart, which can be added or removed with one click without leaving the process and which is never ticked by default.

Measure before you change

GA4 has events for each stage: begin_checkout, add_shipping_info, add_payment_info and purchase. With them you can see at which step customers are lost before touching anything, and compare after the change. Without that measurement, any checkout redesign is just an opinion.

Checklist

• Remove the fields you do not use and make optional the ones that are not essential.
• Guest checkout enabled.
• Shipping cost visible before the last step.
• No pre-ticked box that adds a charge.
• Final button with «obligation to pay» or an equally clear wording.
• A complete test purchase on mobile after every update.
• GA4 funnel measured before and after each change.

How to solve it in PrestaShop

RKR Compra en 1 clic adds a button on the product page, the cart and product listings that opens a modal with name, email, DNI/NIE (Spanish ID number), phone and a note. The address can be typed there, chosen from saved ones or left until after payment: the customer completes it from a portal through a link that expires or from their account, and shipping is recalculated with PrestaShop's native rules. If the email already belongs to a registered customer, it asks them to log in, and you can limit the button to the categories where it makes sense. RKR Buy More Pro places an offer in the cart, in the shipping step or in the payment step, which the customer accepts or removes with one click; if the conditions are no longer met, the discounted line is removed automatically, and an A/B test tells you which variant works.