We Lost 60% of Users Between Cart and Checkout

Voqal TeamNovember 21, 2025

Most mobile shoppers who add to cart never complete the purchase. The average documented cart abandonment rate is 70.22%, and on mobile web it climbs to roughly 85.65% — the worst of any device. The cause is rarely price; it is friction: too many steps, too many form fields, too much typing on a 6-inch screen. Voice-to-actions removes the friction by collapsing checkout into one spoken intent and one confirm tap.

We watched it happen in our own funnel. Sixty percent of users who reached the cart vanished before the order went through. Nobody changed their mind about the product in those ten seconds. They quit because we asked them to type.

The drop-off is real, measurable, and getting worse on mobile

The abandonment problem is not anecdotal. It is one of the most-studied numbers in e-commerce, and the consensus is brutal.

  • The Baymard Institute, aggregating 50 separate studies, puts the average cart abandonment rate at 70.22%.
  • Mobile web abandonment runs around 85.65%, versus roughly 68–69% on desktop — a gap of 15–16 points.
  • That mobile penalty matters more every year. Mobile commerce is projected to reach 62% of global e-commerce by 2026, which means the worst-performing surface is also the dominant one.
  • The cost is staggering. Retailers lose an estimated $18 billion annually to abandoned carts.

If you only optimize for desktop, you are optimizing the channel that is shrinking while the channel that is growing leaks the hardest.

Why people quit: it is the typing, not the price

The instinctive explanation is "sticker shock." Hidden costs are genuinely the single largest driver — nearly 40% of U.S. shoppers abandon over surprise shipping, taxes, or fees. But after that, almost every top reason is a friction problem you control:

The common thread is manual input on a small screen. Every field is a tap, a keyboard, a chance to fat-finger an email and bounce.

The math of form fields

Baymard's benchmarking quantifies exactly how much each field costs you. The average checkout has 5.1 steps and 11.3 form fields, while the optimal count is closer to 7–8. Beyond the eighth field, completion rates drop 4–6% for every additional field.

Read that again. Each field past the eighth is not a minor annoyance — it is a measurable percentage of revenue walking out the door.

Friction point to abandonment impact

Friction pointDocumented impactSource
Unexpected extra costs at checkout~39–48% of abandonmentsStatista
Checkout too long / too complicated~18–22% of abandonmentsBaymard
Forced account creation~19–26% of abandonmentsCartBoss
Each form field beyond the 8th~4–6% drop in completion per fieldBaymard
Mobile web vs. desktop~85.65% vs. ~68% abandonmentMobiloud

The upside is symmetrical. Baymard calculates that the average large e-commerce site could lift conversion by 35.26% through better checkout design alone — about $260 billion in recoverable revenue industry-wide. Checkout is the highest-leverage surface in the entire funnel.

MENA: the same problem, turned up to eleven

If you operate in the Middle East and North Africa, the stakes are higher and the friction is worse. Brands in the Middle East and Africa see the world's highest cart abandonment rate at ~93%, well above the global average.

At the same time, the region is decisively mobile-first: mobile platforms are expected to drive 70% of total online transaction value in MENA by 2025. So the worst abandonment in the world is concentrated on the device with the worst input ergonomics, for users typing across Arabic and English, often switching keyboards mid-form. Arabic address entry on a touch keyboard is its own special tax. We dig into the language side in our Arabic voice SDK complete guide and in voice UI conversion data from banking, delivery, and e-commerce apps in MENA.

The fix: collapse checkout into one spoken intent

The standard advice — autofill, guest checkout, one-tap wallets, fewer fields — is correct and you should do all of it. But it is incremental. It shaves fields off a form that still fundamentally asks the user to drive a multi-screen flow.

Voice-to-actions changes the shape of the problem. Instead of navigating cart, then shipping, then payment, then review, the user says what they want and confirms once:

"Reorder my usual and ship it to home."

The app resolves the intent against the user's real account state — saved address, default card, last order — performs the action, and renders a single confirmation card. One utterance, one tap to confirm. Zero keyboards.

This is the part worth being precise about, because the architecture is what makes or breaks it. A transcription layer that turns speech into text in a search box is not this. It still drops the user into the same form. Voice-to-actions maps a spoken intent directly onto a real in-app action plus the UI to confirm it — that distinction is the whole game, and we break it down in voice-to-actions vs. transcription and what is a voice-to-actions SDK.

What Voqal actually does

Voqal is a voice-to-actions SDK for mobile apps. You drop it in, and users can speak an intent that becomes a real in-app action — add to cart, reorder, pay, settle, schedule — with the confirmation UI rendered automatically. It runs on iOS, Android, React Native, and Flutter, handles Arabic and English natively, and returns the spoken result plus rendered widget in under a second.

The honest framing: Voqal does not magically eliminate abandonment. Surprise shipping costs will still lose you sales — that is a pricing and transparency problem, not an input problem. What Voqal removes is the friction tax: the steps, the fields, the keyboard switching, the password walls. For the large slice of abandonment driven by checkout complexity and manual entry — which is most of the non-cost reasons combined — it turns a five-step form into one sentence.

That is also why it is a confirm, not a blind execution. The user speaks intent; the app shows exactly what will happen and waits for one tap. Speed without a confirmation step is how you erode trust, especially for payments. We cover that balance, and the conversion numbers behind it, in voice commerce checkout conversion for retail and delivery and your users don't want to type.

Is it worth it?

If checkout friction is costing you a documented 30–40% of would-be conversions, and better checkout UX can recover a 35% lift, the ROI question answers itself for high-volume mobile funnels. We lay out the model — where voice pays back, and where it doesn't — in the business case for voice ROI in mobile apps.

We lost 60% of users between cart and checkout because we made them type their way to a purchase they had already decided to make. The fix was not a better form. It was no form.

FAQ

What is the average mobile cart abandonment rate?

The overall average is about 70.22% across 50 studies, but mobile web specifically runs around 85.65% — the highest of any device, and 15–16 points above desktop.

Why do shoppers abandon checkout if it isn't about price?

Unexpected costs are the top single reason (~39%), but the next tier is all friction: a checkout that is too long or complicated (~18–22%) and forced account creation (~19–26%). Most of the controllable loss is input friction, not pricing.

How many form fields is too many?

The average checkout uses 11.3 fields; the optimal is 7–8. Completion rates fall 4–6% for every field beyond the eighth.

Does voice checkout actually reduce abandonment?

Voice-to-actions removes the friction tax — steps, fields, keyboard switching — that drives most non-cost abandonment, by collapsing checkout to one spoken intent and one confirm. It does not fix pricing-driven abandonment like surprise shipping. See voice commerce checkout conversion for the data.

Why is abandonment worse in MENA?

The Middle East and Africa post the world's highest abandonment (~93%) while mobile drives ~70% of online transaction value. Arabic/English keyboard switching during checkout compounds the friction — covered in our Arabic voice SDK guide.

How do I add voice-to-actions to my app?

Voqal ships as an SDK for iOS, Android, React Native, and Flutter with sub-second response in Arabic and English. Start with the docs or join the waitlist.

Related articles