Resend Order Confirmation: setup and help

Upload and install the mprresendorderconfirmation ZIP in Modules > Module Manager. Click Configure. The configuration page is informational; it does not contain resend rules or mail settings. Use Integrity for template, hook, and delivery checks.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.

Before resending, confirm the shop can send a PrestaShop test email from Advanced Parameters > E-mail. Check the mail configuration for the order's shop and the order_conf templates for its language.

There is no module settings form for recipients, templates, employee roles, or resend cooldowns. Enable or disable the module in Module Manager.

PrestaShop controls mail transport. Its PS_MAIL_METHOD values are 1 for PHP mail, 2 for SMTP, and 3 for disabled delivery. The actual configured value belongs to your shop; installing this module does not change it. For SMTP, configure the host, port, authentication, and encryption in PrestaShop. PS_MAIL_SERVER alone is not a complete SMTP setup.

The resend card requires an active Back Office employee session and edit permission on both Orders and this module’s Configuration page. Each resend is an admin POST request that also checks the admin token, the employee’s access to the order’s shop and the current shop context. The module has no role selector.

1. Open Orders > Orders and select the order.
2. Locate Resend Order Confirmation.
3. Check the displayed customer name and email.
4. Click Resend Email and accept the confirmation prompt.
5. Wait for the result before clicking again.

On PrestaShop 1.7.7 and newer, the card uses displayAdminOrderSide. Before 1.7.7, the legacy panel uses displayAdminOrder. The module suppresses that legacy panel on newer versions to avoid duplicate output.

The button is disabled while a request runs. You can resend again later; there is no cooldown setting. You cannot enter another recipient in the card. The message goes to the current email address on the customer account linked to the order.

The module calls Mail::Send() with the order language, shop, currency data, and the standard order_conf template. It rebuilds product and discount rows, invoice and delivery addresses, carrier, payment, reference, date, and totals from saved order information and current related records.

This is not an archived copy of the original email. Later changes to templates, customer account details, or address records can affect the resent content. Resending does not update order status, items, totals, payment, or shipment records. It adds a private note after a successful mail API result.

Templates are managed through PrestaShop, not through a module template picker. The base English files are:

mails/en/order_conf.html
mails/en/order_conf.txt

Mail template resolution may also use your theme's mail templates. Preserve matching templates for every language you use.

Useful rebuilt HTML variables include:

{firstname} {lastname} {email} {order_name} {date}
{products} {discounts} {payment} {carrier} {total_paid}
{total_products} {total_discounts} {total_shipping} {total_wrapping} {total_tax_paid}
{delivery_block_html} {invoice_block_html}

Plain-text variables include {products_txt}, {delivery_block_txt}, and {invoice_block_txt}. For example:

Order: {order_name}
Date: {date}
Products:
{products_txt}
Total paid: {total_paid}

Use an order belonging to an email address you control for your first test. Check the result message, the received email and the private order note. A success message means the mail was handed over for sending; check the inbox to see that it arrived.

After a successful mail result, the module attempts to save a private message containing [mprresendorderconfirmation], the recipient and a timestamp. The message record is linked to the authenticated employee ID; its body does not include the employee name. When module diagnostics are enabled for the request, resend successes and failures are logged there with the order ID.

You can count recent private notes with a read-only query. Replace ps_ with your database prefix:

SELECT COUNT(*)
FROM ps_message
WHERE private = 1
  AND message LIKE '%[mprresendorderconfirmation]%'
  AND date_add >= DATE_SUB(NOW(), INTERVAL 30 DAY);

If the card is missing, check the module enabled state, employee edit permissions for Orders and the module’s Configuration page, the order-page hook, version-specific placement, and that the order and customer still exist. If permission is denied, check the employee’s access to the order’s shop and the selected shop context, then reload the order page to refresh the admin session and token.

If the UI reports failure or the email is absent, check PrestaShop mail logs, transport settings, the order language’s templates, and the receiving mailbox. When PS_MAIL_METHOD=3 for the order’s shop, the module refuses the resend before calling Mail::Send() and does not add a success note. Enable native mail delivery before testing again.

The card selectors are #mpr-resend-order-conf, #mpr-resend-btn, and #mpr-resend-result. Check the active admin theme before styling them.

Uninstall through Module Manager. The module removes its menu and standard hook registration. It does not remove previously saved private order notes or PrestaShop log entries, and it does not change the orders or native mail setup.