DPP Grid legal information
Managed DPP Registry Registration
Operational draft: Plain-English explanation of DPP Grid managed registration support and its boundaries. Professional legal and production-fact review remains pending.
DPP GRID MANAGED REGISTRATION — PUBLIC PAGE COPY
Version 1.2 — 31 July 2026
Hero
Eyebrow: DPP creation, hosting and registration workflow
From product data to a registered passport — without losing control
Bring in product information from Shopify, spreadsheets or your existing systems. Review the evidence, publish a clear Digital Product Passport and, where registration is required and the route is available, let DPP Grid manage the EU Registry submission under your authority.
Your organisation remains named as the responsible economic operator. DPP Grid provides the infrastructure, workflow and technical registration service.
Primary CTA: Prepare your passports
Secondary CTA: See how managed registration works
Small trust line:
No hidden transfer of responsibility. No need to present your products as ours. Every submission is linked to the correct responsible organisation.
One workflow, clear roles
Your organisation
You decide which legal entity is responsible for each product, provide or approve the product information and remain responsible for keeping that information accurate.
DPP Grid
DPP Grid imports and structures product data, keeps source and approval history, hosts the passport and manages the technical registration workflow when authorised and permitted.
EU DPP Registry
The Registry records the product passport's identifying and access information and returns the available registration status and identifier. The full passport remains hosted through DPP Grid or another service selected by you.
How it works
1. Connect your catalogue
Import product and variant information from Shopify or another supported source, or start with a spreadsheet. DPP Grid keeps the source context so your team can see where information came from.
2. Review and approve
Imported and AI-assisted information begins as a proposal, not an approved claim. Your authorised team reviews the data, evidence and public presentation before publication or submission.
3. Publish the passport
Create a browser-ready passport with a stable product identifier and QR-ready link. Configure public and restricted information according to the applicable rules and your chosen workflow.
4. Activate managed registration
Sign a separate digital appointment authorising Fleeta Limited trading as DPP Grid to carry out selected registration actions on your behalf. Registry access and verification are completed separately where required.
5. Submit and track
DPP Grid prepares customer-specific submissions, records status and errors, and stores the registration identifier and available proof against the correct product record. Manual submission may be used first; supported API automation can replace it without changing the approval trail.
Built for catalogue imports — governed for compliance workflows
Shopify and other commerce platforms are excellent sources for titles, variants, media, SKUs and selected metafields. They are not automatically the legal source for every DPP statement.
DPP Grid therefore separates:
- Imported source data — what came from the connected system;
- Proposed DPP data — mapped or AI-assisted values awaiting review;
- Approved passport data — the version authorised for publication; and
- Approved registration data — the version authorised for Registry submission.
Updates can be reviewed as changes rather than silently overwriting approved claims.
What managed registration does — and does not do
Managed registration can reduce repetitive administration and give your team one place to manage submissions, identifiers, proof and errors.
Registration does not turn DPP Grid into the manufacturer, importer or other responsible economic operator. It also does not replace product safety work, conformity assessment, testing, certification or legal advice. A Registry result confirms only the matters checked in that registration process.
Designed for today's workflow and tomorrow's API
The service is designed around a single registration queue and audit trail:
- customer-specific manual JSON or XML submission while that is the supported route;
- automated API submission when an appropriate production interface and delegated-access route are available;
- the same customer approval, tenant separation and registration evidence in either mode; and
- no “EU registered” status unless a successful Registry result is stored for that passport.
Frequently asked questions
Does every customer need to verify its organisation?
Where the Registry requires verification of the responsible economic operator, the relevant customer legal entity must complete and maintain that verification. DPP Grid's appointment does not replace it.
Can DPP Grid submit for several legal entities in one account?
A workspace may support several responsible legal entities, but each product must be assigned to the correct one. Submission files and Registry actions are kept separate by responsible economic operator unless the Registry expressly supports another model.
Can we authorise DPP Grid during normal signup?
You can request the service during onboarding, but the legal appointment is separate from the ordinary Service Terms. It is sent to an authorised signatory and becomes active only after signature and the required setup checks.
Does DPP Grid become responsible for our products?
No. DPP Grid is the passport service provider and, where activated, the limited registration agent. The responsible economic operator remains responsible for the product and approved information. DPP Grid remains responsible for performing its own services with reasonable care and within the authority granted.
Can we start before our product group requires registration?
Yes. You can import data, build evidence, publish voluntary passports and prepare the registration workflow before a product-specific registration duty applies. The account should show the difference between “not currently required”, “not yet available”, “ready to submit” and “registered”.
What happens when our Shopify catalogue changes?
DPP Grid can detect mapped changes and present them for review. Approved passport or Registry data should not be silently replaced by a later catalogue import.
Closing call to action
Prepare now. Register with confidence when the route applies.
Build source-linked passports today and activate managed submission for the relevant products when the legal and technical conditions are in place.
Primary CTA: Create your workspace
Secondary CTA: Talk to us about managed registration
Footer note:
DPP Grid is a trading name of Fleeta Limited. DPP Grid provides product-passport technology and administrative registration services; it is not a conformity-assessment body, product certifier or legal adviser.