PrestaShop 9.2 has not been released yet. The first public beta landed on 22 July 2026, following the feature freeze on 9 July. The 9.1.x branch remains the stable production version.
Do not install the beta on a store that is taking orders. Do install it on a test environment now — and in a moment I’ll explain why this particular release is worth the trouble.
Three things that actually change
1. One Page Checkout moves into the core
This is the most significant change in 9.2, and the only one that touches conversion directly.
Until now, PrestaShop shipped only with a multi-step checkout spread across separate pages. In 9.2, the installation bundle includes a native One Page Checkout module: the entire order flow on a single screen, with no page reload when the customer picks a carrier or a payment method, and a guest-first experience that doesn’t force account creation.
The back office lets you switch between the one-page and the four-step checkout, so nothing is being forced on you.
The PrestaShop team is blunt about why: relying solely on third-party modules created inter-compatibility problems that ultimately hurt merchants. Hard to argue with that. Anyone who has debugged a store where three modules were fighting for control of the checkout knows exactly what this refers to.
What this means in practice. If you’re currently paying a subscription for a commercial OPC module, it’s worth recalculating whether you still need it once 9.2 goes stable. And if your store runs on mostly mobile traffic, this is a reason to schedule the upgrade rather than defer it.
2. Extra Properties: no more rebuilding the same tables
A developer-facing change with a real downstream effect for merchants.
Adding a custom field to a product, a customer or an order has meant, until now: create your own table, wire up the relations by hand, handle multistore, handle multilanguage, plug it into back office forms and grids, expose it on the front office — and then do the whole thing again from scratch in the next module.
PrestaShop 9.2 introduces Extra Properties, a native system for registering additional fields on core entities such as Product, Combination, Customer and Order. A field registered once shows up automatically in back office forms and grids, on the front office, and in the Admin API. Multistore and multilanguage support work out of the box. No overrides required.
The feature was built jointly by the Kiwik and PrestaShop SA teams.
What this means in practice. Integrations built on Extra Properties will survive upgrades. Solutions built on custom tables and overrides will still need an audit every time you update. If you’re commissioning a custom module for 2027, this is the foundation to build it on.
3. Ask AI: an assistant in the back office, without vendor lock-in
9.2 adds a built-in conversational assistant to the back office. Instead of clicking through menus, you ask questions about your store data in plain language and trigger actions the same way.
Two things here matter more than the feature itself.
First, it runs on the PrestaShop MCP Server (Model Context Protocol), which means you connect your own provider on your own API key — ChatGPT, Claude, Gemini or another compatible model. You are not tied to a single vendor or a single price list.
Second, the assistant asks for approval before it acts on your store. That’s the correct design decision, and the first question I’d put to any AI tool with access to a production database.
Ask AI ships with the Classic edition. I’ve written more about practical AI use in a store in my piece on implementing AI in PrestaShop.
What else is in 9.2
Klaviyo is back in the box. The PrestaShop Automation with Klaviyo module is once again bundled with the Classic edition, so email and SMS automation is available straight after installation.
The Symfony migration continues. Another batch of back office pages has been migrated and marked stable: Countries, Merchandise Return, Hook a module, Quick Access, Email body translations, and Tax rules. All of them sit behind feature flags, so you can switch them on and test before they become the default.
B2B foundations. The core gains a B2C/B2B mode switch, a new “Business Entities” menu entry, and a data model for business entities — all behind the improved_b2b feature flag. This is not a finished B2B module yet, but the direction is clear and worth keeping in mind when scoping a wholesale build.
Multi-shipment is maturing. A substantial batch of work on handling several shipments within a single order: creating a shipment on an existing order, splitting and merging shipments, shipment data on invoices, delivery slips, and multi-shipment support in transactional emails.
A new pricing architecture. The rewrite of price calculation (Product calculator, CartCalculator) has started behind its own feature flag. Worth watching, not worth putting on production.
Things only developers will care about. Structured data is now rendered on the core side rather than in the template. Connection::isBot() recognises modern crawlers and AI bots, which should cut down on ghost carts and phantom sessions. New CLI commands: prestashop:module:list, prestashop:htaccess:generate, plus employee password changes and super admin creation from the console. SEO-friendly attachment URLs. The Upgrader class is deprecated. /init.php has been hardened and deprecated. Symfony bumped to 6.4.42.
Why this particular beta is worth installing
I normally tell clients to ignore betas. This time is different, and there is exactly one reason: One Page Checkout changes the contract for payment and carrier modules.
If you maintain a payment module or a carrier integration — or you’re running one written by someone else — its behaviour in the one-page flow is not guaranteed. The PrestaShop team published separate documentation for module authors and for theme authors precisely because some solutions will need adapting.
Translated into merchant terms: there will be a window between the stable 9.2 release and the moment third-party authors ship compatible versions. Upgrading inside that window can leave you with a checkout that looks perfectly fine and doesn’t complete transactions. That is the most expensive class of bug there is.
Which is why the modules I maintain — carrier and payment integrations — are being tested against the beta now, not after launch.
When the stable release lands, and what to do until then
There is no official date. A Release Candidate normally follows the beta, then the stable release. PrestaShop’s minor release cycle typically runs 6–9 months, and 9.1 shipped in March 2026, which puts the realistic window at late 2026. The team has said explicitly that it is now focused on stabilising the beta based on incoming reports.
Running 8.x or 9.0? Don’t wait for 9.2. Move to 9.1.x, which has already been through several maintenance releases. The later jump from 9.1 to 9.2 will cost far less than going from 8.x straight to 9.2. I’ve broken down the cost of that move in my article on migrating to PrestaShop 9.1, and mapped out the longer road in PrestaShop 8 ends in 2027.
Building a new store? Build on 9.1.x. The architecture is the same, and moving to 9.2 will be an update rather than a migration.
Commissioning a custom module? Ask your developer to commit to One Page Checkout compatibility, and to use Extra Properties instead of custom tables wherever it applies. That question, asked today, saves you a budget line next year.
Want to test the beta? The Classic Beta 1 package is available from the PrestaShop developers’ blog. One limitation to be aware of: once you install the beta, you cannot update to the RC or the stable release through the Update Assistant’s standard channel. For real testing, do a fresh install.
The new release does not change how marketplace integrations work. The TikTok Shop module for PrestaShop 8 and 9 runs on 9.2 without core modifications and uses the official TikTok Shop Open API.
In one sentence
9.2 isn’t a release you need to rush into production. It’s a release you need to prepare your modules for — and that work belongs now, not on launch day.
If you want to know whether your store and its modules will survive the move to 9.2, get in touch and I’ll audit it on a staging environment.
