Cart recovery should begin with a reason a shopper might hesitate: unclear sizing, delivery costs, an unavailable option or a payment failure. Sending more messages is not a substitute for fixing checkout. Test the storefront cart and payment gateway first, then use recovery to answer an unresolved question.
A practical test sequence
On a test store, add one product and record its variant, price, cart total and consent state. Leave checkout without completing payment. Verify that the recovery record describes that cart rather than another shopper or an earlier session. Open a permitted recovery link and check that it restores the intended item without creating an order automatically.
- Start with a helpful on-site answer, such as a link to the store delivery policy.
- Use email, SMS or messaging only where the channel is connected and the shopper has the required permission or consent. Provider templates and session rules may limit delivery.
- Stop or suppress reminders after a completed purchase, an opt-out or an expired recovery window. Verify those cases on the test store.
Keep discount limits honest
Zubby checks known product costs before presenting guarded offers. If costs are missing, a percentage cap can limit discount size but cannot establish profitability. Enter costs or block offers for those products. Include shipping, fees and refunds when reviewing the economics; a product-cost floor is not a complete profit calculation.
Separate attributed recovery from additional orders
A click followed by a purchase is evidence of a sequence, not proof that the reminder caused the purchase. Document the attribution window and remove duplicate orders. Compare a controlled group where feasible and report uncertainty. Do not call a recovery-rate scenario a forecast or imply that every merchant will get the same result.
Keep these checks in the weekly review
Review sends, failures, opt-outs, restored carts and completed orders together. Investigate broken or expired links before increasing volume. If the payment gateway rejects a test, confirm that the recovery flow does not turn the failure into a successful order.