Straight answers, no hedging.
The questions product, IT and compliance teams ask us most often.
Do we have to replace our PLM or ERP?
No. OVERWRLD reads from the systems you already run and writes nothing back unless you ask it to. Replacing core systems is the slowest possible route to passport readiness.
What if the delegated act for our product group isn't final?
Most of the work — identifiers, material data, supplier records — is required under every draft. We build the data foundation now and keep validation rules aligned as text lands.
Can we use our own domain and identifiers?
Yes. Your GTINs, your GS1 Digital Link prefix, your domain. Passports resolve under your brand, not ours.
Who can see our data?
Only what you explicitly publish is public. Everything else stays inside your workspace, scoped to your organisation and your roles.
How do published passports stay accurate over time?
Publishing snapshots an immutable version. Later edits create a new version through the same approval flow, and every prior version stays retrievable with a full audit trail.
What happens to the physical products already in market?
Identifiers are permanent and content behind them is updatable, so a carrier printed today can point at an improved passport next year without reprinting.
Know where you stand before you implement.
Start with a DPP Readiness Assessment — fixed scope, fixed fee, no systems replaced.