Yes to PrestaShop 9.2, but in the right order
9.2 is the most complete release of the 9 branch and the natural destination for any store on PrestaShop 8 or 9.1. What it brings is useful: fewer third-party modules for the checkout, less custom code for extra fields and a back office that keeps moving to Symfony. What does not change is the method: an upgrade is tested on a copy of the store, with every payment gateway and every carrier, and goes to production once the first maintenance release is out. A broken checkout lowers conversion more than any new feature raises it.
Wait for the first maintenance release (9.2.1) and test on a copy first. That is what we do with the stores we maintain.
What PrestaShop 9.2 brings and what it changes for your store
Native One Page Checkout
The whole purchase process on a single page, with guest checkout, out of the box. From the back office you choose between one page or four steps, and you can switch back. If you were paying for a third-party module for this, you now have a native option. Warning: PrestaShop has asked payment and carrier module developers to review compatibility. If you take payments with Redsys or Bizum, or your carrier calculates the price on the fly, do not assume they work on the single page until you have tested it.
Ask AI: an assistant in the back office
A conversational assistant inside the back office: you ask in plain language and it queries or acts on the store. It runs on the PrestaShop MCP Server, and you connect your own AI provider (ChatGPT, Claude, Gemini or another compatible one) with your API key. It asks for approval before changing anything. Included in the Classic edition. For queries it saves clicks; for changes to orders or prices, the prior approval is what prevents surprises. Read the section on customer data first.
Extra Properties: extra fields without code
Native additional fields on products, customers, orders and other entities, without overrides (changes to the core code that tend to break on upgrade). If you need a "supplier reference" field on the product or a "contact person" on the customer, that used to mean custom development. Now there is a native path: fewer maintenance hours on every upgrade.
Klaviyo is back, integrated
Klaviyo, the email and SMS automation tool, is once again integrated in the Classic edition. If you already use it, you save installing the module separately. If you don't, nothing changes: it is not a reason to upgrade on its own.
More back-office pages on Symfony
PrestaShop keeps migrating back-office pages to Symfony, its modern technical base. The new ones are enabled with feature flags under Advanced Parameters > New & Experimental Features. Day to day, little changes; if a module misbehaves on a new page, that flag lets you go back to the previous version of the page without uninstalling anything.
Less visible changes that do matter
Better bot detection, including AI bots, to avoid ghost carts (if your abandoned-cart figures don't match your sales, this affects you). The install/ folder deletes itself after installation; many stores used to leave it exposed. Product structured data (the tags that help Google understand price, stock and ratings) is now generated by the core: if your theme or a module was generating it, check it is not duplicated. And B2C/B2B mode adjustments, relevant if you sell to businesses with tax-excluded prices.
Should you upgrade now? It depends on where you are
Three cases, three different answers.You are on PrestaShop 1.7
Your priority is not 9.2, it is leaving 1.7. The last release of that branch (1.7.8.11) dates from 2024 and there have been no patches since. The jump to 9 is a migration, not an upgrade: the PHP version changes, modules change and the theme almost always changes. Plan it as a project, with budget and calendar, and jump straight to 9.2 instead of going through 8. Do it once 9.2 has its first maintenance release.
You are on PrestaShop 8.x
No rush, but there is a date on the horizon. 8.2.8 was a security-only release that fixed 5 vulnerabilities, 3 of them high severity: the 8 branch still gets patches and still has holes to plug. PrestaShop 9 is a major version relative to 8, so some modules and themes will need updating. Install 8.2.8 now if you haven't, ask your module vendors for their 9.2 compatibility date and plan the jump for when 9.2.1 is out.
You are on PrestaShop 9.0 or 9.1
The easiest case. 9.1.5 is the last planned release of the 9.1 branch, so 9.2 is your next destination. The 9.1 branch received 5 maintenance releases after its .0 and a similar pattern is reasonable to expect. Upgrade on a copy this week if you want to try the checkout. In production, wait for the first maintenance release unless you have a concrete reason, such as needing One Page Checkout for a campaign.
Before upgrading: the checklist we run on every store
All of this is done on a copy of the store, never on the one that sells. If your hosting doesn't give you a test environment, ask for one.- Full backup
Files and database, and check it can be restored. A backup you have never restored is not a backup. - Payment gateway
A test order with every method. If you take payments with Redsys, test card and Bizum separately: they are usually different modules or configurations. - Bizum, if you use it
Test the return after payment, which is where new checkouts usually fail. - Every carrier
One by one, with an order that goes all the way through. If it fetches rates in real time, test with and without a saved address. - Theme
Product page, cart and checkout on mobile. If the theme is third-party, confirm it declares 9.2 compatibility. - Third-party modules
List them all, remove the ones you don't use and ask each vendor for their 9.2 version. An abandoned module is the most frequent cause of a failed upgrade. - PHP version
PrestaShop 9 requires PHP 8.1 or higher; check the official requirements table for the exact release you will install, and check with your hosting which version you have and whether you can change it. - Checkout
Decide whether to start with one page or four steps. If in doubt, start with four, which is what your modules already know, and switch to one once you have tested it.
The AI assistant and your customers' data
When Ask AI queries orders or customers, the data it needs to answer travels to the AI provider you have connected. That includes personal data: names, addresses, emails. In data-protection terms, that provider becomes a data processor. That requires a data processing agreement with them, the one Article 28 of the GDPR demands, and knowing where the data is hosted, because if it leaves the European Union additional safeguards apply. We do not claim that any specific provider complies or fails to comply with the GDPR. Checking it is your responsibility as the store owner. Before enabling the assistant: review the AI provider's contract, check the server location, update your record of processing activities and, if you have a data-protection advisor, consult them. If you cannot run those checks, don't enable it yet. The store works just the same without it.How we upgrade to PrestaShop 9
The same phased process we apply to the stores we maintain: nothing reaches production without going through a copy first.Initial technical analysis
Inventory of modules, theme, overrides and customisations. We tell you what is 9.2-compatible, what needs a new version and what can go.
Backup and staging
Restorable backup, staging clone and a check of the hosting's PHP version.
Upgrade on the copy
Technical upgrade, fixing incompatibilities and deciding the checkout mode (one page or four steps).
Real sales tests
Test orders with every payment method (card and Bizum separately) and every carrier, on desktop and mobile.
Launch and monitoring
Go-live in a low-traffic window and follow-up with Lynx Monitor.
Frequently asked questions
Can I upgrade from PrestaShop 8 to 9.2 directly?
Does PrestaShop 9.2's One Page Checkout work with my payment gateway?
Is it mandatory to use PrestaShop 9.2's AI assistant?
How long should I wait before moving PrestaShop 9.2 to production?
Coming from an older version?
If your store is still on 1.6 or 1.7, the jump is a migration: see upgrading PrestaShop 1.6 or upgrading PrestaShop 1.7. And if what you want is someone taking care of upgrades on an ongoing basis, that is our PrestaShop maintenance.