PrestaShop 9 is the platform’s biggest step since 1.6 became 1.7: Symfony 6.4, PHP 8.1 to 8.5, a new Admin API and the Hummingbird theme. That’s why it isn’t a one-click job. We audit first, rebuild what breaks, test everything on a copy of your shop, and only then touch the live store.
PrestaShop 9.0 became generally available in June 2025 after nearly two years of development, and 9.1 followed with the new theme switched on by default. It is not a cosmetic refresh - the core, the admin and the storefront were all modernised. Here is what your shop actually gains:
PrestaShop 9 runs on Symfony 6.4 LTS, which carries security support through November 2027, and requires PHP 8.1 as a minimum. Version 9.1 adds PHP 8.5 as the recommended runtime while keeping 8.1 to 8.4 supported. Staying on an unsupported PHP or framework version is the single biggest long-term risk to an e-commerce store - this removes it.
Built on API Platform, the Admin API exposes back-office functionality through a proper RESTful interface with JSON-LD, GraphQL and JSON:API support. ERP synchronisation, PIM feeds, warehouse systems and headless front-ends no longer need fragile custom bridges or direct database access.
Hummingbird 2.0 is the default front-office theme from 9.1 onward, built on Bootstrap 5, TypeScript and BEM. It also reaches over 95% compliance with the European Accessibility Act requirements out of the box - a substantial head start if the EAA applies to your business.
Cleaner product URLs, an optional language prefix so your main market is not forced into a subfolder, proper 301 and 302 handling for deactivated categories, and native WebP plus AVIF image support. Smaller images and correct redirects both feed directly into Core Web Vitals and rankings.
Database table prefixes are randomised automatically, direct file access is restricted, and module activity is logged so you can see what changed and when. Combined with a supported PHP branch, this closes off a large share of the attack surface we routinely find on older installs.
Modern PHP with JIT, Symfony 6.4 optimisations and the Hummingbird theme together typically deliver a 20-30% improvement in response times compared with the same store running PrestaShop 8. We measure your shop before and after, so you see the real numbers rather than a promise.
PrestaShop 9 needs PHP 8.1 or newer. Most quality hosting already offers it, but some shared plans and older managed servers are still capped at PHP 7.x. We check this in the audit, before any work is quoted or started.
| PrestaShop 9.x - our recommendation | PrestaShop 8.x - the fallback | |
|---|---|---|
| Minimum PHP | 8.1 (8.5 recommended on 9.1) | 7.2.5 |
| Framework | Symfony 6.4 LTS, supported to Nov 2027 | Older Symfony branch |
| Admin API | Yes - REST, GraphQL, JSON:API | No |
| Hummingbird theme | Default from 9.1 | Not available as default |
| When we choose it | Whenever the hosting environment supports it - which is most of the time. | Only when your server genuinely cannot run PHP 8.1+ and moving host is not an option right now. |
If your server cannot run PHP 8.1 yet, we do not force the issue. We will either help you move to hosting that can, or upgrade you to PrestaShop 8.x as an interim step and plan the move to 9 for later. Either way you leave an unsupported version behind - which is the part that actually matters for your security and your rankings.
Upgrading to PrestaShop 9 means dealing with real breaking changes. Many back-office controllers were rewritten for Symfony 6.4, so modules that override legacy admin controllers will stop working. Some front-office hooks were removed in Hummingbird. A heavily customised shop is not going to survive a blind one-click update - so we do not run one.
No blind one-click updates. Every step happens on a copy of your shop first.
We inventory your current installation: PrestaShop version, PHP and MySQL versions on the server, your theme, every module, every override and every third-party integration. This tells us whether 9.x is reachable directly, and what it will cost.
Before anything changes, we take complete backups of your files and database, and verify that they restore. A backup nobody has tested is not a backup. This is your rollback path for the entire project.
Every module is checked against PrestaShop 9. We flag those with an official 9.x release, those that need adapting because they override legacy admin controllers or removed hooks, and those that are abandoned and need replacing. You get that list with costs before we proceed.
We confirm your hosting can run PHP 8.1 or newer with the required extensions and a suitable MySQL or MariaDB version. If it cannot, we tell you straight away and lay out the options: change host, or take the 8.x route for now.
The upgrade runs first on a full staging copy of your shop using Update Assistant 7, including its CLI for repeatable runs. We then test the paths that earn you money: search, filters, cart, every payment method, every carrier, invoices, emails and the order workflow end to end.
Your existing theme can often be adapted, but Hummingbird brings real performance and accessibility gains. We show you both options with honest effort estimates so the decision is yours, not one we make silently on your behalf.
We deploy during off-peak hours, keep URLs stable and put redirects in place wherever they change, so your rankings survive the move. After launch we monitor logs and performance, fix what surfaces, and walk your team through what is new in the back office.
“I made and remade, updated and secured my online stores, with them, because the platforms still generate business and are viable online store solutions, validated by the market.”
It depends almost entirely on where you are starting from and how customised your shop is. These are realistic ranges, not sales figures - your audit gives you the exact number.
A standard shop without exotic modules is usually a short project - often a matter of days including full testing.
A module-heavy 1.7 store typically needs one to two weeks, most of it spent on module adaptation and testing rather than the upgrade itself.
Coming from 1.6 usually means a theme rebuild as well, which puts the project in the two to six week range.
Send us your PrestaShop version and your URL. We’ll tell you whether you can go straight to the new version, what will need work, and roughly how long it will take.
Talk to us in
We reply within one working day.
Leo, Péter, Attila and Szilamér
