Conversion Rate Optimization skill 06 of 13

Checkout and Cart Optimisation SKILL.md

The Checkout Optimisation skill makes Claude, Codex or another AI agent reduce cart and checkout abandonment. It shows total costs early, offers guest checkout, cuts fields with address lookup and autofill, adds wallets and local payment methods, shows delivery dates, places trust cues and returns near payment, fixes validation and speed, handles subscription and international details and sets up consented cart recovery.

checkout-optimisation/SKILL.md, version 1.0.0, 1,514 words.

Checkout is where buyers have already decided and the business can still lose them. Baymard Institute has long reported average documented cart abandonment around 70%, and its research attributes much of it to fixable issues: extra costs revealed late, forced account creation, long or confusing forms, missing payment methods, slow delivery and lack of trust. [Study, Baymard Institute; check current figures] Every percentage point recovered at checkout flows straight to revenue.

This skill audits and improves cart and checkout flows for e-commerce, subscriptions and digital purchases: cost transparency, guest checkout, form fields, payment and delivery options, trust, errors, mobile and recovery, with research and tests.

Operating principles

  1. No surprises. Show total cost, including delivery, taxes and fees, as early as possible.
  2. Remove barriers. Guest checkout, fewer fields, address lookup and saved details.
  3. Offer the payment methods people use. Cards, wallets and local methods for each market.
  4. Build trust at the moment of payment. Security cues, returns policy, contact options.
  5. Recover, don't just prevent. Saved carts, reminders and easy return paths.

Common abandonment causes and fixes

CauseFix
Extra costs revealed lateDelivery estimator on product and cart pages; total shown early
Forced account creationGuest checkout; offer account creation after purchase
Long or complex formsFewer fields, address lookup, autofill, billing same as delivery by default
Missing payment methodsWallets (Apple Pay, Google Pay, PayPal) and local methods by market
Slow or unclear deliveryDelivery dates, not just methods; options with prices
Trust concernsSecurity indicators, recognisable payment logos, clear returns and contact
Errors and validation problemsInline validation; keep entered data; clear messages
Unexpected coupon fieldMake the coupon field less prominent to avoid sending people off to search for codes
Slow pagesLighter scripts, fast payment pages, field data checks

When to use, and when not to

Use it when cart or checkout abandonment is high, when mobile checkout lags desktop, when entering new markets, after platform changes and when adding payment providers.

Don't use it for product page or landing page problems before the cart (landing-page-optimisation) or for subscription plan choice (pricing-page-optimisation).

Inputs to ask for, in one message

  1. Checkout URL flow and platform (Shopify, WooCommerce, Magento, custom).
  2. Funnel data: product view, add to cart, cart, each checkout step, purchase, by device and market.
  3. Payment methods offered and payment failure rates.
  4. Delivery options, costs and timings by market.
  5. Recordings, exit surveys and support tickets about checkout.
  6. Returns policy and trust elements shown.

Raw SKILL.md file

.md

This is the exact file agents read, including the credit header and licence notice. Save it as checkout-optimisation/SKILL.md.

---
name: checkout-optimisation
description: "Reduce cart and checkout abandonment: total costs shown early, guest checkout, fewer fields with address lookup and autofill, wallets and local payment methods, delivery dates, trust cues and returns near payment, inline validation, mobile speed, subscription and international details, fixes before tests and consented cart recovery. Use whenever someone asks about cart abandonment, checkout conversion, checkout UX, guest checkout, payment methods, delivery costs at checkout, mobile checkout problems or improving e-commerce checkout."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/conversion-rate-optimization/checkout-optimisation/
  category: marketing
  subcategory: conversion-rate-optimization
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Checkout and Cart Optimisation

Checkout is where buyers have already decided and the business can still lose them. Baymard Institute has long reported average documented cart abandonment around 70%, and its research attributes much of it to fixable issues: extra costs revealed late, forced account creation, long or confusing forms, missing payment methods, slow delivery and lack of trust. [Study, Baymard Institute; check current figures] Every percentage point recovered at checkout flows straight to revenue.

This skill audits and improves cart and checkout flows for e-commerce, subscriptions and digital purchases: cost transparency, guest checkout, form fields, payment and delivery options, trust, errors, mobile and recovery, with research and tests.

## Operating principles
1. **No surprises.** Show total cost, including delivery, taxes and fees, as early as possible.
2. **Remove barriers.** Guest checkout, fewer fields, address lookup and saved details.
3. **Offer the payment methods people use.** Cards, wallets and local methods for each market.
4. **Build trust at the moment of payment.** Security cues, returns policy, contact options.
5. **Recover, don't just prevent.** Saved carts, reminders and easy return paths.

## Common abandonment causes and fixes
| Cause | Fix |
|---|---|
| Extra costs revealed late | Delivery estimator on product and cart pages; total shown early |
| Forced account creation | Guest checkout; offer account creation after purchase |
| Long or complex forms | Fewer fields, address lookup, autofill, billing same as delivery by default |
| Missing payment methods | Wallets (Apple Pay, Google Pay, PayPal) and local methods by market |
| Slow or unclear delivery | Delivery dates, not just methods; options with prices |
| Trust concerns | Security indicators, recognisable payment logos, clear returns and contact |
| Errors and validation problems | Inline validation; keep entered data; clear messages |
| Unexpected coupon field | Make the coupon field less prominent to avoid sending people off to search for codes |
| Slow pages | Lighter scripts, fast payment pages, field data checks |

## When to use, and when not to
Use it when cart or checkout abandonment is high, when mobile checkout lags desktop, when entering new markets, after platform changes and when adding payment providers.

Don't use it for product page or landing page problems before the cart (`landing-page-optimisation`) or for subscription plan choice (`pricing-page-optimisation`).

## Inputs to ask for, in one message
1. Checkout URL flow and platform (Shopify, WooCommerce, Magento, custom).
2. Funnel data: product view, add to cart, cart, each checkout step, purchase, by device and market.
3. Payment methods offered and payment failure rates.
4. Delivery options, costs and timings by market.
5. Recordings, exit surveys and support tickets about checkout.
6. Returns policy and trust elements shown.

## Workflow

### Step 1. Map the funnel
Step conversion from cart to purchase by device, market and new versus returning customers.

### Step 2. Walk through as a customer
Complete purchases on mobile and desktop, as a guest and a returning user, in key markets.

### Step 3. Check costs and delivery
When does the total appear? Are delivery dates clear?

### Step 4. Review forms and errors
Field count, address lookup, autofill, validation and error recovery.

### Step 5. Review payments
Methods offered versus market expectations; payment failures by method; 3-D Secure friction.

### Step 6. Review trust
Security cues, returns, guarantees, contact options and reviews near the payment step.

### Step 7. Gather evidence
Exit survey at checkout, recordings at leaking steps, support tickets.

### Step 8. Fix, test and recover
Fix bugs and errors immediately; test bigger changes; set up cart recovery emails or messages with consent.

## Checkout checklist
- Guest checkout available and obvious.
- Total cost visible before the payment step.
- Delivery dates shown, not just methods.
- Address lookup or autocomplete.
- Billing address defaults to delivery address.
- Wallets and local payment methods for each market.
- Inline validation that keeps entered data.
- Progress indicator for multi-step checkout.
- Security cues and returns policy near payment.
- Fast, mobile-friendly pages with large tap targets.

## Checkout exit survey
Ask one question when visitors leave checkout: "What made you leave checkout today?" with options such as delivery cost, delivery time, needed to create an account, payment method not available, checkout too long, website errors, just browsing, and other (please tell us). Review answers weekly by device and market.

## Payment method coverage by market (examples)
| Market | Methods customers often expect |
|---|---|
| UK | Cards, Apple Pay, Google Pay, PayPal, buy now pay later |
| Netherlands | iDEAL, cards, PayPal |
| Germany | PayPal, cards, invoice or bank transfer options |
| Brazil | Pix, cards, boleto |
| Nigeria | Cards, bank transfer, USSD and local gateways |
Check current payment preferences with your provider before launching in a market.

## Checkout metrics
| Metric | Why |
|---|---|
| Cart to purchase rate | Overall checkout health |
| Step completion by device | Finds mobile problems |
| Payment failure rate by method | Gateway and 3-D Secure issues |
| Error rate by field | Validation problems |
| Revenue per visitor | Business outcome |
| Recovered carts | Reminder effectiveness |

## Cart recovery basics
With consent, send a reminder within a few hours of abandonment, a second the next day and optionally a third with help or a small incentive only for customers whose economics allow it. Link straight back to the saved cart and mention delivery and returns. Measure recovery against a holdout so reminders are credited only with sales they actually add.

## Speed checks
Payment pages often load extra scripts (fraud tools, tag managers, chat). Check Core Web Vitals field data for checkout templates and remove scripts that are not essential at this step.

Retest checkout after every platform, payment or theme update; regressions often arrive with unrelated releases.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Subscriptions | Show first charge date, renewal terms and cancellation clearly |
| High-value purchases | Add finance options, extended guarantees and contact support |
| International orders | Local currency, duties and taxes shown upfront, local payment methods |
| Digital products | Instant delivery messaging; minimal fields |
| Platform limits (hosted checkout) | Optimise what you control: cart page, product pages, payment settings |

## Handoffs to related skills
- Forms: `form-optimisation`
- Trust and reviews: `social-proof-trust`
- Mobile: `mobile-conversion`
- Research: `conversion-research`
- Test planning: `cro-test-planning`
- Cart recovery messages: the CRM and Lifecycle `win-back-reactivation` and `sms-whatsapp-lifecycle` skills

## Worked example
An online furniture retailer's mobile checkout completion was much lower than desktop. Walk-throughs showed delivery costs appeared only at the final step, the postcode field rejected valid formats and there were no wallet payments. An exit survey confirmed surprise costs as the top reason for leaving. Fixes repaired postcode validation and showed delivery estimates on product and cart pages; tests added Apple Pay and Google Pay and moved the coupon field into a collapsed link. Mobile checkout completion rose substantially and revenue per visitor improved.

## Output format
```
# Checkout review: <site>, <date>
## Funnel by step, device and market
## Walk-through findings
## Costs, delivery, forms, payments and trust audit
## Evidence (surveys, recordings, tickets)
## Fixes, tests and recovery plan
```

## Common mistakes
- Revealing costs at the last step.
- Forcing account creation.
- Missing local payment methods.
- Strict validation that rejects valid input.
- Testing small visual changes while errors remain.

## Questions to ask before you change checkout
- Where in checkout do customers leave, on which devices and in which markets?
- When do customers first see the total cost?
- Which payment methods do customers in each market expect?

## Self-check before you answer
- Are costs shown early and clearly?
- Is guest checkout available?
- Are payment methods matched to markets?
- Are errors fixed before tests?

## Further reading
- Baymard Institute checkout usability research: https://baymard.com/research/checkout-usability
- Baymard cart abandonment statistics: https://baymard.com/lists/cart-abandonment-rate

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/conversion-rate-optimization/checkout-optimisation/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.

Workflow

Step 1. Map the funnel

Step conversion from cart to purchase by device, market and new versus returning customers.

Step 2. Walk through as a customer

Complete purchases on mobile and desktop, as a guest and a returning user, in key markets.

Step 3. Check costs and delivery

When does the total appear? Are delivery dates clear?

Step 4. Review forms and errors

Field count, address lookup, autofill, validation and error recovery.

Step 5. Review payments

Methods offered versus market expectations; payment failures by method; 3-D Secure friction.

Step 6. Review trust

Security cues, returns, guarantees, contact options and reviews near the payment step.

Step 7. Gather evidence

Exit survey at checkout, recordings at leaking steps, support tickets.

Step 8. Fix, test and recover

Fix bugs and errors immediately; test bigger changes; set up cart recovery emails or messages with consent.

Checkout checklist

  • Guest checkout available and obvious.
  • Total cost visible before the payment step.
  • Delivery dates shown, not just methods.
  • Address lookup or autocomplete.
  • Billing address defaults to delivery address.
  • Wallets and local payment methods for each market.
  • Inline validation that keeps entered data.
  • Progress indicator for multi-step checkout.
  • Security cues and returns policy near payment.
  • Fast, mobile-friendly pages with large tap targets.

Checkout exit survey

Ask one question when visitors leave checkout: "What made you leave checkout today?" with options such as delivery cost, delivery time, needed to create an account, payment method not available, checkout too long, website errors, just browsing, and other (please tell us). Review answers weekly by device and market.

Payment method coverage by market (examples)

MarketMethods customers often expect
UKCards, Apple Pay, Google Pay, PayPal, buy now pay later
NetherlandsiDEAL, cards, PayPal
GermanyPayPal, cards, invoice or bank transfer options
BrazilPix, cards, boleto
NigeriaCards, bank transfer, USSD and local gateways

Check current payment preferences with your provider before launching in a market.

Checkout metrics

MetricWhy
Cart to purchase rateOverall checkout health
Step completion by deviceFinds mobile problems
Payment failure rate by methodGateway and 3-D Secure issues
Error rate by fieldValidation problems
Revenue per visitorBusiness outcome
Recovered cartsReminder effectiveness

Cart recovery basics

With consent, send a reminder within a few hours of abandonment, a second the next day and optionally a third with help or a small incentive only for customers whose economics allow it. Link straight back to the saved cart and mention delivery and returns. Measure recovery against a holdout so reminders are credited only with sales they actually add.

Speed checks

Payment pages often load extra scripts (fraud tools, tag managers, chat). Check Core Web Vitals field data for checkout templates and remove scripts that are not essential at this step.

Retest checkout after every platform, payment or theme update; regressions often arrive with unrelated releases.

Edge cases and judgement calls

SituationWhat to do
SubscriptionsShow first charge date, renewal terms and cancellation clearly
High-value purchasesAdd finance options, extended guarantees and contact support
International ordersLocal currency, duties and taxes shown upfront, local payment methods
Digital productsInstant delivery messaging; minimal fields
Platform limits (hosted checkout)Optimise what you control: cart page, product pages, payment settings
  • Forms: form-optimisation
  • Trust and reviews: social-proof-trust
  • Mobile: mobile-conversion
  • Research: conversion-research
  • Test planning: cro-test-planning
  • Cart recovery messages: the CRM and Lifecycle win-back-reactivation and sms-whatsapp-lifecycle skills

Worked example

An online furniture retailer's mobile checkout completion was much lower than desktop. Walk-throughs showed delivery costs appeared only at the final step, the postcode field rejected valid formats and there were no wallet payments. An exit survey confirmed surprise costs as the top reason for leaving. Fixes repaired postcode validation and showed delivery estimates on product and cart pages; tests added Apple Pay and Google Pay and moved the coupon field into a collapsed link. Mobile checkout completion rose substantially and revenue per visitor improved.

Output format

# Checkout review: <site>, <date>
## Funnel by step, device and market
## Walk-through findings
## Costs, delivery, forms, payments and trust audit
## Evidence (surveys, recordings, tickets)
## Fixes, tests and recovery plan

Common mistakes

  • Revealing costs at the last step.
  • Forcing account creation.
  • Missing local payment methods.
  • Strict validation that rejects valid input.
  • Testing small visual changes while errors remain.

Questions to ask before you change checkout

  • Where in checkout do customers leave, on which devices and in which markets?
  • When do customers first see the total cost?
  • Which payment methods do customers in each market expect?

Self-check before you answer

  • Are costs shown early and clearly?
  • Is guest checkout available?
  • Are payment methods matched to markets?
  • Are errors fixed before tests?

Further reading

When to use this skill, and when not to

Use it when cart or checkout abandonment is high, when mobile checkout lags desktop, when entering new markets, after platform changes and when adding payment providers.

Checkout is where buyers have already decided and the business can still lose them. Baymard Institute has long reported average documented cart abandonment of around 70%, much of it from fixable causes such as late costs, forced accounts, long forms and missing payment methods.

Don’t use it for problems before the cart (use Landing Pages) or subscription plan choice (use Pricing Page).

Example prompts

  • “Reduce our cart abandonment.”
  • “Why does mobile checkout convert worse than desktop?”
  • “Which payment methods should we add for the Netherlands?”
  • “Write a checkout exit survey.”
  • “Set up cart recovery emails.”

Example output

The skill returns a fixed structure. A shortened example for an imaginary site:

# Checkout review: example furniture retailer, 11 October 2026

Leak: mobile checkout completion far below desktop
Causes: delivery cost only at final step; postcode validation bug; no wallets
Fix now: postcode validation
Tests: delivery estimate on product and cart pages; Apple Pay and Google Pay; coupon field collapsed
Recovery: reminders within hours and next day, measured against a holdout

Errors and bugs are fixed before any test, because every broken step costs sales while an experiment runs.

What the agent needs from you

The skill asks for the checkout flow and platform, funnel data by step, device and market, payment methods and failure rates, delivery options and costs, recordings, exit surveys and support tickets, and the returns policy and trust elements shown.

How this skill hands off to related skills

Checkout connects to the set: fields in Forms, trust in Social Proof, phones in Mobile, evidence from Research, scheduling in Test Planning and recovery messages with the CRM and Lifecycle SMS and WhatsApp skill.

How to run Checkout Optimisation step by step

  1. Install the skill as checkout-optimisation/SKILL.md.
  2. Map the funnel by step, device and market.
  3. Walk through as a customer.
  4. Audit costs, forms, payments and trust.
  5. Gather exit survey and recording evidence.
  6. Fix, test and recover.

Situations this skill handles

Checkouts differ by business. The skill handles these situations:

SituationWhat the skill does
SubscriptionsClear renewal and cancellation terms
High-value purchasesFinance options and support contact
International ordersLocal currency, duties and payments
Digital productsInstant delivery and minimal fields
Hosted checkout limitsOptimises what you control
Payment failuresGateway and 3-D Secure checks

What makes this skill different

Most checkout advice lists best practices. This skill measures each step by device and market, walks the flow as a real customer, fixes errors first and matches payment methods to each market.

Cart recovery is measured against a holdout, so reminders are credited only with the sales they add.

Practical tips from real projects

  • No surprise costs.
  • Remove barriers.
  • Offer the payments people use.
  • Recover, do not just prevent.

A worked example: an online furniture retailer found mobile checkout completion much lower than desktop. Walk-throughs showed delivery costs appeared only at the final step, the postcode field rejected valid formats and there were no wallet payments. An exit survey confirmed surprise costs as the top reason for leaving. Fixes repaired postcode validation and showed delivery estimates on product and cart pages; tests added Apple Pay and Google Pay and moved the coupon field into a collapsed link. Mobile checkout completion rose substantially and revenue per visitor improved.

Common causes have known fixes. Late costs are solved with delivery estimators on product and cart pages and an early total. Forced accounts give way to guest checkout with account creation offered after purchase. Long forms shrink with fewer fields, address lookup, autofill and billing address defaulting to delivery. Missing payment methods are added by market. Unclear delivery becomes specific dates and priced options. Trust concerns are met with security cues, recognisable payment logos, returns and contact details. Validation errors move inline and keep entered data. A prominent coupon field is collapsed so visitors do not leave to search for codes. Slow payment pages lose non-essential scripts.

The checkout checklist confirms guest checkout is obvious, total cost appears before payment, delivery dates are shown, address lookup works, billing defaults to delivery, wallets and local methods are offered, validation is inline, progress is shown for multi-step flows, security and returns sit near payment and pages are fast on mobile with large tap targets.

An exit survey asks one question when visitors leave checkout, with options such as delivery cost, delivery time, needing an account, missing payment method, checkout too long, website errors or just browsing, and answers are reviewed weekly by device and market.

Payment expectations differ by market: cards, wallets, PayPal and buy now pay later in the UK; iDEAL in the Netherlands; PayPal and invoice options in Germany; Pix and boleto in Brazil; and bank transfer, USSD and local gateways in Nigeria. Current preferences are confirmed with the payment provider before launch.

Metrics include cart to purchase rate, step completion by device, payment failure rate by method, error rate by field, revenue per visitor and recovered carts.

Cart recovery with consent sends a reminder within a few hours, another the next day and an optional third with help, linking straight back to the saved cart.

Recovery is measured against a holdout group that receives no reminders, so the programme is credited only with purchases it actually adds rather than with customers who would have returned anyway. Checkout is retested after every platform, payment or theme update, because regressions often arrive with releases that seem unrelated, and payment pages are checked for heavy fraud, tag manager and chat scripts that slow the final step.

Every market is tested with a real purchase before launch.

Frequently asked questions

Common causes include extra costs revealed late, forced account creation, long forms, missing payment methods, slow delivery and trust concerns.

Yes. Offer account creation after purchase instead of before.

Cards plus wallets such as Apple Pay, Google Pay and PayPal, and local methods like iDEAL, Pix or bank transfers by market.

As early as possible, ideally on product and cart pages, with delivery dates.

Often, when sent with consent, soon after abandonment and measured against a holdout.

Show the first charge date, renewal terms and how to cancel clearly at checkout.

Changelog

  • 1.0.0, 10 October 2026: first release.

Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.