Average Checkout Conversion Rate: Benchmarks and How to Beat Them

On this page 7 sections

1. Conversion Rate vs. Checkout Completion Rate
2. Average Checkout Conversion Rate Benchmarks by Device and Category
3. How to Measure Each Funnel Step Accurately
4. Finding Drop-Off at the Payment Step
5. Using Decline Data to Spot Hidden Losses
6. Quick Wins Ranked by Effort and Impact
7. Next Steps

Key takeaways

• Store conversion rate and checkout completion rate measure different problems, so track them separately.
• Published benchmarks vary widely by device, category and method, so your own trend line matters more than any outside number.
• Payment-step losses (missing methods, form errors, declines) are often the cheapest to fix and the easiest to overlook.
• Decline reports from your processor can reveal lost sales that analytics tools miss.

The average checkout conversion rate is one of the most searched numbers in ecommerce, and one of the most misunderstood. Many stores compare one blended percentage against an outside benchmark and stop there. That number can't tell you whether shoppers leave because they're still browsing or because your payment step failed them. This guide shows you how to split your funnel into measurable stages and how to read benchmarks without being misled. It also shows how to find losses at the payment step, including declined orders that never appear in your analytics.

Conversion Rate vs. Checkout Completion Rate

People often use these two metrics interchangeably, but they measure very different things.

Store Conversion Rate

Store conversion rate is completed orders divided by sessions. It reflects everything: traffic quality, product pages, pricing, shipping costs, trust and checkout. A low store conversion rate might mean your ads bring the wrong visitors. It doesn't necessarily mean your checkout is broken.

Checkout Completion Rate

Checkout completion rate is completed orders divided by checkouts started. It isolates the part of the funnel where the shopper has already decided to buy. Losses here usually come from friction, surprise costs, limited payment options or failed payments. They rarely reflect a lack of interest in the product.

The Stages in Between

To find out exactly where your store underperforms, measure each handoff:

The first three rows are mostly browsing losses. The last three are checkout and payment losses. Each group needs a different fix, and different people on your team usually own each one.

Average Checkout Conversion Rate Benchmarks by Device and Category

Analytics vendors, platform providers and research firms all publish ecommerce conversion benchmarks. Their numbers differ widely because each one defines "conversion" differently, samples different stores and measures different time periods. Treat any outside figure as a rough reference point, not a target. Before you compare yourself to a report, check how it defines its terms.

Device Patterns

Many stores see mobile bring more traffic than desktop but convert at a lower rate. Check whether that holds in your own device segments. Two common reasons are that shoppers browse on phones and buy later on a laptop, and that typing card numbers and addresses on a small screen is harder. Both make mobile the place where express wallets and autofill are most likely to help. To decide which wallet buttons to offer, see our comparison of Shop Pay, Apple Pay and PayPal express checkout buttons.

If your mobile checkout completion rate trails desktop by a wide margin, examine the checkout itself before you blame mobile browsing habits. A gap that appears after shoppers start checkout usually points to a usability or payment-method problem. Our guide to choosing between one-page and multi-step checkout explains which layout suits your mobile traffic.

Category Patterns

Conversion behavior often varies by what you sell. Compare these patterns against your own data:

• Apparel and boutiques: Shoppers may add several sizes or colors to the cart and treat it as a wishlist. That can lower the cart to checkout rate even when the checkout works well. Product drops and launches bring traffic spikes and sometimes bot activity.
• Consumables and replenishment items: Repeat buyers know what they want, so checkout completion usually matters more than browsing metrics.
• High-ticket, considered purchases (furniture, jewelry): Shoppers often visit several times before buying. They also tend to look for financing options and clear trust signals at the payment step.

Your Best Benchmark Is Your Own Baseline

Record each stage weekly. Segment the results by device, by new vs. returning customers and by traffic source. If your payment-step completion drops after a theme update, that tells you far more than any industry average.

How to Measure Each Funnel Step Accurately

Bad tracking creates fake problems. Before you change anything, confirm that your numbers are real.

Set up the Right Events

If you use Google Analytics 4, its recommended ecommerce events map well to the funnel: add_to_cart, begin_checkout, add_shipping_info, add_payment_info and purchase. The event list can change, so confirm it in Google's current documentation.

• Shopify stores: The built-in analytics include a conversion funnel view. Check which stages your plan reports, then decide whether you need a GA4 integration for step-level detail.
• WooCommerce stores: Step-level tracking usually comes from a plugin or a custom tag setup. Place real test orders to confirm that each event fires.

Common Measurement Traps

1. Express wallets skip steps. A shopper who pays with a wallet button may never fire your shipping or payment-info event. Those steps can then look leaky when they aren't.
2. Hosted payment pages break sessions. If checkout redirects to a gateway domain and back, configure cross-domain tracking. Otherwise, orders may be credited to the wrong source.
3. Thank-you page reloads double-count purchases. Deduplicate purchases by order ID.
4. Bots inflate the top and bottom of the funnel. Card testing attacks generate payment attempts that never came from real customers.
5. Consent banners reduce tracked sessions. Compare analytics order counts against your platform's order count to estimate the gap.

Reconcile weekly: analytics purchases, platform orders and processor-approved transactions should roughly agree. Large gaps mean a tracking problem, a payment problem or both.

Finding Drop-Off at the Payment Step

The payment step is where a committed buyer turns into revenue. Losses here hurt the most because you've already paid to acquire that shopper. For a per-order look at ad and processing costs across sales channels, see our guide to selling on Amazon vs. your own website.

Signs Your Payment Step Is the Problem

• Shoppers complete the information step at a healthy rate, but few payment-info events turn into purchases.
• Payment-step completion differs sharply between iPhone and Android or between browsers.
• Customer emails say things like "the card wouldn't go through" or "I didn't see PayPal or Apple Pay."

Common Causes

• Missing or hidden payment methods. If a wallet button doesn't appear on certain devices, mobile buyers may leave. WooCommerce merchants should read about why Apple Pay may not appear on WooCommerce. Shopify merchants can reorder payment methods at Shopify checkout so the most-used options appear first.
• Surprise costs at the final step. Shipping, taxes or card fees that first appear at payment often trigger abandonment. If you add a card fee, disclosure rules apply and state laws vary. Confirm the requirements with your processor and a qualified professional.
• Forced account creation. Requiring a login before payment adds a barrier. Our comparison of guest checkout vs. forced accounts covers the trade-offs.
• Form validation errors. A vague message like "payment failed" leaves shoppers guessing. Specific errors for a mistyped expiration date, CVV or ZIP code let them fix the problem and try again.
• Authentication friction. 3-D Secure can shift fraud liability, but a poorly configured challenge flow can stall mobile buyers. See how to use 3D Secure without losing sales.
• International shoppers. Showing prices only in USD, or declining cards because of cross-border settings, can quietly suppress sales from overseas visitors.

Using Decline Data to Spot Hidden Losses

Analytics tools record that a shopper reached the payment step and left. They don't record why. Your processor or gateway does.

What to Pull From Your Gateway

Export these items from your gateway, or ask your processor for them:

• Authorization rate: approved transactions divided by attempted transactions.
• Decline reason codes: insufficient funds, do not honor, expired card, suspected fraud, AVS or CVV mismatch and others.
• Declines blocked by your own filters: fraud rules, AVS settings or velocity limits that you or your platform set.
• Declines by card type and country: domestic vs. international and debit vs. credit.

How to Read the Patterns

Separate attempts from people. One shopper who tries three times creates three declines but represents only one lost sale. Card testing works the other way: it creates large numbers of attempts that were never real sales. If bots are hitting your checkout, our guide to stopping card testing attacks explains the defenses.

Don't set up automatic retries on declined cards. Card network rules restrict reattempts on certain decline types, and excessive retries can lead to penalties. Ask your processor which declines can be retried and when. If you sell items before they ship, our guide to taking preorders online without triggering processor holds compares charge-now, authorize-later and deposit models.

An Illustrative Example

The numbers below are illustrative, not benchmarks. Two apparel stores each complete 200 orders from 10,000 sessions, so both show the same store conversion rate.

• Store A loses most shoppers between cart and checkout. That's a browsing problem tied to size uncertainty and shipping costs. Store A needs better sizing guides and earlier shipping estimates.
• Store B gets plenty of shoppers to the payment step but loses many to AVS-related declines. Store B needs to review its filter settings with its processor.

The blended number hides both problems.

Quick Wins Ranked by Effort and Impact

Impact depends on your store. Treat these rankings as a starting order and test each change against your baseline.

Start with the low-effort fixes in whichever stage your own data shows the biggest leak. Change one thing at a time so you know what worked. If local-currency pricing is on your list, see our guide to multi-currency checkout and pricing in your shopper's currency.

Next Steps

1. Build a stage-by-stage funnel report and segment it by device.
2. Reconcile analytics orders, platform orders and approved transactions.
3. Pull decline reason codes from your gateway for the last 30 to 90 days.
4. Fix the cheapest problem in your weakest stage, then measure again.

If your decline data points to processing settings, MannyPay offers online payment processing for ecommerce stores and payment gateway options, including Authorize.net and NMI. MannyPay also integrates with Shopify and WooCommerce. You can request a free quote, and a MannyPay specialist will respond within one business day to review your current setup.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.