From import to downstream availability, including the cases that fail.
The lifecycle is not a guaranteed path to READY. Wrong contacts, uncertainty, delegation, permission denial, expired evidence, conflicts, and manual escalation are part of the product — not exceptions hidden from the manufacturer.
Stage 1
Import what you already have
Connect files from ERP, PIM, PLM or spreadsheets. SOURCE does not replace those systems. Native connectors and APIs are assessment-dependent, not assumed generally available.
Stage 2
Reconcile identity
Names, identifiers and aliases are scored. High-confidence matches can proceed. Uncertain contacts and duplicate suppliers stay visible for review.
Stage 3
Identify evidence gaps
Required properties are compared with attached evidence. Missing, expired, unscoped or unpermissioned items become the work list.
Stage 4
Prepare focused requests
Gaps are grouped for the likely owner — a supplier or an internal role — not one mail per SKU. Wrong or uncertain owners are not auto-resolved.
Stage 5
Record supplier outcomes, including unsuccessful ones
A supplier may answer, decline, delegate, express uncertainty, deny reuse permission, or not respond. Each outcome is stored. Silence is not success.
Stage 6
Apply readiness gates
Identity, value, evidence, scope, validity, permission and conflict must all pass where they apply. READY is not a marketing label; it is the conjunction of those gates.
Stage 7
Make the record available downstream
Exports and, where in scope, APIs can feed DPP, compliance or procurement tools. SOURCE prepares evidence before publication. It does not publish passports or create data carriers.
A request that does not resolve is still a recorded result.
SOURCE keeps these outcomes on the product record so a reviewer can see why a claim is not READY.
- Wrong contact — the named party is not the evidence owner; the request is redirected or left open.
- Uncertainty — the supplier cannot confirm the value; the claim stays UNRESOLVED with that reason.
- Delegation — a downstream party is asked to respond; the chain is recorded, not collapsed.
- Permission denial — evidence exists but reuse on this identity or channel is refused.
- Expired evidence — a previously valid file falls outside its validity window.
- Conflicts — two sources disagree; neither value is silently preferred.
- No response — the request remains open until the manufacturer escalates or closes it.
- Manual escalation — SOURCE prepares the trail; a person decides the next commercial step.