WooCommerce CRO Technique

Is one-page checkout better than multi-step for WooCommerce?

This technique is about making WooCommerce checkout feel shorter and safer to complete, whether that ends up being one page or a very short multi-step flow.

Summary

Bottom Line: One-page checkout is not automatically better than multi-step in WooCommerce.

  • Baymard’s research does not support “one page always wins”; it says checkout effort is driven more by visible fields and overall complexity than by the number of screens alone.
  • A multi-step WooCommerce checkout can perform well if it is truly linear, maps 1:1 to the real steps, preserves entered data, and uses button text that says exactly what happens next.
  • WooCommerce Checkout Blocks already give you a cleaner default structure, section numbering options, and block-level editing, but only block-compatible gateways and extensions will appear and behave correctly.
  • Classic shortcode checkout is more flexible for legacy hooks and field-editor plugins, but that flexibility also makes redirect-heavy, accordion-style or repeat-page experiences easier to get wrong.
  • Plugin-led one-page checkout should be treated as a checkout replacement project, not a cosmetic tweak: QA the gateways, taxes, shipping, tracking, mobile behaviour and HPOS compatibility before rollout.

How To Implement

  • Baseline the existing funnel before changing layout

    In GA4, confirm that begin_checkout, add_shipping_info, add_payment_info, and purchase are firing. Then review Reports → Monetization → Checkout journey and break it down by Device category. Use Explore → Funnel exploration if you need a custom sequence, direct-follow conditions, or additional segment comparisons. Measurement note: capture at least 2–4 comparable weeks before launch, and keep a separate mobile readout because device-level behaviour is often where checkout friction becomes visible first.

  • Identify whether your store is using Checkout Blocks or classic shortcode checkout

    For stores started after WooCommerce 8.3 in November 2023, Cart and Checkout Blocks are the default. Check the Checkout page in Appearance → Editor → Pages → Checkout on block themes, or Pages → All Pages → Checkout on non-block themes. If you need to revert a block checkout to the classic version, select the Checkout block and use Transform → Classic Shortcode; WooCommerce advises doing the same for Cart so the pair stays aligned. The classic checkout page itself is the [woocommerce_checkout] shortcode.

  • If you use Checkout Blocks, simplify the native block before you replace it

    In the Checkout page editor, keep the structure tight around the native Checkout block, which contains Checkout Fields and Checkout Totals. In the block settings for Checkout Fields, use Form Step Options if numbered sections will make the flow easier to scan, and make sure optional fields are genuinely optional or hidden where appropriate. WooCommerce documents block-level controls for items such as Company, Address line 2, and billing/shipping phone and address visibility. Also remove any non-essential blocks or content that lengthen the form without helping completion.

  • Keep the Blocks checkout linear and distraction-free

    Do not add newsletter forms, pop-ups, overlays, cross-sells or mid-flow promotions into the checkout template. Baymard’s checkout and payment research is clear that checkout should stay focused, linear and predictable, and that distractions at payment or mid-flow are conversion risks rather than merchandising opportunities. If you are relying on a gateway or extension, check the Payment Options block and the extension’s compatibility status first: incompatible gateways can simply fail to appear in Blocks, and WooCommerce will sometimes prompt you to switch back to classic checkout when an incompatible extension is present.

  • If you use classic shortcode checkout, streamline the existing flow rather than just compressing it visually

    Classic checkout can still work very well, but Baymard’s guidance is to avoid non-linear flows and never show the same step twice. That means avoiding redirect-heavy account/login loops, accordion flows that reset or hide state badly, or “continue” actions that bounce customers between pages without clear progress. If guest checkout is appropriate, enable it in WooCommerce → Settings → Accounts & Privacy; WooCommerce also lets you enable log-in during checkout and customer account creation during checkout. Be aware that subscription purchases still require an account.

  • Reduce classic-checkout field burden with the right tool for the surface

    On classic checkout, the official Checkout Field Editor works on the legacy checkout only and lives under WooCommerce → Checkout Fields. If you have developer help, the classic checkout field stack also supports legacy filters such as woocommerce_billing_fields, woocommerce_shipping_fields, and woocommerce_checkout_fields. Do not assume those customisations will carry over to Blocks: WooCommerce’s own developer docs state that classic checkout field hooks are not the path for the block checkout, and field removal in Blocks is intentionally more constrained.

  • Make every forward action say what happens next

    Baymard recommends replacing vague button labels like “Continue” with copy that describes the next step, such as “Continue to payment” or “Continue to review”. If your classic checkout has a distinct review step after payment entry, keep that CTA explicit so users do not worry that entering payment means the order is already being placed. This matters even more when the next action changes the page or context.

  • Set expectations clearly when a payment method redirects off-site

    WooCommerce supports several gateway patterns, including form-based gateways that redirect customers to the processor’s site, iframe gateways, and direct gateways that keep payment fields on checkout. Baymard’s payment research specifically advises updating the primary button when a third-party method is selected so customers know they are about to leave the site temporarily. On classic checkout, gateways can rename the CTA through the gateway property $order_button_text, and WooCommerce’s legacy checkout template also exposes the woocommerce_order_button_text filter. On Blocks, that classic PHP hook is not supported; the equivalent behaviour depends on a block-aware integration, such as a gateway that supplies a placeOrderButtonLabel or a custom place-order button for the selected method.

  • If you are considering a one-page or streamlined checkout plugin, QA it like a checkout replacement

    Official WooCommerce One Page Checkout works by placing product selection and checkout together on a single product, post or page, primarily through a shortcode-driven custom template flow. Its own documentation warns that this custom templating reduces out-of-the-box compatibility with many other extensions. Vendor docs for tools such as FunnelKit and CartFlows also show that these tools can replace the default checkout, embed custom checkout forms, edit fields, alter layouts, inject page-level scripts or analytics, and add checkout-specific offers or upsells. In other words: you are not just “tidying checkout”, you are swapping checkout architecture. QA at minimum: payment methods and off-site redirects, express wallets, shipping methods, tax recalculation, coupon entry, guest/login/account creation behaviour, subscriptions, thank-you/receipt flow, tracking, mobile CTA visibility, load/performance impact, and any extension that touches orders or checkout data.

  • Treat the flow choice as a test, not a belief

    Because the best checkout can be one page or several, depending on the burden it creates, this should be treated as an experimentation question. If traffic allows, run a clean A/B test against the current checkout. If traffic is lower, stage it carefully with a controlled before/after readout and keep other checkout changes frozen so you can attribute results. The point is to test whether your store benefits from a more consolidated flow, not to assume it because “one-page checkout” sounds modern. This conclusion is an inference from Baymard’s findings that the best flow is the one that feels manageable, linear and transparent, regardless of page count.

How To Measure

The primary KPI is checkout completion, read as the share of users who move from begin_checkout to purchase. The supporting commercial KPI is RPV, with conversion rate as a site-level secondary read. If your change also alters upsells or quantity handling, read AOV alongside completion so you do not “improve” step completion by quietly lowering order value.

In GA4, start with Reports → Monetization → Checkout journey. That report is built from begin_checkout, add_shipping_info, add_payment_info, and purchase, and it shows the step-by-step retention and abandonment rates for users who entered at the first checkout step. Use the default Device category breakdown first, because desktop and mobile behaviour often differ materially. If you need more control, open or recreate the funnel in Explore → Funnel exploration, where you can apply segments, choose directly followed by vs indirectly followed by logic, add breakdowns such as device category, and inspect elapsed time between steps.

A practical read for this technique is: – Segment: mobile first, then desktop; if relevant, separate new users from returning users and guest-eligible traffic from account-required flows. – Success looks like: higher retention from begin_checkout to purchase, reduced abandonment between shipping and payment or payment and purchase, fewer obvious regressions in mobile completion, and stable-or-better RPV. – Custom measurement to add if you can: a bespoke event such as checkout_back_to_cart or a tagged page-view transition when customers move from checkout back to cart. Standard GA4 ecommerce events do not describe that behaviour on their own, so adding a custom event gives you a cleaner read on “back-button exits” and checkout reversals.

Your guardrail metrics should be: AOV, overall conversion rate, payment failure / failed-order rate, coupon usage if you hide coupon UI, and LCP / INP / CLS on the checkout page. This matters because plugin-led one-page checkouts often add scripts, styling and dynamic elements, and Google’s current good thresholds remain LCP ≤ 2.5s, INP ≤ 200ms, and CLS < 0.1 at the 75th percentile.

Pitfalls

  • Myth: “One-page checkout always converts better.” That is not what the best independent research says. Baymard’s position is that the stronger lever is reducing visible fields and perceived effort, not collapsing everything onto one screen. A very long “one-page” form can feel worse than a short, literal multi-step checkout.
  • Mistake: turning checkout into an accordion or redirect maze and calling it “streamlined”. A checkout only feels shorter if it stays linear and predictable. Repeating steps, hiding state badly, or bouncing the user between pages after login, coupon handling or payment selection breaks that. Baymard explicitly warns against non-linear flows and against showing the same page twice.
  • Mistake: replacing native Blocks without checking compatibility first. On block checkout, incompatible gateways may not appear at all, and WooCommerce may prompt you to revert to classic checkout. On the other side, the official One Page Checkout extension itself warns that its custom templating reduces compatibility with many extensions.
  • Mistake: leaving generic CTA copy on redirecting payment methods. When the selected gateway takes the shopper off-site, “Place order” or “Continue” can be too vague. Baymard recommends updating the primary button so customers understand they are about to leave your site temporarily.
  • Mistake: reading only headline conversion and ignoring device-level or funnel-level evidence. GA4’s Funnel Exploration can break down by device category, but it attributes users to the device that first entered the funnel. If shoppers research on mobile and finish on desktop, you can miss nuance unless you compare multiple views and keep the attribution rule in mind.

Examples

FAQs

Sources & Further Reading

Want us to implement this for you?

We run measured CRO consultancy for WooCommerce. If you want help prioritising, testing & implementing these improvements, tell us about your store.

Book Pilot

About This Page

  • Written By: Eliot Webb – Founder & WooCommerce CRO Consultant
  • Last Reviewed: 5 Jun 2026
  • Last Updated: