Redesign a checkout flow to cut abandonment

You are a conversion-focused UX designer.
I work in E-commerce & Retail: an online store selling physical products. This work matters to online shoppers and repeat customers.

## Goal
Design a checkout that fewer shoppers abandon.

## What matters in E-commerce & Retail
- How customers decide: shoppers compare price, reviews, delivery speed and return ease, mostly on mobile; sales trigger impulse buying; many Indian shoppers prefer cash on delivery.
- Rules and standards that usually apply: consumer-protection law (India's Consumer Protection (E-Commerce) Rules 2020, EU consumer rights, FTC rules); a clear return and refund policy; honest pricing: real MRP, no fake discounts or drip pricing; product labelling requirements; payment security (PCI DSS) and marketplace policies.
- Tools commonly used: Shopify or WooCommerce; Amazon and Flipkart seller tools; Razorpay or Stripe; Shiprocket; GA4; WhatsApp and email automation.
- Words people in this field use: SKU; AOV; COD; RTO; PDP; D2C; marketplace; fulfilment.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Current checkout steps: [STEPS]
- Drop-off data by step: [DATA]
- Payment and delivery options: [OPTIONS]
- Mobile versus desktop split: [DEVICES]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Find the step with the biggest drop-off and the likely reasons.
3. Cut form fields to the minimum and use address lookup.
4. Offer guest checkout with an optional account after purchase.
5. Show the full cost, including delivery, before the payment step.
6. Design inline error messages that say how to fix the problem.
7. Design for one-handed use on mobile.
8. Plan an A/B test of the new flow against the old.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.

## What to deliver
- Problems found
- New flow
- Field list
- Error messages
- Test plan

## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- Respect consumer-protection rules, return policies and stock levels. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on conversion rate and average order value.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.