Separate unexpected costs, stock loss and payment errors
Separate the unexpected-cost path from stock loss and payment failure before proposing a cart change. Each needs different evidence and a different repair. Match the stopped journey to its displayed state and operational record, then keep unexplained exits unknown rather than assigning a convenient reason to every departure.
Worked example — illustrative data.
| Observed state in specimen | Evidence to request | Candidate response |
|---|---|---|
| Cart reaches delivery then stops | Shown shipping amount and task observation | Show verified constraints earlier |
| Item becomes unavailable | Inventory event and selected SKU | Resolve stock synchronization |
| Payment attempt fails | Sanitized gateway error and sandbox replay | Repair the specific payment path |
Define the denominator and sequence before comparing periods: cart creation, checkout start and completed order are different events. Check whether duplicate events or consent changes alter the apparent drop. Select one problematic journey and reproduce it with a synthetic order in staging. Ask what the shopper could see at the moment of failure. Record an unknown reason as unknown rather than assigning every exit to the most convenient explanation.
Saved carts and cross-device visits complicate abandonment
A cart may be used as a saved list or reopened on another device. An unfinished session is not automatically a rejected purchase. Avoid labeling the whole difference between cart and order counts as recoverable revenue.
For the fictional paths, investigate stock and payment faults before changing persuasion. Use cost explanations only when the actual displayed cost and customer task support that diagnosis.
Continue with Guides for stores, software teams and local businesses, Conversion rate optimization services and Diagnose discount code friction.
For ecommerce event definitions, see Google Analytics ecommerce event documentation (checked November 2026).