Most PrestaShop stores should automatically notify customers about pending actions such as unpaid orders, abandoned carts and awaiting-stock confirmations. Use automation for routine, time-sensitive triggers and keep manual contact for high-value or complex cases. This guide shows how to price the silence, choose the triggers worth breaking it for, and set the whole thing up.
Picture a customer who fills a basket on a Friday evening, reaches the payment page, and gets distracted by a bank verification prompt. PrestaShop records the cart as abandoned, the order never reaches a valid status, and nobody on your team notices until Monday. By then, the customer has bought elsewhere.
Industry tracking puts the average cart abandonment rate at 70.22%, and the recovery channel with the best track record is email: recovery emails reportedly convert at 10.7% with a 41% open rate. Those are market-wide averages, not your store, but they show the size of the pool that silence leaves untouched.
Silence has a second cost that rarely appears on a dashboard: support load. A customer who pays by bank transfer and hears nothing emails you. A pre-order sitting in awaiting-stock with no update earns another email. Each is a query your team answers manually because the store said nothing first.
The most expensive notification is the one you never send, because the revenue leaves quietly and never shows up as a loss.
The next step is separating the pending actions that benefit from a nudge from the ones where a reminder does more harm than good.
What counts as a 'pending action' in an online store?
A pending action is any point where the order, the customer account or the feedback loop is waiting on someone or something to move. Split the triggers into two groups, because they call for different treatment.
Money and stock events (time-sensitive, usually safe to automate)
- Abandoned carts: a PrestaShop Cart row still tied to a visitor rather than a validated Order.
- Unpaid orders: an order stuck in the Awaiting payment state, common with cheque, bank wire or delayed card capture.
- Bank transfer not confirmed: payment made but not yet matched on your side, so the order sits in Payment accepted limbo.
- Awaiting stock: the order is paid, but the Processing status cannot move because inventory is short.
- Out-of-stock back-in-stock requests: a customer is waiting for a product to return.
Relationship events (needs judgement)
- Review requests: asking for feedback after delivery, which lands differently on a cheap accessory than an expensive item.
- Account verification: unconfirmed email addresses or customer groups awaiting approval.
- Incomplete subscriptions or reorders: a saved payment or repeat order the customer still has to confirm.
PrestaShop's Orders > Statuses screen is the natural spine here. Each status is a signal you can hang a notification on, and the Customer service messages area is where human follow-ups belong. Matching the trigger to the right channel matters more than how many messages you send.
The trap is treating a relationship trigger like a stock alert: the more personal the waiting point, the less a template should say.
Work out which of these triggers currently generate zero contact. If your store also gates content or downloads to approved customers, the account verification trigger overlaps with a private download area for authorised customers, so plan them together.
Automatic vs manual customer notifications: pros and cons
Automation wins on speed and coverage. A human wins on tone and context. The right mix depends on what the pending action is worth and how much judgement the message needs. A customer with a full cart late on a Sunday evening will not get a personal call, but an automated reminder triggered from the abandoned Carts in your back office can reach them while intent is still warm. A wholesale buyer unhappy about a stock delay needs a sentence written by a person.
| Aspect | Automated notification | Manual notification |
|---|---|---|
| Speed | Sends immediately when a status changes | Waits for someone to spot the case |
| Coverage | Runs overnight and at weekends | Limited to working hours and inbox capacity |
| Consistency | Same wording every time, on brand | Varies by who handles the case |
| Personalisation | Limited to order and customer data | Reads the history and adapts the message |
| Best for | Cart recovery, order status, payment reminders | Disputes, delays, VIP and B2B accounts |
Cost is only half the argument. The other half is consent and fatigue. PrestaShop's native emails for order states are transactional and expected. Promotional nudges need the customer to have agreed to them, under rules such as the UK GDPR and the Privacy and Electronic Communications Regulations. An automated reminder that arrives without consent is not a feature, it is a complaint waiting to happen.
Volume matters too. A store that fires a message at every small status change trains customers to ignore all of them, and the important one gets buried. Keep automated sends to genuine pending actions with a deadline attached.
How does automatic pending action notification work?
Every pending action notification follows the same five-stage path: a store event fires, a rule decides whether that event deserves a message, a template fills in the customer's details, a channel delivers it, and a log records what happened. Most automation disappoints at stage two, not stage four. This applies whether you build it with a PrestaShop module, an email platform or a custom script.
The event trigger
Something has to fire the notification. In PrestaShop, the usual triggers are changes to an order's status, a saved cart going idle for a set period, and a customer account action such as a product sitting in a wishlist. Some platforms also expose webhooks; check what your setup actually pushes out before designing rules around it.
The rules engine
This is where the store decides. A rule typically combines a trigger with conditions (cart value, customer group, products left behind, number of previous notifications) and a delay. The rule layer is where automation earns its keep or ruins it, so treat condition-setting as the main design job, not an afterthought. A sensible first rule sends one reminder, once, only to customers who reached checkout.
The template and the channel
Templates pull in live data from the order or cart: product names, images, a recovery link, the customer's first name. Email is the default almost everywhere; SMS and in-store messenger notifications usually need a separate provider and consent. Whatever you send, a recovery link should take the customer back to a working cart, not a dead page.
Delivery and logging
Finally, the system sends the message and writes an entry: sent, opened, clicked, or bounced. Those logs are the only way to learn whether a rule is helping. Review them alongside PrestaShop's own order and customer records when a rule underperforms, because the problem is often a stale template or a link that no longer resolves.
Stores handling gated files or account-only content should keep access controls in mind when a message contains a link, which is something a private download area for authorised customers module handles at the account level rather than inside the email itself.
How to set up automatic customer notifications for pending actions in PrestaShop
Setting this up is less about installing a module and more about deciding, trigger by trigger, which silences are worth breaking. PrestaShop gives you a workable baseline through its transactional email system, and a notification module extends that into scheduled, rule-based messages.
1. Choose your notification module
PrestaShop fires order confirmation and status-change emails from Shop Parameters and the order states you configure under Orders. Those cover transactional moments, not "your cart has sat for two hours". For behavioural triggers you need a module that reads cart, order and customer data and sends on a schedule.
- Built-in transactional emails for order, shipping and account states.
- A marketing automation or notification module for abandoned carts, unpaid orders and dormant quotes.
- Where you already run an external platform, its PrestaShop connector can handle the sending and reporting.
2. Define triggers and timings
Map each pending action to a trigger and a delay, and write the delay down. A short delay reads as attentive; a long one reads as pressure. As a starting frame:
| Pending action | Reasonable first trigger | Second touch |
|---|---|---|
| Cart left at checkout | A few hours after last activity | A day later, only if still open |
| Order awaiting bank transfer | Same day, reminder on due date | One nudge after the deadline |
| Custom quote awaiting approval | A few working days | Hand off to a human |
Cap total touches per customer per week. Two messages about the same cart is a reminder; five is a campaign.
3. Write the messages
Keep each message to one action and one line of context. Say what is pending, what happens next, and what the customer loses if they wait (a reserved stock item, a quote expiry). Avoid countdown theatre unless the deadline is real.
4. Set consent and unsubscribe properly
Recovery messages sit close to marketing, so honour the customer's marketing consent settings and include a working unsubscribe route on anything promotional. Purely transactional notices (an unpaid order, a failed payment) can usually go out regardless, but keep the two categories separate in your templates so a customer can tell which is which.
5. Test with a sandbox order
Place a test order, abandon a test cart, and leave an order in an unpaid state. Confirm each trigger fires at the expected time, that the templates render correctly, and that the customer receives exactly the number of messages you intended. Test the unsubscribe link too.
6. Monitor delivery and results
Track open and click behaviour per trigger, not per campaign. A trigger that never converts is a candidate for a human touch instead. Automation is a filter, not a replacement: put a real person on the highest-value pending actions, and let the module handle the rest.
Best practices for notifying customers about pending actions
Automation decides what gets sent; these rules decide how it feels to the customer. Get them right, and a reminder reads as helpful. Get them wrong, and the same email reads as nagging.
Timing: wait long enough to be useful
Send the first nudge while the action is still fresh, but not so fast that it feels like surveillance. Wait long enough for a genuine interruption (a lost connection, a phone call) to resolve itself, then send once. If the customer returns and completes the action on their own, the queued reminder should cancel automatically.
Message tone: lead with the customer's benefit
A reminder about an abandoned cart, an unpaid bank transfer, or a missing product review should open with what the customer gets, not what the store needs. "Your basket is still saved" beats "You forgot to check out". Name the specific item or task, keep it to two or three sentences, and include one clear action link.
How many reminders, and through which channels
More than two reminders on the same pending action is where fatigue starts. Mix channels deliberately rather than blasting every one at once.
- Email remains the default for anything with detail: order confirmation, payment link, delivery follow-up.
- SMS suits time-sensitive pending actions such as a delivery slot or a card payment that will expire.
- On-site notices (a banner or account-area message in PrestaShop) work best for logged-in customers who are already browsing.
The best reminder is the one the customer would have sent themselves, at the moment they would have sent it.
When to escalate to a human
Route high-value or high-friction pending actions to manual follow-up. An order stuck in "Awaiting bank wire payment" above a certain threshold, or a customer who has opened three reminders without acting, is a signal to pick up the phone. Automation handles volume; people handle the edge cases that protect revenue.
Consent and UK/EU data rules
Under UK GDPR and the EU's ePrivacy rules, transactional messages about an order the customer placed are generally permitted, but marketing-flavoured reminders need a lawful basis, usually consent. Keep an unsubscribe route on anything promotional, honour it across every channel, and store the consent record. Review your notice wording with whoever handles your data protection compliance.
When manual outreach still beats automation
Automation earns its keep on volume. It stops earning it the moment a pending action carries real money, a relationship, or a risk of embarrassment. Four situations call for a human message every time:
- High-value orders. A sizeable basket deserves a named sender and a real reply address, not a template. One recovered order can pay for the extra minutes.
- B2B and trade accounts. Buyers ordering on behalf of a company want a contact they can chase, especially when a purchase order is pending approval. A colleague-to-colleague note keeps the account warm.
- Payment failures with context. When a card is declined, the customer often does not know why. A short, careful email from a human, offering to hold the stock or take payment another way, defuses the frustration a dry system message can trigger.
- Sensitive delays and complaint-adjacent cases. If an order is late, damaged or was already the subject of a complaint, an automated nudge reads as tone-deaf. Write that one yourself.
A customer who has just had a bad experience will judge your whole brand on the next message they receive. If you store documents or files for those trade accounts, a private download area for authorised customers keeps sensitive material out of public view while your team handles the personal follow-up.
Final Verdict
Automate the routine and time-based, personalise the high-value and the exception. Let PrestaShop send the generic nudges (an unpaid order reminder, a back-in-stock alert, a review request) on a schedule, while a human handles the messages where a small personal touch recovers real money: a delayed order, a large cart sitting untouched, a wholesale buyer whose payment failed.
To put the rule to work this week, work through this short checklist:
- Sit with your Orders and Carts lists and write down every trigger you actually want to notify on, then delete the ones that would annoy rather than help.
- Match each trigger to a channel: email for anything a customer needs to read and act on, and keep your store's on-site or account messaging for quieter status updates.
- Set a clear threshold above which a cart or order gets a human review before any message is sent.
- Review the first fortnight of sends, watch which get acted on and which get ignored, then prune without sentiment.
The module lets customers upload product photos on the product page, gives you an attractive photo slider and configurable upload settings such as maximum image size and format, and even lets you motivate customers with discounts for uploading. For stores where a plain automated nudge is not enough, that user-generated content answers questions before they become a stalled cart, and it creates a genuine reason for a personal, human follow-up.
Start With the Cost of Silence
The honest way to decide is to price the silence first. Every pending action that nobody chases has a recovery value you are quietly writing off. Cart abandonment sits at an average of 70.22% across e-commerce, so a large share of your PrestaShop carts will stall no matter how good your checkout is. The question is not whether pending actions happen, but whether your store speaks up when they do.
What Counts as a Pending Action in PrestaShop
In PrestaShop terms, a pending action is any customer journey that has started but not finished. It leaves a record you can see in the back office, but the customer has gone quiet.
- An abandoned cart is when items sit in the cart, but no order is validated.
- An order stuck in an "Awaiting bank wire payment" or "Awaiting cheque payment" status because the customer never completed the transfer.
- An order awaiting confirmation from the customer before it moves to "Payment accepted".
- A customer message in the order thread or the contact form that has not been answered.
- A custom quote or product enquiry that needs a reply before the customer commits.
Quantifying the Missed Recovery
Start with order statuses you can already see in the PrestaShop Orders list, filtered by status and date range. Count how many sit in an awaiting-payment or awaiting-confirmation status at the end of a typical week. Multiply that count by your average order value, then apply a realistic recovery rate. That number, not a gut feeling, is what automation is competing against.
The damage is not only lost revenue. A customer who pays by bank transfer and hears nothing for days assumes the order failed. Some will reorder elsewhere. Some will contact you frustrated. Both outcomes cost you time and trust that a single automated email would have protected.
Automatic pending action notifications are not a marketing extra; they are a recovery system for revenue you have already earned the right to collect.
The Cost of Getting It Wrong: Notification Fatigue
A customer who receives three reminders about a cart they were only browsing will read the fourth as pressure. Your store moves from helpful to needy in one inbox. The fix is rules, not volume: send one reminder, wait, then send a second only if there is a genuine reason (the cart still holds the item, or a payment window is closing).
- Cap reminders per pending action so no customer gets more than a short, defined sequence.
- Suppress notifications for actions the customer has already completed.
- Keep the message specific: name the product, the amount, or the payment step still open.
Email recovery still performs when it is measured. Abandoned cart emails reach a 44.76% open rate and a 10.7% conversion rate, which is why a single well-timed message beats a barrage.
A Concrete Rule for When to Automate
Automate when the action is high-volume, time-sensitive, and the next step is unambiguous. Keep it human when the action is low-volume, high-value, or needs judgement.
| Scenario | Volume and value | Best approach |
|---|---|---|
| Abandoned cart reminder | High volume, low to medium value | Automate with a capped sequence |
| Awaiting bank wire payment | High volume, clear next step | Automate with payment instructions |
| Large custom quote | Low volume, high value | Human follow-up call or email |
| Complaint or order dispute | Low volume, high sensitivity | Human reply only |
The dividing line is whether a scripted message can answer the customer's next question. If yes, automate. If the customer needs a person to reassure them, automate nothing and call.
Where a Human Touch Still Wins
Automation is poor at the moments that decide whether a customer trusts you again. A delayed high-value order, a payment that failed for a confusing reason, or a question about a bespoke product all need a person. Customers often stall because they cannot tell what they are buying, and letting buyers upload real photos on the product page answers that question before it becomes a stalled cart. Prestashop Product Images by Customers lets customers upload product photos, adds an attractive photo slider, and gives you configurable upload settings such as maximum image size and format, with the option to motivate customers with discounts for uploading.