A Research Summary on Where Lifestyle Brand Checkouts Lose People Mid-Flow

Around 70% of mobile checkout journeys end without a purchase, according to Baymard Institute. That figure has been quoted so often it has almost lost its power to shock. But the more interesting question is where people go and why the flow lost them at that precise moment rather than three screens earlier or three screens later. The pattern, once you start looking at it carefully, is not random.

The drop-off concentrates at recognisable points, always where the flow asks something before confidence has formed.

Drop-off concentrates at recognisable points. It clusters around fee disclosures, progress ambiguity, account creation walls, and data-entry tasks that fall entirely on one person. These are not random friction points. They share a common structure: the flow is asking something of the user at the exact moment the user has least confidence in what comes next.

This article pulls together what we have observed across travel, health and wellbeing, and marketplace products, alongside published research on checkout behaviour. The aim is to give you a clearer picture of where lifestyle brand checkouts typically lose people, and why the standard fixes often miss the actual problem. Shorter forms and fewer steps help, but they do not address the underlying cause when that cause is a mismatch between what the flow demands and what the user is ready to give.

Why Complex Checkouts Fail Differently to Simple Ones

A three-field checkout can fail in ways a fifteen-field checkout cannot, and the reverse is also true. Simple flows fail when they strip out information users actually need to feel confident. Complex flows fail when they present the full weight of a process all at once, without helping users understand how long it will take, how it is structured, or whether they are making meaningful progress.

The failure mode for complex checkouts is almost always one of the same three things: users cannot see the shape of the process, they hit an unexpected demand for information mid-flow, or they lose the thread of where they are and what still remains. All three cause abandonment, and all three are structural rather than cosmetic. Redesigning the button colour does not fix them.

On an OTA travel product we worked on, the checkout covered accommodation, flights, transfers, extras, and integration with multiple third-party providers. It was, by any measure, a genuinely complex booking flow. Users were dropping off mid-way through entering information, not at the beginning and not at the payment screen. They were leaving in the middle, which told us the problem was not the total length of the process but the experience of being inside it without knowing how much remained.

Complex checkouts need a different design approach to simple ones, because the user's cognitive task is different. They are filling in fields while simultaneously managing a mental model of a multi-part process. Anything that disrupts that model, or that fails to provide it in the first place, will produce abandonment.

The Drop-Off Points That Appear Most Consistently

Across checkout flows, certain moments produce abandonment at a higher rate than the steps around them. Forced account creation is one of the most documented. Baymard Institute links a 19% abandonment rate specifically to this step, which is a significant share of people who were ready to buy until the flow asked them to register before they could proceed.

Fee disclosure points are another consistent location. The moment a total updates to include a service charge, a booking fee, or a delivery cost that was not visible earlier, a portion of users stop. The fee amount matters less than the surprise of it. Users who were not expecting a change to the total experience something close to a betrayal of the implied contract they thought they were in.

Data-entry screens that ask for multiple types of information at once, particularly personal details combined with payment information on the same screen, also produce measurable hesitation. The cognitive load is part of it, but so is the emotional register of the moment. Entering a card number is a different kind of act to entering a delivery address, and screens that treat both as equivalent data-collection tasks do not match how users experience them.

Map your checkout against the three consistent drop-off points: account creation walls, unexpected fee disclosures, and screens that mix personal and payment data. Test each one in isolation before assuming the overall flow length is the problem.

Progress indicators that stop at the screen level, showing "step 2 of 6" without any indication of what each step contains or how long it takes, produce their own form of abandonment. Users make an implicit calculation about whether the remaining effort is worth it, and if they have no information on which to base that calculation, many of them decide it is not.

What Happens When Users Cannot See the Shape of a Process

Uncertainty about what remains in a process is a reliable driver of abandonment, and it compounds over time inside a flow. At the start of a checkout, users are willing to commit effort because the destination feels close. As they progress and encounter more screens, more fields, more decisions, the original mental estimate of the task becomes less reliable. If the flow gives them nothing to recalibrate against, anxiety builds.

On a health and wellbeing product we worked on, we tested two versions of a multi-step flow. One primed users at the start with a clear indication of how long the process would take. The other showed only a progress bar during the flow itself, with no upfront time expectation. Without priming, drop-off rates ran at around 80 to 85%, typically occurring within the first three or four questions. After introducing upfront priming, telling users what to expect before they began, completion rates rose to approximately 95%.

Telling users what to expect before they begin proved more powerful than any in-flow progress indicator alone.

The OTA travel product required a different approach because the flow was longer and more variable. We redesigned the progress indicator to be interactive, allowing users to jump between sections, see an estimated time per section, and view an overall time estimate for the full booking. This covered everything from traveller details and passport numbers through to room sharing, ticket distribution, and payment. Giving users that navigable view of the whole process reduced mid-flow abandonment measurably.

What both of these show is that users are managing their own willingness to continue as they complete tasks. A flow that gives them accurate information about what remains keeps that willingness intact. A flow that withholds it forces users to make assumptions, and the assumptions they make are usually more discouraging than the reality.

Before users enter your flow, tell them how many steps it contains, roughly how long it takes, and what information they will need to have ready. This single intervention does more work than most in-flow redesigns.

How Fee Ambiguity Kills Transactions That Price Alone Would Not

The fee that causes drop-off is rarely the fee that looks largest on screen. On a marketplace checkout project we worked on, we observed hesitation and drop-off caused by confusion around platform fees, specifically whether a fee was added on top of the stated price or already included within it. The amounts involved were small. The confusion itself was what stopped people, not the cost.

On a travel booking product, we initially decided to wrap the platform's Stripe booking fee into the total price. The reasoning was clean: travellers want to see one total, so show them one total. What we found was that users expected to see a platform fee as a separate line item, because that matches their mental model of how apps and platforms work. By not showing the fee, even though it was already covered within the price, we created a fear that a hidden fee would appear later. Users assumed the single total was not the real total.

When we switched to breaking out all fees transparently, showing users exactly what each component of the price was, confidence increased even though the screen now contained more information. Showing more gave users more trust rather than less. The principle here is that users carry strong expectations about how certain types of platforms present pricing, and designing against those expectations, even with good intentions, produces distrust. Baymard Institute reports that 14% of US online shoppers have abandoned orders because they could not see the total cost upfront before initiating checkout, which points to the same pattern: ambiguity about what the final number will be is enough to end a transaction.

When the Data-Entry Burden Falls on One Person

Group bookings create a specific version of the data-entry problem. The person making the booking is responsible for entering accurate details on behalf of everyone in the group. For a party of six travelling together, that means passport numbers, dates of birth, dietary requirements, and contact details for five other people, all entered by one individual who may not have that information immediately to hand.

On the group travel OTA product we worked on, we redesigned the checkout to distribute the data-entry burden across all travellers rather than placing it entirely on the person making the booking. For steps such as personal details and passport numbers for each traveller, we built the ability to invite individual travellers to fill in their own information directly, with the booking updating as each person completed their part. The lead booker only needed to complete the minimum required to reserve the booking, while the others contributed their own details in parallel.

This worked particularly well because the product was aimed at friendship groups and colleague trips. It is worth noting that this model is context-dependent: for a family booking where a parent is entering children's details, distributing entry to each traveller makes less sense. The principle is that collaborative data entry works as an opt-in option, available where it suits the group's structure, rather than a replacement for the ability to enter everything manually.

The average ecommerce checkout carries 19.9 form elements, according to Baymard Institute, while an optimised flow can be as short as 12. For group bookings, that gap between observed and achievable widens considerably when the burden is concentrated on one person entering data for many.

Asking for High-Trust Actions Before Trust Has Been Earned

On a map-based fitness social network we worked on, designed to connect people for runs and cycle rides, users were dropping off at the point where the flow asked them to share their precise location with a potential match. The location-sharing request came before users had any opportunity to converse with or learn about the other person. The product was asking for a high-trust disclosure before the conditions for that trust existed.

We redesigned the flow to sequence trust-building interactions first. Users could view profiles, exchange messages through the platform's built-in messaging, and then, once they felt confident enough, choose to share their location to arrange a meeting. The drop-off at the location step fell sharply, because by that point users had already decided they were comfortable with the other person.

This pattern appears across checkout flows in a different register. Asking for payment information before users have seen delivery terms, asking for account creation before users have seen what the account provides, asking for marketing opt-ins before users have completed their purchase: all of these place a high-trust demand ahead of the foundation that would make it feel reasonable.

Audit your checkout for moments where you are asking something of the user before they have the information needed to feel comfortable giving it. Reordering those moments costs nothing in development terms and often produces the largest gains in completion rates.

The sequencing of requests matters as much as the requests themselves. A demand that feels reasonable at the end of a relationship feels invasive at the beginning of one, even if the words on screen are identical.

The Signals in Your Analytics That Predict Drop-Off Before It Happens

Standard funnel analytics show you where users left. They do not show you why, and they do not show you the screens where departure is building before it happens. To get that picture, you need more granular data than a typical team is set up to capture.

The behavioural signals that predict drop-off are consistent across flow types. Time on screen is one: a screen that typically takes thirty seconds to complete but is averaging two minutes is a screen where something is wrong, either the cognitive load is too high, the user cannot find what they need, or they are hesitating over a request they are not yet ready to fulfil. The screen time figure alone tells you to look; it does not tell you why.

Repeated entry and exit on the same screen is another signal. A user who enters a screen, returns to the previous screen, and then re-enters the same screen is uncertain about something. Tracking this pattern at scale shows you which screens produce the most decision-hesitation, independent of whether users ultimately complete or abandon.

• Time on screen, compared against median completion time for that step
• Repeated entry and exit from the same screen within a single session
• Scroll behaviour, particularly repeated up-and-down scrolling through terms, fee disclosures, or dense information screens
• Field focus patterns, where users click into a field and then click away without entering anything

Repeated scrolling through a dense screen, particularly through terms and conditions or fee disclosures, signals either a lack of comprehension or a lack of trust in what is being presented. Both require a different fix, but both become visible when you are tracking scroll behaviour rather than only page-level exit rates.

Structural Patterns That Predict Abandonment Across Flow Types

Across travel, health, marketplace, and fitness products, certain structural features appear in flows with high abandonment rates at a higher frequency than in flows with low abandonment rates. They are not guarantees of failure, but their presence is a reliable signal that the flow has a problem worth investigating.

The first is information presented before users have a reason to need it. A screen that asks for passport expiry dates on the first screen of a booking flow is an example: that information is required eventually, but presenting it before users have confirmed the core booking details loads them with a task they are not yet oriented towards.

The second is the absence of any indication of what comes next. A progress indicator that shows "step 3" without naming what step 3 contains leaves users with no ability to anticipate the flow ahead. Users who cannot anticipate tend to assume the worst.

The third is a mismatch between the visual register of the flow and the emotional register of the action being performed. A payment screen that looks identical to a preferences screen does not signal to the user that this moment is different, and that absence of signal can actually work against completion: some users need the heightened attention that a clearly distinguished payment step creates.

The fourth is asking for account creation before showing the user the value of having one. Flows that gate purchase behind registration, without explaining what registration provides, produce abandonment at rates that registration flows with clear value statements do not.

What These Patterns Mean for How You Design and Sequence Complex Flows

The patterns above point to a consistent principle: drop-off is primarily a sequencing and expectation problem. Users who know what to expect, who understand the shape of the process, who see fees presented in the way they expect them to be presented, and who are asked for high-trust information only after lower-stakes trust has been established, complete at higher rates regardless of how many screens or fields the flow contains.

Sequence information by when users need it

Every field in a checkout flow should be necessary at the point it appears. If a piece of information is needed eventually but not yet, moving it later in the sequence reduces cognitive load at the current step without removing it from the flow entirely. This is a straightforward exercise: take each screen, list every field, and ask whether the user genuinely needs to supply this information right now or whether it belongs later.

Match the display to user expectations

Users arrive at your checkout with a mental model of how this type of purchase should work. Travel bookings, wellness subscriptions, fashion orders, and marketplace transactions each carry different expectations about pricing display, account requirements, and data sharing. A checkout that designs against those expectations, even with good intentions, produces distrust. The question is whether your flow is clear in the way that users of this product category expect clarity to look.

Testing checkout flows in a usability session produces different results to what live analytics reveal, because participants in a session are assessing functionally rather than committing financially in a real emotional moment of a transaction. Live analytics show you what happens when users are genuinely about to part with money, and that is the data that tells you where the flow is actually losing people.

Conclusion

The common thread across every drop-off pattern described here is that users abandon when the flow asks more of them than they are currently ready to give. That readiness is shaped by what they know about what remains, what they understand about the costs involved, what trust they have built with the product, and how much of the process they have had to carry alone.

Fixing checkout abandonment by shortening forms or adding a progress bar addresses the surface. The structural work is in sequencing: ordering the flow so that each demand on the user arrives after the conditions that make it feel reasonable have been met. Fees disclosed early and clearly. Progress communicated before the flow begins, not only during it. High-trust requests placed after lower-trust interactions have established confidence. Data-entry distributed where the context allows it.

These are often straightforward changes in technical terms, but they require changes in thinking: about what the user knows at each point in the flow, what they are being asked to do, and whether the flow has earned the right to ask it. Getting that sequencing right is the consistent difference between the flows that complete and the ones that do not.

If your checkout is losing people at a predictable point and you want to understand what is driving it, let's talk about your checkout flow.

Frequently Asked Questions