Two women enjoying a shopping spree and sharing a moment on their smartphone in a clothing store.
Photo by Vitaly Gariev on Pexels

Tools and providers

Part of Retail media software procurement: reading official supplier records without verdicts

Implementing a retail media tool from release boundary to operable handover

Retail media implementation for England retailers: define release scope, configure access, inspect permissions and prepare placement checks and operational handover.

Retail media tool implementation should move a defined advertising workflow into controlled operation, with a clear way to stop it. For an England retailer or marketplace, begin with the approved inventory and data scope. For a grocery property such as Tesco Media and Insight Platform, the first release might cover sponsored product placements on grocery search results only.

Do not treat a signed software order as authority to activate every available format or audience feature.

These steps describe proposed implementation work based on sources inspected on 6 September 2026. No integration was built and no tests were run for this article. Actual deployment requires competent engineering and security assessment, plus qualified UK privacy and legal review where relevant; the guide offers no compliance assurance.

What to take away

  • Set the release boundary first: property, paid format, catalogue segment and campaign users.
  • Configure an isolated test environment with labelled synthetic records, trace permissions including withdrawn consent, run an acceptance task for the paid unit and rehearse the disable and restore step before handover.
  • Hand over access instructions, escalation contacts and the agreed reporting definitions.
  • Confirm who owns catalogue changes and supplier communications.
  • Limit expansion to further properties or data uses until their owners have assessed the change.

Establish the release boundary

Write down the retailer property, paid format, catalogue segment and campaign users included in the first release. Identify excluded functions so the project team can recognise scope changes. Give the release owner access to the agreed service description and the unresolved procurement conditions.

First release scope

  • Retailer property included
  • Paid format included
  • Catalogue segment included
  • Campaign users included
  • Excluded functions listed
  • Release owner has service description
  • Unresolved procurement conditions noted

For each connection, name the sending system, receiving service and information exchanged. Keep catalogue information distinct from shopper identifiers and purchase events. A data-flow diagram should describe this release rather than reproduce a supplier's generic architecture diagram.

Three artefacts carry the release, and each needs a named owner:

ArtefactMinimum content
Data-flow diagramSending system, receiving service, fields exchanged, retention period
Release noteConfiguration, evidence inspected, outstanding conditions
Acceptance recordTask run, date, actual result, open exceptions

A worked example: map a product identifier such as a GTIN to the catalogue segment the ad server reads, and hold a loyalty identifier, such as a Nectar card number, in a separate field.

Prepare a separate test configuration

Ask the engineers to configure an isolated environment and clearly labelled test material. Start with synthetic records where possible, without presenting them as representative shoppers or observed sales. Document any later request for real data and route it through the retailer's privacy decision process.

Isolated test setup

  1. Configure isolated environment
  2. Label test material clearly
  3. Start with synthetic records
  4. Do not present as real shoppers
  5. Document requests for real data
  6. Route through privacy decision process

An ad server such as Google Ad Manager, a retail media platform such as Criteo Retail Media and a consent management platform such as OneTrust each need their own isolated configuration and access list.

NCSC guidance on identity and authentication addresses access for both users and service identities. Apply that guidance to the proposed campaign administrators, advertiser accounts and automated integrations. Allocate permissions deliberately and record who is responsible for credential changes. The document is the NCSC Cloud security principles, principle 10 (identity and authentication).

Do not carry shared demonstration credentials into live operation. Ask the security assessor to review the intended account model, support access and removal procedure before release.

Trace permissions through the advertising path

The ICO's advertising storage-and-access guidance requires consent for technologies used for online advertising. Prepare an authorised exercise showing the expected handling when consent is absent or withdrawn, and identify the downstream operations affected. The documents to cite are the ICO's Guidance on the use of storage and access technologies and the ICO's Guide to the UK GDPR.

Consent through advertising path

  1. Consent required for online advertising
  2. Exercise handling when consent absent
  3. Exercise handling when consent withdrawn
  4. Identify downstream operations affected
  5. Inspect personal-data processing separately
  6. Privacy reviewer confirms purposes and roles

Inspect personal-data processing separately from device activity. Ask the privacy reviewer to confirm the purposes, recipients and contractual roles reflected in the configuration. The exercise should not assume that an advertising label, account login or purchase supplies permission for unrelated targeting.

Check the placement and event record

Create a documented acceptance task for the selected paid unit. Ask the assessor to follow campaign creation, product eligibility, display and reporting, using the same event identifiers throughout. Record actual results only after the exercise takes place.

CAP recognition rules require the advertising nature of a marketing communication to be obvious. Include disclosure in the rendered-placement review, alongside technical delivery. Preserve the execution inspected so a changed layout is not mistaken for the approved version. The rule to cite is the CAP Code, section 2 (recognition of marketing communications).

For reporting, define how retries, missing events and corrections will be investigated. Compare the exported record with the agreed measurement specification. Do not interpret a populated dashboard as proof that attribution is correct or that sales were caused by the campaign.

Rehearse interruption before launch

Request a controlled exercise for disabling the unit and restoring the expected shopping page. Identify the person authorised to pause delivery, the route for notifying operations and the treatment of any affected campaign records. Any financial remedy belongs in the actual contract. A limited launch is an operating control, not an exemption from applicable duties.

Hand over an operable service

Provide the operational team with access instructions, escalation contacts and the agreed reporting definitions. Confirm who owns catalogue changes and supplier communications. Recheck current guidance before publication and future deployment, and retain a genuine acceptance record rather than signing off the project from this article alone.

Licensing and delivery timing are contractual, not technical. No public tariff covers retail media tool licensing. Fees usually turn on the number of properties and formats, whether the charge is a platform fee, a share of media spend or a CPM, the minimum term and the support level.

Delivery time follows the number of connections, the privacy review and the retailer's trading calendar, not the software release cycle. Ask the seller to set out the fee basis and the release window in writing before the release boundary is agreed.

Common questions

What should the release boundary cover?

The retailer property, paid format, catalogue segment and campaign users in the first release, plus the excluded functions the team has to watch.

How should test data be handled?

Use an isolated environment and clearly labelled synthetic records first, and send any later request for real data through the retailer's privacy decision.

What does the interruption exercise involve?

A controlled disable and restore run, plus the person authorised to pause delivery and the route for notifying operations. Financial remedies belong in the contract.

More in Tools and providers