Enter workspace

Workflow · Sustainability & Product Compliance · DPP

DPP Readiness

For one product in one market under one regulation: what does a Digital Product Passport require, what evidence exists, and what is missing?

Start — not yet availableAbout this capability
Foundation — in development

Who it is for — and what you will need

Manufacturers and operators of products heading into EU passport regulation.

  • The product/product family
  • Destination market and regulation
  • Product identity, specifications and materials where relevant

Anything OrenAtlas already knows is prefilled with its evidence state — you are asked only for what is missing or unresolved.

How it works

6 stages. Save and resume at any point; each stage keeps its evidence attached to the exact item it supports.

  1. Product

    Product/product family, manufacturer/operator role.

    in development
    Stage details
    What OrenAtlas already knows
    Product identity, specifications, manufacturer/operator from canonical records
    What you provide
    Operator role confirmation (required) — DPP obligations depend on the economic-operator role
    Evidence used
    No evidence collected at this stage.
    What happens
    Product-scoped ALWAYS — company-level DPP is unrepresentable
    If something is missing
    Missing product records create product-data tasks.
    Done when
    Product + role fixed.
    What comes next
    DPP case (product-scoped).

  2. Applicability

    Market + regulation + version resolved; applicability assessed product-level — never company-level.

    in development
    Stage details
    What OrenAtlas already knows
    Market + regulation + version resolved from the regulation registry; applicability assessed product-level
    What you provide
    Destination market + regulation selection (required) — One assessment per product × market × regulation × role
    Evidence used
    No evidence collected at this stage.
    What happens
    Regulation version retained; food/feed and non-applicable guards honored
    If something is missing
    Pending delegated acts → "product rules pending", an explicit state.
    Done when
    Applicability state recorded.
    What comes next
    Applicability assessment.

  3. Required data

    Identifiers, specifications, materials, regulatory attributes and sustainability/product evidence.

    in development
    Stage details
    What OrenAtlas already knows
    Required data schema for the regulation; existing product data prefilled
    What you provide
    Missing product fields (if applicable) — Identifiers, specifications, materials, regulatory attributes — supplier data requests for what only the supplier knows
    Evidence used
    Product specifications, Material declarations, Test reports. Reuse: Existing product data reused; requests only for genuinely missing fields.
    What happens
    Fields validate against the regulation schema
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Required data assembled (gaps explicit).
    What comes next
    Field-level data coverage.

  4. Gaps

    Missing evidence and identifiers as concrete items.

    in development
    Stage details
    What OrenAtlas already knows
    Field-level evidence links with provenance
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    Product evidence records. Reuse: Evidence attaches per field; reuse never upgrades state.
    What happens
    Every filled field shows its supporting evidence or its absence
    If something is missing
    Missing items become owned, actionable tasks (request evidence / assign owner) — never a dead warning.
    Done when
    Evidence mapping complete.
    What comes next
    Field evidence map.

  5. Review

    Human review.

    in development
    Stage details
    What OrenAtlas already knows
    PREVIEW: what would appear, what is missing, what is restricted/private, what evidence supports each field
    What you provide
    Review confirmation (required) — Human review of the preview before any output
    Evidence used
    No evidence collected at this stage.
    What happens
    Preview-before-commit is mandatory
    If something is missing
    Missing fields visible in the preview.
    Done when
    Preview reviewed.
    What comes next
    Reviewed passport preview.

  6. Readiness Pack

    DPP Readiness Pack. Never "company is DPP compliant".

    in development
    Stage details
    What OrenAtlas already knows
    Everything above
    What you provide
    Nothing — OrenAtlas assembles this stage.
    Evidence used
    No evidence collected at this stage.
    What happens
    Versioned; product-scoped; never "company is DPP compliant"; next actions present
    If something is missing
    Gaps listed with owners.
    Done when
    Versioned DPP Readiness Pack generated.
    What comes next
    DPP Readiness Pack (versioned) → ESG / Compliance.

What you receive: DPP Readiness Pack

A versioned result — not just a PDF. It preserves:

product + market + regulation scopeapplicability staterequired data coverageevidence with provenancegapsreview states

Current state

Foundation — in development.

Product-level applicability engine and regulation registry are live in the engine; the readiness workspace is specified but not yet built.

Where this hands off next

Your case context (company, product, market, requirement) travels with you — nothing is re-selected.

Partially live

ESG Workspace

Collect, calculate, review and report sustainability information with traceable evidence.

View workflow →Foundation — in development

Compliance

Understand whether available evidence covers a defined requirement set — and exactly what to do about every gap.

View workflow →