PrestaShop 9

A new generation of the e-commerce platform, the first major version after PrestaShop 8. It introduces Symfony 6.4 LTS, PHP 8.1-8.4 (8.5 from PS 9.1), the new Admin API, Hummingbird 2.0 and native WebP/AVIF.

AI integration (MCP Server), Symfony 6.4 LTS and newer PHP, the Admin API (REST/OAuth2/OpenAPI 3), Hummingbird 2.0 compliant with the EAA, native WebP/AVIF, as well as multi-carrier shipping and a new discount system.

A framework jump (Symfony 4.4 → 6.4), newer PHP, the XML Webservice replaced with a modern API, native AI, the Hummingbird 2.0 theme and native WebP/AVIF.

Yes, if you plan to develop your store over the next 2-3 years. Don’t upgrade „because you should”: make the decision after a migration audit.

It depends on the number of modules and the scope of theme customisation and integrations. We give an exact quote after a compatibility audit.

Some modules need updating to a version compatible with PrestaShop 9, and some need rewriting (especially custom ones based on the old XML Webservice). You get the full list after a compatibility audit.

Not every PrestaShop 8 store has to move to PrestaShop 9 straight away. The decision depends on the store’s technical condition, the number of modifications, the modules used, integrations and development plans.

Migration makes the most sense when the store needs modernising, new features are being developed or the current version is starting to limit further development. If the store runs stably, has no technical problems and you’re not planning major changes, sometimes the better solution is to start with an audit and a migration plan rather than an upgrade „right now”.

In practice, it’s not just about moving to a higher version. It’s about moving safely, without losing stability, sales or control over the store.

Module compatibility with PrestaShop 9 has to be checked technically, not just based on the vendor’s declaration. We verify the module version, compatibility with PrestaShop 9, compatibility with the required PHP version, and how it integrates with the cart, orders, payments, delivery, the admin panel and other key elements of the store.

The most important thing is to run the store in a test environment and check whether the modules work correctly after the upgrade. It’s worth paying particular attention to custom modules, older extensions, ERP, PIM and marketplace integrations, payments, delivery and all features that affect the purchasing process.

The result of such an analysis should be a list of compatible modules, modules that need updating and modules that need replacing or rewriting.

Not always. Migrating to PrestaShop 9 doesn’t automatically mean changing the theme, but the theme needs to be checked carefully before the upgrade.

If the store runs on a heavily modified theme, an older template or uses many overridden views, there may be problems with compatibility, the look of the page, the cart, the product page, the listing or JavaScript elements.

In some cases adapting the current theme is enough. In others it may be more cost-effective to move to a newer theme or rebuild the front end. The decision is best made after a technical analysis, not on the basis of „let’s change it, it sounds modern”. That’s usually the most expensive kind of optimism.

The time of the audit depends on the size of the store, the number of modules, integrations and the degree of modification. For simpler stores the analysis may take a few business days. In larger projects, especially with ERP, PIM or marketplace integrations, custom modules or an extensive checkout, the audit may take longer.

As part of the audit we check, among other things, the PrestaShop version, the server environment, modules, the theme, integrations, the purchasing process, the store’s key features and potential migration risks. Stores running in multistore mode, with many languages, currencies, price lists, customer groups or individual tax logic require a more thorough check of store configuration, domains, URLs, translations, taxes and pricing rules.

After the audit you get a recommendation: whether it’s worth migrating now, what needs to be prepared beforehand and which areas may require additional work.

When upgrading to PrestaShop 9, problems most often appear in modules, the theme, integrations and the purchasing process. There may be errors in the checkout, payments, delivery, the admin panel, ERP integration, stock synchronisation, invoicing, search or product display.

Stores with a large number of custom changes, older modules, a heavily modified theme or integrations written for a specific PrestaShop version are particularly at risk.

That’s why an upgrade shouldn’t be done without a test environment, a backup, a rollback plan and a list of areas to check after migration. Upgrading production „live” sounds dynamic, but it usually ends up looking less like a strategy and more like a fire in the server room.

Yes, the migration can be planned to keep store downtime to a minimum. The safest scenario involves preparing the upgrade in a test environment, carrying out an audit, fixing problems, running tests and only then a planned production switchover.

In practice, the store usually isn’t upgraded directly on production. First a copy of the store is prepared, and the modules, theme, integrations, purchasing process, payments, delivery and the most important sales scenarios are checked.

A short technical break may be needed for the final switchover, data synchronisation and order checks, but a well-planned migration avoids a long shutdown of the store and accidentally testing your customers’ patience.

It’s good practice to prepare a list of test scenarios before the migration: registration, login, guest purchase, customer purchase, discount calculation, delivery selection, payment, order statuses, transactional emails and the basic admin paths.

No, if it’s planned properly. During the migration you need to verify the URL structure, 301 redirects, canonicals, meta data, XML sitemaps, robots.txt, structured data, filter indexing and the behaviour of the key subpages that generate organic traffic.

The goal of the migration is not just to launch the store on a newer version, but to keep sales, visibility in Google and the correct operation of the whole purchase path.

Yes. Before migrating, you need to check whether the current server meets the technical requirements of the chosen PrestaShop 9.x version. This includes the PHP and MySQL versions, memory limits, PHP configuration, extensions, database performance and CRON tasks.

Even a correctly performed upgrade can cause problems if the server environment isn’t prepared for the new version of the store. That’s why the audit should assess not only the code and modules, but also the infrastructure the store runs on.

After implementation we provide support and monitoring, and we fix any faults as part of post-implementation support, with a guaranteed response time.