• New
Automatic order statuses in PrestaShop Pro | PrestaDev
Automatic order statuses in PrestaShop Pro | PrestaDev
Automatic order statuses in PrestaShop Pro | PrestaDev
Automatic order statuses in PrestaShop Pro | PrestaDev

Automatic Order Statuses Pro module for PrestaShop

Module version: 1.0.0

PrestaShop compatibility: 1.6.x 1.7.x 8.x 9.x

Module file updated: 08/5/2026 21:30:22

Product data updated: 08/5/2026 21:29:45


The PD Automatic Order Statuses Pro module enables automatic changes of order statuses in a PrestaShop store based on configurable rules with a time delay. Instead of manually changing the statuses of hundreds of orders, you create a rule specifying which initial status should be changed to which target status and after how much time. The module allows you to precisely filter orders by carrier and payment module, so different rules can apply to different delivery and payment methods. Order processing is carried out automatically via a CRON task triggered cyclically using a secured key. Each automatic status change is recorded in the event log, including the order number, the applied rule, and the execution date. The module fully supports multishop environments, where rules and logs are assigned to a specific store. Compatible with PrestaShop from version 1.7.0 to 9.x and PHP from 7.1 to 8.5, with no external dependencies.
zł 79.00
zł 64.23no tax
Price history:

Description

Automation rule configuration

  • Any number of rules — you can create an unlimited number of automation rules, each with its own set of conditions and time delay.
  • Initial and target status — for each rule, you select the status the order is currently in and the status it should be automatically changed to.
  • Delay in days, hours, and minutes — precise configuration of the waiting time before the status change. The time is counted from the moment the order entered the initial status.
  • Rule name — an optional text field that lets you assign the rule a clear name, e.g. “Cancel unpaid bank transfers after 3 days”, making it easier to identify in the list.
  • Start date — an optional date from which the rule starts working. It allows you to schedule the rule activation for the future or avoid processing historical orders.
  • Enabling and disabling rules — each rule has an activity switch, allowing you to temporarily pause its operation without deleting the configuration.
  • Rule validation — the module does not allow saving a rule in which the initial status is identical to the target status.

Order filtering

  • Carrier filter — the rule may apply to all orders or only to orders shipped by the selected carrier. The list of carriers is automatically retrieved from the store’s active carriers.
  • Payment module filter — the rule may apply to all orders or only to orders paid with a specific payment module. The list of payment modules is automatically retrieved from the installed payment modules.

Automatic CRON processing

  • Secured CRON endpoint — order processing is triggered by calling a URL with a unique security key generated during the module installation. The URL is displayed directly in the module panel.
  • Batch processing — up to 100 orders per rule are processed in a single CRON call, which protects against server overload when handling a large number of orders.
  • Full status change — the automatic status change triggers the same actions as a manual change in the administration panel, including sending email notifications to the customer if the given status provides for it.
  • Error handling — if changing the status of a single order fails, the error is logged in the PrestaShop log, and processing of the remaining orders continues.
  • Information about the last run — the module panel displays the date and time of the last CRON run and the number of orders changed during the last execution.

Administration panel

  • Rule list with filtering — a clear table with all rules, containing the following columns: name, initial status, target status, delay, start date, carrier, payment module, number of matching orders, and activity switch. The carrier and payment module columns have filters in the form of drop-down lists.
  • Matching orders counter — next to each rule, the current number of orders meeting that rule’s criteria is displayed, allowing you to immediately assess its scope.
  • Rule duplication — an existing rule can be copied with a single click. The copy is created as inactive, with “(copy)” appended to the name.
  • Bulk actions — selecting multiple rules in the list allows you to enable, disable, or delete them simultaneously.
  • Header with summary — above the rule list, an information panel is displayed with the number of active rules, the number of orders changed on the current day, the date of the last CRON run, and the URL for configuring the CRON task.

Change log

  • Full change history — every automatic order status change is logged with the order number, the identifier of the applied rule, the initial and target status, and the execution date.
  • Direct link to the order — the order number in the log is a clickable link leading directly to the order details page in the administration panel.
  • Filtering and export — the log allows filtering entries by order number, rule identifier, and date. The data can be exported to a file.
  • Cleaning old entries — a button in the panel allows you to remove entries older than 30 days with a single click, preventing unlimited growth of the log table.

Compatibility and security

  • PrestaShop 1.7.0 – 9.x — the module works on all PrestaShop versions from 1.7.0 to the latest 9.x, supporting both the classic administration panel and the new Symfony-based one.
  • PHP 7.1 – 8.5 — the module code is compatible with a wide range of PHP versions without the need to install additional libraries or Composer.
  • Multishop support — automation rules and the change log are assigned to the currently selected store in the multistore context.
  • Secure SQL queries — all database queries use PrestaShop security mechanisms: integer casting, the pSQL() function, and prepared statements.
  • Translations — the module is fully translated into Polish in both PrestaShop translation systems: the classic one (dictionary file) and the new one (XLF files).

Product Details

Prestashop 9.x support
Yes
Support for Prestashop 8.x
Yes
Prestashop 1.7.x support
Yes
Prestashop 1.6.x support
Yes
Module translations
EN, ENG
Free support
Yes
Free updates (1 year)
Yes
PDASZP

FAQ

Find answers to the most common questions about this product.

The module automatically changes order statuses in the PrestaShop store based on the rules you create. You specify which initial status should be changed, to which target status, and after what time (in days, hours, and minutes). Instead of manually reviewing and updating orders, the module does it automatically via a CRON job.

Go to the Modules > PD Automatic Order Statuses > Rules tab and click Add new rule. Select the initial status (e.g. Awaiting bank transfer payment), the target status (e.g. Cancelled), set the delay (e.g. 3 days, 0 hours, 0 minutes), and click Save. The rule will be active and will start working at the next CRON run.

The CRON task URL is displayed in the green information panel above the list of rules. Copy this URL and add it as a CRON task on your server (e.g. every 5 or 15 minutes). The URL contains a unique security key that protects the endpoint from unauthorized access. Example CRON entry: */5 * * * * curl -s "cron_url_address" > /dev/null 2>&1

Yes. When creating a rule, two optional filters are available: Carrier and Payment module. If you select a specific carrier, the rule will apply only to orders shipped using that delivery method. Similarly with the payment module — for example, you can cancel only orders paid by bank transfer, without affecting orders paid by card.

The delay consists of three fields: days, hours, and minutes. These values are added together to create the total waiting time. For example: 1 day, 12 hours, and 30 minutes means that the order status will change after 36 hours and 30 minutes from the moment the order entered the initial status.

The start date is an optional field. If you set it, the rule will only start working from the specified date. Orders that received the initial status before this date will not be processed. This is useful when you want to schedule the rule activation for the future or avoid processing old orders on the first run.

Yes. Automatic status change works exactly the same as a manual change in the administration panel. If a given status in PrestaShop is configured to send email notifications to the customer, the email will also be sent when the status is changed automatically by the module.

In the module panel, there is a Logs tab available, where every automatic status change is recorded. Each entry contains the order number (a clickable link to the order), the identifier of the applied rule, the initial and target status, and the execution date. Additionally, the date of the last CRON run and the number of changed orders are displayed in the green information panel.

The Matching orders column shows the current number of orders in the store that meet the criteria of a given rule: they have the appropriate initial status and match the configured carrier and payment module filters. This value does not take the time delay into account — it shows the full pool of orders that will ultimately be processed by the rule.

Yes. Each rule has an Active (Yes/No) toggle. Setting it to No causes the rule to be skipped during CRON processing, while its configuration is preserved. You can re-enable it at any time. The toggle is available directly in the list of rules without the need to enter edit mode.

In the list of rules, the Duplicate action is available for each item. Clicking it creates a copy of the rule with identical settings, with “(copy)” added to the name. The copy is inactive by default, which allows its parameters to be modified before it is enabled.

Yes. In a multishop environment, automation rules and the change log are assigned to the currently selected shop. Each shop can have its own set of rules. CRON processes rules from all shops, but each rule applies exclusively to orders from the assigned shop.

In the Logs tab on the toolbar, the Clear logs older than 30 days button is available. Clicking it removes all entries older than 30 days from the currently selected store. Newer entries remain untouched.

In a single CRON run, the module processes up to 100 orders per rule. If a rule matches a larger number of orders, the remaining ones will be processed in the next CRON run. This limitation protects the server from overload when handling a large number of orders.

The module works with PrestaShop from version 1.7.0 up to the latest 9.x, and with PHP from version 7.1 to 8.5. It does not require Composer or any external libraries. It supports both the classic administration panel in older versions and the new Symfony-based panel in PrestaShop 8 and 9.

Reviews (0)

No reviews