How to Choose a Retail Media Platform: Buyer Scorecard
Evaluate retail media platforms with tested requirements for relevance, operations, reporting and finance. Compare build, buy and augmentation on your scope.
How to choose a retail media platform
Choose a retail media platform against the jobs your team must perform and the evidence each supplier can provide. Define essential shopper, advertiser, operational and financial requirements before scoring proposals. A useful evaluation distinguishes available functionality from partner delivery, roadmap commitments and unanswered questions.
Write the decision before the feature list
Identify the problem that makes a purchase worthwhile. You may need to launch a programme, improve relevance in an existing network, reduce manual operations or reconcile revenue more reliably. These are different buying decisions.
Record the existing stack and the systems you intend to retain. Define which team owns campaign setup, ranking, event collection, advertiser reporting and invoicing. An attractive demonstration can conceal an unresolved handoff.
Turn important requirements into tests
For relevance, ask the vendor to show an ineligible high-bid product being excluded and a relevant organic fallback when no advertiser qualifies. For operations, follow an approved booking through a stock change, budget exhaustion and a reporting correction.
For measurement, request metric definitions and a report whose numbers can be reconciled. Separate attributed sales from causal estimates and inspect the design behind any claimed lift. For finance, trace a delivered billable event through adjustments, invoice and payment.
Use your catalogue and representative edge cases where possible. A vendor's polished sample is evidence of the sample, not acceptance of your implementation.
Preserve capability boundaries
The PA retail-media RFP library distinguishes vendor-declared capabilities, partner delivery, roadmap items and requirements not stated as supported. Keep those statuses visible. An empty competitor response means unanswered, not unavailable.
Give each essential item an evidence owner, observed result and unresolved dependency. Agree what must pass before signing and what can be phased later. A promise about future work belongs in a separate commitment with a named owner and acceptance condition.
Compare build, buy and augmentation
Estimate the same scope for each option: initial delivery, ongoing engineering, commercial operations, reporting, support and retained systems. Include migration and exit effort. Avoid claiming that building always takes a particular number of years or that buying automatically removes operating cost.
An augmentation option may be useful when only one part of the stack is failing. Its feasibility depends on the actual interfaces, contracts and ownership model. Document the integration that would make the proposal work.
Make the score explainable
Use must-pass requirements before a weighted preference score. In the synthetic example, a platform with attractive creative tools still fails the shortlist if it cannot demonstrate the required stock fallback. Do not allow a high total to hide a critical gap.
Finish with an agreed pilot, commercial assumptions and a stop or expansion decision. The launch guide provides the next operating steps once the required evidence is credible.
Illustrative example
{"label":"Synthetic procurement gate","requirement":"Selected-store stock fallback","must_pass":true,"vendor_creative_score":5,"observed_stock_test":"Failed","decision":"Do not shortlist until the essential requirement is resolved; preference score does not override gate."}
Sources
- RevenueOS, checked 2026-10-25
- IAB Europe Commerce Media Measurement Standards V2.1, checked 2026-10-25
How Particular Audience does it
Frequently asked questions
Should every requirement be weighted equally?
No. Identify requirements whose failure makes the proposal unusable before scoring preferences. Use agreed weights for the remaining criteria and retain the evidence behind every rating.
How should we score a roadmap promise?
Keep it separate from demonstrated functionality. If it is essential, require a concrete commitment and acceptance condition; do not score it as available merely because it appears in a presentation.
Should we build or buy the whole network?
Compare the same operating scope and retain an augmentation option where appropriate. Consider engineering ownership, integrations, commercial workflows, ongoing costs and exit effort rather than applying a universal rule.
Related guides
- Retail media platform: a buyer's guide: How to choose a retail media platform or software: the capabilities that matter, an evaluation checklist, pilot design and free RFP and business case tools.
- How to launch a retail media network: Build a retail media launch plan covering inventory, suppliers, eligibility, measurement and billing. Use readiness gates and a practical pilot checklist.
- What is a retail media network?: Understand what a retail media network sells, how media and product revenue differ, and the data, operations and measurement a retailer needs to launch.
- How to measure retail media incrementality: Plan a retail media holdout with stable assignment, comparable outcomes and visible uncertainty. Separate incremental sales from attributed ROAS and brand halo.