PrestaShop 9.2 Checkout: Mastering One-Page vs. Multi-Step & Module Compatibility

Navigating PrestaShop 9.2 Checkout: One-Page vs. Multi-Step & Module Compatibility Deep Dive

PrestaShop 9.2 introduces the native ps_onepagecheckout module, offering a choice between a modern, AJAX-driven one-page checkout (OPC) and the traditional four-page flow. While enhancing user experience, OPC integration demands careful consideration of theme and module compatibility.

Understanding Your Checkout Options

Configure checkout under Design > Checkout. OPC is default-installed but needs activation. Multi-store settings are per shop.

  • Four-Page Checkout: The classic approach, guiding customers through personal info, address, shipping, and payment, with full page reloads between steps. Robust and widely compatible.
  • One-Page Checkout (OPC): Presents all sections on a single page. Sections dynamically unlock, and updates occur via AJAX. Ideal for guest buyers and virtual products, which can skip shipping.

Choosing the Right Checkout

Optimal choice depends on traffic, theme, and modules:

  • OPC is Ideal for:
    • High mobile traffic (reduces friction).
    • Low average order values (fewer steps).
    • Many guest buyers.
    • Digital/downloadable products.
    • Themes built on PrestaShop's Hummingbird framework.
  • Four-Page Checkout is Safer When:
    • Using Classic-based or custom themes (OPC may require template overrides).
    • Relying on carrier or payment modules with complex interfaces (e.g., pickup point maps, express payment buttons) that lack confirmed OPC compatibility.

The Compatibility Challenge: AJAX Re-rendering

A key OPC concern is how modules with widgets handle AJAX updates. Unlike the four-page flow's full page reloads, OPC's AJAX re-rendering of carrier/payment sections can cause widgets to fail or disappear (e.g., pickup point selectors, payment buttons).

Developer's Solution: PrestaShop's Event Bus

PrestaShop offers a robust developer solution: the JavaScript event bus. Modules can listen for specific events to re-initialize widgets upon checkout section updates.

Monitor core events:

prestashop.on('opcCarriersUpdated', () => {
initPickupPointWidget(); // module's init function
});

prestashop.on('opcPaymentMethodsUpdated', () => {
initPaymentButtons();
});

Implementation Notes:

  • Use prestashop.on(); document.addEventListener() won't work.
  • Ensure script loads after OPC bundles (e.g., via actionFrontControllerSetMedia).
  • For self-submitting payment options (binary = true), call window.ps_onepagecheckout.submitBeforePayment() before payment flow to save customer, address, and carrier data.

Essential Testing Steps

Thorough staging environment testing is crucial before enabling OPC live:

  1. Enable OPC.
  2. Add a product to cart.
  3. Test carriers with pickup point selectors: change delivery address and confirm selector reappears/functions.
  4. Select and interact with each payment method.

If widgets break, revert to four-page checkout until module updates. If OPC is selected but four steps appear, check for conflicting third-party OPC modules; PrestaShop uses a module checkout only if one provider is enabled.

Conclusion

PrestaShop 9.2's native one-page checkout can significantly enhance user experience. An informed decision, backed by comprehensive testing and developer adjustments, is vital for a smooth, error-free customer experience.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools