PrestaShop 9.1 vs. PrestaShop 9.2: What Actually Changed for Merchants?

1. PrestaShop 9.1 vs. PrestaShop 9.2: What Actually Changed for Merchants
2. Who This Guide Is For
3. What You'll Learn
4. Why PrestaShop 9.x Matters Now
5. What Exactly Changed Between PrestaShop 9.1 and 9.2?
6. Is the New Checkout Faster in 9.1 and 9.2?
7. How Does PrestaShop 9.2 Handle PHP and Symfony Compared to 9.1?
8. Which Version Should You Choose: 9.1.x or 9.2?
9. How to Upgrade from PrestaShop 8.x or 1.7 to 9.2 Safely
10. Advanced Strategies: Handling Custom Modules and Performance Tuning
11. Best Practices for Upgrading to PrestaShop 9.2
12. Common Mistakes When Upgrading to PrestaShop 9.x
13. Practical Upgrade Checklist
14. Recommended Tools and Resources
15. Related Guides
16. Key Takeaways

PrestaShop 9.1 vs. PrestaShop 9.2: What Actually Changed for Merchants

PrestaShop 9.2 is not a feature-packed release; it is a reliability and compatibility update built on top of 9.1, focusing on smoother pre-update audits, better handling of incompatible modules, and overall stability for stores already running the 9.x line. For merchants, the practical difference between 9.1 and 9.2 is less about new customer-facing features and more about reducing the risk of a broken shop during maintenance. This guide explains exactly what changed, why it matters for your store, and how to decide whether upgrading now is the right move.

This guide is written for PrestaShop merchants, store managers, and the agencies that support them. You will learn the concrete differences between 9.1 and 9.2, what the upgrade process involves, how module compatibility is handled, and which version you should be running based on your store's age and technical debt.

Who This Guide Is For

Whether you are running a legacy shop on PrestaShop 1.6 or 1.7, or you already jumped to 8.x, this comparison helps you make an informed decision about the 9.x line.

• Merchants on PrestaShop 1.6 or 1.7: You are on outdated software with real security and performance risks. This guide shows you why the 9.x line is the logical destination.
• Stores on PrestaShop 8.x: You are close to the current foundation but need to understand what moving to 9.1 or 9.2 involves, especially regarding Symfony and PHP requirements.
• Agencies and freelancers: You need a clear breakdown of version differences to advise clients accurately and plan migrations without scope creep.
• Merchants with custom modules: If you rely on bespoke functionality, the upgrade path requires careful module auditing. This guide explains what 9.2 improves in that area.
• Decision-makers evaluating a replatform: You want to know if staying with PrestaShop 9.x is viable long-term compared to migrating elsewhere.

What You'll Learn

• The core difference between 9.1 and 9.2, and why 9.2 is described as a reliability-focused release.
• How PrestaShop 9.x modernises your stack with Symfony 6.4 and PHP 8.1-8.3 support.
• What the pre-update audit improvements in 9.2 actually do for stores with incompatible modules.
• Why the new checkout is faster, including the benchmark improvement over 1.7.x.
• How to decide between 9.1.x and 9.2 based on your store's age and technical debt.
• A practical upgrade workflow that minimises downtime and risk.
• Advanced strategies for handling custom modules and performance tuning after the upgrade.
• Common mistakes merchants make during a major version change and how to avoid them.

Why PrestaShop 9.x Matters Now

PrestaShop 9.x represents a major evolution from the 8.x series. The most significant shift is the move to Symfony 6.4, a significant leap from the previous version. This modernisation affects everything from request handling to security patches, and it means the platform is built on a framework that is actively maintained.

For merchants still on 1.7 or 8.x, the gap is growing. Launched on June 10, 2025, this version marks a major evolution: faster, more visible, more reliable. If you are still using PrestaShop 1.7 or 8, you are missing out on performance gains and security hardening that directly impact your conversion rate.

The practical implications include:

• Security: Older Symfony versions (4.4) reached end-of-life, meaning no more security patches for the core framework your shop runs on.
• Performance: The newer architecture handles PHP 8.1-8.3 more efficiently, reducing memory usage and improving response times.
• Maintenance: Module developers focus their testing on the newest versions, so older platforms see slower bug fixes.

Staying on 1.7 or 8.x is a compounding risk, not a stable choice. Every month that passes, the gap between your store and the current codebase widens, making the eventual migration harder and more expensive.

What Exactly Changed Between PrestaShop 9.1 and 9.2?

The short answer is that 9.2 is an incremental refinement of 9.1, not a new feature release. According to the PrestaShop Product Roadmap this new version adds compatibility with PrestaShop 9.1, improves reliability, and enhances pre-update audits with better handling of incompatible modules.

To understand what 9.2 changes, you first need to see what 9.1 introduced. Here is a comparison of the two versions:

If you are starting a new project, 9.1.x is a perfectly solid choice. As PrestaShop 9.1.x is a current modern foundation for new ecommerce projects and a logical upgrade direction for stores that need to remove technical debt. However, if you are migrating an existing store, 9.2's improved audit process gives you a clearer picture of what will break before you commit to the upgrade.

What "Better Handling of Incompatible Modules" Means in Practice

The pre-update audit in 9.2 is more than a cosmetic change. In earlier versions, the upgrade tool might list incompatible modules but leave you guessing about severity. In 9.2, the audit is designed to give clearer warnings and, where possible, suggest alternatives or blocking actions.

For a merchant, this translates into fewer surprises. Instead of running an upgrade and discovering a payment module no longer works, you find out before you start, which saves hours of debugging and lost sales.

Is the New Checkout Faster in 9.1 and 9.2?

Yes. The checkout improvements were introduced in the 9.0 line and carried through 9.1 and 9.2. PrestaShop 9.0's new checkout shaved an average of 0.6 seconds off checkout load time versus 1.7.x in internal benchmarks. That might not sound like much, but in ecommerce, half a second can be the difference between a completed order and an abandoned cart.

Here is how that improvement breaks down in real terms:

• Faster page rendering: The checkout uses modern Symfony components that render more efficiently.
• Reduced server load: Better memory handling with PHP 8.x means the server responds quicker under concurrent traffic.
• Fewer redirects: The new checkout architecture simplifies the step flow, reducing round trips.

If you are still on 1.7 and losing sales at checkout, the improved checkout alone justifies the upgrade conversation.

How Does PrestaShop 9.2 Handle PHP and Symfony Compared to 9.1?

Both 9.1 and 9.2 run on the same foundation, so there is no version-specific difference here. The key facts apply to the entire 9.x line. PrestaShop 9.0 has been upgraded to rely on Symfony 6.4, a significant leap from the previous version, 8.x, which was based on Symfony 4.4. This is not just a version number change; Symfony 4.4 is end-of-life, meaning no security fixes. Symfony 6.4 is actively maintained.

The PHP requirements are equally important. PrestaShop 9.0 introduces support for PHP 8.1, 8.2, and 8.3, allowing merchants to benefit from improved performance, better memory handling, and security. Before the 9.x line, many stores were stuck on PHP 7.4 or early PHP 8.0 versions, which are now insecure and slow.

Consider the practical difference for a mid-sized store:

• PHP 7.4: Slower execution, known vulnerabilities, no official support.
• PHP 8.2: Faster execution, active security support, better type safety.
• Symfony 4.4: No security patches; your store is a target.
• Symfony 6.4: Long-term support, modern dependency injection, better performance.

If your host is still running PHP 7.4, you cannot run PrestaShop 9.x. The upgrade requires a hosting change or at minimum a PHP version switch, which is a separate operational step you must plan for.

Which Version Should You Choose: 9.1.x or 9.2?

The decision between 9.1.x and 9.2 largely depends on your starting point. If you are building a brand-new store, 9.1.x gives you a stable, modern base. If you are migrating an existing store, especially one with custom modules or a long history of add-ons, 9.2's improved audit process is the safer choice.

Here is a direct comparison to help you decide:

If you have any custom code or third-party modules, choose 9.2 and run the pre-update audit before you do anything else. The audit result will tell you which modules need replacing, which need updating, and which you can keep.

How to Upgrade from PrestaShop 8.x or 1.7 to 9.2 Safely

Upgrading to PrestaShop 9.2 is a structured process, not a one-click operation. Here is a practical workflow that reduces risk and downtime.

Step 1: Audit Before You Touch Anything

Before upgrading, run the pre-update audit included in the PrestaShop upgrade tool. This will flag:

• Modules that are not compatible with the 9.x architecture.
• Overrides that conflict with the new Symfony version.
• Theme files that use deprecated functions.

This is exactly where 9.2 shines over 9.1. The improved audit gives you a clearer list of what will break, so you can plan replacements or updates before you start the upgrade.

Step 2: Create a Staging Environment

Never upgrade a live production store directly. Clone your store to a staging server that mirrors your production environment, including PHP version and server configuration. This lets you test the upgrade without risking live sales.

Step 3: Update PHP First

Before running the PrestaShop upgrade, ensure your staging environment runs PHP 8.1, 8.2, or 8.3. If your host only offers PHP 7.4, you need to arrange a PHP upgrade first. Some modules may behave differently on PHP 8.2, so test your critical paths, especially payment and shipping modules.

Step 4: Run the Upgrade and Test Core Functions

Using the upgrade tool, move from your current version to 9.2. After the upgrade, test these functions in order of importance:

1. Checkout flow (add to cart, payment, order confirmation).
2. Customer login and account creation.
3. Product search and category navigation.
4. Cart rules and discounts.
5. Email sending (order confirmations, password resets).

Create a test order with a low-value item or a test payment gateway so you can confirm the full flow works.

Step 5: Replace Incompatible Modules

The audit will likely flag one or more modules. For each one, check if the developer has released a version compatible with PrestaShop 9.x. If not, you have three options:

• Find an alternative module that replicates the functionality.
• Have a developer migrate the module to the new architecture (this can be costly).
• Remove the functionality if it is not critical.

Step 6: Go Live with a Rollback Plan

Once staging tests pass, back up the live store, including the database and all files. Then run the upgrade on production. If something goes wrong, you can restore the backup within minutes.

Advanced Strategies: Handling Custom Modules and Performance Tuning

Once you are on 9.2, there are advanced considerations that go beyond the basic upgrade.

Migrating Overrides to Hooks and Modules

If your store uses overrides to modify core behaviour, these are the highest-risk items in a 9.x upgrade. The modern approach is to convert overrides into dedicated modules that use hooks and Symfony events. This makes your custom code easier to maintain and prevents conflicts when PrestaShop releases future updates.

For example, if you have an override that modifies product page behaviour, a developer can rebuild that functionality as a module that hooks into the displayProductExtraContent hook. This is more work upfront but eliminates the risk of overrides breaking with every core update.

Optimising Performance Post-Upgrade

After moving to 9.2 with PHP 8.2, take advantage of the improved performance:

• Enable OPcache: PHP 8.x handles OPcache more efficiently, which reduces CPU load.
• Review cache settings: Use the built-in cache options for Smarty templates and the database cache.
• Check the checkout: Run a performance test specifically on the checkout pages, since this is where the speed improvement matters most.
• Monitor memory limits: PHP 8.x uses less memory in many cases, but your server configuration may still have limits that are too low for complex product pages.

Using the 9.2 Audit as a Continuous Tool

The improved audit in 9.2 is not just for the initial upgrade. Run it periodically to check module health and catch issues before they become outages. This is particularly useful for stores that frequently install and remove modules.

Best Practices for Upgrading to PrestaShop 9.2

Follow these best practices to ensure your upgrade succeeds the first time.

• Test on a staging server that matches production exactly. If your staging environment uses different PHP versions or server software, you will miss compatibility issues that only appear in production.
• Back up everything, not just the database. Your theme files, module code, and uploaded images are all part of the upgrade. A full backup allows a complete rollback.
• Schedule the upgrade during low traffic periods. Even with a rollback plan, you want to minimise the window where the store might behave unpredictably.
• Update all modules before upgrading the core. A module updated to support 9.x will be more stable than an older version that the upgrade tool tries to patch.
• Use a child theme if you have customisations. This isolates your theme changes from the core theme, making it easier to identify issues after the upgrade.
• Document your custom code changes. If you have overrides or custom modules, note exactly what they do before the upgrade. This helps your developer rebuild them if they fail.
• Run the pre-update audit twice. Once before you make any changes, and once after you update modules, to confirm the remaining issues are understood.
• Plan for module replacement costs. Some third-party modules for 1.7 may not have a 9.x version. Budget for purchasing alternatives or paying for custom development.

Common Mistakes When Upgrading to PrestaShop 9.x

These are the most frequent errors we see merchants make, and how to avoid them.

• Skipping the staging environment. Upgrading directly on production is the fastest way to lose sales. Even a minor module conflict can take hours to resolve, and during that time your store is down or broken.
• Ignoring the pre-update audit warnings. If the audit says a module is incompatible, it will break. Hoping it will work is not a strategy. Replace it before you upgrade, not after.
• Forgetting to check payment modules first. Your payment gateway is the most critical integration. If it breaks, you cannot take orders. Verify payment module compatibility before anything else.
• Not testing emails. Order confirmations, shipping notifications, and password resets all depend on email templates and settings that can change during the upgrade. Test email delivery in staging.
• Assuming PHP 8.2 works with all modules. Some older modules have not been tested with PHP 8.2 or 8.3. The staging environment is where you find this out, not after going live.
• Upgrading during a flash sale or peak season. Even a well-tested upgrade can have unforeseen issues. Do not risk your highest-revenue periods on a major version change.
• Forgetting custom overrides. If a developer modified core files directly, the upgrade tool will overwrite them, and your custom behaviour will silently disappear. Audit for overrides before upgrading.

Practical Upgrade Checklist

Use this checklist when you are ready to move to PrestaShop 9.2.

• Confirm your host supports PHP 8.1, 8.2, or 8.3 and Symfony 6.4 requirements.
• Take a full backup of files, database, and media directories.
• Create a staging environment that mirrors production exactly.
• Run the pre-update audit and review all module compatibility warnings.
• Update all modules that have a version compatible with 9.x.
• Identify and replace modules that have no 9.x version.
• Check for and document any core file overrides.
• Run the upgrade on staging using the official upgrade tool.
• Test checkout, customer accounts, search, and email sending on staging.
• Compare staging performance against your old production to confirm improvements.
• Back up the live store again immediately before the production upgrade.
• Run the upgrade on production during a low-traffic window.
• Retest checkout and critical functions on the live store.
• Monitor error logs and server performance for the first 48 hours.

Recommended Tools and Resources

Several resources support your upgrade journey, from audit tools to documentation.

• PrestaShop Product Roadmap: The official roadmap shows what the core team plans for upcoming versions, so you can anticipate future requirements.
• PrestaShop Developer Documentation: The core updates page documents exactly what changed between versions, which helps your developer plan the migration.
• PrestaShop Modules Directory: When you need to replace incompatible modules, the official marketplace is the first place to look for verified alternatives.

These resources help you verify compatibility, plan your migration, and understand what the platform supports.

Related Guides

• Migrating from PrestaShop 1.7 to 9.x: A Step-by-Step Migration Plan
• PrestaShop 9 vs 8.1: Key Differences and Upgrade Considerations
• Optimising PrestaShop Checkout Speed for Higher Conversion Rates
• PHP 8.3 Compatibility: What PrestaShop Merchants Need to Know
• Choosing the Right PrestaShop Hosting for Symfony 6.4

Key Takeaways

PrestaShop 9.2 is the safer choice for existing stores, while 9.1x works well for new projects. The core architecture, Symfony 6.4 and PHP 8.1-8.3, is identical across the 9.x line, so your performance and security gains come from the major version, not the minor one.

The 9.2 improvements target the upgrade experience itself, with better pre-update audits that handle incompatible modules more clearly. If you have any custom code or third-party modules, this alone justifies choosing 9.2 over 9.1.

Your next step is to run the pre-update audit on a staging environment. This gives you the concrete list of what needs to change before you commit to the upgrade. From there, the transition becomes a manageable checklist rather than a leap of faith.

Frequently Asked Questions