How PIM Selection evaluates PIM vendors

Every vendor record carries a source and a verification date

PIM Selection treats each vendor fact as a dated claim with a source. A vendor record stores the deployment model, pricing model, target segment, main integrations, supported standards and the date the record was last verified. Each fact links to the document it came from: a vendor documentation page, a release note, a public price list or a statement the vendor confirmed in writing.

A fact without a source is left out. A fact older than its review cycle is flagged on the page until an editor checks it again. This keeps profiles honest about what is known and when it was known.

The record also has fields it deliberately lacks. Vendor records hold no partner, sponsorship or featured field, so no list in the hub can sort on commercial status. The neutrality policy explains that firewall in full.

How the Fit Finder scores fit

The PIM Fit Finder shows its working. Each question in the Fit Finder maps to requirements in the four checklist domains. Each answer adds weight to some requirements and removes others from consideration. The match for each vendor is the coverage of the weighted requirements, based on the vendor record.

The result screen lists the answers that drove each match and the gaps that remain. A reader can change one answer and see which vendors move. No commercial input enters the calculation, and lists with equal fit appear in alphabetical order.

The Fit Finder produces a longlist for a conversation. A shortlist still needs validated requirements and scenario demos, as described in from longlist to shortlist.

Vendors are judged on scenario demos

PIMvendors' scenario method asks vendors to show real use cases on the buyer's own sample data. Scenarios are derived from validated requirements: onboarding a supplier file, enriching a product family in three languages, publishing to a marketplace, or producing packaging data for a regulatory report.

Generic demos predict little about fit. A scripted demo shows the vendor's best path through its own data. A scenario shows what happens with the buyer's messy attributes, missing translations and odd hierarchies.

The scenario-based demo guide explains how to write scenarios. The demo scenario library lists ready-made scenarios by industry and requirement domain.

The 4-domain requirements checklist

Every vendor assessment in the hub uses the same four requirement domains. The domains come from the full PIMvendors method, which holds 400+ requirements. The hub publishes them progressively, starting with the requirements that most often decide a selection.

The requirements checklist renders the published requirements and lets a buyer mark priorities. The sequence of the domains follows the house thesis: Data, then Process, then People, then Tooling.

Review cycles by page type

Pages are reviewed on a fixed cycle that matches how fast their subject changes.

Each page shows its last review date. Material changes are logged in the update log, so readers can see what moved and when.

Fact checks and right of reply

Vendors see the factual sections of a new profile before publication. The vendor receives the record and the factual paragraphs, with 10 working days to send evidence of any error. Opinions, verdicts and comparisons are not shared for approval.

After publication, a vendor can submit a correction at any time. The editors correct facts that the evidence supports and note the change on the page. Where a vendor disputes a verdict, the editors may publish a short vendor response under that verdict, clearly labelled.

Sources policy

External facts need a source a reader can open. Regulation dates link to the official text or the Commission's guidance. Vendor facts link to vendor documentation or written vendor confirmation. Market statistics appear only with a named, checkable source.

Estimates from PIMvendors engagements are labelled in the sentence as estimates. Illustrations are labelled as illustrative examples or composite patterns, and never name a client. The editorial policy sets out the full sourcing and correction rules.