PrestaShop 9.2.0 beta landed on July 9, 2026, and it is one of the most feature-rich minor releases the platform has shipped in years. After PrestaShop 9.1 brought Hummingbird 2.0, PHP 8.5 support, and a stronger Admin API, version 9.2 pushes in a different direction — checkout conversion, AI-assisted back office work, and cleaner module extensibility.

This guide breaks down everything in the PrestaShop 9.2.0 beta: the three headline features, what they mean for merchants and developers, what is still unfinished, and how to test safely before the stable release.

If you run a live store today, treat 9.2.0 beta as a preview — not a production upgrade. The core team entered feature freeze on the 9.2.x branch in July 2026 and is now focused on stabilization ahead of the public stable build.

PrestaShop 9.2.0 Beta — Full Feature Breakdown:

1. Release Overview: What Changed at a Glance

PrestaShop 9.2 is a minor version release tracked on GitHub milestone 9.2.0. The beta branch was cut from develop on July 9, 2026, marking the start of feature freeze — meaning no major new capabilities will land before stable; only bug fixes and polish.

Where PrestaShop 9.1 focused on storefront accessibility (Hummingbird 2.0, European Accessibility Act alignment) and infrastructure (Symfony 6.4 LTS, PHP 8.5, Admin API improvements), 9.2 targets day-to-day merchant workflows:

Three Headline Features in 9.2.0 Beta:
  • One Page Checkout — a native single-step checkout module to reduce cart abandonment.
  • AskAI — a pre-installed back office assistant for natural-language store queries and actions.
  • Extra Properties — a native way to attach custom data fields to core entities without modifying core database tables.

According to the official PrestaShop versions page, 9.2.0 beta is available specifically for testing. Stable 9.1 remains the recommended production version until 9.2 reaches general availability.

Beta warning: PrestaShop 9.2.0 beta and its new modules — especially One Page Checkout — are not production-ready. Test on staging or a local copy only. Do not upgrade a live store until the stable release and your modules are confirmed compatible.

2. One Page Checkout — Native Single-Step Ordering

Cart abandonment at checkout has been a long-standing pain point for PrestaShop merchants. The platform’s classic multi-step checkout — separate pages for address, shipping, and payment — works, but it adds friction, especially on mobile.

PrestaShop 9.2 introduces a native one-page checkout through the ps_onepagecheckout module. It consolidates address entry, carrier selection, and payment into a single screen with AJAX-based updates — no full-page reloads between steps.

One Page Checkout — Key Details:
  • Single-screen flow — address, shipping, and payment on one page.
  • AJAX updates — carrier and payment changes refresh in place, not via page reloads.
  • Optional, not forced — the classic multi-step checkout remains available; merchants enable one-page checkout from the back office.
  • Login moved outside the funnel — account creation and login happen before checkout, reducing distractions during payment.
  • Hummingbird v2 required — built for the new theme, not the legacy Classic theme.
  • Feature flag — controlled via the PS_ONE_PAGE_CHECKOUT_ENABLED configuration flag.

The module requires PrestaShop 9.2.0 or later and is published under the Academic Free License 3.0 on GitHub at PrestaShop/ps_onepagecheckout.

Still in heavy development: The official module README states that ps_onepagecheckout is under active development and should not be used in live environments. Expect UX polish, payment module compatibility fixes, and theme adjustments before stable.

Impact on module developers: Any module that hooks into the current checkout flow — payment gateways, shipping widgets, address validators — will need to adapt for the one-page layout. PrestaShop has committed to publishing integration documentation as the feature matures.

Impact on merchants: If your store still runs the Classic theme, one-page checkout will not apply out of the box. Merchants on Hummingbird 2.0 (introduced in 9.1) are best positioned to test it. Lower average-order-value and mobile-heavy stores stand to benefit most once the module is stable.

3. AskAI — Back Office Assistant Powered by MCP

PrestaShop 9.2 ships with AskAI, a native conversational assistant embedded in the back office. Instead of clicking through menus to find an order, check stock, or draft a customer email, merchants can ask questions in plain language and get answers pulled from live store data.

Related Read:  How to Display the Content of Last Shopping Cart after login in PrestaShop

AskAI is powered by the PrestaShop MCP (Model Context Protocol) Server — the same bridge PrestaShop released separately for connecting external AI tools to your store. In 9.2, that capability moves inside the admin panel as a first-class feature.

AskAI — What It Can Do:
  • Query store data — stock levels, order statuses, customer segments, product details.
  • Trigger back office actions — update product images, review order histories, prepare restocking summaries.
  • Bring your own AI provider — connect ChatGPT, Claude, Gemini, Mistral, or other MCP-compatible assistants.
  • Secure by design — uses PrestaShop OAuth, granular member permissions, and tool annotations (read-only vs destructive actions).
  • Extensible — module developers can register their own MCP tools, prompts, and resources via PHP attributes.

PrestaShop’s MCP Server documentation outlines practical use cases merchants can try today — even before upgrading to 9.2:

Example Prompts (via MCP-connected AI):
  • “What is the stock of the product with SKU ‘TSHIRT-001’? If it is below 10, list other products from the same supplier.”
  • “What is the status of order #12345? If shipped, get the tracking number and draft a customer email.”
  • “Identify all products with stock below 5 units and generate a restocking summary table.”

AskAI builds on infrastructure PrestaShop has been developing throughout 2026, including the .ai/ source-of-truth directory for AI-enabled development standards, prompt templates, and MCP resources. If you already use the standalone MCP Server module on PrestaShop 8.2+ or 9.x, the concepts will feel familiar — 9.2 simply integrates them natively into the back office experience.

For merchants exploring AI store management more broadly, our guide on llms.txt for PrestaShop merchants covers a complementary angle — helping AI tools discover and understand your storefront, while AskAI focuses on back office operations.

4. Extra Properties — Custom Fields Without Core Overrides

Extending PrestaShop entities has historically meant one of three painful paths: alter core database tables, build custom side tables with manual wiring, or override core classes. All three work, but they create upgrade debt and repeated boilerplate across modules.

Extra Properties — developed jointly by PrestaShop SA and the Kiwik agency — solves this with a native extension point available in 9.2. Modules can register custom fields on core entities like products, combinations, customers, orders, and more, without touching core tables or shipping overrides.

Extra Properties — Platform Coverage:
  • Back Office — fields appear in entity edit forms and admin grids using native Symfony form types.
  • Front Office — accessible via $product->extraProperties['my_module']['field_name'] or Smarty templates; lazy-loaded for performance.
  • Admin API — serialized automatically in an extraProperties JSON node with matching entity permissions.
  • Multistore and multilang — scopes include common, per-language, and per-shop values, combinable as needed.
Developer API Highlights:
  • registerExtraProperty() / unregisterExtraProperty() on the Module class.
  • Typed SQL columns (int, float, date, varchar, etc.) — not a generic key-value store.
  • Dedicated tables: product_extra, product_extra_lang, product_extra_shop, and equivalents per entity.
  • Central registry in extra_property_definition for metadata, validation, labels, and visibility.
  • Tables and columns created automatically on registration; removed when no longer needed.

The design deliberately avoids Entity-Attribute-Value (EAV) patterns. Each property gets a real typed SQL column, which keeps queries readable and indexes efficient at scale — a meaningful difference for catalogs with thousands of SKUs carrying module-specific metadata.

For merchants, Extra Properties means cleaner integrations: ERP references on orders, internal product specs, customer metadata — all manageable from the back office without fragile custom code that breaks on every upgrade.

5. What Developers Need to Know

PrestaShop 9.2.0 beta is as much a developer release as a merchant one. If you maintain modules or agency client stores, plan for these changes:

Developer Checklist for 9.2:
  • Checkout modules — audit hooks and templates tied to the multi-step checkout; test against ps_onepagecheckout on staging.
  • Entity extensions — evaluate migrating custom field tables to Extra Properties where supported.
  • MCP integration — module authors can declare MCP tools, prompts, and resources to expose functionality to AskAI.
  • Theme compatibility — one-page checkout targets Hummingbird v2; Classic theme stores need a theme migration path first.
  • Autoupgrade — the 9.2.0 upgrade path includes the new extra_property_definition registry table; test migrations on copies before production.
  • Bug fix targeting — fixes for 9.2 go to the 9.2.x branch; new features for future versions target develop.

PrestaShop’s AI architecture work — centered on the .ai/ directory — continues in parallel. This provides structured context files so AI coding assistants understand PrestaShop-specific patterns, which should accelerate module development and theme work throughout 2026.

Related Read:  Gifts & Flowers – Premium PrestaShop Themes & Templates

6. Coming Next on the PrestaShop Roadmap

While 9.2.0 beta focuses on checkout, AI, and extensibility, PrestaShop’s public roadmap shows additional work in progress for Q2–Q3 2026 that may land in or after 9.2 stable:

On the Horizon (Roadmap — Q2–Q3 2026):
  • B2B foundations — structured data model separating business entities from B2B customer contacts, with feature-flagged support for roles, approval workflows, and scope-based rules (developed with Soledis).
  • Extended multi-user customer accounts — organization owners invite users, delegate rights, and manage granular permissions.
  • Multiple URLs per module organization — easier deployment across production and pre-production environments.
  • Headless architecture (2027+) — API Platform integration progressing toward headless-ready storefronts and integrations.

These items are tracked separately from the 9.2.0 beta milestone. Some may ship as feature-flagged experiments in 9.2.x patch releases; others target later versions. Always check the official PrestaShop product roadmap before planning client projects around them.

7. Should You Upgrade or Test the Beta?

The answer depends on your role and environment:

Who Should Test 9.2.0 Beta:
  • Module and theme developers — validate compatibility with one-page checkout, Extra Properties API, and MCP hooks.
  • Agencies with staging environments — evaluate Hummingbird 2.0 + one-page checkout for upcoming client migrations.
  • Merchants curious about AskAI — explore the assistant on a sandbox store before stable.
Who Should Wait for Stable:
  • Live production stores — stay on PrestaShop 9.1 (or your current stable branch) until 9.2.0 stable ships and your modules confirm support.
  • Stores on Classic theme — one-page checkout requires Hummingbird v2; plan a theme migration separately.
  • Stores with heavy custom checkout modules — wait for payment and shipping module vendors to certify 9.2 compatibility.

If your store sells to EU buyers, remember that compliance modules — such as EU withdrawal button and returns tools — need independent testing on any new PrestaShop version. A platform upgrade does not automatically validate third-party module behavior.

8. How to Download and Test 9.2.0 Beta

PrestaShop 9.2.0 beta is available from the official versions page for testing purposes:

Testing Steps:
  • Download PrestaShop 9.2.0 beta from prestashop.com/versions.
  • Install on a local XAMPP, Docker, or staging server — never on production.
  • Install or enable ps_onepagecheckout and set PS_ONE_PAGE_CHECKOUT_ENABLED to test the new checkout flow.
  • Configure AskAI via the PrestaShop MCP Server and connect your preferred AI provider.
  • If you develop modules, register a test Extra Property on a product entity and verify back office, front office, and Admin API output.
  • Report bugs to the PrestaShop 9.2.0 release tracker on GitHub.
Pro Tip for Module Developers

If you have open pull requests against the develop branch that you want included in 9.2, rebase them onto 9.2.x now — the feature freeze window is the time to get fixes merged before stable.

Take Action Now

Spin up a staging copy, install 9.2.0 beta, and run your critical checkout and compliance flows end to end. Stable 9.2 is expected in Q2–Q3 2026 — merchants and agencies that test early will upgrade faster when it ships.

PrestaShop 9.2.0 beta marks a clear shift: faster checkout, AI-native back office tools, and cleaner extensibility for module developers. It is not ready for production yet — but for anyone building on PrestaShop in 2026, it is the most important preview release of the year.


Related Posts: