PrestaShop 9.2 Unleashed: A Developer's Essential Guide to Key Changes

PrestaShop 9.2: Navigating the Future of E-commerce Development

The release of PrestaShop 9.2.0, announced on September 30, 2026, marks a significant milestone for the platform, bringing a host of developer-facing changes that will shape how modules, themes, and integrations are built and maintained. This community insight, derived from a detailed forum thread, provides a crucial overview for anyone involved in PrestaShop development or considering an upgrade.

Key Innovations and Developer Considerations in PrestaShop 9.2

  • Extra Properties (Experimental): This exciting new feature allows developers to attach custom fields to core entities like Products, Combinations, Customers, and Orders without resorting to custom tables or overrides. Supporting multistore, multilingual data, back office forms, grids, front office access, and the Admin API, it promises greater flexibility. However, its 'experimental' status means potential backward compatibility breaks, urging thorough testing and comparison with the reference module, demoextraproperty.
  • Native One Page Checkout: PrestaShop 9.2 introduces a native One Page Checkout module, offering a streamlined customer experience. Developers of payment, carrier modules, and themes must rigorously test their components against this new flow. A new hook, actionCheckoutBuildProcess, is available for integration.
  • Ask AI and the MCP Server: The platform now boasts 'Ask AI', a conversational assistant in the back office capable of answering data queries and triggering store actions. Operating via a separate PrestaShop MCP Server, its impact on modules that add back office actions or data needs investigation, though a module-facing API is not yet detailed.
  • Structured Data from the Core: The core now provides JSON-LD structured data via the actionFrontControllerSetVariables hook and a getStructuredData() method. Themes are responsible for rendering this data. Developers should review existing code that prints its own JSON-LD to prevent duplication, referencing the demoseo module for guidance.
  • Module Service Configuration Priority: A documented priority system for module service files simplifies version-specific wiring. Files like config/services-9.2.yml take precedence over services-9.yml and the generic services.yml, potentially reducing conditional version checks in module code.
  • Back Office and Data Enhancements: New product conditions (open_box, damaged, new_with_defects) require updates for code with fixed condition lists. Several core areas (Countries, Merchandise Return, Hook a module, Quick Access, Email body translations, Tax rules) are migrating to Symfony, with feature flags for testing. New console commands (e.g., prestashop:module:list, prestashop:employee:create-admin, prestashop:htaccess:generate) enhance administrative capabilities. The installer now automatically deletes the install/ folder.
  • Themes and Image Management: Image types gain a 'thumbnail fitment' setting (Fit, Crop, Bound). Hummingbird 2.1.2 introduces a manufacturer_product_page image type, a displayOrderDetailProductLine hook, and requires Node.js 24 and npm 11 for building. Theme developers should review child themes and custom overrides, especially concerning the provided beta QA checklist for theme validation.

System Requirements and Upgrade Path

PrestaShop 9.2 mandates PHP 8.1 as the minimum version, with support extending to PHP 8.5. Stores on 9.0.x or 9.1.x must use Update Assistant 7.6.6 or newer for a smooth upgrade.

Migration and Compatibility Best Practices

The forum thread strongly advises performing upgrades on a cloned environment with identical modules, themes, overrides, and PHP versions. Critical areas for testing include the One Page Checkout (ensuring all payment and carrier modules function correctly), migrated back office pages, and front office rendering to avoid duplicate JSON-LD blocks. Given that details can evolve between 9.2.x releases, developers are encouraged to consult the official release notes and DevDocs for the exact version in use.

Community Engagement and Future Outlook

Despite the comprehensive nature of the initial post, the thread received no replies, indicating a missed opportunity for community-driven findings and shared solutions regarding these significant changes. This highlights the ongoing need for developers to actively engage with official documentation and perform thorough in-house testing to adapt to PrestaShop's evolving ecosystem.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools