WakeMyCart
Do not treat an order awaiting payment as an abandoned cart. Hold the reminder while payment is uncertain. Check the order against the payment provider’s record—or the receiving bank’s record for a transfer—before asking the shopper to return.
For a WooCommerce store accepting delayed-confirmation methods, an unfinished purchase may need payment instructions or confirmation, not a recovery message. Permission to receive reminders remains a separate prerequisite; payment evidence does not supply it.
Start with evidence, not the status label
Choose one unresolved order. Gather its reference, creation time, displayed status, available order notes and any transaction reference. Compare these with the relevant payment records to establish whether payment is unresolved, definitively unsuccessful or confirmed.
Match records using order or transaction references where available. Similar amounts or timestamps can help investigation but should not be the sole basis for a match.
A missing payment reference or unmatched attempt does not establish that payment was never initiated. If you cannot resolve the uncertainty, record it and hold the reminder.
Apply four payment-state rules
These are operating rules to document and enforce, not assumptions about what your reminder software does automatically. Eligible for reminder checks means you can assess permission and your remaining reminder rules—not send immediately.
No matching order found
Evidence: No matching order appears in the records checked.
Decision: Eligible for reminder checks only if there is no known purchase or unresolved payment. Otherwise, hold.
Next action: Investigate any evidence that a payment attempt began, even without a matching order. If the uncertainty is resolved and the case becomes eligible, check current reminder permission and your remaining reminder rules.
Order exists, but no payment initiation is recorded
Evidence: An order exists, but the available records do not show a payment starting. This does not prove that no payment was initiated.
Decision: Hold while payment remains uncertain or the order is still within its documented payment process.
Next action: Check the payment instructions and expected confirmation path. Missing or unclear instructions belong with ordinary order support, not promotional recovery.
Before reconsidering, establish that no payment is progressing. Inspect the proposed reminder and its destination in a controlled test: would it continue the existing order or restart the same purchase? If it would restart the purchase—or you cannot tell—keep the hold and route the case to order support.
Payment started, but confirmation is unresolved
Evidence: A payment is pending, its outcome is unclear, or order and payment records disagree.
Decision: Hold until reliable evidence establishes the outcome.
Next action: Assign a reviewer to resolve the payment state or mismatch. A definitively failed attempt permits reconsideration, not automatic eligibility. First check for another attempt or purchase, then inspect the proposed message’s next step against the existing order. One failure does not prove that every attempt failed. If uncertainty remains, keep the hold.
Purchase confirmed
Evidence: Reliably matched payment evidence confirms the purchase, even if the store still displays an unpaid status.
Decision: Exclude the corresponding abandoned-cart reminders.
Next action: Resolve any order-record mismatch separately. Do not ask the shopper to retry because the store display has not caught up. This exclusion concerns that purchase, not unrelated future carts.
Write one review rule for each payment method
Do not apply a universal waiting period to every unpaid order. Use provider guidance and your reconciliation process to justify when someone should investigate.
A review deadline is a prompt to check, not permission to send. An unresolved payment remains unresolved when a timer expires.
Complete this outline for each delayed-confirmation method:
- Payment method: name the method covered by this rule.
- Expected confirmation path: describe the steps from order creation to a known payment outcome.
- Evidence source: identify where the reviewer verifies the outcome and matches records.
- Review point: state when to investigate and why that timing is appropriate.
- Owner: name the person responsible for review and follow-up.
- Release or exclusion conditions: specify the evidence required for each decision, including the existing-order check.
- Sending control: identify the existing mechanism that keeps held or excluded cases out of recovery.
For each individual case, record the order or cart reference, evidence and time checked, decision, reason, and next review point. Use the labels hold, exclude, or eligible for reminder checks.
See how the evidence changes the decision
The following hypothetical example shows how three payment outcomes change the decision for the same existing order. It does not test your store or its settings.
TRY THE SCENARIOS
What changes when the payment evidence changes?
Hypothetical example: an existing order uses a delayed-confirmation method with provider records. Records are reliably matched; no automatic filtering is assumed.
The provider record remains unresolved
Hold. Assign the next review and keep the corresponding reminder out of recovery. Reaching the review deadline does not establish abandonment.
The provider confirms payment, but the store still displays unpaid
Exclude reminders for this purchase. Correct the order-record mismatch separately rather than asking the shopper to restart checkout.
The attempt definitively failed, with no other purchase or progressing payment found
Eligible for reminder checks only after reviewing the existing order and proposed next step. Retain the hold if that step is unclear or would restart the same purchase. Current permission and other reminder rules still apply.
Compare all scenarios
| Situation | What happens |
|---|---|
| The provider record remains unresolved | Hold. Assign the next review and keep the corresponding reminder out of recovery. Reaching the review deadline does not establish abandonment. |
| The provider confirms payment, but the store still displays unpaid | Exclude reminders for this purchase. Correct the order-record mismatch separately rather than asking the shopper to restart checkout. |
| The attempt definitively failed, with no other purchase or progressing payment found | Eligible for reminder checks only after reviewing the existing order and proposed next step. Retain the hold if that step is unclear or would restart the same purchase. Current permission and other reminder rules still apply. |
Illustrative examples. Your selection is not saved or sent, and changes no store settings.
Verify that the decision controls sending
Confirm how your current workflow keeps held and excluded cases out of recovery. A note on a review sheet does not, by itself, stop an automated email. Do not assume a generic purchase check covers unresolved payments.
Keep affected cases out of automated recovery. If your workflow cannot isolate them reliably, pause the broader sending workflow until a dependable control is in place.
Do not automatically cancel orders merely to fit a reminder rule. Cancellation is a separate operational decision and does not establish what happened to payment. Before releasing a hold, recheck the latest purchase and payment records and reminder permission.
Start with one unresolved case: complete its payment-method rule, record the evidence and decision, and verify that the sending workflow respects any hold or exclusion. If you cannot demonstrate that control, keep the affected recovery workflow paused.