Does the Flow place real orders?

No. It stops before payment and only types test values. It does create a test cart on each run, which can trigger an abandoned-cart reminder.

Does Lumi recognise every shop?

It recognises PrestaShop. If your theme is heavily customised and Lumi cannot find the checkout, you record the Flow yourself in Pathly, without writing code.

Do my customers see anything?

Only if you turn the badge on: a small image in the footer, loaded from pathlyhq.com, that links to your status page. Everything else happens in the back office.

What happens if I uninstall the module?

Its settings are deleted from the shop. Your Ping and Flow stay in your Pathly account, where you can keep or delete them.

November 2026

PrestaShop module: know your checkout is broken before your customers do

JourneysAgencies

By The Pathly teamWeb journey monitoring · 5 min read · November 3, 2026

The Pathly module for PrestaShop creates the shop’s Ping, has Lumi prepare the Flow from cart to payment, and replays it after every update.

The Ping is green, the Flow is red

A cart module has just been updated. The home page loads, the server answers 200. But the button that leads to checkout is gone. Nobody can pay any more, and you hear about it from a customer, or from falling sales.

An uptime check sees nothing wrong: as far as it knows, the shop answers. Pathly splits the two questions. Ping checks that the shop answers. Flow opens a real browser and does what a visitor does: add a product to the cart, then go on to the payment page.

Pathly widget on the PrestaShop dashboard, test shop: Ping OK, Flow failing after a cart module update, with a screenshot of the step that breaks.

What the module does

Ping: as soon as the API key is saved, Pathly checks that the shop answers. A Ping that already exists for the shop is attached, never duplicated.
Flow prepared by Lumi: Lumi, the Pathly assistant, recognises PrestaShop and prepares the checkout Flow, from the cart to the payment page. Each proposed Flow is replayed before you see it. You validate it in one click.
Replay after an update: when PrestaShop or a module is updated, Pathly replays the Flow straight away.
Dashboard widget: status of the Ping and the Flow, date and screenshot of the last failure, plan and quotas, links to Pathly.
Availability badge in the shop footer, linked to your public status page. It is off by default.

Install the module and connect the shop

Download the module from the Modules page on pathlyhq.com. In the PrestaShop back office, open Modules > Module Manager > Upload a module, then choose the zip. Then click “Configure”. No account yet? The “Create a free account” button takes you there. In Pathly’s Settings, create an API key, ideally limited to a single Space. Paste it into the module and click “Connect”. The Ping is created.

Then click “Prepare the checkout Flow with Lumi”. Lumi explores the shop and replays each Flow before offering it to you. It never pays, never sends a form and only types test values. You keep the Flow you want with one click on “Validate this Flow”.

Module configuration page on a test shop: Pathly account connected, Ping active, checkout Flow proposed by Lumi with the “Validate this Flow” button, availability badge.

Only an administrator (SuperAdmin profile) sees the configuration page and the dashboard widget. The module runs on PrestaShop 1.7.7 to 9, with PHP 7.2 or later.

The replay after an update

An update is often what breaks a checkout. PrestaShop 9 and 8 tell the module when a module is updated. On every version, the module also compares the installed versions of PrestaShop and of the modules when an administrator opens the back office. As soon as a version changes, Pathly replays the Flow. Two replays are at least 10 minutes apart.

Within minutes you know whether the update broke the checkout. If the Flow fails, the dashboard widget shows the date and a screenshot of the step that breaks.

What goes to Pathly, and what does not

Nothing goes to Pathly before an administrator saves an API key.
After that, only the shop’s address and the versions of PrestaShop and of the module.
No data about your customers, no orders, no list of modules: module versions are compared inside the shop.
The API key is encrypted in the shop, never shown again and never written to logs.

On Pathly’s side, we apply the GDPR. The app, API, workers and screenshots are hosted on GCP, in europe-west1. A DPA is available.

Good to know before you run the Flow

Each run of the Flow creates a real cart on the shop, with test values. It can trigger your abandoned-cart reminders and show up in your cart statistics. Keep that in mind when you set up your reminders.

The availability badge stays off until you turn it on. Once it is on, your visitors’ browsers load its image from pathlyhq.com, like any image hosted elsewhere. Mention it in your privacy policy.

For agencies that maintain client shops

Install the module on each client shop, with one API key per shop, limited to that client’s Space. The day a module breaks a client’s checkout, the alert reaches you with the screenshot, before the client calls. Plans, frequencies and quotas are on the Pricing page.

Does the Flow place real orders?: No. It stops before payment and only types test values. It does create a test cart on each run, which can trigger an abandoned-cart reminder.
Does Lumi recognise every shop?: It recognises PrestaShop. If your theme is heavily customised and Lumi cannot find the checkout, you record the Flow yourself in Pathly, without writing code.
Do my customers see anything?: Only if you turn the badge on: a small image in the footer, loaded from pathlyhq.com, that links to your status page. Everything else happens in the back office.
What happens if I uninstall the module?: Its settings are deleted from the shop. Your Ping and Flow stay in your Pathly account, where you can keep or delete them.