Checkout Atlas
Patterns we keep finding in commerce apps
A living reference of purchase-path shapes—used to frame readouts and recovery work, not as a generic playbook.
Four atlas entries
Each pattern names the signal, the usual false story, and the engagement that clarifies it.
Address wall before payment
Drop-off clusters on shipping or address capture while payment looks healthy. Teams often blame the gateway. We separate form friction from decline rates before anyone rewrites checkout.
Promo-inflated paid rate
Paid conversion spikes during campaign weeks, then “fails” on ordinary days. The atlas marks calendar windows so product does not ship permanent UX changes for temporary traffic.
Recoverable vs decorative abandons
High-intent carts with payment or stock blockers sit beside browse-heavy abandons. Recovery messaging only earns attention when segments match intent.
Search success without PDP
Search reports “success” while empty or thin results never reach product detail. Catalog path reviews expose the empty-result tax merchandising can actually fix.
Use the atlas to choose an engagement
Most teams start with a Checkout Funnel Readout when step ownership is unclear, then add Cart Recovery Diagnostics or a Catalog Path Review when the pattern points there. The Commerce Pulse retainer keeps atlas language shared after releases.
