Retail media software procurement: reading official supplier records without verdicts

Retail media tools and providers should be selected against the advertising service a retailer intends to operate. Define the controlled inventory, the buying workflow and the associated data processing before comparing software. A capable product can still leave the retailer with an integration, staffing or reporting obligation it has not budgeted for.

This guide concerns retailer or marketplace controlled advertising space and related data operations, with procurement for an England operation as the working context. It is a procurement method, not a ranked tools guide. The 2027 edition is a planning guide researched on 6 September 2026, not a prediction of prices. No ranking, pricing or product verdict is given.

What to take away

Describe the service being bought

Begin with an operating specification that a supplier can answer without guessing. Name the retailer property, the proposed paid format and the team that will approve advertiser content. Decide whether the initial service includes only on-site inventory or also retailer-controlled off-site delivery. Keep general advertising tools outside the shortlist unless their proposed role belongs to this defined service.

Describe the purchase from the retailer's side. Buying software to run a marketplace advertising programme is different from buying an advertiser interface to spend a brand's campaign budget. Do not compare those purchases as if they supplied the same capability simply because both mention retail media.

For a first scope document, identify what the retailer already operates and what it expects the supplier to deliver. Include catalogue feeds, campaign administration, ad decisions, reporting and support. Mark each item as existing, included in the request or deliberately excluded. This is an editorial procurement method, not a regulatory form.

A useful boundary is the point where the supplier's output becomes the retailer's responsibility. For example, ask whether the service returns an ad decision or also renders the paid unit. Then ask who handles product availability changes, disclosure presentation and the consequences of a failed response. These are proposed questions, not assertions about any named product.

Read official product records

Three official sources illustrate the evidence available.

Criteo's Commerce Yield introduction, inspected on 6 September 2026, describes retailer inventory monetisation, supply-side tools and reporting. Inspection question: does the described reporting reconcile with the retailer's order system?

CitrusAd's retailer page, inspected on 6 September 2026, describes sponsored products and retailer-controlled ad serving. Inspection question: which retailer controls the ad-serving configuration?

Kevel's retail media documentation, inspected on 6 September 2026, sets out ad-serving APIs and sponsored listings. Inspection question: which API calls return an ad decision rather than a rendered unit?

The records do not establish your England contracting terms, deployment availability or implementation performance. Obtain a dated written scope for the configuration you need before treating a feature description as a purchase commitment.

Separate a factual description from a promotional claim. A page that lists reporting can support the statement that the vendor describes reporting. It cannot, by itself, prove that the report reconciles with your order system, meets your retention rules or produces incremental sales. Those questions require different evidence.

Avoid recording a missing detail as an absent capability. Use an unresolved field and ask the supplier for the relevant documentation. Equally, do not infer that a feature is included in the proposed fee because it appears somewhere in a wider product family. Tie every inclusion to the particular service schedule.

Turn requirements into inspectable evidence

Write requirements as behaviours that an assessor can observe. Instead of requesting complete control, ask who may create a campaign, change its budget or export its report. Describe the expected outcome and the evidence needed to demonstrate it. Leave the result blank until an authorised test has been performed.

A supplier demonstration should use the same retailer-defined task across candidates. Keep the product catalogue, placement scope and expected report fields consistent. If one candidate needs an additional module or retailer development work, record that dependency rather than quietly simplifying its task.

Distinguish the product demonstration from the commercial proof. A vendor employee showing a feature establishes less about your operating environment than a documented acceptance exercise with the proposed configuration. Record who performed each activity and whether it used a demonstration tenant, test integration or production environment.

For every mandatory requirement, choose a decision owner before evaluation. The commercial lead may own billing reconciliation while an engineer owns response handling. A privacy decision should have the appropriately qualified reviewer. Do not let an attractive overall presentation erase an unresolved requirement owned by another team.

Put privacy questions before live shopper data

The ICO's online advertising guidance says advertising storage and access technologies require consent. Product procurement should therefore ask how the relevant permissions affect the proposed integration, including withdrawal. A claim that a service uses first-party data does not answer that implementation question.

Map personal information independently of the feature list. State what the retailer supplies, what the vendor derives and which recipients can access the result. Ask the privacy reviewer to determine the relevant purposes, lawful bases and roles. Do not upload live loyalty or purchase records simply to make a demonstration realistic.

Where a processor is involved, UK GDPR Article 28 requires a binding processing contract or other legal act with specified content. Match the proposed instructions to the actual audience and reporting operations. A generic processor annex is not evidence that the commercial service has been accurately described.

International access needs examination too. The ICO transfer guide asks whether UK GDPR applies, who initiates the transfer and whether the overseas recipient is a separate legal entity. Obtain the contracting and access map; an English sales address does not settle those questions.

This is procurement information, not individual legal advice. Qualified UK privacy and commercial review must assess the actual arrangement, current legislation and any required transfer mechanism. Neither a software purchase nor completion of this guide guarantees compliance.

Investigate the service behind the interface

The NCSC's cloud supply-chain principle addresses risks from a provider's dependencies. Use it as UK security guidance when asking which other services support the proposed advertising system. It is not a certification of any supplier named in this article.

Request evidence relevant to the product and environment being bought. A security certificate should be checked for its scope, dates and covered legal entity by a competent assessor. Treat a company-wide claim as a starting document, not a conclusion about every integration or subcontractor.

The NCSC's identity and authentication principle recommends authenticated, authorised access and strong identity controls. For the proposed workflow, ask how advertiser accounts are separated from retailer administration and how service credentials are managed. Have the assessor inspect the supplied evidence rather than accept a yes-or-no questionnaire alone.

Ask what support staff can see when investigating a campaign issue. Determine whether their access is temporary, recorded and limited to the relevant work. Keep those questions tied to the retailer's data classification and incident process. Do not publish an assurance verdict where only a public marketing page was examined.

Compare cost using a shared scope

Prepare a quotation schedule before asking for a price. Specify the service period, inventory environments, support coverage and the usage quantities on which each quote should be based. Request GBP figures with VAT treatment stated.

Separate implementation charges from recurring platform fees and variable usage charges. Ask which events are billable and how retries, unsuccessful decisions or overages are treated. Those are quotation questions; no uniform pricing model is assumed across suppliers.

Worked example of a shared-scope cost comparison table, using illustrative GBP placeholders only, not real quotes.

Replace each placeholder with the supplier's own GBP figure on the same scope unit.

If candidates price different units, preserve the original units and calculate a comparable scenario only after the terms and quantities are known. Do not substitute ad requests for rendered impressions or purchases for attributed conversions. Explain the definitions and any conversion assumptions beside the calculation.

Include retailer work in the decision record: engineering, operational training, catalogue maintenance and supplier oversight. These are proposed budgeting categories rather than measured costs. A low software quote is not a complete cost comparison if the specified responsibilities differ materially.

Write acceptance around a controllable launch

Propose a limited initial placement with a documented release boundary. Name the property, eligible products, advertiser access and reporting destination. Exclude unapproved formats or audiences explicitly so a successful check on one unit cannot be used as permission to expand the service without review.

Acceptance work should inspect both normal and failure behaviour. Request exercises for an unavailable product, an invalid campaign instruction, a delayed report and withdrawal of the relevant permission. Record the expected handling and the person who will assess it. These are suggested tests; none has been conducted for this guide.

For labels, CAP's recognition rules require marketing communications to be obviously identifiable. Keep the rendered paid unit within the acceptance scope even when ad selection is supplied remotely. A technically successful response says nothing by itself about the shopper's understanding of the display.

Plan how the retailer can stop serving the unit without damaging the rest of the shopping journey. Agree what remains visible, what happens to advertiser budgets and which reports require reconciliation. Define the rollback decision before the launch window, while the parties can still amend the plan.

Leave with an exit route and a dated decision

Before signing, request a description of the information and configurations that can be exported, in what format and at what stage of termination. Separate retailer-owned materials from licensed supplier components. Ask the commercial lawyer to examine what the agreement actually permits rather than assuming access will continue indefinitely.

Consider how campaigns would be closed, outstanding charges checked and unnecessary access removed. Keep retention and deletion obligations with the privacy review. A downloadable report is not the same as a portable operating system, so describe the work another provider would still need to perform.

The decision paper should identify the selected scope, inspected evidence, unresolved conditions and the person authorised to accept each condition. There is no obligation in this editorial method to choose a product merely because a procurement exercise has started.

To turn this procurement method into a ranked guide, we would need dated testing results for each named product, observed GBP quotations from real scopes, and independent verification of performance. We would also need real named authorship, fact-checking and specialist review. Confirm any commercial relationships for disclosure.

Use the guide to organise the purchase conversation, then retain the actual contract, evidence and acceptance record as the basis for the retailer's decision.

Before you act

Common questions

What should a retailer define before comparing retail media software?

The article says to define the controlled inventory, the buying workflow and the associated data processing first. It also advises naming the retailer property, the proposed paid format and the team that will approve advertiser content, and deciding whether the initial service includes only on-site inventory or also retailer-controlled off-site delivery.

How should a retailer treat a missing detail on a supplier page?

The article says to avoid recording a missing detail as an absent capability. Instead, use an unresolved field and ask the supplier for the relevant documentation. It also warns against inferring that a feature is included in the proposed fee because it appears somewhere in a wider product family.

What privacy questions should come before live shopper data is used?

The article says procurement should ask how the relevant permissions affect the proposed integration, including withdrawal. It advises mapping personal information independently of the feature list, stating what the retailer supplies and what the vendor derives, and not uploading live loyalty or purchase records just to make a demonstration realistic.