P

PassportMap

EVIDENCE READINESS

Product-family data preparation

Know what you have.
Request what you do not.

For EU-facing brands preparing product data: turn your existing product and supplier facts into a bounded evidence register before you start a Digital Product Passport publishing workflow.

1. Identify the product family

Build an honest evidence starting point.

The result flags only what is missing from the input you provide. It does not inspect suppliers or external records.

2. Record only facts you can name

Materials or component facts

What is known about the material or main component?

Use a source that can be shared with your publisher or supplier.

Origin or manufacturing facts

What country, facility, or production origin is evidenced?

Keep the source reference separate from the claim.

Supplier declaration or contact

Which supplier can confirm the relevant product facts?

A supplier name alone is not evidence; record a person, document, or request path.

Care, repair, or end-of-use facts

What documented instructions are available?

Do not infer durability, recyclability, or repairability from a marketing claim.

Certificate or test reference

Which certificate, test, or declaration is actually available?

Record the reference only; this tool does not validate it.

Runs in this browser. Your facts are not sent to PassportMap.

The paid outcome

One product family. One accountable handoff.

USD 49 once delivers a durable readiness register: supplied facts, source gaps, accountable owners, and targeted supplier requests for one product family. Checkout stays fail-closed until the fixed URL, expected path, and payment mode match.

  • Different from a publisher: organize the evidence before you configure a DPP platform.
  • Different from a consultant: use a bounded, repeatable input and automatic register without an account or handoff.
  • After verified payment: the buyer-specific first register is saved for re-download.

The boundary matters

Preparation is not a passport.

PassportMap helps a team organize its own product facts before it enters a publisher workflow. It does not issue QR codes, connect to suppliers, assess certification validity, or say a product meets ESPR, DPP, or any other legal requirement.

Use only authorized product information. Do not enter credentials, personal data, confidential contracts, or claims you cannot trace to a source. Keep local recovery packages in an approved location.

Buyer trust

Support, refunds, privacy, and recovery

  • Support: contact Arelvia Studio support with the Checkout email and purchase date. Never attach product files, credentials, personal data, or confidential contracts.
  • Delivery-failure refunds: if a verified paid register cannot be generated or re-downloaded after reopening the exact success link and retrying once, request refund eligibility within 14 calendar days. The register’s readiness result is not a refund condition.
  • Privacy and data handling: the preview runs in this browser. After verified payment, only the authorized fields the buyer submits are sent to Commerce Core, which stores the minimum Session/product entitlement and first saved register, never card data.
  • Recovery: reopen the exact Stripe success link to retry generation or re-download the first saved register without paying again.