DPPora

Before building screens, we defined the operating model: an organisation maintains a catalogue; each product keeps a structured record; the passport is prepared in stages; publishing creates a permanent public output; and later changes can evolve without destroying history.

The public experience was designed around one simple idea: product data becomes lasting trust. In parallel, the private application was conceived as a guided workspace with clear states, progressive validation and visible next steps.

Organisation onboarding does more than ask a user to type a company name. DPPora performs business-registry lookups according to jurisdiction. In the UK, for example, the platform queries Companies House and returns the registered details for confirmation.

EU businesses can use VIES validation where applicable. The flow also supports individual professionals and jurisdictions where automated lookup is unavailable, allowing manual entry without breaking onboarding.

The workspace organises products by passport status and supports search by name, SKU, GTIN, UPI, date or material. Each product moves through four stages: identity, passport data, EU regulatory information and preview/publish.

The goal was for the platform to explain what is missing and what happens next. States, contextual help and validation reduce the chance of publishing an incomplete or inconsistent record.

DPPora accepts identifiers such as GTIN/EAN and SKU and includes barcode scanning to accelerate data capture. Materials include percentage and country of origin, with validation ensuring composition reaches exactly 100%.

Beyond composition, a record can store repair, recycling and sustainability information plus supporting evidence. Contextual tooltips explain the purpose of complex fields inside the workflow itself.

One of the most important product decisions was not to pretend that every DPP scheme is fully defined. The EU regulatory module separates voluntary preparation from mandatory schemes and retains schema identifiers, versions, registry status and correlation fields for future integrations.

This allows customers to organise data now and evolve records as delegated acts, semantic schemas and official systems become concrete.

The product was designed for a European market from the start. The public site and portal are localised, and published passports can be served in multiple languages. Automatic translations are cached to avoid repeated work and can be manually corrected when an editorial version is required.

The architecture keeps source content separate from translated output so a passport update can invalidate or refresh affected translations without losing version control.

On publication, DPPora generates a permanent URL and downloadable QR code that can be placed on a product or its packaging. The QR does not point to a static image: it opens the public record maintained by the platform.

Publishing was designed as a clear transition from draft to live, showing the operator exactly which URL and QR to use.

The commercial layer was built as part of the product rather than bolted on later. Plans control published-passport limits, users and capabilities. The dashboard shows current usage, the next renewal and the expected next payment.

Upgrades calculate prorated cost, VAT where applicable, amount due today and the next charge. Billing-period changes and downgrades are handled as explicit operations so subscription state remains understandable.

DPPora extends beyond the private application. A public regulation tracker distinguishes binding deadlines, adopted frameworks and ESPR priorities. Each sector can show what to prepare and link back to the relevant official source.

This turns regulatory research into a useful acquisition and education tool, helping prospective customers understand readiness before they register.