Shoppers leave checkout for different reasons: some were just browsing or not ready to buy, some encounter a cost or delivery term they dislike, and some cannot complete payment. Start with the gap between checkout and purchase, inspect failed attempts, then reproduce the affected route. Send a recovery reminder only when the checkout works and that shopper is eligible to receive one.
A checkout-start count tells you where a visit stopped. It does not tell you why the person stopped or whether you can reach them by email. If the payment route is broken, changing the reminder will leave the original obstacle in place.
Read the funnel before counting recoverable shoppers
In Shopify’s Conversion rate breakdown, the steps are sessions, sessions with cart additions, sessions that reached checkout and sessions that completed checkout. Those are session counts. The guide notes that one session can contain multiple orders, so the completed-checkout session count need not equal your order count.
Check whether the report uses an open or closed funnel before comparing the steps. The open funnel can include a visit that goes directly to checkout without a recorded cart addition. Its closed funnel counts only visits that follow the defined sequence. Keep the funnel type, date range and segment together when making a comparison.
For an invented example, suppose a selected report shows 40 sessions reaching checkout and 4 sessions completing it. The gap is 40 − 4 = 36 sessions, and the completion-stage ratio is 4 ÷ 40 = 10%. This is not 36 identified people, 36 failed payments or 36 addresses for a recovery email. It is a place to start investigating.
The distinction matters when you open a recovery list. In the platform’s documented legacy abandoned-checkout experience, an incomplete checkout becomes an abandoned-checkout record after the customer has provided an email address and more than ten minutes have passed. That is a narrower condition than simply reaching the checkout stage in a session report. Check the current recovery setup for your store rather than treating the two counts as interchangeable. Our abandoned-cart email guide explains why platforms and flows use different starting events.
Match the symptom to the next check
Baymard’s shopper-reason research, summarised on its 2026 cart-abandonment statistics page, includes people who were browsing and people who report extra costs, slow delivery, trust concerns, a complicated checkout, errors or payment limits. The page does not date the underlying study. Those are possible causes reported by surveyed US online shoppers. They do not diagnose your store or any one visitor.
Use the checkout and order records to narrow the possibilities:
| What you observe | Check next | What it would change |
|---|---|---|
| Checkout started, with no recorded payment attempt | Revisit the total shown, delivery estimate, available payment methods and the affected device or country | A visible purchase barrier needs investigation before a reminder or discount is chosen |
| Failed payment event | Open that abandoned checkout’s payment Timeline and read the event message | A decline, verification failure, processing error and fraud block call for different repairs |
| Reports of a changed price or currency | Compare the customer’s country with the market and currency settings | A market setting may be the problem, rather than the email copy |
| One redirect-based payment method fails | Check that provider’s transaction status and complete its return-to-store path | The failure may sit in the offsite payment route |
| Every customer and payment method fails | Check the Shopify Status page, payment settings including test mode, and provider account status | Treat a store-level fault as an incident, not a persuasion problem |
The first row is a prompt to investigate, not a verdict about intent. A shopper who stops before pressing Pay could be unready, could dislike a delivery term, or could have encountered a problem you have not yet reproduced. Keep the reason unassigned until a record, a reported symptom or a test supports it.
Inspect a failed payment before editing recovery copy
For a Shopify store, go to Orders → Abandoned checkouts, open an affected checkout, then expand its payment event in Timeline and read the Message field. The payment guide says a failed attempt usually creates no order, which is why the checkout Timeline is the place to look. A very recent attempt may take more than ten minutes to appear as abandoned.
Write down what actually happened. A card issuer decline is different from a failed 3D Secure verification, a technical processing error or a high-risk block. For a redirect-based method such as PayPal, the payment guide notes that leaving the provider page before returning to the store can cause payment failure; if a customer says they were charged without an order, check the provider’s transaction status. If the price or currency is unexpected, the guide directs merchants to verify the assigned currency and shipping country in Markets.
If several customers report the same general processing error, check whether it affects all methods or one provider. The payment guide directs a store-wide investigation to payment settings and status pages. Do not infer a store outage from one checkout, or an individual card problem from repeated failures across methods.
Reproduce the route that appears to fail
Record the affected country, device and payment method, then walk through the same available checkout route. Note the product price, final total, delivery estimate, payment options and any error or redirect. Compare the displayed experience with what the store intended to offer.
If you can use a simulated order, the platform’s test-order guidance says it can verify checkout, shipping, tax, inventory and notification settings. It also warns that customers cannot place live orders while payment providers are in test mode. Plan a safe test window and return the store to its intended live payment configuration. A simulated order verifies the configured route you exercised; it does not prove every shopper’s payment will succeed or tell you why an earlier visitor left.
Keep one short investigation record:
Date range and funnel type · affected country/device · last recorded stage · payment event and message, if any · displayed total and delivery terms · payment method tested · result · unresolved question.
This makes a later change reviewable. If the same route succeeds and there is no recorded error, keep “shopper changed their mind” and “unseen checkout friction” as possibilities rather than turning either into a fact.
Choose recovery only after the route is usable
Once the checkout can complete, a reminder may help a reachable shopper resume. Eligibility still depends on the address, consent rules and the configured flow. Our consent guide covers the sending decision; our flow-handoff guide covers how to avoid duplicate cart and checkout messages.
The legacy recovery guide lists cases in which its automated email is withheld, including a payment-processing error, a shipping address the store does not support, a customer who entered a phone number instead of an email, a checkout in which none of the products are still available, or a purchase before the message sends. Do not assume that making the subject line stronger will reach those records. Check the rules of the automation your store actually uses.
Treat a recovered-status label carefully, too. In that same documented workflow, a checkout can be marked recovered after the customer places the order on their own following an email send, without clicking its link. The label records the order’s later completion; by itself, it does not prove the email caused it. Fix an observed checkout obstacle first, then evaluate reminders separately from the funnel fault.
Why do shoppers add to cart but leave before paying?
Cart addition shows an action in a session, not a commitment to buy. Baymard’s shopper-reason research includes browsing without purchase readiness alongside costs, delivery, trust and checkout friction. Use your own funnel, payment events and route test to determine what can be checked at your store.
Does reaching checkout mean I can send a recovery email?
No. A checkout-stage session is not automatically an email-identified shopper. In Shopify’s documented legacy experience, an abandoned-checkout record requires an email address and an incomplete checkout for more than ten minutes. Sending permission and automation eligibility are separate checks.
Where can I see why a Shopify payment failed?
Open Orders → Abandoned checkouts → the affected checkout → Timeline, then expand the payment event and read its Message. A failed payment usually leaves no order. The message may identify a decline, verification failure or processing problem; the payment guide notes that many banks return only a generic decline reason.
Should I offer a discount to every abandoned checkout?
First identify what the shopper encountered. A discount does not repair a failed payment route, an unsupported shipping address or a checkout error. If the route works and the shopper is eligible for a reminder, test the offer as a separate decision; neither an abandonment record nor a later recovered-status label proves the discount was necessary.