PrestaShop 9.2: what retailers need to know
PrestaShop 9.2 has been available as a stable release since 30 September 2026. New features include a One Page Checkout module, extra data fields and an AI assistant in the Classic edition. At sjmedia, our key question is practical: which changes improve a retailer’s processes, and what needs checking before an update?
What is new in PrestaShop 9.2?
- One Page Checkout: the included module brings checkout onto one page. The admin lets you switch between this flow and the previous four-page checkout.
- Extra Properties: additional fields for products, customers and orders, for example, can be managed natively. The feature supports multiple languages, multiple stores and the Admin API.
- Ask AI: the Classic edition includes an assistant for questions about store data and actions in the admin. It connects through the PrestaShop MCP Server using your own API key from the chosen AI provider.
- Theme and technology: Hummingbird 2.1.2 includes fixes and improvements. Further admin pages migrated to Symfony can initially be enabled through feature flags.
Source: official PrestaShop 9.2 release announcement. Our assessment is dated 12 October 2026.
Our view: checkout needs to fit the business
A shorter checkout is interesting, but your actual orders determine whether it works better. We would not decide solely by counting checkout pages. For a B2B store, company details, separate delivery addresses, customer groups and payment terms may matter more than the shortest possible screen.
Before changing checkout, all payment methods and shipping rules in use belong on the checklist. Does guest checkout work? Does the free-shipping threshold apply correctly? Are discounts and billing addresses carried over accurately? A new checkout should handle these reliably. A version number alone does not imply higher sales.
Extra fields are particularly useful for custom processes
As a PrestaShop agency, we see potential in additional data fields. Examples include internal product identifiers or information exchanged between the store and inventory software. It remains important to decide which system owns the data, who can edit it and which interface passes it on.
Existing module data is not automatically transferred into new fields. We would first check what information is already stored and whether adapting it offers a real benefit. For us, this inventory comes before technical implementation. Read more in our guide to ERP and inventory management for online stores.
AI in the admin: define the task first
We see AI as support for clearly defined tasks. Before connecting an assistant to a real store, responsibilities, access rights and data sharing should be clarified. Planning should also cover the chosen AI provider’s terms and costs. An included module does not automatically make every connected service free.
We would start with a manageable task and a result that can be checked. Approval of important changes and review of results remain part of the workflow.
Should retailers move to PrestaShop 9.2 immediately?
Our recommendation: assess the store first, then choose the right update path. A stable store needs a clear transition plan. We begin by documenting installed modules, customisations, integrations and relevant data. Extensions in particular may hold their own histories that a migration needs to preserve.
We then check business-critical processes in a test environment: orders, shipping, payments and the customer-facing display. Together with the retailer, we also test regularly used admin workflows. Where versions are far apart, migration may be needed rather than a straightforward update.
This assessment draws on the published changes and our approach to store projects. It is not a report of a completed practical test of version 9.2 in a specific client store.
What does this mean for your store?
You do not have to assess module and integration compatibility alone. We review the existing store with you and work out sensible next steps. Learn about our approach to store updates and technical support.