Tools and providers
Part of What to look for in a customer data platform for UK retail
What to look for in a customer data platform for UK retail
A UK retail buyer's guide to customer data platform selection: loyalty, ecommerce and till data, identity match rates and the evidence to request.
What to take away
- Judge a retail customer data platform on the sources you actually hold: loyalty cards, ecommerce orders, in-store tills and returns, not on a US feature list.
- Match rates vary by channel because guest checkout and store returns arrive without an identifier, so request a measured rate on your own sample.
- UK rules on lawful basis, consent and retention decide what may be done with basket-level data, whatever a demo suggests.
- Ask for a written source-to-field map, a deletion route and a named owner before you sign anything.
- Treat store hierarchy and product catalogue as first-order data, not as a nice-to-have for reporting later.
Why UK retail data differs from the US template
Most US retail technology assumes one national ecommerce stack, an email address as the main identifier and a single currency of measurement. UK groups rarely look like that. A typical retailer runs a loyalty scheme, two ecommerce platforms kept after acquisitions and a store estate that still processes returns at the till.
UK vs US retail data
US template
- Ecommerce stack
- one national
- Main identifier
- email address
- Measurement
- single currency
- Returns
- online process
- Checkout
- account required
UK reality
- Ecommerce stack
- two after acquisitions
- Main identifier
- loyalty card or guest
- Measurement
- store and online split
- Returns
- at the till
- Checkout
- guest checkout common
Guest checkout is common, and many transactions never touch a loyalty card. Any claim about a single customer view has to survive that gap. Our guide to how to handle identity resolution in UK CDPs covers the matching decisions that follow.
The Data Protection Act 2018 governs how personal data is processed in the UK, including the joining of a till receipt to an online account. That statute, not the supplier's data-processing annex, sets the outer limit.
Electronic marketing, cookies and text or email permissions are governed by the Privacy and Electronic Communications Regulations (PECR), which sits alongside UK GDPR. A retail customer data platform has to respect PECR when it activates campaigns, sets non-essential cookies or sends messages, even if the profile itself rests on another lawful basis.
Most UK retailers that process personal data must also pay the ICO data protection fee and appear on the ICO register; check the register before shortlisting.
The ONS Retail Sales Index is the most neutral published view of the split between store and online spending, so read it before accepting a channel mix from a supplier.
Source inventory to complete before a demo
Nothing can be assessed until the source list is complete. Work through these six before any supplier demo.
- Loyalty card transactions, including earn and redemption events, with the scheme and card identifier.
- Ecommerce orders from each platform, including guest checkout and any identifiers captured at checkout.
- In-store till transactions, including store, terminal, timestamp and receipt identifiers.
- Returns and refunds, whether processed at the till or online, and how they link back to the original sale.
- Service and contact-centre interactions, including complaints, product queries and the channel they arrived on.
Source inventory before demo
- Loyalty card and app events with till, store, timestamp
- Ecommerce orders, baskets, returns, refunds, marketplaces
- Store POS lines including cross-branch returns
- Payment recordscredit, gift cards, buy now pay later
- Service contacts from phone, email, chat, social
- Marketing permissions with source, wording, timestamp
Features that earn their place in retail
Feature lists are long, and most rows matter to somebody. The table below covers the six areas where UK retail buyers need evidence rather than a promise.
| Feature | Why it matters in UK retail | Evidence to request |
|---|---|---|
| Identity resolution | Loyalty, guest and card-linked transactions use different keys | Match rate on your own sample, with the method stated |
| In-store event ingestion | Tills often batch upload overnight, which delays activation | Timestamp audit from till to profile |
| Consent and preferences at line level | One customer may accept email and refuse text or profiling | Permission history per identifier |
| Returns and refunds | A return reverses an order and changes lifetime value | Recalculated value after return windows close |
| Store and product hierarchy | Branch reporting needs an estate structure that stays current | Field map covering closures and refits |
| Retention and deletion | Loyalty schemes hold records for years | Documented deletion route with timings |
Ask for each row against your own data, never against a demo tenant. A demo tenant is built to look clean. A supplier that cannot evidence the first rows is unlikely to manage the rest.
Questions to put to each shortlisted vendor
Ask how the platform handles a return processed in a store that never saw the original sale, and whether the customer record is reversed or adjusted.
Ask what happens to a profile when someone withdraws consent for profiling but keeps receiving service emails. That single case shows whether preferences sit at the right level.
Ask for the deletion route in writing, with a defined retention period for each data category and the trigger that starts deletion, and name the person accountable when it fails. The ICO's storage limitation guidance expects a documented schedule rather than a default number, so the period has to be justified per purpose; a supplier that answers these three questions plainly is worth a second meeting.
Common questions
These are the questions UK retail buyers ask most often.
Does a UK retailer need a customer data platform or just a better warehouse?
A warehouse stores events, but it rarely resolves identities across loyalty, ecommerce and till data. If joining those sources into one usable profile is the real problem, a platform discussion is legitimate, and clean customer data before implementation will do more for the outcome than the tool choice.
How long should a CDP selection take?
A shortlist of three, a defined sample extract and four weeks of evaluation is usually enough for a first decision. Extending it rarely improves the answer unless you are still collecting sources.
What should we refuse to sign?
Refuse any contract that prices on profiles without defining a profile, and any that omits retention, deletion and exit terms.
Do we need consent for every loyalty record?
No. Consent is one lawful basis among several, and a loyalty scheme may rely on contract or legitimate interests for parts of the journey. Document the basis per purpose rather than per database.
