On 30 September 2026, PrestaShop published the stable release of PrestaShop 9.2. It is the second minor release of the 9.x branch and one of the most substantial in years: the core now ships with a native one-page checkout, a custom field system for core entities, and an AI assistant inside the back office.
In our earlier article on PrestaShop 9.2 we looked at the direction the platform was taking. This one covers the final release: what it contains, what is ready for production, what is still experimental, and what you need to do before upgrading a live store.
What's new in PrestaShop 9.2 at a glance
- One Page Checkout — a native
ps_onepagecheckoutmodule included in the bundle. - Extra Properties — custom fields on products, combinations, customers and orders, with no extra tables and no overrides.
- Ask AI — a conversational assistant in the back office, powered by the PrestaShop MCP Server.
- PrestaShop Automation with Klaviyo — included in the PrestaShop Classic edition.
- New thumbnail modes — Fit, Crop and Bound for every image type.
- Hummingbird 2.1.2 — the updated default theme.
- More back office pages migrated to Symfony, plus new CLI commands.
- PHP support from 8.1 to 8.5.
One Page Checkout: the most visible change
For years PrestaShop shipped only with a four-step checkout, and merchants who wanted a single-page flow depended on third-party modules. Those modules were one of the most common sources of conflicts with payment and carrier modules — a problem we covered in detail in our article on Frankenstein stores.
With 9.2, one-page checkout becomes part of the platform itself. Contact details, address, delivery, carrier selection and payment sit on a single screen, and each section updates without a page reload. When a customer changes their delivery address, the available carriers are recalculated automatically. The flow is designed guest-first, and login and account creation have been moved to dedicated pages outside the checkout.
A few practical details that matter during rollout:
- The module is installed by default but not enabled automatically. You turn it on under Design > Checkout by selecting the "One-page checkout" or "Four-page checkout" layout.
- You can switch between the two at any time. That makes a controlled conversion test possible instead of a blind switchover.
- The new checkout works out of the box with Hummingbird-based themes. Themes built on Classic may require template adaptation.
What this means for modules
For developers, this is a significant change. The core introduces a new actionCheckoutBuildProcess hook that lets a module provide its own checkout process. If exactly one enabled module returns such a process, PrestaShop uses it instead of the default multi-step checkout; in every other case it falls back to the native flow.
The official documentation explicitly warns that payment modules, carrier modules and themes must be tested against the new flow. In real stores this is exactly where problems surface: a payment method that fails to initialise after an AJAX refresh, a carrier module with pickup-point selection that relies on a step reload, or custom fields hard-coded into the old theme's templates.
If you currently run a paid OPC module, the question is not whether to move to the native one, but when and with what migration plan. The built-in solution is maintained alongside the core and removes an entire class of conflicts from future upgrades.
Extra Properties: custom fields without custom tables
Until now, if a store needed extra data on a product, customer or order — an internal order reference, a product certificate, a business customer's VAT status — the answer was a module with its own tables, its own persistence logic and often a core override.
Extra Properties replaces that pattern with a single native extension point. A module can register a new field on a supported entity (Product, Combination, Customer, Order). Each field has its own type and validation rules, supports multiple languages, and automatically appears:
- in back office forms and grids;
- on the front office;
- in the Admin API.
Merchants can also create fields themselves under Advanced Parameters > Extra Properties, choosing whether each field shows in forms, in grids or in the API.
One important caveat: the developer documentation marks the Extra Properties code as @experimental. The PrestaShop team states that it has anticipated a wide range of scenarios specifically to avoid breaking changes, but the possibility formally remains. For business-critical data, that means the architecture should be planned carefully rather than built field by field without a design.
Ask AI and the PrestaShop MCP Server
Ask AI is a conversational assistant built directly into the back office. Merchants can ask questions about their store data (such as sales figures, orders, or stock levels) and trigger actions in natural language. Under the hood it runs on the PrestaShop MCP Server, so you are not locked into a single vendor: you connect your own AI provider (OpenAI, Gemini, Claude, Mistral and others) with your own API key. Before any action that modifies store data, Ask AI asks for explicit approval.
An important clarification: Ask AI is part of the PrestaShop Classic edition. The ecosystem offers two distinct download packages:
- The bare open-source core (from GitHub / prestashop-project.org) — the minimalist engine aimed primarily at developers building custom stacks.
- PrestaShop Classic (the package downloaded from prestashop.com) — the standard free, self-hosted distribution used by most merchants. It contains the exact same open-source core, but comes pre-bundled with official modules from PrestaShop SA, including Ask AI, the new Klaviyo automation module, and PrestaShop Marketplace connectivity.
We cover the protocol and what it can do in our guide to PrestaShop and MCP.
This highlights PrestaShop's core advantage over closed SaaS platforms once again: the AI layer is open to the provider you choose, and your data stays in your own store and on your own server.
Technical improvements worth your attention
Thumbnail fitment modes
Every image type in PrestaShop has configured target dimensions (for example, 800 × 800 px for product photos or 250 × 250 px in the cart). In earlier versions, if an uploaded image was not a perfect square, PrestaShop forcibly added blank white padding on the sides. In 9.2, every image type gets an Image fitment setting with three distinct modes:
- Fit (Default): Resizes proportionally so the full image fits inside the box. Remaining space is padded with a blank white background. The full item stays visible, but inconsistent photo ratios cause uneven product grids with white sidebars.
- Crop (Fill & Crop): Scales the image to completely fill the target dimensions, automatically cropping off top/bottom or side overflows. Produces a modern, razor-sharp, uniform grid with zero empty padding — ideal for fashion brands and modern storefronts.
- Bound (Max bounds without artificial whitespace): Resizes the image proportionally within maximum boundary limits, but generates the final image file with its exact reduced dimensions without adding artificial white canvas pixels. Essential for brand manufacturer logos (
manufacturer_product_page), banners or transparent PNG assets.
For stores with inconsistent product photography, this is a direct improvement to the visual consistency of listing pages. Keep in mind that changing the mode requires regenerating thumbnails, which takes time and server resources on large catalogues.
Core-side structured data
PrestaShop 9.2 renders JSON-LD structured data on the core side instead of relying on microdata in templates. Modules can add, override or remove structured data (for example AggregateRating or MerchantReturnPolicy) through the actionFrontControllerSetVariables hook without editing templates. This matters for traditional SEO and for visibility in AI-driven search alike.
New product conditions
Alongside the existing new, used and refurbished, three values have been added: open_box, damaged and new_with_defects. Product feed and marketplace modules that read the product condition should be checked to make sure they handle the new values correctly.
Module service configuration
Modules can now declare their Symfony services in a PHP file or in version-specific files. The loading priority is:
config/services.php config/services-9.2.yml config/services-9.yml config/services.yml
This makes it easier to maintain a single module across several PrestaShop versions.
New CLI commands
Several commands have been added for maintenance and automation:
# List modules (script-friendly output) php bin/console prestashop:module:list --simple --disabled # Create a SuperAdmin and reset a password php bin/console prestashop:employee:create-admin php bin/console prestashop:employee:change-password employee@example.com --password='S0meStr0ngP@ss!' # Regenerate .htaccess without back office access php bin/console prestashop:htaccess:generate --force
The installer also now removes the install/ folder automatically after a successful installation.
Hummingbird 2.1.2
PrestaShop 9.2 ships with Hummingbird 2.1.2, the default theme since version 9.1. The changes that matter for a live store:
- Checkout and orders — the address step no longer nests forms, so the Continue button works correctly when editing an address with a separate billing address. The guest order tracking form now submits with
POST. - New
displayOrderDetailProductLinehook — modules can display information next to each individual product in the order details. - Accessibility — accordion toggles on the store page are now real
<button>elements, and decorative icons are marked as such for screen readers. - Images — a new
manufacturer_product_pageimage type uses the new thumbnail mode, so brand logos on the product page appear without extra whitespace. - Fixes — tax-excluded prices in B2B mode are formatted with the currency, and the per-country tax label setting is respected on the product page.
- Security and development — development files have been removed from the theme package, and building from source now requires Node.js 24 and npm 11. This does not affect stores using the packaged theme.
If your store runs a child theme or a theme built on Hummingbird, test the parent theme update separately, because changes to the checkout templates may affect your overrides.
The Symfony migration continues
More back office pages have been migrated: Countries, Merchandise Return, Hook a module, Quick Access, Email body translations and Tax rules. They are available behind feature flags under Advanced Parameters > New & Experimental Features. If one of your modules extends any of these pages through grid or form hooks, test it against the migrated version before it becomes the default.
What is not production-ready yet
Not everything in 9.2 is meant for live production stores. Under Advanced Parameters > New & Experimental Features, there are two significant features still in early development:
- The new pricing engine (
new_pricing): Price calculation in PrestaShop (Product::getPriceStatic(), cart totals, specific prices and volume tiers) is historically one of the oldest and heaviest subsystems in the core. It generates multiple repetitive database queries and often bogs down catalog performance on large stores. PrestaShop has begun a ground-up architectural rewrite (Pricing v2 /CartCalculator) built on Symfony services for massive speed gains and clean extensibility. However, in 9.2 this engine is only in initial beta. Never enable it on a live store to avoid billing and cart calculation discrepancies. - The improved B2B mode (
improved_b2b): The first milestone towards native corporate accounts with multiple users and buying permissions. Its schema and APIs are still under active development and subject to breaking changes. The documentation explicitly advises against building on it today. If you sell B2B, see why PrestaShop is a strong choice for a B2B portal with the stable tools available right now.
Our recommendation is straightforward: never enable experimental feature flags on a production store.
How to upgrade to PrestaShop 9.2
System requirements
PrestaShop 9.2 runs on PHP 8.1 to PHP 8.5. The full server requirements (supported MySQL/MariaDB engines, required PHP extensions and server modules) are detailed in the official PrestaShop system documentation. If your hosting runs an older PHP version, the environment upgrade has to come before the store upgrade.
Where you are upgrading from
- PrestaShop 9.0.x and 9.1.x — upgrade with the Update Assistant module, version 7.6.6, which officially supports 9.2.
- A 9.2 beta or RC build — a direct upgrade to the stable release with Update Assistant is not possible. A fresh installation and data transfer are required.
- PrestaShop 8.x, 1.7 or older — this is not a routine update but a migration to a new major version. The theme, modules and customisations must be reviewed for compatibility with PrestaShop 9, Symfony 6.4 and PHP 8.1+. Our Aquamatrix.bg case study shows what such a project looks like in practice.
Pre-upgrade checklist
- A full backup of files and database, with a tested restore.
- Upgrade a staging copy first, never production directly.
- Inventory modules and overrides: which are active, which have 9.2-compatible versions, and which are no longer needed.
- Test the theme, especially if it is Classic-based and you plan to adopt the new checkout.
- Place complete test orders on mobile and desktop — with every payment method, every carrier, discounts and vouchers.
- Verify integrations: ERP, warehouse, invoicing, product feeds.
- Monitor the first real orders after go-live and keep a rollback plan ready.
On paper, that is seven steps. In practice, for a store with 30 to 40 modules, a custom theme and several integrations, the upgrade is a project of anywhere from a few days to a few weeks — and the most expensive mistake is a checkout incompatibility discovered only after launch.
Why 9.2 strengthens the case for PrestaShop
PrestaShop 9.2 solves problems that previously required paid modules, without introducing a monthly subscription or a percentage of turnover. The checkout is in the core, yet the code remains yours to adapt. On Shopify, checkout customisation is heavily restricted and much of it is reserved for the most expensive plan. On WooCommerce, comparable functionality still depends on a combination of plugins from different vendors. You will find a full comparison in our article on PrestaShop, WooCommerce or Shopify.
Add an open AI layer through MCP and Extra Properties instead of overrides, and 9.2 becomes the strongest foundation yet for a store that needs to grow without changing platforms.
What's next: GS Vision at PS Summit 2026
PrestaShop 9.2 is one more step in the platform's evolution. To follow the roadmap closely, the GS Vision team will attend PS Summit 2026, the international open-source ecommerce event organised by PrestaShop and Sylius, taking place on 4 and 5 November 2026 at the Lyon Convention Centre.
The event brings together more than 500 merchants, agencies and developers from across the PrestaShop ecosystem. For us, it is an opportunity to get first-hand insight into upcoming platform releases, discuss real-world experience with One Page Checkout and Extra Properties with the PrestaShop core team, and bring that knowledge straight into our clients' projects across Bulgaria and the EU.
We will share our key takeaways here on the blog after the event.
Frequently asked questions
When was PrestaShop 9.2 released?
The stable PrestaShop 9.2.0 release was published on 30 September 2026.
Do I have to use the new One Page Checkout?
No. The module is installed by default but not enabled automatically. You can choose between the one-page and four-page checkout under Design > Checkout and switch at any time.
If you currently use a third-party paid module (such as One Page Checkout PS, The Checkout, etc.) and prefer to keep it, you can continue using it, provided its author has published an update compatible with PrestaShop 9.2 and PHP 8.1+. However, transitioning to the native module eliminates annual subscription renewal fees and removes third-party compatibility risks during future core updates.
Can I upgrade directly from PrestaShop 8 to 9.2?
Moving from 8.x to 9.x is a major migration rather than a routine update. We recommend a full audit of the theme and modules and working on a staging environment before going live.
Which PHP version does PrestaShop 9.2 require?
PHP 8.1 at minimum. Versions up to and including PHP 8.5 are supported.
Is Ask AI free?
Yes, the module, source code, and integration within PrestaShop are completely free — there are no license fees or monthly software subscription costs owed to PrestaShop.
You only pay for your actual consumption (API tokens for generated queries) directly to the AI provider you connect with your personal API key (such as OpenAI, Anthropic Claude, Google Gemini, or Mistral). For standard daily back-office work, these costs typically range between a few cents and a few dollars per month on a pay-as-you-go model, and providers like Google Gemini even offer free daily tiers.
Upgrading to PrestaShop 9.2 with GS Vision
GS Vision is a team of Certified PrestaShop Developers (Level 2) based in Veliko Tarnovo, working with merchants across Bulgaria and the EU. We handle the 9.2 upgrade as a project: module and theme audit, a staging environment, migration to the native One Page Checkout, testing of every payment and carrier scenario, and a go-live with no interruption to sales.
If you are planning an upgrade or a migration from an older version, get in touch for an assessment of your store.
Sources
- PrestaShop Project — PrestaShop 9.2 is available
- PrestaShop DevDocs — Changes in PrestaShop 9.2.x
- PrestaShop DevDocs — One Page Checkout for module developers
- PrestaShop Project — Introducing One Page Checkout
- PrestaShop DevDocs — Extra properties
- PrestaShop DevDocs — System requirements
- GitHub — PrestaShop Update Assistant v7.6.6
- GitHub — Hummingbird v2.1.2 release notes
- PS Summit 2026