One-Page Checkout for PrestaShop: Fewer Steps, More Completed Orders

Here is a distinction that trips up most PrestaShop merchants: your store already has a one-page checkout — and it still isn't a "one-page checkout." Since PrestaShop 1.7, the default checkout lives on a single URL. But it reveals itself one step at a time: personal information, then addresses, then shipping, then payment, each section unfolding only after you finish the last. One page, four gates. A true one-page checkout puts everything in front of the customer at once — visible, editable, with a running total that updates as they go. That gap is where orders quietly leak away, and closing it is one of the highest-return changes you can make to a PrestaShop store.

This guide is specifically about getting a genuine one-page checkout onto PrestaShop: what the platform gives you out of the box, why it stops short, and the three realistic routes to the real thing. For the wider science of trimming a checkout — field counts, validation, payment placement — see our full checkout optimization guide.

What PrestaShop's default checkout actually is

PrestaShop 1.7, 8 and today's 9.0–9.1 ship the same default checkout architecture: a single controller (the order controller) that runs a sequence of steps defined in code — personal information, addresses, delivery, and payment. Each step is its own class (you'll see CheckoutPersonalInformationStep, CheckoutAddressesStep, CheckoutDeliveryStep and CheckoutPaymentStep if you ever look under the hood; a virtual cart with nothing to ship simply skips the delivery step). The customer never changes pages, but they do move through gates: a step stays collapsed until the one before it is complete. (PrestaShop 9.2 is changing this with a native one-page option — more on that below.)

For a simple catalogue this is fine. The friction shows up the moment a customer wants to change something — pick a different delivery option after seeing the price, edit an address, apply a code. In the stepped model that often means scrolling back up, re-opening a completed step, and watching sections re-validate. Every one of those moments is a chance to think "this is too much effort."

The one-page toggle PrestaShop used to have — and quietly removed

If you ran a store on PrestaShop 1.5 or 1.6, you may remember the setting under Preferences → Orders called Order process type (the PS_ORDER_PROCESS_TYPE configuration value), which let you switch between a five-step checkout and a one-page checkout with a single click. That toggle was removed in PrestaShop 1.7 (an upgraded database may still carry the leftover config key, but it no longer drives the 1.7+ checkout) when the checkout was rebuilt. So if you upgraded from 1.6 and went looking for "that one-page option" — it's gone, and it isn't coming back in the old form. This is the single most common source of confusion we hear from merchants migrating to 1.7+: the native one-page button no longer exists, and the new default checkout is the stepped single-page flow described above.

What a true one-page checkout changes

A real one-page checkout collapses the gates. Address, delivery and payment sit on screen together, the order summary stays visible, and the total — including shipping — recalculates live as the customer enters a postcode or switches carrier. The psychological effect is the point: there is no "how many more steps?" anxiety because the customer can see the whole finish line at once. Commonly cited studies put the conversion uplift in the 10–30% range versus a multi-step flow; treat that as a directional figure, not a promise — the real number depends on how rough your current checkout is and is something you should measure on your own store (see How to measure below).

Your three routes to one-page checkout in PrestaShop

Because the native toggle is gone, getting a genuine one-page checkout onto a modern PrestaShop store comes down to three options. None is wrong — they suit different situations.

PrestaShop is building a native one-page checkout into the platform — a genuinely positive direction for the ecosystem. If you're weighing "wait or act," we broke down the trade-off in detail in should you wait for native OPC or act now, and what the 9.2 version specifically means in PrestaShop 9.2 native one-page checkout. The short version: if your checkout is leaking orders today, waiting a release cycle (or several, once you factor in upgrade timing) is itself a cost.

Implementing it with Checkout Revolution

The module route exists precisely because most merchants can't wait for a future core release and don't want to pay for custom work that breaks at the next upgrade. Our Checkout Revolution module turns the stepped native checkout into a true single-page flow on PrestaShop 1.6 through 9 — no theme surgery, no core edits, so it survives upgrades. So what does that mean for you? The change customers feel: every section on one screen, a live-updating total the moment an address is entered, guest checkout as the default, and inline validation that flags a bad email as they type instead of after they submit. The change you feel: it installs and configures from the back office rather than a developer invoice, and it doesn't fork your theme. We rebuilt it from the ground up for this — the story is in Checkout Revolution 3.0.

The details that make or break a one-page checkout

Putting everything on one page is necessary but not sufficient. A handful of decisions decide whether that single page actually converts — and each is deep enough to deserve its own treatment, so here's the map rather than a rushed paragraph:

• Guest checkout vs forced registration. Forcing account creation is one of the biggest abandonment causes; make guest the default and offer the account as a one-click add after the order. The data on this is clearer than most merchants expect — see guest checkout vs account creation.
• Mobile. Over half of checkouts happen on a phone, where a one-page layout lives or dies on tap targets, the right input types, and wallet payments. Full treatment in mobile checkout optimization.
• Express and wallet payments. Apple Pay / Google Pay let a returning customer pay with a fingerprint instead of typing a card — covered in express checkout.
• The coupon field. An empty, obvious coupon box sends customers off to Google hunting for a code — and some don't come back. Hide it behind a "Have a code?" link, and pre-apply codes for customers who arrived from a promo link.
• Recovering the ones who still leave. Even a perfect checkout loses some carts; an abandoned-cart email sequence wins a share of them back. See reducing cart abandonment in PrestaShop and the abandoned-cart email automation that does it.

If your checkout is converting poorly and you're not sure which of these is the leak, start with the diagnosis: why your checkout page is losing you sales.

How to measure whether it worked

Don't trust a gut feeling — and don't trust three days of data. Before you change anything, record four numbers from your analytics: cart-to-order conversion rate, checkout abandonment rate (customers who start checkout but don't finish), average time to complete checkout, and mobile-versus-desktop conversion. After switching to a one-page checkout, compare the same four numbers over at least 30 days and 200+ orders — enough volume that you're seeing a real trend, not the natural week-to-week noise that fools merchants into reverting a change that was actually working.

The checkout is the most valuable page in your store: every visitor who reaches it has already decided they want to buy, and your only job is to not get in their way. Whether you wait for native one-page checkout, install a module, or build your own, the principle is the same — fewer gates, less typing, a total that's honest from the first screen. On PrestaShop specifically, that means knowing the native checkout won't get you there on its own, and choosing the route that gets you a genuine one-page flow before the leaked orders add up.