The number on the proposal
The fastest way to lose my trust in an e-commerce proposal is a single line that reads something like "add one-tap checkout, lift conversion 50%." I've seen that exact shape of sentence in pitch decks, plugin listings and agency proposals, and when you follow the number home it almost always lands on the website of the company selling the button.
So this article does something slightly awkward for an agency that builds stores. It ranks ten e-commerce app features by what independent, methodical research actually measured, and it names the lift numbers I won't use, with the reason for each.
The research base is narrow on purpose. Baymard Institute's checkout and abandonment work, Nielsen Norman Group's product page studies, Google's web.dev guidance (with its case studies clearly labelled as company-reported) and one university research center. Everything checked today, September 30, 2026.
If you want the build side of this, what an app costs and who should build it, that lives in our guide to e-commerce app development services. This one is about which features earn their place once you're building.
Features are not the unit
The wrong model is that conversion is a sum of features, so adding features adds conversion. It isn't. Conversion is what's left after you remove the reasons people leave.
Think of a grocery store with a broken door, a long line and prices hidden until the register. You could add a free coffee bar by the entrance. Some people would stay. More people would stay if you fixed the door and put the prices on the shelf.
That's the shift. A feature list is useful only when each item maps to a documented reason shoppers abandon. Therefore the ranking below starts from the reasons, not from the features, and several of the top items are removals rather than additions.
To be clear, this makes for a less exciting roadmap. "Delete four checkout fields" doesn't demo well. It also costs a fraction of a 3D configurator, and the evidence behind it is much stronger.
What the research says
The verified baseline is that about 70% of online carts are abandoned, and extra costs are the largest stated reason. Baymard Institute's running meta-study averages 50 published abandonment studies and lands on 70.22% (Baymard, cart abandonment).
Don't over-read that figure. It averages studies with different samples and definitions, and a good chunk of abandonment is people using the cart as a wish list. Baymard separates that out: its reasons survey excludes shoppers who say they were just browsing.
Among the shoppers who were ready to buy, here's what they said drove them off, from the same Baymard page:
| Reason shoppers gave for abandoning | Share | Feature that answers it |
|---|---|---|
| Extra costs too high (shipping, tax, fees) | 40% | 1. Total cost shown early |
| Delivery was too slow | 20% | 1. Delivery date shown with the cost |
| Didn't trust the site with card details | 19% | 5. Express wallets |
| Site wanted me to create an account | 18% | 2. Guest checkout |
| Checkout too long or complicated | 17% | 3. Fewer fields, address autocomplete |
| Website had errors or crashed | 17% | 4. Performance and stability |
| Returns policy wasn't satisfactory | 13% | 6. Returns shown before checkout |
| Couldn't see or calculate total cost upfront | 12% | 1. Total cost shown early |
| Credit card was declined | 10% | 5. More payment methods |
| Not enough payment methods | 9% | 5. Express wallets |
Two more Baymard findings set the scale of the problem. Its benchmark of 343 large US and European sites rates 65% of checkouts mediocre or worse and only 2% good (Baymard, checkout usability). And its 2024 benchmark found the average checkout runs 5.1 steps and 11.3 form fields, against an ideal of about 8 fields (Baymard, form fields).
How I ranked the ten
The order is based on two things: how many shoppers name the problem a feature solves in Baymard's abandonment survey, and how strong the independent evidence behind the feature is. Features that answer a bigger stated reason rank higher. Features with only vendor evidence rank lower, whatever the vendor says.
That means the list is not a ranking by measured lift. No neutral study measures the lift of each feature against the others, and I'd be inventing precision if I claimed one. It's a ranking by the size of the documented problem, which is the next best thing and something you can check.
One more boundary. Survey reasons are what shoppers say, not a controlled test of what they do. People can name several reasons at once, so the percentages don't add up to 100. Use them to set order, then test in your own store.
The 10 features
Here are the ten, most important first. Each one says what problem it answers, what the evidence is, and what it costs you to get wrong.
Total Cost Upfront
no surprises at the last step
Showing the full price, including shipping, tax, fees and a delivery date, before the customer reaches payment is the single most evidence-backed change you can make. Extra costs were named by 40% of abandoning shoppers in Baymard's survey, and a separate 12% said they couldn't see or calculate the total upfront (Baymard).
In practice that means a shipping estimator on the product page or cart, a free-shipping threshold stated at the top of the store rather than discovered at checkout, and fees shown as line items early. Slow delivery was the second biggest reason at 20%, so put an estimated delivery date next to the cost.
The downside: showing a high shipping cost early may lose some people sooner. That's fine. They were going to leave anyway, and now they leave before you've spent a remarketing budget chasing them.
Guest Checkout
buy first, register later
Letting people buy without an account answers the fourth largest reason in the table: 18% of abandoners in Baymard's current list said the site wanted them to create one. An earlier Baymard study of 4,384 US adults in 2022 put that figure at 24% (Baymard, guest checkout). Different survey waves, same direction.
Having the option isn't enough. Baymard found 47% of sites that offer guest checkout fail to make it the most prominent choice, and in testing people assumed an account was mandatory when the guest path was a faint text link or sat below the sign-in form.
So label it "Guest checkout", make it a button, put it first, and offer account creation on the confirmation page when the shopper already has a reason to say yes. In a native app where login is part of the value, allow browsing and cart building before sign-in at minimum.
Short Checkout Form
fewer fields and address autocomplete
Cutting the form to what fulfilment needs answers the 17% who called checkout too long or complicated. Baymard's 2024 average is 11.3 fields; its ideal is about 8, or 12 to 14 form elements in total, against an average US checkout that displays 23.48 elements by default (Baymard).
Do the arithmetic out loud. Going from 11.3 fields to 8 means removing about 3.3 fields, roughly 29% of the form. The usual candidates: a second address line shown by default, separate first and last name, a company field for consumers, and billing address when it matches shipping.
Address autocomplete belongs here too, because it turns five fields of typing into one lookup. The caveat is real: autocomplete fails on new builds, rural routes and apartment numbers, so the manual path has to stay one tap away. I don't have a neutral lift figure for autocomplete on its own, and I won't invent one.
Speed and Stability
fast pages that don't break
A fast, crash-free app answers the 17% who left because the site had errors or crashed, and it sets the floor for every other feature. Google's web.dev defines good Core Web Vitals as Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, at the 75th percentile of real page loads (web.dev).
The business case studies need careful handling, because they're company-reported through Google. Vodafone reported 8% more sales after a 31% LCP improvement; Lazada reported a 16.9% mobile conversion increase after making LCP three times faster (web.dev case studies). Those are the companies' own numbers, published by the company that runs the metrics. Directionally useful, not neutral.
The same goes for Milliseconds Make Millions, which Google commissioned from 55 and Deloitte: over 30 million sessions across 37 brand sites, reporting that a 0.1 second mobile speed improvement went with an 8.4% higher retail conversion rate (web.dev). It's a larger sample than most, and it's still funded by a party with an interest in a faster web. I cite it as that.
Express Wallets
pay without typing a card
Offering the wallets your customers already use, such as Apple Pay, Google Pay, Shop Pay or PayPal, answers two independent findings: 19% of abandoners didn't trust the site with their card, and 9% said there weren't enough payment methods (Baymard). A wallet solves both, because the card never gets typed into your form.
Here's where I part ways with the marketing. Every specific lift figure I could find for wallets came from the wallet company or a study it paid for. I explain the two biggest in the refusals section below. The feature ranks fifth because the problem is documented independently; it doesn't rank first because the lift numbers aren't.
Practical note: pick the two or three wallets your audience uses and place them at the top of checkout. A row of eight payment logos adds visual weight to the page that it didn't need.
Returns Information
the policy before the purchase
Stating the returns policy on the product page and in the cart answers the 13% who abandoned because the policy wasn't satisfactory. Sometimes the fix is a better policy. Often it's just a visible one, because a shopper can't be satisfied by a policy they can't find.
One line near the add to cart button (window, who pays return shipping, how refunds arrive) with a link to the full terms. That's the feature. It's cheap, and it matters most on higher-priced items where the downside of a wrong purchase is larger.
Search and Filters
find the product before the patience runs out
Search and filtering decide whether shoppers reach a product page at all, and Baymard's research says most large sites get it wrong. Its benchmark of 343 US and European sites found more than 700 search-specific usability issues and condensed its findings into 31 search guidelines (Baymard, e-commerce search).
The basics that follow from that work: autocomplete that suggests categories as well as products, tolerance for misspellings and synonyms, filters that match how customers describe the product rather than how your warehouse does, and no dead-end empty results page.
It ranks seventh only because it sits upstream of checkout and doesn't appear as a reason in the abandonment survey. For a catalogue of thousands of SKUs, I'd move it higher. For a store with twelve products, a clear category page matters more than search.
Product Imagery and Honest Reviews
answer the question a shelf would
Several images and real reviews replace the handling a shopper would do in a store. Nielsen Norman Group's study of 49 ecommerce sites found one product view is rarely adequate, that shoppers deliberately seek out negative reviews to judge the worst case, and that they want review summaries they can sort (NN/g).
There's an old and often repeated finding that purchase likelihood peaks for products rated about 4.2 to 4.5 stars rather than a perfect 5. Its source is a 2015 Spiegel Research Center student project using data supplied by PowerReviews, a reviews vendor (Spiegel Research Center). It isn't peer reviewed, and I'd treat it as a plausible pattern, not a law. It agrees with NN/g on one thing: shoppers distrust a wall of perfect scores.
Which is also a legal point now. The FTC's reviews rule bans suppressing negative reviews and buying positive ones. More on that in the rules section.
Accessibility
a checkout everyone can finish
An accessible checkout is both a conversion feature and a legal one. WCAG 2.2, the current W3C Recommendation, added criteria that read like a checkout review: Redundant Entry (don't make people retype what they already gave you), Accessible Authentication (don't gate login on a memory or puzzle test), Target Size (Minimum) for tap targets, and Dragging Movements alternatives (W3C WCAG 2.2).
Notice how much overlaps with features 2 and 3. Redundant Entry is the billing-same-as-shipping checkbox. Accessible Authentication is a reason to allow guest checkout and passkeys. Good accessibility work and good conversion work are mostly the same work.
It ranks ninth for conversion only because I found no neutral study that isolates its effect on checkout completion. On legal exposure it ranks much higher; see the rules section.
Saved Carts and Push Reminders
the return visit
Saving the cart across devices and sending a reminder is the feature with the most marketing and the least independent evidence. Every recovery rate I found for abandoned cart push or email came from a vendor selling the tool, so I don't quote any.
I'd still build saved carts, because a cart that vanishes when the app restarts is a bug, not a missing feature. Push reminders I'd treat as an experiment: send them to part of your abandoners, hold the rest out, and compare completed orders after two weeks. That gives you your own number, which beats anyone's benchmark.
Push permission is also a one-shot ask on iOS. Ask after the first order, when the shopper has a reason to want shipping updates, not on first launch.
The numbers I refuse
The refusal pattern is simple: if the number comes from the company selling the feature, or from a study that company paid for, and the method isn't published in enough detail to check, it doesn't go in as evidence. Here are the ones you'll meet most.
Shop Pay, "as much as 50% better conversion compared to guest checkout." Shopify's Shop Pay page also claims a 5% lower-funnel lift from the button's presence and at least 10% over other accelerated checkouts. The footnote says only that the figures are based on an external study with a large global management consulting firm in April 2023, with no sample or method shown (Shopify). "As much as" is also a ceiling, not an average.
PayPal, a 46% average increase in conversions. PayPal's footnote is more detailed, which I appreciate: a Nielsen panel study commissioned by PayPal, desktop purchases with small and medium merchants, April 2022 to March 2023, measured from the point the customer starts to pay (PayPal). It's commissioned, desktop only, and starts counting after the shopper has already chosen to pay, which leaves out everyone who dropped earlier.
"53% of mobile visits are abandoned after three seconds."This one traces to a 2016 study from DoubleClick, Google's ad business, on publisher sites. It's ten years old and wasn't measuring stores. I don't use it as a current benchmark.
"Reviews raise purchase likelihood by 270%."This circulates with a Spiegel Research Center attribution. I couldn't find it on a Spiegel page I could open, so I don't print it.
The rules that touch features
Four sets of rules shape how these features must be built in 2026: subscription cancellation, reviews, US accessibility and EU accessibility. I'm not a lawyer, and this is the status as published today, not legal advice.
| Rule | Status on September 30, 2026 | Feature it touches |
|---|---|---|
| FTC Click-to-Cancel (amended Negative Option Rule) | Vacated by the Eighth Circuit, July 8, 2025; new ANPRM March 2026, no rule text | Subscribe and save, memberships |
| ROSCA and FTC Act Section 5 | In force | Any negative option or subscription |
| California Automatic Renewal Law (AB 2863) | In force for contracts from July 1, 2025 | Online cancellation, consent records, reminders |
| FTC rule on consumer reviews and testimonials | Final, effective October 21, 2024 | Reviews, ratings, testimonials |
| ADA Title III (DOJ web guidance) | Applies; no detailed technical regulation for businesses | Every screen |
| WCAG 2.2 | Current W3C Recommendation (a standard, not a law) | Checkout, login, touch targets |
| European Accessibility Act | Applies to EU consumer e-commerce from June 28, 2025 per legal summaries | Every screen, for EU sales |
Click-to-Cancel is vacated, not paused. The US Court of Appeals for the Eighth Circuit vacated the FTC's amended Negative Option Rule on July 8, 2025 in Custom Communications v. FTC, days before its main requirements were due on July 14, finding the FTC skipped a required preliminary regulatory analysis (Latham & Watkins). The FTC announced an advance notice of proposed rulemaking on March 11, 2026, published March 13 with comments due April 13, and it contains no draft rule text (Covington; FTC). I found no proposed rule published since.
Vacated doesn't mean anything goes. ROSCA, Section 5 of the FTC Act and state auto-renewal laws still apply to any subscribe-and-save or membership feature.
California's law is the one to build to. AB 2863 applies to contracts entered, amended or extended on or after July 1, 2025. If a customer can sign up online, they must be able to cancel online through a prominent link or button. If you show a retention offer, a button labelled click to cancel must stay visible alongside it. You must keep proof of consent for three years or one year after the contract ends, whichever is longer, and send an annual reminder (AB 2863 text). For an app, that's a cancel button in account settings and a consent log in your database.
The reviews rule is final and live. The FTC's rule on consumer reviews and testimonials took effect October 21, 2024. It bans fake and AI-generated reviews, incentives conditioned on positive sentiment, undisclosed insider reviews, company-controlled "independent" review sites, suppressing reviews through threats, and buying fake social indicators, and it lets the FTC seek civil penalties for knowing violations (FTC; Federal Register). You can still ask for reviews and even reward them, as long as the reward doesn't depend on the review being positive.
The ADA applies to your store; the standard is guidance. The Department of Justice's March 2022 guidance says ADA requirements cover goods and services that public accommodations offer on the web, that it has no detailed technical regulation for businesses, and that WCAG is helpful guidance (ADA.gov). In practice WCAG 2.2 AA is the target most teams build to.
The European Accessibility Act covers EU sales. The Commission lists e-commerce among the services the Act covers (European Commission), and legal summaries state that obligations apply from June 28, 2025 to e-commerce offered to EU consumers wherever the seller is based, with EN 301 549 as the working technical reference (CMS). Size exemptions and national enforcement vary, so a US store shipping to the EU should check its position with counsel.
What we built
Four of our own projects show these features in real stores and apps, and I'll describe only what their case study pages say.
Players Choice CBD. We rebuilt Players Choice CBD on WordPress and WooCommerce. Two details map straight onto this list: the $50 free shipping threshold is stated at the top of the store rather than discovered at checkout (feature 1), and checkout carries the payment methods its customers use, including card, PayPal and cash on delivery (feature 5). The catalogue was also reorganised by product type so it's browsable rather than a flat list, which is feature 7 at small-catalogue scale.
Grillz. For the Grillz e-commerce build on Shopify Plus, the page describes a mobile-first design for a store where 70% of traffic came from phones, work on Core Web Vitals, a high-resolution zoomable gallery, a customer review system with photos, and Klarna and Afterpay alongside standard payments. That's features 4, 5 and 8 in one project. The case study page also reports a conversion increase; it doesn't state how that was measured, so I'm not using it as evidence here, by the same standard I apply to vendors.
LIVV Audio. LIVV Audio is a companion app rather than a store: native iOS and Android apps that control headphones over Bluetooth Low Energy, with preferences synced across devices through a NestJS backend and a React admin dashboard. It's here because it shows the other half of an e-commerce brand's app. Cross-device sync of a user's state is the same plumbing a saved cart (feature 10) needs.
Abat Jour. Abat Jour sells services, not boxes, but the conversion pattern carries over: dedicated pages for each service line, a repeated Start Your Project entry point, a stated 24 to 48 hour response time, and a separate trade application flow for professionals. Clarity about what happens next is the service-business version of showing total cost upfront.
If you run a store and want the vertical view, our e-commerce industry page collects this work in one place.
A worked example
A checkout project pays back fast only if your volume is real, so here's the arithmetic with every input labelled as an assumption. Consider a store with 4,000 monthly sessions that reach checkout, 40% of which complete, at an $80 average order.
| Step | Input | Result |
|---|---|---|
| Monthly sessions that reach checkout | Scenario assumption | 4,000 |
| Checkout completion today | Scenario assumption | 40%, so 1,600 orders |
| Average order value | Scenario assumption | $80 |
| Monthly checkout revenue | 1,600 x $80 | $128,000 |
| If completion rises 2 points to 42% | 4,000 x 42% | 1,680 orders, +80 |
| Added monthly revenue | 80 x $80 | $6,400 |
| Break-even on a $12,000 checkout project | $12,000 / $6,400 | about 1.9 months of revenue, before margin |
The 2-point improvement is a scenario, not a prediction. I picked it because it's small. Notice I didn't apply Baymard's 35.26% or Shop Pay's 50%. Either would make the payback look like days, and neither was measured on this store.
The $12,000 project is also a scenario: at our $150 to $225 hourly rate it buys roughly 53 to 80 hours of senior work ($12,000 / $225 is about 53; $12,000 / $150 is 80). That's enough for the top three features on most existing platforms, which are mostly configuration and design rather than new code.
So the question isn't whether 50% is achievable. It's whether you'd still do it at 2 points. At this volume, yes. At 400 checkout sessions a month, the same 2 points is 8 orders and $640, and the payback stretches to about 19 months of revenue. Know your volume before you buy the project. If you're on Shopify, most of this lives in Shopify development and theme settings; a custom native app needs a full e-commerce build.
What breaks first
Checkout changes break in predictable ways, and each has a signal you can watch and a way back.
- Removed a field fulfilment needed: watch for a rise in address-related support tickets or failed deliveries in the first two weeks. Roll back by restoring the field as optional.
- Autocomplete fills the wrong address: watch returns marked undeliverable. Keep manual entry one tap away and show the chosen address for confirmation.
- Wallet button fails on one device: watch payment errors split by browser and OS. Keep card entry visible as a fallback.
- Guest checkout breaks loyalty: watch repeat purchase attribution. Offer account creation on the confirmation page and link guest orders by email later.
- Speed work breaks tracking: watch for a sudden drop in recorded conversions without a drop in revenue. Compare against payment processor totals.
- A cancellation flow built to the old federal rule: watch nothing, because there's no signal until a complaint. Build to California's law and keep the consent log.
The last one is the risk worth bounding. Getting a subscription feature wrong costs a regulator's attention, not a few orders. Building the cancel button properly costs a day or two. That trade isn't close.
Red flags in a proposal
A proposal to add conversion features should show its evidence, and these are the signs it isn't going to.
- A lift percentage with no source, or with a source that is the vendor of the feature.
- A revenue forecast built by multiplying your revenue by that percentage.
- A new feature recommended before anyone has looked at your checkout's field count, total cost display or guest option.
- No plan to measure: no holdout group, no before and after window, no named metric.
- Review features that filter or gate negative reviews, which the FTC rule now prohibits.
- Subscription features that make cancelling harder than signing up.
- Accessibility described as an overlay or widget rather than as work on the screens themselves.
A good partner will tell you which of the ten you already have. That's the core of our conversion optimization work, and when the answer needs a new app capability rather than a setting, our Shopify app development team builds it. For a wider comparison of who builds these apps, see our e-commerce app developers guide.
What I could not verify
Several things in this article rest on sources I could only partly check, and you should know which.
- Baymard's abandonment reasons page did not show the survey sample size or year for the current figures. The 2022 guest checkout study (4,384 US adults, 24%) is a different wave from the 18% on the list page.
- Baymard's 35.26% improvement figure is its own modelled estimate across large sites. I could not check the model.
- The web.dev case studies are company-reported and published by Google. I could not see the underlying data.
- The Spiegel star-rating finding comes from a 2015 student project on vendor-supplied data and is not peer reviewed.
- The EU directive text did not load for me; the June 28, 2025 date comes from legal summaries and the Commission page, not from my own reading of Article 31.
- I found no neutral study measuring the conversion effect of push reminders, saved carts, address autocomplete or accessibility on its own.
- Grillz's reported conversion increase has no stated method on its case study page, so it is not evidence here.
None of these gaps change the order. They change how much weight each number can carry, which is why the ranking rests on the reasons survey and not on any lift claim.
Three things this week
- 1.Walk your own checkout on a phone as a new customer. Count the fields and note the first screen where the full total, shipping included, appears. If it's the payment step, that's feature 1.
- 2.Check whether guest checkout is a button, labelled 'Guest', and placed first. If not, that's a same-week fix.
- 3.Pull your Core Web Vitals from Search Console or PageSpeed Insights for the product page and cart. Anything outside 2.5 seconds LCP, 200 milliseconds INP or 0.1 CLS goes on the list.
Then look at the sibling guides for other verticals: the real estate app features article uses the same ranking method. Time to fix the door before building the coffee bar.
Want a Straight Read on Your Checkout?
Book a discovery call with Frenchy Digital, a senior-led Black-owned Los Angeles agency operating since 2016. Bring your funnel numbers. You get a fixed-price phased proposal, full code ownership and a 30-day post-launch warranty.
Want Your Checkout Read Against the Research?
Book a discovery call. Bring your checkout funnel numbers and we will tell you which of these ten features your store is missing, in the order that matters.
1517 S Bentley Ave Apt 204, Los Angeles CA 90025
Frequently Asked Questions
Sources & References
- 1Baymard Institute: cart abandonment rate statistics and reasons↗
- 2Baymard Institute: checkout flow average form fields (2024)↗
- 3Baymard Institute: make guest checkout prominent↗
- 4Baymard Institute: cart and checkout usability research↗
- 5Baymard Institute: e-commerce search usability research↗
- 6Nielsen Norman Group: UX guidelines for ecommerce product pages↗
- 7Spiegel Research Center: 4.5 stars are better than 5 (2015)↗
- 8web.dev: Web Vitals thresholds↗
- 9web.dev: business impact of Core Web Vitals (company-reported case studies)↗
- 10web.dev: Milliseconds make millions (Google commissioned)↗
- 11Latham & Watkins: Eighth Circuit vacates FTC Click-to-Cancel rule↗
- 12Covington: FTC launches new rulemaking on the Negative Option Rule (2026)↗
- 13FTC: Negative Option Rule page↗
- 14FTC: final rule banning fake reviews and testimonials↗
- 15Federal Register: Trade Regulation Rule on the Use of Consumer Reviews and Testimonials↗
- 16California Legislature: AB 2863 bill text↗
- 17W3C: Web Content Accessibility Guidelines (WCAG) 2.2↗
- 18US Department of Justice: guidance on web accessibility and the ADA↗
- 19European Commission: European Accessibility Act↗
- 20CMS: European Accessibility Act, what it means for your organisation↗
- 21Shopify: Shop Pay (vendor conversion claims, refused)↗
- 22PayPal: checkout (vendor-commissioned conversion claim, refused)↗

