PrestaShop 9.2: All the New Features and What Changes for Online Stores

PrestaShop 9.2 is not one of those releases made up mainly of background fixes and minor refinements. It changes several areas that merchants and developers have been asking about for years.

The stable release arrived on September 30, 2026, with three major additions: a native One Page Checkout, Ask AI inside the Back Office, and the new Extra Properties system. At the same time, PrestaShop continues moving legacy Back Office pages to Symfony, lays new foundations for B2B, improves structured data, adds developer tooling and introduces a number of smaller changes that are genuinely useful in day-to-day e-commerce work.

In practical terms, PrestaShop 9.2 makes the direction of the platform much clearer: fewer workarounds, more native capabilities, cleaner extensibility and a more modern technical foundation.

Native One Page Checkout: no third-party module required by default

One Page Checkout has been one of the most common requirements in professional PrestaShop projects for years. Until now, merchants who wanted the entire buying process on a single page usually relied on a third-party module.

PrestaShop 9.2 now includes a native One Page Checkout module in the distribution.

The main purchase steps are brought together on one page:

• customer details,
• address,
• shipping,
• payment,
• final confirmation.

The flow is guest-first, so a customer does not need to create an account before completing an order. Shipping and payment changes can be handled without a complete page reload, which makes the experience smoother, especially on mobile.

Merchants can switch between the new one-page flow and the traditional four-step checkout from the Back Office.

This does not mean every store should automatically change its checkout. What it does mean is that PrestaShop now provides an official baseline that theme, payment and carrier developers can target, instead of every store depending on a different third-party implementation.

Ask AI: artificial intelligence inside the Back Office

The most eye-catching addition in PrestaShop 9.2 is probably Ask AI.

It is a conversational assistant built into the Back Office that can answer questions using real store data and can trigger actions through natural language.

The important distinction is that this is not simply a generic chatbot embedded into an admin panel. Ask AI is powered by the PrestaShop MCP Server and can interact with the store itself.

This opens the door to questions and operations involving:

• products,
• orders,
• customers,
• stock,
• statistics and operational data.

PrestaShop does not lock Ask AI to a single AI vendor. Through MCP, merchants can connect a compatible provider using their own API key. This gives businesses much more control over which model and provider they use.

Ask AI also requests approval before performing actions that modify store data. That detail matters when AI moves from simply answering questions to actually operating parts of an e-commerce system.

MCP and PrestaShop: potentially the most important long-term change

Ask AI is the visible feature. The deeper change underneath it may be more important: Model Context Protocol support.

The PrestaShop MCP Server gives the platform a standardized way to communicate with AI models and agents. That can eventually support far more than an assistant panel in the Back Office.

AI agents could be used for tasks such as:

• stock monitoring,
• product updates,
• order analysis,
• report generation,
• automated commercial workflows,
• connections to external systems and tools.

For anyone following the development of agentic commerce, this may be one of the most strategically important additions in the release.

Extra Properties: custom fields without rebuilding the plumbing every time

Anyone who has developed serious custom PrestaShop modules knows the problem. You need one additional field on a Product, Customer, Order or Combination, and suddenly you are creating custom tables, relationships, persistence logic and hooks just to store one more piece of information.

PrestaShop 9.2 introduces Extra Properties to solve exactly that.

Typed fields can be attached to core entities with built-in validation, multistore and multilingual support.

Once an Extra Property is defined, it can be exposed in:

• Back Office forms,
• Back Office grids,
• the Front Office,
• the Admin API.

For developers, the key benefit is that this can be done without overrides and without rebuilding the same storage layer inside every module.

For merchants, that technical change translates into cleaner custom development, less duplicated code and a better chance that custom functionality will remain maintainable through future upgrades.

Improved B2B mode: foundations for more serious B2B projects

PrestaShop 9.2 also introduces the foundations of an improved B2B mode.

The new approach includes native business entities, B2B customer profiles, business identifiers, B2B addresses and role-based access for B2B users.

This is particularly interesting for companies that need several users under the same business account, more structured billing information or more complex corporate account management.

There is an important caveat: improved B2B is still behind a feature flag and is considered beta. We would not build a large production B2B project around it without careful evaluation yet.

It does, however, clearly show that PrestaShop is investing more heavily in an area that has traditionally required significant custom development.

New product condition values

PrestaShop traditionally supported the basic conditions new, used and refurbished.

Version 9.2 adds three additional values:

• open box,
• damaged,
• new with defects.

This is a small but useful improvement for merchants selling returns, display products, outlet stock or items with damaged packaging.

Modules and themes that read or display product condition should be checked so they correctly support the new values.

Better structured data for SEO

One of the more interesting changes for SEO and module developers is the new core-side approach to JSON-LD structured data.

Previously, a large part of structured data customization often ended up inside the theme or in custom template logic.

In PrestaShop 9.2, modules can add, modify or remove structured data through the core mechanism without editing templates.

This is useful for schema such as:

• AggregateRating,
• MerchantReturnPolicy,
• ContactPoint,
• and other JSON-LD entities.

For a modern store, where structured data helps both traditional search engines and AI systems understand products and policies, this is a meaningful architectural improvement.

The Symfony migration continues

PrestaShop continues its long-running migration of legacy Back Office pages to Symfony.

In 9.2, more areas are included, such as:

• Countries,
• Merchandise Return,
• Hook a module,
• Quick Access,
• Email body translations,
• Tax rules.

Some of these pages are still controlled through feature flags under Advanced Parameters → New & Experimental Features.

For merchants, the visual difference may be subtle. For developers, however, it means more modern routing, forms, security and easier extension through grid and form hooks.

New CLI tools for developers and administrators

PrestaShop 9.2 adds several Symfony console commands that are useful in staging, production and automated environments.

Among them:

• prestashop:module:list to list installed, active or disabled modules,
• prestashop:employee:create-admin to create a SuperAdmin from the CLI,
• prestashop:employee:change-password to reset an employee password,
• prestashop:htaccess:generate to regenerate .htaccess without using the Back Office.

These are not marketing features, but they are exactly the kind of improvements that make serious production stores easier to manage.

More flexible service configuration for modules

Modules can now provide Symfony service definitions not only through the classic services.yml, but also through PHP configuration and version-specific YAML files.

This makes it easier for module developers to support PrestaShop 9.2, PrestaShop 9 and older compatible versions without creating unnecessary forks of the same codebase.

Hummingbird 2.1.2 and Front Office improvements

PrestaShop 9.2 ships with Hummingbird 2.1.2, bringing additional fixes and refinements to the platform’s modern theme stack.

Image types also gain a new thumbnail fitment setting, giving stores better control over how images are fitted into predefined dimensions.

This can be especially useful in catalogues where inconsistent product image ratios would otherwise produce awkward crops across category pages.

PrestaShop Automation with Klaviyo

PrestaShop Automation with Klaviyo is included in the PrestaShop Classic distribution.

The integration makes it easier to build automated email and SMS campaigns, audience segments and personalized communication based on real store data.

That does not mean Klaviyo is the right tool for every merchant. What matters is that PrestaShop is placing more emphasis on marketing automation as part of the standard e-commerce stack.

Smaller changes that still matter

There are also less visible changes worth mentioning.

After a successful installation, the install/ directory is now removed automatically. Update Assistant 7.6.6 also supports upgrading to PrestaShop 9.2 from 9.0.x and 9.1.x.

The database schema changes to support Extra Properties, the new B2B foundation, additional product conditions and feature flags.

As with any meaningful platform upgrade, this is a reminder that a production store should not be treated as a site where you simply click “Update” and hope for the best.

Should you upgrade to PrestaShop 9.2 now?

The short answer is: it depends on your store.

If you are already running PrestaShop 9.0 or 9.1 with compatible modules and a modern theme, 9.2 is a very attractive upgrade.

If your store contains extensive custom development, a custom checkout, an older theme or mission-critical ERP and payment integrations, the right process is different:

1. take a complete backup,
2. clone the store to staging,
3. check module and theme compatibility,
4. test checkout, payments and carriers,
5. test ERP, feeds and automations,
6. run performance and SEO checks,
7. only then upgrade production.

The new One Page Checkout deserves particular attention where payment or carrier modules heavily modify the buying flow.

What does PrestaShop 9.2 really mean for an online store?

The value of 9.2 is not one isolated feature.

One Page Checkout reduces dependence on third-party solutions at one of the most important points in the buying journey. Extra Properties makes custom development cleaner. MCP and Ask AI bring PrestaShop closer to an agentic-commerce future. Structured data becomes easier to extend. Symfony continues replacing legacy areas. B2B starts gaining a more serious native foundation.

That is probably the most important message in this release: PrestaShop is not simply adding more features. It is trying to make the platform easier to extend, more modern technically and better prepared for how online stores will operate over the next few years.

Considering an upgrade to PrestaShop 9.2?

At Hot Web Design, we can handle compatibility assessment and migration to PrestaShop 9.2 using a staging environment, with full checks of the theme, modules, checkout, payments, ERP integrations, SEO and performance before anything reaches production.

We can also make use of the new 9.2 capabilities in custom development, Extra Properties, MCP integrations and automation, so the upgrade is not simply a version change but a real improvement to the store.

Explore our PrestaShop e-commerce development services or contact us to review your current installation.