PrestaShop Administration & Productivity

PrestaShop 500 & 404 Error Email Alerts 8 & 9: Checkout with No Carrier or Payment

The errors that cost you sales land in your inbox, with their cause.

A customer who hits a blank page, a newsletter link that leads to a 404, a Belgian buyer who is offered no carrier, a payment module disabled by an update: the shop does not warn you, and the customer leaves without a word. This module watches these four situations and sends an email to the addresses you choose, with the URL, the error message and what to check to fix it.

At a glance

500 error reported with the PHP message, the file, the line and the page concerned
404 errors grouped by URL, with an alert threshold and immediate alerts for broken internal links
Checkout with no carrier: country, zone, cart weight and the reason each carrier was excluded
Checkout with no payment method: country, currency, carrier and allowed payment modules
Emails sent after the page is displayed, anti-spam per problem and a daily summary

PrestaShop 8 & 9 500 and 404 errors Checkout diagnosis 8 languages

30-day refund
12 months updates
24h support

Built by a PrestaShop Certified Agency

www.datafirefly.com/en/

PrestaShop 500 & 404 Error Email Alerts 8 & 9: Checkout with No Carrier or Payment

v1.0.0 · updated 2026-10-26

What it does

The short version.

The diagnosis in the email

A “no carrier” alert lists every active carrier for the zone with the reason it is missing: outside its weight ranges, outside its price ranges, excluded by a product restriction. A “no payment method” alert compares the active payment modules with those allowed for the customer's country, currency, group and carrier.

500 errors with their cause

PHP fatal errors, uncaught exceptions and pages answering with a 5xx status are captured at the end of the request. The email gives the message, the file and line as a relative path, the page, the controller and the stack trace. For a PrestaShopException, the message is taken from the day's exception log.

Useful 404s, not noise

404s are grouped by URL, with tracking parameters (utm, gclid, fbclid) ignored. Bots, static files and known scans (/wp-*, .env) are filtered out. An alert is sent at the visit threshold you choose, or on the first visit if the broken link is on your own shop.

A readable inbox

The same problem is alerted only once per adjustable delay, with the number of occurrences between two alerts. A cap on emails per hour protects your inbox if the whole shop goes down, and a daily summary lists everything that was recorded.

The long version

Everything you'd want to know before you install.

A detailed look at how PrestaShop 500 & 404 Error Email Alerts 8 & 9: Checkout with No Carrier or Payment works, why we built it the way we did, and the thinking behind the features above.

§ 01

Four problems the shop does not report

A 500 error shows the customer a blank page and is written to a log that nobody reads. A 404 on an old Google link or a newsletter link loses the visit. A checkout that offers no carrier for a country, or no payment method, blocks the purchase without leaving any trace in the orders. The module detects these four cases on the front office and sends you an email when they happen.

§ 02

Why a customer has no carrier

PrestaShop's “no carrier available” message does not say why. The alert does: it gives the country, state, postcode and zone of the address, the cart weight and total, the products, the customer group, then each active carrier for that zone with the reason it was excluded. It also flags products in the cart that are limited to certain carriers, a frequent cause when bulky products and small parcels are mixed.

§ 03

Why no payment method appears

The restrictions in Payment > Preferences combine country, currency, group and carrier. A new shipping zone, an added currency or a newly created customer group is enough to empty the payment step for some customers. The alert gives the customer's country, currency, carrier and group, then lists the active payment modules and those allowed for that combination. The gap between the two lists shows where to fix it.

§ 04

500 errors a developer can fix

For a fatal error, the email contains the full message, the file and line as a relative path, the page requested, the HTTP method, the controller, peak memory and the PrestaShop and PHP versions. Identical errors are grouped and the server path is removed from messages. The cron availability check covers errors that occur before PrestaShop starts, such as a PHP-FPM crash.

§ 05

A focused module, alongside full monitoring

The module concentrates on 500 errors, 404s and checkout, with a detailed diagnosis for each. To also monitor response times, failed payments, drops in orders and the SSL certificate, and to receive alerts on Telegram, Slack or Discord, our PrestaShop Monitoring & Alerts module covers full monitoring of the shop.

Everything included

The long list.

The diagnosis in the email — A “no carrier” alert lists every active carrier for the zone with the reason it is missing: outside its weight ranges, outside its price ranges, excluded by a product restriction. A “no payment method” alert compares the active payment modules with those allowed for the customer's country, currency, group and carrier.

500 errors with their cause — PHP fatal errors, uncaught exceptions and pages answering with a 5xx status are captured at the end of the request. The email gives the message, the file and line as a relative path, the page, the controller and the stack trace. For a PrestaShopException, the message is taken from the day's exception log.

Useful 404s, not noise — 404s are grouped by URL, with tracking parameters (utm, gclid, fbclid) ignored. Bots, static files and known scans (/wp-*, .env) are filtered out. An alert is sent at the visit threshold you choose, or on the first visit if the broken link is on your own shop.

A readable inbox — The same problem is alerted only once per adjustable delay, with the number of occurrences between two alerts. A cap on emails per hour protects your inbox if the whole shop goes down, and a daily summary lists everything that was recorded.

Multiple recipients, one address per line, each one receives its own email

Alert language chosen independently of the shop language

Capture of PHP fatal errors and uncaught exceptions on the front office

Capture of any front office page answering with a 5xx status, maintenance mode (503) ignored

Message, error type, file and line as a relative path, stack trace, controller, memory

PrestaShopException message taken from the day's var/logs log

Identical errors grouped together, variable numbers being ignored

404s grouped by path, tracking parameters utm, gclid, fbclid ignored

404 alert threshold adjustable in number of visits

Immediate alert when the 404 comes from a link on your own shop

Filters for bots, static files and a list of URL patterns to ignore

Checkout with no carrier: country, state, postcode, zone, weight, total, products and group

Exclusion reason for each carrier and products limited to certain carriers

Checkout with no payment: country, currency, carrier, group, active and allowed modules

Emails sent after the response to the visitor (PHP-FPM and LiteSpeed)

Delay between two alerts for the same problem and cap on emails per hour

Daily summary at the time you choose, not sent if nothing happened

Cron availability check on up to 10 URLs

Cron via token URL or command line, task can also be run from the back office

Alerts saved to a file when the database stops responding, then replayed

Log filterable by type, detail view, deletion and CSV export

Test email button and counter for the last 24 hours

Translated into 8 languages: English, French, Spanish, German, Italian, Dutch, Polish, Portuguese

Compatible with PrestaShop 8.0 to 9.x, multistore

Questions

Anything still unclear?

Will I receive an email for every 404?

No. 404s are grouped by URL and the alert is sent when the same URL reaches the threshold you choose (5 visits by default). Bots, static files and known scans such as /wp-admin or .env are ignored. A URL that has already been reported is not reported again during the delay between two alerts, and all 404s, even below the threshold, appear in the daily summary.

Does the module slow down the shop?

On a page that displays normally, the module makes no database query. It only writes when there is an error or a 404, and emails are sent after the page has been delivered to the visitor when the server uses PHP-FPM or LiteSpeed.

Do I need a cron task?

It is recommended, every 15 minutes, from the command line or through the token URL shown in the module. It sends the summary at the scheduled time and runs the availability check. Without cron, real-time alerts work and the summary is sent after the next visit to the shop.

Do the emails contain customer data?

Checkout alerts give the cart ID and customer ID, the country, the postcode, the weight and the cart contents, which is enough to reproduce the problem. They contain no customer name, postal address, email or phone number.

How does it differ from the PrestaShop Monitoring & Alerts module?

This module focuses on 500 errors, 404s and blocked checkouts, by email, with a detailed carrier and payment diagnosis. The Monitoring & Alerts module also monitors response times, failed payments, drops in orders, SSL and disk space, and sends its alerts to Telegram, Slack, Discord or a webhook.

Are there cases the module cannot see?

A complete server or database outage prevents PHP from running: no module can then send an email, and you need an external monitoring service. The back office is not monitored. Checkout detection relies on the native checkout process; with a third-party one-page checkout module, it may be partial.

€89.00

One-time · 12 months updates

Read the docs

Unlimited dev & staging installs
Source code included
30-day refund
24h support · EN / FR

5.0/5 20 reviews

Marion TRONCHON 19 October 2026 ★★★★★

“Super responsive developer. The module was adapted to our needs. We're delighted to have bought our module from them. We recommend them 200%.”
Product Packs & Bundles Module for PrestaShop 8 & 9: Discounted Bundles & Kits
Gérard Burton 3 October 2026 ★★★★★

“Great, works really well+++++++++++”
Shopware 6 Abandoned Cart Recovery — Reminder Emails & Unique Discount Codes
jingjinghao6 24 September 2026 ★★★★★

“We purchased the DataFirefly Faceted Filter module for our PrestaShop 9 website, which uses Creative Elements. Alexandre has been incredibly responsive, professional, and helpful throughout the…”
AJAX Faceted Filters for PrestaShop
giuliano stella 17 September 2026 ★★★★★

“very useful module. after importing from woocommerce and after three years of work i had a lot of duplicate attributes, especially sizes, making the related filter…”
Merge Duplicate Attributes & Features PrestaShop 8 & 9
giuliano stella 7 September 2026 ★★★★★

“great, it makes it much easier to quickly edit a product page by going directly from the front office to the back office and back again…”
Front Office Admin Bar PrestaShop 8 & 9 – Edit Products from Your Storefront
Giuliano 20 August 2026 ★★★★★

“Simple and functional. Exceptional support.”
DataFirefly SEO Glossary — Industry term lexicon, automatic tooltips in your descriptions and internal linking to your products for PrestaShop 8 & 9
Tristan 28 July 2026 ★★★★★

“Spot on”
Free Gift Above a Cart Threshold — PrestaShop 8 & 9
Alex 27 July 2026 ★★★★★

“This module is really handy”
DataFirefly Product Positions — Drag & drop categories for PrestaShop 1.7.8, 8 & 9

PrestaShop 500 & 404 Error Email Alerts 8 & 9: Checkout with No Carrier or Payment