Make free-gift thresholds clear before checkout

A free gift can become surprisingly difficult to explain once discounts, delivery charges and several spending thresholds enter the picture. I want the customer to understand the offer from the basket they can see, without doing arithmetic against hidden rules.

The first job is to define the rule precisely. “Spend £100 for a gift” leaves open whether delivery counts, whether a discount reduces eligible spend and whether every product qualifies. The interface cannot explain a rule the business has not settled.

Write a worked example before the banner

I use fictional baskets to make the intended behaviour concrete. Suppose eligible products total £95 and delivery costs £8. Does that qualify for a £100 threshold? If the answer is no, the promotion should explain that delivery is excluded rather than celebrating a £103 order total.

Then apply a £10 discount to a £105 basket. Whether eligibility remains depends on the actual promotion rules. I record the intended answer and make the message follow it. These examples are specifications for checking the offer, not claims about any particular shop’s implementation.

The same exercise should cover excluded products and multiple currencies where those apply. It is better to discover an ambiguous rule while writing examples than when somebody has already completed an order expecting a gift.

Keep progress messages honest

“Add £5 more to qualify” should describe the additional eligible spend, not merely the difference from a convenient total. I check that the amount updates after quantity changes, discounts and item removal. A message that describes the previous basket can be more confusing than having no progress message.

Once the threshold is reached, explain whether the gift has been added automatically or needs choosing. Those are different actions. If a selection is required, the control should be easy to find and should say how many gifts the customer may select.

I avoid turning the basket into a stream of pressure messages. A concise explanation of an optional benefit is enough. The main task remains reviewing the purchase and deciding whether to continue.

Decide what happens when eligibility changes

Remove an item after selecting a gift. The result should match the promotion’s rules and be explained before the order is placed. Quietly charging the usual price for something introduced as free would create an unpleasant surprise; any paid alternative needs an explicit customer decision.

Stock availability also matters. If the advertised gift is unavailable, the shop needs a clear response: an approved replacement, another selection or an honest explanation that the offer cannot currently be fulfilled. A stale banner should not keep promising a choice that no longer exists.

I check the basket, checkout, order confirmation and customer email for consistency. The gift and its price should remain understandable throughout, rather than appearing as an unexplained adjustment on the final record.

Build a compact acceptance table

Use one row for each meaningful condition: below the threshold, exactly at it, above it, discounted below it, an excluded item, a removed qualifying item and an unavailable gift. Record the expected message and expected basket contents beside each row.

Run those checks in a test environment before launching the promotion and again after any material rule change. The useful outcome is not merely a banner that appears at the right time. It is an offer customers can understand, qualify for and receive without contradictory messages along the way.

A sample threshold check you can adapt

This fictional offer requires £100 of eligible products after discounts, excludes delivery and adds one available gift automatically. Your own rules may differ; write them above your test table.