PrestaShop Order Workflow: Troubleshooting Custom Status Emails & Admin Filters

Streamlining PrestaShop Order Preparation: Custom Statuses, Email Control, and Admin Filters

Managing order fulfillment efficiently is a cornerstone of any successful e-commerce operation. For growing PrestaShop stores, the default 'Payment accepted' to 'Shipped' workflow often proves insufficient. This community insight delves into common challenges faced by merchants attempting to introduce intermediate order statuses, specifically focusing on unwanted email notifications and the inability to save custom filtered views in the PrestaShop admin panel.

A merchant running PrestaShop 8.1.7 (PHP 8.1) with a daily volume of 30-40 orders sought to improve their two-person order preparation process. They created a new custom status, 'En préparation' (In Preparation), configured with:

  • 'Consider order validated': Checked
  • 'Send email to customer': Unchecked
  • 'Display PDF invoice': Unchecked
  • An orange color for easy identification.

Despite explicitly unchecking the 'Send email to customer' option, some customers continued to receive emails when orders transitioned to this new status. The merchant suspected the order_conf template or a third-party module but found debugging difficult as 'Advanced parameters > Logs' offered no clear insights. The second challenge was the inability to save a default filtered view of orders for each preparer in the admin list, necessitating manual filtering every time.

Debugging Unwanted Email Notifications

The community offered crucial advice for diagnosing the persistent email issue:

  • Verify Status Configuration: Double-check that the email template associated with the 'En préparation' status is indeed empty or disabled under 'Orders > Order Statuses'.
  • Leverage Email Logging: The most critical step is to consult 'Advanced parameters > E-mail' (distinct from 'Advanced parameters > Logs'). This section logs every email sent by PrestaShop, including the template used and the exact time. By comparing this log with the time an unwanted email was received, merchants can precisely identify which template (e.g., order_conf) was triggered.
  • Investigate Third-Party Modules and Hooks: If the email log points to a template other than the one for your custom status, or if your custom status's template is somehow still being sent despite being unchecked, third-party modules (like payment or delivery modules) might be overriding the standard behavior via hooks. Testing in debug mode with cache disabled ('Advanced parameters > Performance') can help identify hooks being called during the status change.
  • Understanding order_conf: If the order_conf email is identified as the culprit, it's typically triggered by payment modules using PaymentModule::validateOrder() upon initial order validation. Its unexpected sending during a manual status change to 'En préparation' would be unusual and points strongly to a module conflict or an override.

Mastering Admin Order List Filters

For the filtering challenge, the community provided clarity and workarounds:

  • Native PrestaShop Limitations: PrestaShop, by default, does not allow saving custom default filtered views for the order list per employee. While PrestaShop 8.1.7 does remember the last filter applied by an employee for their session, it doesn't offer a way to set a permanent, default filtered view.
  • Module Solutions: The most robust solution is to use specialized modules like 'Advanced Order List' or 'Custom Order Views', which extend PrestaShop's administrative capabilities to allow saving and managing custom views.
  • Direct URL Workaround: A simple, code-free workaround involves constructing a direct URL with the desired filters applied (e.g., &order_state=X where X is the ID of your 'En préparation' status) and sharing this link with preparers. Each preparer can then bookmark their specific filtered view.
  • Cache vs. Database: It was clarified that PrestaShop's cache is not involved in remembering admin filters; these settings are stored directly in the database. Therefore, clearing the cache won't resolve filter persistence issues, nor will it typically cause them.

This thread highlights common PrestaShop configuration nuances. By understanding how email logging works, recognizing native admin panel limitations, and leveraging community-suggested workarounds or modules, merchants can significantly improve their order fulfillment workflows and internal communication.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools