1. Verify the package and requirements
Record your current module, PrestaShop and PHP versions. Read the new release notes and vendor requirements, including any configuration changes or additional steps.
Obtain packages from the vendor. Purchased WO Software modules are available through your customer account subject to licence and update entitlement. No update notice in Module Manager does not prove that a module supplied outside Marketplace is current.
2. Prepare a backup and recovery plan
Back up the store files and database, record module settings and preserve any custom code changes for comparison. Include .htaccess when protection relies on server rules.
Confirm where the backup is and how to restore it. Replacing module files alone may not undo a database migration. Restoring a production database can discard later orders, so use an isolated test copy first.
3. Use an isolated test store first
Prevent the copy from sending real emails, using production payments or synchronising changes to external systems. Use the integration's proper test mode and a domain allowed by the licence.
Update one module, then test before making the next change. Protect the copy from accidental customer use.
4. Follow the vendor's upgrade procedure
Schedule maintenance if checkout may be interrupted. For a ZIP package, use Module Manager and the vendor's instructions. Wait for the operation result and confirm the installed version.
Do not uninstall or reset a module simply to upload an update. These actions may remove configuration or data. Use the intended upgrade process.
5. Test both storefront and back office
Choose checks appropriate to the module and compare with the pre-update baseline. A successful installer message does not test integrations or customer journeys.
- Browse the homepage, category, filters and product.
- Test cart and sign-in in a new session.
- Check delivery and the payment transition without an unplanned charge.
- Review configuration, required scheduled jobs and logs.
- For traffic protection, verify genuine customer activity before tightening rules.
6. If something fails
Record the time, exact message and reproduction steps. Avoid adding more updates while diagnosing. Send the vendor version numbers and a sanitised diagnostic sample.
Follow your recovery plan, considering database changes and new production data. Repeat the functional checks after restoring a working version.