Written by DROPS.ST.
An abandoned cart needs help returning to shopping. An unpaid order needs help completing or resolving payment for an order that already exists. Check which situation you have before sending a reminder. DROPS brings cart recovery, order records and payment status into the same operating context, so your team can choose a useful next action instead of treating every unfinished purchase alike.
Start with the order, not the reminder text
A basket can exist without a submitted order. A submitted order can remain unpaid. A payment can also be under review while the customer believes they have finished. These situations may look similar in a quick activity report, but they need different customer instructions.
Do not tell a customer to create another order simply because the first one is not marked paid. First inspect the current record and the intended payment path. A duplicate order can create a second set of instructions, another stock question and more support work.
The cart recovery guide covers how to evaluate a recovery candidate. Use that work after deciding whether shopping, payment or support is the next job.
Classify a few ordinary situations
The following fictional events show how the message changes with the evidence.
| Observed event | Working classification | Useful next action |
|---|---|---|
| Customer selects products but never submits | Unfinished cart, if the available records support that conclusion | Return to the current basket or menu |
| Order exists and payment instructions were displayed | Unpaid order | Open that order’s payment instructions |
| Customer says payment was sent but status is unresolved | Payment-support case | Review the existing order before asking for more money |
| Order is paid and awaiting preparation | Fulfilment update | Explain the shop’s next service step |
| Customer cancelled or asked to stop reminders | Closed or excluded from this follow-up | Respect that decision |
An uncertain record belongs in review, not in a confidently worded campaign. This does not require an elaborate scoring system. It requires checking the most relevant state before the next message.
Write around the action you actually want
For a fictional unfinished basket, the message might say: “Your selected products may still be available. Return to the shop to review the current selection and total.” Avoid promising that stock or an old offer has been reserved unless that is true.
For an unpaid order, the message should point to the existing order: “Order 482 is awaiting payment. Open its current payment instructions, or contact us if you have already paid.” Use a fictional reference in public examples and an appropriately protected route in real communications.
For an unresolved payment report, a promotional discount is the wrong response. The customer needs clarity about what has already happened.
Keep follow-up relevant and permitted
Cart activity does not grant blanket permission to contact someone through every channel. Use the customer’s actual choices and the rules that apply to the intended message. Do not infer consent from an account label or a previous purchase alone.
DROPS follow-up tools are useful because they lead back to the shop where products and orders can be understood. The team still needs to review the audience and message. Do not assume a campaign automatically distinguishes every payment exception without checking its configured selection rules.
Measure each path separately
In an illustrative review, 20 unfinished baskets and 10 unpaid orders are not one group of 30 identical recovery opportunities. Count resumed shopping separately from payments completed on existing orders. Remove cancelled, already-paid or otherwise resolved cases before the next contact.
Read payment method labels to prevent uncertainty at the source, then inspect the corresponding states in a demo.
See DROPS cart recovery, payment status and order tools and make the next customer message move the right purchase forward.