Does Flow place a real order?

No. It stops at the payment page. It pays nothing and only enters test values. Each run leaves a test cart: exclude it from your abandoned-cart reminders.

Do I need the module to use Flow?

No. Flow opens the shop from the outside, like a visitor. The module adds the replay after each update and the state in the dashboard.

What does Pathly see of the shop?

Nothing before an administrator saves a key. Then only the address of the shop and the versions of PrestaShop and of the module. No customer or order data.

Do I need a copy of the shop to test?

It is better for a major update. If the copy has its own address, it can have its own Flow. The check right after going live is still essential.

November 2026

PrestaShop update: the checklist to test the checkout right after

AgenciesJourneys

By Simon RaynaudFounder of Pathly · 4 min read · November 10, 2026

A PrestaShop, module or theme update can break the cart with no visible error. Here is what to check right after, in order, before the client notices.

The back office says the update succeeded. The home page opens. Yet the Add to cart button does nothing, or the payment module has vanished from the last step. A PrestaShop update touches the core, the modules and the theme at once. The problem is rarely visible at first glance.

Before the update

Back up the database and the files, and check that the backup restores.
Write down the versions of PrestaShop, PHP, the theme and the payment and shipping modules.
Run the update on a copy of the shop first, if you have one.
Pick a quiet hour, and tell the client when it will happen.

Right after: the checkout, step by step

Clear the cache: Advanced Parameters > Performance. A stale cache often hides the error, or causes it.
Product page: add a simple product to the cart, then a product with combinations.
Cart: the total is above zero, and a voucher applies.
Checkout: address, carriers with a price for each zone, then the payment page.
Payment: every payment module is still offered, in live mode and not in test mode.
Customer account: login and account creation still work.
Back office: Advanced Parameters > Logs shows no new error, and no module has been disabled.
Place a real test order, and check that the confirmation email arrives.

The trap: everything works right after, then breaks later

A checklist says everything worked at 10 am. It says nothing about 4 pm, when the cache rebuilds, a scheduled task runs or a module updates itself. The server still responds, and an uptime tool stays green. Only a journey replayed to the end sees that the cart no longer works.

That is what Flow is for. A real browser opens the shop, adds a product to the cart, checks that the total is above zero and goes all the way to the payment page. It pays nothing and only enters test values. If a step breaks, the alert comes with a screenshot of the failing step.

Replay the Flow right after each update

The Pathly module for PrestaShop does this replay for you. It sees the update of PrestaShop or of a module, then asks for a Flow run once the update has finished. It also compares the installed versions, at most every five minutes, when an administrator opens the back office. It works from PrestaShop 1.7.7 to 9.

At install, paste an API key: the Ping of the shop is created. Lumi, the Pathly assistant, recognises PrestaShop and prepares the Flow of the checkout, and you validate it. The state of the Ping and of the Flow shows in the PrestaShop dashboard.

Does Flow place a real order?: No. It stops at the payment page. It pays nothing and only enters test values. Each run leaves a test cart: exclude it from your abandoned-cart reminders.
Do I need the module to use Flow?: No. Flow opens the shop from the outside, like a visitor. The module adds the replay after each update and the state in the dashboard.
What does Pathly see of the shop?: Nothing before an administrator saves a key. Then only the address of the shop and the versions of PrestaShop and of the module. No customer or order data.
Do I need a copy of the shop to test?: It is better for a major update. If the copy has its own address, it can have its own Flow. The check right after going live is still essential.