Update PrestaShop safely
with a verified upgrade path

As a PrestaShop agency, Waldbyte updates existing shops using a documented upgrade path. We assess more than the core version: payment, shipping, checkout, customer data, product logic, modules, overrides, theme, PHP, database, and integrations must continue to work together on the target version.

Which PrestaShop versions do we update?

The appropriate route depends on the starting point and customizations. This overview shows the typical update or migration path:

Version status: 8 August 2026. For production shops, we recommend the latest stable 9.1.x release. PrestaShop 9.2 is currently beta software and is not intended for production. Before every project, the official release status and module approvals are checked again.

Audit → staging → testing → deployment → monitoring

1. Audit and upgrade plan: We inventory PrestaShop, PHP, database, modules, licences, theme, overrides, cron jobs, integrations, hosting, and known errors. The result is a risk list with a target version, upgrade route, test scope, and budget range.
2. Staging upgrade: The shop is prepared in a separate environment. We update the core and server environment, correct or replace incompatible components, and document the required changes.
3. Functional and acceptance testing: Tests cover login, search, filters, variants, prices, vouchers, tax, cart, checkout, payments, shipping, emails, refunds, cron jobs, tracking, and ERP, PIM, or marketplace workflows.
4. Controlled deployment: We agree on the maintenance window, responsibilities, backup, and acceptance criteria. Deployment is followed by data reconciliation and technical smoke tests.
5. Monitoring and handover: After launch, we closely monitor logs, orders, payment callbacks, cron jobs, integrations, and performance. Findings are prioritized and the implemented changes are documented.

How long does a PrestaShop update take and what does it cost?

These are non-binding indicative ranges for typical projects. A reliable quote is prepared after the technical audit.

Additional module licences, hosting migrations, new functionality, extensive design work, and external provider costs are not automatically included. Scope and exclusions are documented before commissioning.

What commonly causes extra upgrade effort?

• abandoned, encrypted, or individually modified modules,
• core modifications and undocumented overrides,
• custom themes, checkout, or pricing logic,
• old PHP or database versions and differing server configurations,
• ERP, PIM, CRM, payment, shipping, or marketplace integrations,
• multistore, B2B, and multilingual installations,
• large databases, inconsistent product data, or legacy data errors,
• previously failed updates and missing backups or version control,
• very short maintenance windows or near-zero-downtime requirements.

Rollback and post-launch monitoring

Before deployment, shop files and the database are backed up and rollback decision points are documented. Before the updated shop accepts new orders, the verified previous state can be restored completely. Once the shop has reopened, rollback also requires reconciliation of new orders, customer accounts, and stock changes. This is why data synchronization and clear decision points form part of the deployment plan.

A typical arrangement includes 48 to 72 hours of intensified checks after the update, followed by an agreed monitoring period. Checkout, payment, shipping, email, cron jobs, integrations, logs, tracking, 404 errors, and performance are monitored. Scope, response times, and responsibilities are defined in the quote.

Experience from a supported PrestaShop project

Waldbyte supports Ballonswelt, a product-rich PrestaShop shop in live operation. The technical work includes custom modules, theme and storefront adjustments, checkout and payment processes, and ongoing development. This experience directly informs upgrade audits: it is not enough for the core to start; business-critical workflows must remain stable under real operating conditions. Publicly approved project details are available on the Waldbyte projects page.

Frequently asked questions about PrestaShop updates

Can a PrestaShop update be performed directly in production? Small patch updates may be manageable depending on the setup. For version jumps, many modules, or customizations, we work in staging first and deploy only after documented acceptance.

Which PrestaShop versions does Waldbyte support? We assess shops from PrestaShop 1.6 onward. For 1.6 and early 1.7 versions, migrating data into a current new installation is often safer than a direct update. PrestaShop 1.7.8, 8.x, and 9.x are assessed against the actual module and theme landscape.

How much does a PrestaShop update cost? An update pre-check with a focused technical audit typically ranges from €350 to €750 net. Patch and minor updates commonly range from €600 to €1,500. An upgrade from PrestaShop 8.x to 9.1.x typically ranges from €1,500 to €3,500, while an upgrade from 1.7.8 to 9.1.x usually ranges from €2,500 to €6,000.

How long is the shop unavailable during deployment? Preparation takes place outside the live shop. The maintenance window depends on the data volume, deployment process, and required reconciliation and is tested and agreed in advance.

What happens to incompatible modules? We document whether each module should be updated, replaced, adapted, or removed. Business-critical payment, shipping, and ERP processes receive dedicated test cases.

Does Waldbyte support PrestaShop 1.7 to 9.x? Yes. Because of theme, PHP, module, and database changes, this is planned as a controlled upgrade or migration project. See our guide to upgrading PrestaShop 1.7 to 9.1.

Related services: PrestaShop agency for development and support, PrestaShop migration, and PrestaShop support after the update.