Build and simulate conditional recovery flows

Build a flow

1. In Pro Conditional flows, use the guided setup to start at full price, target higher-value carts with a threshold you enter in the store currency, or choose confirmed new or returning shoppers. Preparing a setup creates a paused draft, with no discount or experiment enabled. Unknown customer history is excluded from both confirmed customer groups.
2. Review the draft messages and conditions, then run the simulator with matching and nonmatching examples. Save and deliberately enable only after reviewing sender readiness. Preparing a draft does not save it, start recovery or send email.
3. Alternatively, open Flows → Create a flow. Give it a recognizable name and a priority; lower numbers run first.
4. Add conditions. Every condition within a group must match; matching any group is enough. An empty set matches all eligible checkouts.
5. Edit one to five emails. Delays are whole hours from the latest checkout activity, strictly increasing between 1 and 168 hours.
6. Run the sample-checkout simulator. Try matching and nonmatching products, multiple items, unknown costs, missing consent and a completed purchase.
7. Save, review sender readiness, then enable the flow deliberately. Creating or duplicating a flow does not activate recovery.

One checkout, one chosen flow

The first matching enabled flow is snapshotted when an eligible new checkout enters recovery. Equal priorities use creation order, then ID. A flow edit creates a new version for future enrollment; existing checkouts retain their enrolled copy and timings. If no flow matches, the default sequence applies.

Purchase, suppression, consent, plan limits, stock, store pause and flow conditions are checked before dispatch. Pausing a flow stops its queued reminders; skipped messages do not automatically replay when it resumes. A checkout does not jump between campaigns after enrollment.

Value conditions use the store base currency. Foreign-currency carts do not match value conditions; identifier and language conditions can still match. No implicit exchange-rate conversion occurs. Unknown customer history does not count as confirmed new or returning.

What the simulator proves

The simulator explains entry conditions, planned timings, permission ceilings and estimated offers for the data you enter. It sends no emails and does not connect to the shopper’s live cart. WordPress performs final stock, price, cost and coupon checks at send and redemption time. Test a real opted-in checkout before launch.