Why Shoppers Abandon Checkout: The Missing Information

A product has been added to the basket, the shopper has moved on to checkout, and the order has not been completed. The first reflex of most businesses looking at this picture is to set up a discount scheme or switch on a reminder email. Both sometimes work, but both are answers given without asking why the shopper walked away.

The checkout step is where shoppers are still asking questions while they decide. How much will delivery cost, when will it reach me, can I send it back if I do not like it, is it safe to enter my card here. If the answers to these questions are not on the screen, the shopper goes looking for them and often does not come back. A large share of abandonment is not a price objection but an information gap.

The text below looks at abandonment from that angle: which information needs to appear at which step, at which points in the checkout flow unnecessary friction is created, and how to measure where in the funnel the loss happens. We give no percentages; these figures vary so much between sectors and basket types that a rate borrowed from outside does not produce a target for your own store.

Abandonment is often an information problem, not a price problem

The person who reaches checkout is already persuaded. They have found the product, liked it, put it in the basket and set out to complete the purchase. If they are lost at this point, the cause is no longer the product or its price; it is uncertainty about the process.

That uncertainty takes two typical forms. The first is the surprise: a cost that was not visible in the basket appearing at the last step. The second is the gap: no information at all about delivery time, return conditions or payment security. A surprise damages trust, a gap makes people postpone the decision; and a postponed decision often never returns.

This distinction has a practical consequence: the fix is not a discount but making the information visible at the right moment. Because a discount does not close an information gap, it means paying for the same gap again every time.

Six questions the shopper wants answered at checkout

The fastest way to assess a checkout screen is to check whether the answers to these six questions are visible on it. Every answer the shopper has to hunt for is an item of friction.

1. What will I pay in total? Product price, delivery and any other items in a single total.
2. When will it reach me? An estimated delivery window; a range, even if not an exact day.
3. What happens if I do not like it? The return period, who pays for return shipping, when the money is refunded.
4. Who is selling? The business name, contact details, a channel that can actually be reached.
5. Is my card safe? Where the payment is taken, how the security step works.
6. Who do I contact if something goes wrong? The post-purchase support channel and its working hours.

It is not enough for these six answers to exist at checkout; they have to be readable. A return policy link buried in the footer technically exists, but at the moment of decision it does not.

Delivery cost: in the basket, on the product page, at which moment

Where the delivery cost appears is one of the most decisive design choices in the checkout flow. The rule is simple: the later the cost appears, the more it feels like a surprise.

It is healthiest for it to be a piece of information on the product page. If the cost varies with order value and delivery region, giving an exact figure may not be possible; in that case, write down the rule itself. A sentence such as "free above a certain amount" or "different for within the city and outside the city" is better than writing nothing.

At the basket step the cost should appear already calculated. If it cannot be calculated before the address is entered, then the address step is moved forward or an estimate is shown. A delivery cost that appears for the first time on the final checkout screen undoes every expectation built up to that point.

If a free delivery threshold is used, how far the basket is from the threshold should be visible in the basket. That is both a piece of information and the only data the shopper needs to make their own decision.

Why delivery time and return conditions belong on the product page

Traditionally these two pieces of information sit on separate pages and are brushed past at checkout with a link. Yet both are part of the purchase decision, and that decision is made on the product page.

Delivery time. If the answer to "it's a gift, will it arrive by Saturday" is not on the product page, the shopper either sends a message to ask or buys from somewhere else that guarantees it will arrive. You do not have to give an exact date; stating the dispatch time and the transit time separately is enough in most cases.

Return conditions. The return period, who pays for return shipping and which products cannot be returned can be summarised in a box on the product page. There is a second benefit: when this information is written out plainly, it becomes readable both by customers and by the automated systems that collect information about products. How information on a product page is read by machines is covered in detail in our article on product pages and AI visibility.

A third piece of information belongs in the same place: stock status and, if the item has sold out, when it will be back. Uncertainty produces the same result here too.

Guest checkout: the cost of forced registration

Forced registration is the most expensive friction that can be put into a checkout flow, and it is usually introduced for a good reason: collecting customer data, making repeat purchases easier, linking order tracking.

All of these reasons can also be met with guest checkout. Name, address, phone and email are collected during the order anyway; registration only adds a password to them. Asking "would you like to create an account with these details" after the order is complete is the way to collect the same data without risking abandonment.

The cases where forced registration can be defended are narrow: corporate and dealer sales, products that require age or authorisation checks, subscription-based sales. In standard retail, the requirement is usually there for the business's internal convenience, and the shopper pays the price.

Collecting and storing personal data is a separate area of responsibility; when assessing which data is actually necessary and how it is used, the framework in our article on customer data analysis and metrics can help.

Number of form fields and mobile keyboard behaviour

Every field in the checkout form lowers the chance of completion a little more. So one question should be asked of every field in the form: can the order be shipped without this information?

Commonly seen unnecessary fields: a second phone number, date of birth, gender, company name (in consumer sales), "how did you hear about us". None of these is needed to ship the order, and all of them can be moved to a post-purchase survey.

On mobile there is an extra layer. When the field type is not defined correctly, a letter keyboard opens for the phone number, automatic capitalisation kicks in for the email address, and the shopper fights a small battle in every field. Autofill fails for the same reason. Each of these is a small problem on its own; stacked on top of each other at checkout, they become a reason to leave.

The third point is error messages. A warning that says "invalid entry" forces the shopper to guess, because it does not say which field is wrong or where. The error message should sit next to the field, in plain language, and say how to fix the problem. The form should also not be cleared after an error: wiping the fields that were entered correctly turns a single typo into a form that has to be filled in from scratch.

The fourth point is the address field. The delivery address is the longest and most error-prone part of the checkout form. Having the province and district filled in automatically from the postcode, offering a choice of saved addresses and treating the billing address as the same as the delivery address by default noticeably reduce the load in this section.

Payment methods and instalment display: choice or clutter

Increasing the number of payment methods intuitively looks good; each method serves a group of customers. But when the options are arranged haphazardly on the screen, the decision load goes up.

Two simple rules help. First, the most frequently used method sits at the top; putting the method most of your customers use further down adds an extra step for the majority. Second, write briefly what each method means: when the order will be processed if bank transfer is chosen, whether cash on delivery carries an extra charge.

The instalment table is a separate topic (in Turkey, shoppers routinely split card purchases into instalments at checkout). Because instalment options vary by card and bank, the table quickly gets crowded. The useful view is a table narrowed down to the shopper's own card; showing every option from every bank at once produces noise, not information.

A warning: the scope of virtual POS and instalment options is decided not by the platform but by the bank and the payment institution. The platform only tells you which providers it has ready-made connections with; the party that sets the number of instalments and the commission structure is the provider itself.

Where in the funnel you are losing people: setting up step-by-step measurement

Instead of guessing why people abandon, it is possible to measure it, and the setup needed for that is simpler than it seems. Every step of the checkout flow is recorded as a separate event.

The steps to measure are at least these: viewing the basket, moving to checkout, completing delivery details, choosing a payment method, attempting payment, completing the order. There is also a seventh item: the failed payment attempt. This last item is not measured at all in most setups, and some of the orders taken for abandonment actually got stuck here.

Once the setup is in place, what to look at is not the absolute numbers but where the drop between steps is concentrated. A drop concentrated at the delivery details step points to delivery cost or the address form; a drop concentrated at the payment step points to the payment method or the security step.

The device breakdown should also be read separately. The same flow can run smoothly on desktop and be blocked on mobile, and in the totals this is invisible. Reading by traffic source is also useful: a shopper arriving from an ad and one arriving from a search result do not have to behave the same way at checkout.

How return reasons reveal what the product page is missing

Return records measure something that checkout cannot: what the shopper misunderstood on the page. That is why the return reason field should not be free text but a choice from a short list.

The reasons usually fall into three clusters. Did not match expectations (colour, size, material) — this shows that the images and attribute information on the product page are incomplete. Arrived late — the gap between the stated delivery time and reality. Faulty or missing item — this is an operations issue, not a page issue.

The first two clusters feed straight back into the product page: a size chart is added, the images are varied, the material information is clarified, the delivery time is brought closer to reality. Once this loop is in place, the return rate stops being a cost item and becomes content feedback.

The same feedback is found in customer reviews; what reviews mean for both shoppers and automated systems is covered in our article on Google reviews and AI recommendations.

You can find how the checkout flow and product page information are set up during the build in the scope section of our setup service page, and the sector visibility side on our ecommerce sector page. If you would like us to look at your checkout screen together, you can reach us through our contact page.

Frequently Asked Questions

What should our cart abandonment rate be?

There is no target figure to borrow from outside, and aiming for one is misleading. This rate varies across a very wide range depending on sector, basket value, traffic source and how long shoppers take to decide; for expensive, considered purchases it is naturally high. The meaningful measure is your own measurement: calculate your current rate, treat it as a starting point and look at how the same step changes after each individual change. The only correct benchmark to compare against is your own figure from last month.

Should delivery be free, or is showing the cost enough?

Free delivery is a marketing decision, and its cost is covered from somewhere; it is not right for every business. What decides abandonment is not whether the cost is free but when it is seen. If the delivery cost appears as a rule on the product page and as a calculated figure in the basket, the shopper decides knowingly. If the same cost only appears on the final screen, it is perceived as a surprise. If you use a threshold, showing in the basket how far the shopper is from it both informs them and leaves the decision to them.

Does opening guest checkout lead to data loss?

It does not, because name, address, phone and email are collected for the order anyway; the only thing registration adds is a password. The right order is to let the shopper complete the order and then offer to create an account with the same details. That way no order is lost, and the registration rate reflects a real choice. Corporate sales, products that require authorisation checks and subscription sales fall outside this rule; there, registration is part of the business itself.

Which is better, one-page checkout or multi-step?

Both can work; what decides it is not the number of pages but how much information is asked for at each step and whether the total is visible. The advantage of a multi-step flow is that each screen holds few fields and is less tiring on mobile; its condition is that progress is visible and entered information is not lost when going back. The advantage of a one-page flow is that everything is visible together; its condition is that the screen does not turn into a long wall of form fields. Whichever you choose, the order total should stay visible at every step of the flow.

Is it legal to send an email to an abandoned basket?

Sending commercial electronic messages depends on the recipient's prior consent, and that consent must be obtained separately; an email address typed into the order form is not on its own a substitute for consent. In practice, the right setup is to present the consent box separately and unticked, to state clearly what the consent is for, and to leave an easy way to opt out in every message. Without consent, what can be sent is not a marketing message but only transactional information about the order itself. If there is any hesitation about how to draw this line, it is sensible for the business to have its own adviser check the wording legally.