A warm optical impression remains defined at one edge and fades into cyan depth.

Retail and E-commerce

Retail Personalisation That Customers Find Useful

Make recommendations helpful without crossing a customer's boundaries.

MT BYTES6 min read
Read the perspective

Start with a service customers would request

Picture a returning shopper who buys the same coffee every month. A reminder at the right interval could save them a search. Remembering their preferred grind could remove a repeated question. Both features have a service proposition that fits in a sentence.

Now imagine using their browsing history to infer how much they will pay, then changing the offer without an explanation. The data may come from the same relationship, but the bargain has changed. The retailer benefits from knowing more while the customer has a harder time understanding the transaction.

That distinction should lead a retail personalisation brief. Describe the inconvenience being removed, the information required and the customer's control over the result. “Increase engagement through richer profiles” leaves all three unanswered.

A smaller retailer has an advantage here: it can begin with a specific service rather than a comprehensive profile. A saved branch, a preferred product size or a reminder requested after purchase may be enough. Each has an identifiable owner and a result the shopper can recognise.

The strongest starting point is often a question customers already answer repeatedly. Ask whether remembering the answer would help them, whether it might change and whether sharing it could cause embarrassment. A shoe size is straightforward in some contexts. A purchase made as a gift can be misleading. A shared account makes even ordinary assumptions less reliable.

Customer control is part of the feature's quality.

Review recommendations, loyalty and pricing separately

Recommendations, loyalty benefits and individual pricing are frequently bundled under personalisation. They deserve separate commercial reviews.

A recommendation changes what someone sees. Its quality depends on relevance, availability and the room it leaves for exploration. A shopper who buys a saucepan may appreciate a compatible lid. Showing saucepans for months afterwards suggests the system recognises a transaction but misunderstands its meaning.

A loyalty benefit changes what an identified group can receive. The retailer should be able to explain who qualifies, when the benefit expires and how it interacts with other offers. A returning customer should not need a lengthy conversation at the till to establish that an advertised reward applies.

Individual pricing changes the amount offered to a particular person. That carries a different expectation of fairness. The US Federal Trade Commission's January 2025 update on surveillance pricing describes the use of direct and inferred consumer information in pricing. It gives retailers a reason to examine this category closely, rather than treating it as another recommendation setting.

Before introducing any of these features, ask a colleague to explain it as a customer would experience it. If a simple description sounds uncomfortable, additional configuration is unlikely to resolve the underlying concern. The commercial team needs to settle the proposition first. Technical feasibility answers whether the feature can operate; the business must still justify the exchange.

A remembered preference needs an expiry date

Retail data accumulates faster than understanding. Someone purchases baby clothes for a relative, orders a different size for a partner or shops at another branch while travelling. Treating each event as a lasting personal characteristic makes the profile increasingly confident and increasingly wrong.

Separate what customers state from what the system infers. A chosen communication preference carries a different meaning from a category viewed once. Keep that distinction available to the people designing offers and resolving complaints. Otherwise, a guess can quietly become an operational fact.

For an explicitly hypothetical example, consider a homeware retailer introducing replenishment reminders. A customer buys cleaning concentrate and opts into a reminder. The retailer could offer a changeable interval and a visible pause control. It does not need to infer the size of the household, connect purchases from other retailers or estimate income to deliver that service.

The record also needs a sensible life. A preference may remain until changed; an abandoned basket or temporary campaign audience may need much shorter treatment. Decide this by purpose rather than by how cheaply a supplier can store the information.

The FTC's Start with Security guide recommends limiting the information a business collects, retains and makes accessible. Applied to retail personalisation, that discipline keeps the project focused: every additional field should have a reason someone can explain and a responsibility someone accepts.

Let the customer repair the experience

An explanation helps only if the shopper can act on it. “Recommended because you bought this item” should lead naturally to a way to correct an irrelevant signal. A gift purchase should be removable from future recommendations. A changed preference should affect the experience quickly enough for the customer to notice.

Controls should be close to the feature they govern. A shopper hiding a recommendation should not have to navigate an account deletion process. Someone pausing promotional messages should still understand how they will receive order updates. These are different purposes and should remain distinguishable.

Consider the language as carefully as the control itself. A refusal framed as “No, I prefer to miss out” pressures the customer instead of clarifying a choice. A screen that makes acceptance prominent and withdrawal difficult creates similar friction. The FTC's report on dark patterns examines interfaces that obstruct informed consumer choices.

Staff need a corresponding view. If someone asks why they received an offer, a support agent should be able to identify the campaign and qualification rule without gaining unnecessary access to the customer's full history. If a profile is wrong, there should be a route to correct it across the systems using it.

Customer control is part of the feature's quality. A recommendation engine that can learn from purchases but cannot recover from a mistaken assumption is unfinished.

Test the benefit without hiding the cost

A higher click rate can conceal a weaker commercial result. Recommendations may draw attention while promoting unavailable stock. Loyalty discounts can increase orders that would have happened anyway. An offer may convert today and create a complaint tomorrow.

Choose a primary measure that matches the proposed service. For replenishment, it might be completed repeat orders within an appropriate interval. For size preferences, it could be the rate at which returning shoppers successfully choose an available product. The measure should connect to a customer task, not simply to interaction with the feature.

Then examine the cost around it. Track discount expense, product margin, returns and the staff effort required to resolve mistakes. Include customer reactions such as hidden recommendations, paused reminders and requests to correct data. These signals help explain why an apparently successful campaign may be wearing out its welcome.

Where the audience permits a fair comparison, retain a group receiving the ordinary experience. Keep the offer period and stock conditions comparable. Avoid drawing a broad conclusion from a seasonal rush or a small number of high-value orders.

Make the stopping conditions explicit. A rise in incorrect offers or a failure to honour customer controls should trigger investigation even when revenue looks encouraging. The retailer needs enough independence from its campaign targets to withdraw a feature that has stopped serving its stated purpose.

Begin with a promise the shop can keep

Before buying another personalisation product, select one customer promise and trace it through the business. Who provides the information? Which system stores it? What changes on the website or at the till? Who corrects an error? What happens when the shopper opts out?

This exercise often exposes work that belongs in the retail operation first. Branch availability may be unreliable. Loyalty terms may differ between channels. A preference captured online may never reach the staff member expected to honour it. More sophisticated targeting would amplify those weaknesses.

Give the first release a deliberately clear boundary. One preference, one service and one accountable team make it easier to observe whether the exchange works. Expand when the retailer can explain both the customer benefit and the operational burden.

The ambition should be a shopping experience that remembers well and forgets appropriately. Customers do not owe a retailer a richer profile. Each request for information needs to earn its place through what the business does with it.

MT
MT BYTES

Perspectives on technology and business.

Explore perspectives

Define a personalisation project customers can understand

MT BYTES can help connect retail experience design, customer data and campaign delivery around a clear service proposition. Bring the feature you are considering and the systems expected to support it.

Discuss your project