Selecting customer data platform software on an edition-specific dossier and one fixture

Software selection should begin with a rejectable requirement, not a longlist. For an England buyer, name one data journey, the people affected, the accountable entity and the decision the system must support. Then admit only an exact service whose current evidence can be checked against that journey.

This is a desk-research method dated 6 September 2026. No supplier account, production data or interface was examined. It offers no legal advice, security assurance, product recommendation, vendor shortlist or product comparison.

What to take away

Write the requirement in observable terms

Avoid "single customer view", which omits whether the buyer needs CRM work, warehouse storage, identity matching or preference management. It also omits analytics and audience activation. Instead write an input, transformation and expected state: receive authorised fictional account and purchase events, propose duplicate links without merging ambiguous records, preserve a later correction, exclude a suppressed record from an export.

Add the operating facts: England entity, eligible population, sources, identifiers, destinations, retention event, expected volume unit and named owner. Keep thresholds and costs blank until the buyer approves evidence for them.

Apply gates before scoring

Create separate pass, fail and unresolved columns for these gates:

Do not average these into one attractive score. The ICO's data protection by design guidance places privacy consideration at the design stage and through the lifecycle. A missing rights route cannot be offset by easier reporting.

Demand an edition-specific dossier

Ask the supplier to identify its legal entity, UK availability, service and edition, document versions, subprocessors, access locations, support boundaries and change history. Match each claimed function to a current official record. Mark a field unknown where the evidence is generic, expired or silent.

Ask for edition-specific pricing in writing, covering platform fee, event or profile volume tiers, identity resolution, activation, connectors, sandbox, support and exit or portability charges. Public list prices may not match negotiated editions; the written quote determines the figure.

Roles require factual analysis. ICO guidance on controllers and processors explains that the distinction depends on who determines purposes and means. A contract label cannot settle what the configured service actually does.

Security evidence also needs a buyer-side check. The NCSC guide to using SaaS securely covers privileged access, service identities, audit data, incident response and recovery. Record what the service exposes, what the buyer must configure and what remains untested. Check the supplier's ICO registration entry and the NCSC SaaS guidance against the dossier.

Use one common fixture

Give every admitted route the same fictional records. Include an ambiguous identity, a proven duplicate, stale and corrected fields, an objection, suppression, deletion, refused tracking, administrator removal, a log event and export data. Predeclare the expected result and inspect evidence rather than a sales narrative.

Worked example for a rejectable requirement: fictional England retailer Northbridge Books Ltd, population 250,000 consented customer records, expected volume 40,000 purchase events a month. Predeclared expected result: two accounts link as duplicate, a third remains ambiguous, a correction replaces the stale field, an objection suppresses the record and the export excludes it.

Keep production activation disabled. A pass means only that the stated version behaved as expected with the fixture. It does not show lawfulness, scale, reliability or suitability for another journey.

Record the selection decision

The decision record should list admitted and rejected routes, unresolved facts, evidence owners and expiry dates. Name each qualified privacy, PECR, security, accessibility, procurement, commercial and legal reviewer. If an essential gate has no current evidence, pause the selection and obtain the missing record.

The next action is to obtain the missing record, not to replace it with a favourable assumption.

Before you act

Common questions

What should the supplier dossier contain?

Ask the supplier to identify its legal entity, UK availability, service and edition, document versions and subprocessors. It should also cover access locations, support boundaries and change history. Match each claimed function to a current official record, and mark a field unknown where the evidence is generic, expired or silent.

What does a fixture pass actually prove?

A pass means only that the stated version behaved as expected with the fixture. The article says it does not show lawfulness, scale, reliability or suitability for another journey. Keep production activation disabled and inspect evidence rather than a sales narrative.