The Basket That Almost Made It: Reading Free-Delivery Thresholds as a Traffic Signal

Every UK shop has a number. Sometimes it is £50, sometimes £75, occasionally it is whatever the courier pricing spreadsheet said on a rainy Tuesday. Free delivery over that amount. Most teams treat it as a checkout nudge: a banner, a progress bar, a polite reminder that another £6.40 would unlock the good bit.

That is fine as far as it goes. But the threshold is doing more than nudging baskets. It is sorting your traffic into groups. Some visitors are nowhere near it. Some are miles past it. And a useful chunk are sitting just underneath it, close enough to touch. That last group is a traffic segment worth measuring, because it tells you which channels are sending people who are nearly ready to buy rather than people who are merely curious.

The threshold is a behavioural marker

A visitor who adds £43 of stock to a basket on a shop with a £50 free-delivery line is not the same as a visitor who reads one blog post and leaves. They have crossed a small but meaningful bridge. They have chosen something. They have shown a delivery preference, even if they have not typed an email address yet.

That makes the near-threshold basket a useful signal for acquisition. It is not a guarantee of conversion. It is not a replacement for proper attribution. But it is a cleaner read on intent than a click, a scroll or a three-second visit from a paid social ad.

If you can spot the channels sending near-threshold sessions, you can ask better questions. Is paid search bringing in people who fill a basket and then stall? Is organic landing on category pages that get people close but not over the line? Is email bringing back people who already had £47 in the basket last week? Those are traffic questions, not just merchandising questions.

Build a simple near-threshold segment

You do not need a data warehouse for this. Start with a band. If your threshold is £50, define near-threshold as roughly £35 to £49.99. The exact range depends on your average order value and how much friction delivery adds. The point is to create a group that is close enough to be useful and wide enough to produce a decent sample.

In your analytics setup, track add-to-cart and cart-value events where consent allows. Then build a segment for sessions that hit that band at least once. Keep it aggregate. You are looking for patterns in channel, landing page and device, not trying to peer into individual shopping habits.

A simple monthly view works well: near-threshold sessions by channel, conversion rate for that group, and revenue per session. Compare it with sessions that never get near the threshold. The gap is the story. If paid social sends a lot of near-threshold traffic but converts it badly, that is different from organic search sending fewer near-threshold visitors who convert well.

Which channels send the almost-customers?

This is where the threshold earns its keep. Pull channel-level data for the near-threshold segment and look for two things: volume and quality. Volume tells you where the almost-baskets come from. Quality tells you whether they turn into orders.

A few patterns tend to show up. Paid search often sends high-intent near-threshold traffic because the query was specific. Paid social can send plenty of near-threshold sessions that stall at delivery cost because the ad promised a deal and the basket did not quite match it. Organic category pages can produce a steady stream of visitors who get close and then vanish, which usually points to a mismatch between the landing page and the next step.

None of those patterns are universal. That is why you measure them in your own shop rather than borrowing someone else's dashboard. Use consistent UTMs, keep campaign naming tidy, and review the segment monthly. A weekly check is fine for peak periods, but monthly is enough to spot a channel that is sending the wrong kind of almost-customer.

Adjust the page, not just the banner

Once you know which pages produce near-threshold sessions, you can make small changes that help rather than nag. A product page that says you are £7 away from free delivery is useful. A product page that pushes random add-ons to close the gap is not. The difference is relevance.

Try showing a short delivery-progress note near the basket, then recommend one or two products that genuinely fit the basket. Keep the wording plain. UK shoppers are used to delivery thresholds, and they can spot a guilt-trip from a mile off. The goal is to make the next step obvious, not to make the customer feel like they are failing a test.

Landing pages deserve the same treatment. If a paid campaign sends people to a page that talks about free delivery but does not show the threshold clearly, the near-threshold segment will grow and the conversion rate will sag. Fix the page before you blame the channel.

Paid campaigns: aim for intent, not just clicks

Near-threshold data can sharpen paid campaigns without turning them into a surveillance project. If you see that a particular search theme sends visitors who regularly land in the near-threshold band, make sure the ad copy and landing page line up with that behaviour. If another theme sends visitors who bounce before adding anything, stop paying for the privilege.

For remarketing, keep it consent-safe and simple. A near-threshold segment can inform a campaign that shows the delivery threshold and a relevant product category, rather than a generic discount. You are not trying to chase every click. You are trying to reach people who have already shown a reason to come back.

Email nudges with a soft touch

Email is often the best place to use near-threshold traffic, because the visitor has already given you a way to reach them. A browse-abandon or basket-abandon email can mention the threshold once, show one useful product, and leave it there. No countdown timer. No fake urgency. Just a clear reminder that delivery is free over £50 and here is something that fits.

Measure the traffic that comes back, not only the revenue. Did the email bring a near-threshold visitor back to the site? Did they convert? Did they need a second visit? Those answers help you decide whether the nudge is doing real work or just filling an inbox.

Measure the traffic, not just the average order value

The free-delivery threshold has always been an AOV lever. That is the obvious job. The less obvious job is as a traffic segment that tells you where intent is clustering. Once you can see near-threshold sessions by channel and landing page, you can adjust acquisition spend with a bit more confidence and a lot less guesswork.

Start with one band, one monthly report and one channel. If the near-threshold group is large and converts well, you have found a signal worth protecting. If it is large and stalls, you have found a page or a promise that needs fixing. Either way, the £50 line is doing more than building baskets. It is showing you where the almost-customers are.