Skip to main content

Configuring Reminders

The module sends reminders based on individual message entries you create. Each message defines exactly when it is sent (relative to the order creation date) and what it contains. There is no global first-delay or interval setting β€” the schedule is entirely determined by the set of messages you create.

πŸ“‹ Accessing the Configuration​

  1. Log in to your PrestaShop back office.
  2. Navigate to Modules > Module Manager.
  3. Search for Wire Transfer Reminder and click Configure.

The configuration page is divided into sections: the Messages list at the top, followed by Global Settings, Test Mode, Email Template, and Cron Job.

πŸ“§ The Message List​

The message list is the core of the module. Each row represents one reminder email that will be sent at a specific point in time. The list shows:

ColumnDescription
Payment ModuleWhich payment module this message applies to (e.g., bankwire, ps_wirepayment)
TimelineHow many days or hours after order creation this message is sent
Email titleThe subject line of the reminder email
Message to sendA text preview of the email body
Cancel OrderWhether the order is cancelled automatically after this message is sent

Messages are sorted chronologically by their send time, so the full reminder sequence is visible at a glance.

Adding a New Message​

  1. Click Add new Message in the message list toolbar.
  2. Fill in the form:
FieldDescription
Payment ModuleSelect the payment module this reminder applies to. The list is populated from payment modules that have been used in your store's orders (defaults to bankwire / ps_wirepayment if no orders exist yet).
Time unitChoose Days or Hours as the unit for the offset below.
Time after the order is createdEnter the number of days or hours to wait before sending this message. For example, 3 with unit Days sends the message 3 days after the order is created.
Email subjectThe subject line for this reminder. Supports per-language tabs and template variables.
Message to sendThe HTML body of the reminder email. Supports per-language tabs, a rich-text editor, and template variables.
Cancel the order after this messageEnable to automatically cancel the order when this message is sent. The order status is changed to Cancelled.
  1. Click Save to add the message to the sequence.
tip

When adding a new message, you can select a pre-written template from the Use a template dropdown at the top of the email content section. Templates are grouped into "Gentle Nudge", "Persistent Follow-up", and "Urgent / Final" categories and pre-fill the subject and body for you.

info

You can define messages in days or hours. 1 day = 24 hours. If you mix units, the module converts them to hours internally when sorting the sequence.

Editing or Deleting a Message​

Click the Edit icon in any message row to change its timing, subject, content, or cancel-order setting. Click Delete to remove a message from the sequence.

Building a Sequence Example​

To send three reminders over two weeks, create three messages:

Day offsetPurpose
Day 3Friendly first reminder with bank details
Day 8Follow-up noting payment is still pending
Day 15Final notice β€” enable Cancel the order after this message

The cron job checks orders each time it runs and sends whichever message in the sequence is now due for each order.

βš™οΈ Global Settings​

The Global Settings section controls module-wide cancellation and admin notification behavior.

FieldDescription
Activate Cancel Orders FeatureEnable to let the module automatically cancel orders once the configured number of expiration days has passed, regardless of whether a specific message has the cancel toggle enabled.
Cancel Order after (days)Number of days after order creation after which the order is cancelled. Only active when the feature above is enabled. If a message with the cancel-order toggle is reached before this number of days, that message's cancellation takes priority.
Admin Digest EmailEnable to receive a summary email listing orders that are approaching their cancellation deadline. Helps you take action before losing the sale.
Digest EmailEmail address to receive the admin digest. Leave empty to use the shop email address.
Alert Before Cancellation (hours)Send the digest when orders are within this many hours of being cancelled. For example, 24 means you are notified one day before cancellation.
warning

Cancelling an order releases the reserved stock and sets the order status to Cancelled. This cannot be undone automatically. Set the cancel days high enough to give customers adequate time to complete the transfer.

πŸ§ͺ Test Mode​

Test Mode lets you verify your reminder setup without affecting real customers or orders.

FieldDescription
Enable Test ModeWhen on, all reminder emails are sent to the test email address instead of the real customer. Orders are not cancelled and message-sent status is not updated, so the same messages will be sent on every test run.
Test Email AddressAll reminder emails go here while test mode is active.
Test OutputChoose Email to receive test emails at the test address, or Screen to display the output in the browser when the cron URL is called.
info

A banner is shown at the top of the configuration page whenever test mode is active, so you cannot accidentally leave it on after going live.

πŸ• Cron Job Setup​

The module sends reminders only when its cron endpoint is called. Without a configured cron, no emails are sent.

The Cron Job section displays the full cron URL to use:

https://yourstore.com/wiretransferreminder/cron?key=YOUR_TOKEN

The token (key parameter) is generated automatically during installation and is unique to your store.

info

If your store has friendly URLs disabled, use the raw URL instead: https://yourstore.com/index.php?fc=module&module=wiretransferreminder&controller=cron&key=YOUR_TOKEN

Setting up on a server (SSH / cPanel / Plesk)​

Add a cron job that calls the URL with curl. Recommended frequency: once per hour (so hour-based messages fire on time) or once per day if you only use day-based offsets.

Hourly example:

0 */1 * * * curl -l -k "https://yourstore.com/wiretransferreminder/cron?key=YOUR_TOKEN" >/dev/null 2>&1

Every 3 hours example:

0 */3 * * * curl -l -k "https://yourstore.com/wiretransferreminder/cron?key=YOUR_TOKEN" >/dev/null 2>&1
tip

If your hosting does not provide SSH access, use the "Cron Jobs" tool in cPanel or Plesk. Alternatively, a free external cron service such as cron-job.org can call the URL on your chosen schedule.

warning

Keep the cron URL (and the key parameter) private. Anyone who can call that URL can trigger email sending. The key is token-protected and returns HTTP 403 for unauthorized requests.

βœ… Final Checklist​

  • At least one reminder message has been created with the correct payment module, day offset, subject, and body
  • Additional follow-up messages created if needed (the sequence is defined by all individual messages)
  • Bank details variables are configured in the Custom Variables section ({account_info}, {account_number}, {bank_address})
  • Global Settings reviewed β€” cancel orders feature configured if wanted
  • Test Mode is enabled and a test email has been received successfully
  • Cron job is set up on the server using the URL from the Cron Job section
  • Test Mode is disabled before going live
How do I define a reminder schedule with multiple follow-ups?

Create one individual message entry per reminder. For example, to send reminders on day 3, day 8, and day 15, create three separate messages with those day offsets. The module works through the sequence in order for each order.

Is there a global first-delay or interval setting?

No. The timing of each reminder is defined entirely by the individual message entries you create. There is no separate global delay or interval field. The sequence is whatever combination of messages you have configured.

What is the difference between the Global Settings cancel option and the per-message cancel toggle?

The per-message cancel toggle cancels the order as soon as that specific message is sent. The Global Settings cancel option cancels the order once the configured number of expiration days has passed, regardless of which message was last sent. If a per-message cancel fires before the global days limit, it takes priority.

Does the cron need to run daily or can it run more frequently?

More frequent is better if you use hour-based message offsets. Running hourly ensures hour-precision messages fire on time. If you only use day-based offsets, once per day is sufficient.

What happens during test mode?

All reminder emails are redirected to the test email address. Orders are not cancelled. The message-sent status is not updated, so the same messages are sent on every subsequent test run. This lets you verify email rendering without affecting real customers.

Need Help?​