Start with an identity entry point
Each product first receives a PID identity and QR lookup entry so customers can review publisher, basic data, update time and public records.
DPP data preparation
Evidence Pack traceability
Clear service boundaries
Give product compliance data structure, evidence and clear boundaries rather than vague claims.
GEXYRAL helps merchants organize PID identities, QR public lookup pages, DPP structured fields, evidence archives, machine-readable data and viewing rules. The platform presents data readiness, evidence indexes and verifiable records; it does not replace testing, third-party review, regulatory admission or legal conclusions.
Compliance-preparation guidance for merchants
The platform first turns product data, evidence traceability and disclosure scope into a maintainable system.
Many merchants already have product data, but it is scattered across test reports, manuals, authorization files, platform backends, spreadsheets and chats. GEXYRAL turns that data into product identity, fields, evidence packs, viewing scopes and version records so customers, partners and future review processes can refer to one consistent entry.
Then build DPP fields
Organize materials, composition, origin, batch, certificates, manuals, recycling and maintenance fields around industry templates rather than relying on unstructured text.
Finally create evidence traceability
Connect reports, certificates, declarations, manuals and images with fields to form evidence archives, record indexes, signatures and reviewable version snapshots.
What the platform can provide
Turn scattered files into product records that can be reviewed, exported and shown by access level.
These capabilities support merchant data governance, customer review, partner communication and DPP-light readiness. They are technical and data-readiness capabilities inside the platform, not final conclusions issued by an external authority.
Product ID code and QR code entry point
Create a stable identity number, scan entry point and public lookup page for each product, so customers can first see who published the record and which product it refers to.
Digital Product Passport data preparation
Helps merchants organize product data into structured records step by step around industry fields, required items, recommended items, evidence requirements and data completeness.
Supporting material archiving and Evidence Pack
Archive test reports, certificates, manuals, authorization documents and declarations, and export Evidence Packs by product for later review and communication.
Machine-readable data preparation
Generate machine-readable data from fields allowed for public disclosure, making future search, system integration, partner access and higher-level DPP workflows easier.
Access scope tiers
Separate public data, consumer-visible data, partner data, reviewer data and internal data, so the merchant’s internal, commercial or review materials are not all placed on the public page.
Data checklist, signature and verification
Create data checklists and signature records for published snapshots, machine-readable data, Evidence Packs or export tasks, so a specific export can be checked against the platform record at that time.
Service boundaries
GEXYRAL makes data clearer and easier to verify, but does not present technical records as a final compliance conclusion.
The platform is suitable for
- Help merchants create product identities and public lookup entry points
- Help organize DPP fields, evidence materials and data completeness
- Help export Evidence Packs, data checklists and record snapshots
- Help distinguish public, partner, review and internal materials
- Help customers and partners verify information against the same record
The platform is not equivalent to
- Regulatory access, external audits or third-party endorsement
- Test reports, third-party audit documents, legal opinions or customs conclusions
- An organization that makes absolute judgments on product authenticity, quality or source
- A party that assumes the merchant’s responsibility for data authenticity and applicable regulations
- A platform that discloses all business materials without authorization
Product data, supporting materials and external statements remain the responsibility of the publishing entity.
Merchants, manufacturers, importers or other publishing operators remain responsible for product data, evidence materials, claims, product compliance and the accuracy of external disclosures.
The platform helps reduce data chaos, repeated communication and manual searching, but the merchant must ensure uploaded content is accurate, sourced, updated and assessed against applicable industry and market requirements.
The platform is responsible for records, traceability, exports and access control.
As a technical service provider, the platform provides records, versions, access controls, exports, signatures and re-checking capabilities. Technical verifiability is not a legal conclusion and does not replace testing, certification, regulatory registration or legal advice.
The platform should record publication, edits, exports, verification, access and evidence linking, so merchants can explain data source, publication time, public scope and authorization scope.
Merchant implementation path
You do not need to implement every DPP capability from the start; you can begin with product identity and data archiving.
Generate PID and QR code
First give each product a stable identity code and public lookup entry point for packaging, hangtags, manuals, after-sales cards or customer communication.
Organize public information
Confirm which product information is suitable for public display, such as brand entity, model, material, origin, update time, service notes and data boundaries.
Add supporting materials
Link test reports, certificates, authorization materials, manuals and declarations to fields so evidence does not become detached from product records.
Generate DPP and Evidence Pack
When a product needs cross-border data, partner verification or more professional disclosure, generate DPP, machine-readable data, Evidence Packs, data checklists and signature records.
Data governance and ongoing maintenance
Compliance preparation is not a one-off page, but a continuously updated product data management mechanism.
GEXYRAL explains data retention, export, signatures, permissions, service-shutdown contingency and merchant exit migration within the same service-boundary framework, so merchants see not only features but also long-term maintenance responsibilities.
Data retention
The platform retains DPP structured fields, evidence indexes, access logs, export records, record indexes, signatures and version history for business continuity, audit traceability and security needs. Retention periods can be configured and adjusted according to contracts or applicable legal requirements.
Exit and migration
When a merchant exits, evidence archives, public field snapshots, field lists, evidence indexes, record indexes, signature records and access log summaries can be exported first. The platform can assist migration, but does not guarantee import results in third-party systems.
Evidence Pack export
Evidence archives organize field snapshots, evidence indexes, timelines, audit summaries, record indexes and signature records. They help review data versions and evidence indexes, but are not testing reports, certification certificates or regulatory conclusions.
Service shutdown contingency
In case of service interruption, migration, domain adjustment or system maintenance, the platform should prioritize public access notices for published DPP records, data export, evidence archive download, record index re-checking and merchant migration communication.
Private keys and signatures
The platform records signatures for record indexes, DPP publication snapshots, machine-readable data snapshots, evidence archives or export tasks. Verification keys are managed according to security requirements and used to re-check whether records were changed.
Access rights tiers
DPP records are separated into public, consumer, partner, reviewer and internal scopes. Public data may appear on public pages and in public machine-readable data; consumer, partner and reviewer data requires authorization; internal data is not included in public pages, public machine-readable data or ordinary public evidence archives.
Registry integration pre-check
“Ready to be checked” does not mean “externally registered.”
Registry-readiness pre-check means the platform has completed an internal check of fields, evidence, machine-readable data, record indexes, signatures, viewing scopes and export capabilities. It does not mean external registration, regulatory connection or third-party confirmation has been completed.
Registry-readiness in the platform is an internal pre-check: whether PID, structured fields, required evidence, machine-readable data, evidence archives, record indexes, signatures and viewing scopes are in place. It helps merchants find gaps, but does not mean an external registry has been connected or confirmed by a regulator.
PID linked
Structured fields completed
Required supporting materials linked
Machine-readable data generated
Evidence Pack exported
Data checklist and signature verifiable
Public wording guidance
Public pages should use accurate, restrained and verifiable wording.
When presenting data to consumers and partners, focus on identity, data source, evidence, update time, disclosure scope and responsibility boundary, instead of misleading phrases such as external endorsement, absolute genuine claims or automatic market admission.
Recommended wording
Expressions to avoid
Start preparing
Start by organizing product identity, public information and supporting materials, then gradually upgrade to DPP.
Suitable for brand merchants, cross-border sellers, SME manufacturers, distributors and high-value product teams that need a lower-cost, maintainable product data entry point.
Go to the merchant portal to prepare data
Contact us for onboarding advice
Service contact email:mike@gexyral.com