Blog navigation

Latest posts

Install Pushover on PrestaShop: Complete Guide (BdPushover Module)
Install Pushover on PrestaShop: Complete Guide (BdPushover Module)
84 views

Are you looking for a reliable solution to receive a push notification on your smartphone for a new PrestaShop order...

Lire la suite'
PromoBar – New PrestaShop Module: Customizable Announcement Banner, Lightweight and Without Dependencies
PromoBar – New PrestaShop Module: Customizable Announcement Banner, Lightweight and Without Dependencies
309 views

New October 17, 2025 by BeDOM – Web Solutions We are releasing PromoBar, an open-source module that displays an...

Lire la suite'
🐞 PrestaShop Bug Fix: What You Need to Know
🐞 PrestaShop Bug Fix: What You Need to Know
355 views

Discover how to effectively diagnose and fix a bug on PrestaShop. Common causes, debugging method, concrete examples,...

Lire la suite'
🛠️ WordPress Bug Fixing: Complete Guide to Solving Your Problems
🛠️ WordPress Bug Fixing: Complete Guide to Solving Your Problems
456 views

Discover how to master WordPress bugs with our comprehensive guide! Learn how to identify and fix common errors,...

Lire la suite'

Install Pushover on PrestaShop: Complete Guide (BdPushover Module)

Contents

  1. Why connect Pushover to PrestaShop?
  2. Prerequisites: Pushover account + PrestaShop/PHP compatibility
  3. Create your API Token Application and retrieve your User Key
  4. Install the BdPushover module on PrestaShop
  5. Configure BdPushover (events, statuses, recipients)
  6. Templates: ready-to-use examples + available variables
  7. Advanced Pushover options (sound, priority, Emergency)
  8. Notification test and debug: diagnose quickly
  9. GDPR / privacy: what is sent to Pushover
  10. Troubleshooting: the most common causes
  11. FAQ “Pushover PrestaShop”

Why connect Pushover to PrestaShop?

Many PrestaShop stores still rely on emails for order tracking. In practice, common issues include: spam, reception delays, disorganized shared inboxes, or simply the need to alert multiple people (logistics, customer support, management) in real-time. The Pushover PrestaShop approach involves sending a push notification directly to a phone when a critical event occurs.

The BdPushover module was designed for seamless integration into the PrestaShop order lifecycle: new order and status change, with configurable and multilingual messages. Result: you receive the right information at the right time without constant connection to the Back Office.

View the official Pushover PrestaShop module page

Prerequisites: Pushover account + PrestaShop/PHP compatibility

1) What you need from Pushover

  • A Pushover account
  • An Application API Token (created via a Pushover “application”)
  • One or more User Key(s) (recipients)
  • (Optional) A Device name if you want to target a specific device

2) PrestaShop Compatibility

BdPushover declares compatibility from PrestaShop 1.7.0 (and is used on modern branches, including 8 and 9). In practice, if your store runs on PrestaShop 1.7+, you're within scope.

3) PHP Compatibility (exhaustive, by PrestaShop family)

The module follows the official PHP compatibility of your PrestaShop version. If your PrestaShop is compatible with a version of PHP, the module can run within the same range. For accuracy, refer to the official PrestaShop tables:

Practical references (verify according to your PrestaShop sub-version):

  • PrestaShop 1.7.x: depending on the sub-version, typically PHP 5.6 → 7.4.
  • PrestaShop 8.x: typically PHP 7.2.5 → 8.1 (8.1 recommended).
  • PrestaShop 9.x: PHP 8.1 minimum, extended support up to 8.4 as per documentation.

4) Server Prerequisites (important for “Pushover PrestaShop”)

Pushover operates via HTTPS API. Your server must be capable of making outgoing HTTPS requests. Without this, no notification can be sent.

  • PHP cURL extension: required (BdPushover needs it to call the Pushover API)
  • HTTPS output allowed (port 443) to Pushover domains
  • Environment conforming to usual PrestaShop prerequisites (OpenSSL, JSON, PDO, etc.)

5) Available Languages

The module is available in the following languages: FR, EN, DE, IT, ES. Templates are multilingual and can be adapted by language in the configuration.

Create your API Token Application and retrieve your User Key

To use Pushover with PrestaShop, you need two pieces of information: the Application API Token and the User Key(s).

Step A — Create a Pushover application

  1. Log in to your Pushover account.
  2. Create a new “application” (name of your choice, for example, “PrestaShop”).
  3. Copy the Application API Token: this is the token to paste into BdPushover.

Step B — Retrieve the User Key (recipient)

  1. In Pushover, locate your User Key (user key).
  2. If you want to notify multiple people: retrieve the User Key of each person.
  3. You can paste multiple keys into BdPushover (one per line).

Step C — (Optional) Target a device

If you use Pushover on multiple devices (smartphone + tablet, for example), you can target a device via the Device field in the module configuration.

Install the BdPushover module on PrestaShop

Method 1 — Installation via the Back Office (recommended)

  1. Download the module archive from your BeDOM customer area (or the designated location upon purchase).
  2. In PrestaShop: Modules → Module Manager.
  3. Click on “Add a module” and then select the module archive.
  4. Once installed, open the configuration page for the BdPushover module.

Method 2 — Manual Installation (FTP/SSH)

  1. Decompress the archive and check that the folder is named bdpushover.
  2. Upload the bdpushover folder to /modules/ on your hosting.
  3. In the Back Office, go to Modules and install BdPushover.

Tip: After installation, clear the PrestaShop cache if your environment requires it (especially on heavily customized shops).

Configure BdPushover (events, statuses, recipients)

1) Enter Pushover credentials

  • Application API Token: paste the token from your Pushover application.
  • User keys: paste one or more User Keys (one per line).
  • Device (optional): specify a specific device if you want to target a device.

2) Choose PrestaShop events to notify

BdPushover manages two main events:

  • New order: notification at the time of order validation.
  • Order status change: notification during a status update.

3) Select the statuses that trigger a notification

To avoid noise, you can select only important statuses (e.g., “Payment accepted,” “Shipped”). This is key for an “agency / multi-client” use: you adapt the statuses according to the merchant's process.

4) Enable Back Office link to the order (option)

If you enable the corresponding option, you can use the variable {admin_order_url} to include a direct link to the order in the Back Office.

Templates: ready-to-use examples + available variables

Available variables in BdPushover

You can construct your messages with the following variables:

  • {shop}
  • {order_id}
  • {order_reference}
  • {customer}
  • {total}
  • {currency}
  • {status}
  • {date}
  • {admin_order_url} (if “admin link” option is enabled)

Example 1 — Template “New order” (simple and effective)

Title:

New order {order_reference}

Message:

Shop: {shop}
Customer: {customer}
Total: {total} {currency}
Date: {date}

Example 2 — Template “Status change” (for logistics/customer support)

Title:

Order {order_reference} → {status}

Message:

Customer: {customer}
Total: {total} {currency}
Date: {date}

Example 3 — Template with Back Office link

(Enable the admin link option, then use {admin_order_url})

Order: {order_reference}
Status: {status}
BO Link: {admin_order_url}

Multilingual: best practices

If your store is multilingual, define templates per language (FR/EN/DE/IT/ES) and avoid ambiguous abbreviations. The goal is for the notification to remain immediately understandable, even when multiple people are recipients.

Advanced Pushover options (sound, priority, Emergency)

Choose a sound

Pushover allows you to choose a sound for the notification. This can be useful for distinguishing an order from a status change or making the notification more “visible” in logistics.

Priority

BdPushover exposes the notion of Pushover priority. Use a standard priority for most cases. Reserve high priorities for truly critical situations (e.g., payment accepted on flash sales, incidents).

“Emergency” mode (retry / expire)

The Emergency mode triggers persistent notifications (according to Pushover rules). BdPushover allows setting: retry (repetition interval) and expire (maximum duration). Use sparingly, only if your organization justifies it.

Notification test and debug: diagnose quickly

1) Send a test notification

BdPushover includes a test button/form. Before testing real events (orders/statuses), always start with a test: this validates token, User Key, and server connectivity to the Pushover API.

2) Enable logs (debug mode)

If issues arise (no notification, partial notifications, etc.), enable the debug option. The module then writes useful information in PrestaShop logs (via the logger).

3) Then test in real conditions

  1. Place a test order (or duplicate an order in pre-production environment if you have one).
  2. Change the order status to a status selected in the configuration.
  3. Verify that the notification arrives and that the content matches the template.

GDPR / privacy: what is sent to Pushover

BdPushover sends a notification payload to the Pushover API. The exact content depends on your templates and the variables you choose. For example: order reference, total, status, customer name... or a minimalist message otherwise.

Good practice: limit content if multiple people are recipients, and avoid sending sensitive information if not necessary. In an agency context, consider documenting this in your project file.

Troubleshooting: the most common causes (Pushover PrestaShop)

1) The test does not work

  • Verify the Application API Token and the User Key(s).
  • Check that the PHP cURL extension is active.
  • Check HTTPS output (firewall / hosting rules) to the Pushover API.
  • Enable debug and check PrestaShop logs.

2) The test works, but not orders/statuses

  • Verify that the “new order” event is enabled.
  • For statuses: check that the statuses you test are selected.
  • Test with a simple status (e.g., “Payment accepted”) to isolate the issue.
  • Enable debug and verify the trigger during status changes.

3) Incomplete notifications or unexpected content

  • Check the templates (title/message) and variables.
  • Verify the language used: the module can rely on the order's language when available.
  • If using {admin_order_url}, check that the admin link option is enabled.

4) In agency / multi-module environments

On heavily customized shops, modules can override behaviors or modify the order/status workflow. In such cases, debugging is your best ally. If necessary, isolate by temporarily disabling modules related to checkout.

FAQ “Install Pushover on PrestaShop”

Is the module multilingual?

Yes. The module is delivered in FR/EN/DE/IT/ES and templates can be adapted by language.

Can multiple people be notified?

Yes. You can paste multiple User Keys (one per line). Convenient for an e-commerce team.

Can you receive only certain statuses?

Yes. You can select statuses that trigger a notification to limit noise.

Does it work on PrestaShop 8 / 9?

The module declares compatibility from PrestaShop 1.7.0. PHP compatibility depends on the installed PrestaShop version (see prerequisites and links to official documentation).

Pushover PrestaShop Module: go further

If you want to quickly deploy a PrestaShop push notification solution based on Pushover, BdPushover is designed for: configuring events, choosing statuses, customizing templates, notifying multiple recipients, and easy testing and diagnosis.

View the official Pushover PrestaShop module page

Disclaimer (trademark / logo)

Pushover is not a trademark of BeDOM – Web Solutions. The use of the name "Pushover" and the Pushover logo in the module name, visuals, and description has been approved by Pushover.

Ce blog vous a-t-il été utile?
Posted in: PrestaShop Modules
I am Bertrand Domat, a Full-Stack Web Developer and founder of BeDOM – Web Solutions. Passionate about creating WordPress and PrestaShop sites, I have over ten years of experience in the development, maintenance, and optimization of digital projects. I place great importance on UX/UI, performance, and SEO, to provide users with a seamless experience and enhance online brands. Through this blog, I share my tips, tutorials, and best practices, to help you develop your business, gain visibility, and increase your sales online.

Leave a comment

Security code