GEXYRAL provides record and verification infrastructure
GEXYRAL provides product identity, structured fields, evidence indexes, machine-readable output, viewing scopes, record indexes and evidence archive exports.
DPP service provider · Responsibility boundary
We provide recordable, exportable and reviewable DPP infrastructure. Product information responsibility remains with the publishing merchant.
GEXYRAL does not make compliance conclusions on behalf of merchants. It helps organize product identity, structured fields, evidence, public pages, viewing control, machine-readable data and evidence packs into a maintainable record system.
Clarify roles first
DPP capabilities should be professional, but responsibility boundaries must be clear and restrained.
Customers, partners and reviewers need to know who provides the data, what the platform does, whether evidence is traceable and what should not be misunderstood as an official conclusion.
Merchants remain responsible for product information
Merchants, manufacturers, importers or other publishing operators remain responsible for product data, evidence, claims, product compliance and disclosure accuracy.
The platform does not replace testing, certification or legal judgment
As a technical service provider, the platform provides records, versioning, access control, export, signatures and re-checking. Technical verifiability is not a legal conclusion and does not replace testing, certification, regulatory registration or legal advice.
What the platform provides
From product identity to evidence packs, the service provider builds a maintainable record system.
Connect products, batches or items to a stable entry point
Merchants can use PID as a product identity base and add DPP fields, evidence and public notes as needed.
Turn scattered information into maintainable fields
Model, material, origin, batch, maintenance and compliance notes can be recorded as structured fields.
Link claims to evidence instead of plain text only
Reports, certificates, authorizations, media, manuals and declarations can be indexed and tiered by access scope.
Prepare for platform review and system integration
Public fields can produce machine-readable data. Snapshots, record indexes and evidence archives help show version consistency.
Separate public pages, partner review and internal materials
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; other scopes require authorization, and internal data is not exposed publicly.
Merchants can export important record snapshots when needed
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.
Reviewability is not a slogan
Evidence archives, record indexes and signatures help answer whether this version of data is consistent.
They do not replace test reports or legal advice, but they help merchants, customers and partners communicate around one data snapshot.
Evidence Pack
Evidence archives organize field snapshots, evidence indexes, timelines, audit summaries, record indexes and signature records. They support review of data versions and evidence indexes, but are not testing reports, certificates or regulatory conclusions.
Record index and signature
The platform records signatures for record indexes, DPP publication snapshots, machine-readable snapshots, evidence archives or export tasks. Verification keys are managed for later checks of whether records were changed.
Registry-ready pre-check
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.
Suggested path
Start with a sample product set before expanding to more SKUs and batches.
For small and medium merchants, DPP should not start as an oversized project. A practical path is to first complete identity, fields, evidence, public pages, viewing scopes and export flow.
Confirm product identity and publisher
Decide whether the record is product-level, batch-level or item-level, and who publishes it.
Organize fields and evidence
Organize descriptions, reports, certificates, declarations, media and maintenance notes into fields and evidence indexes.
Set disclosure scope and viewing scopes
Consumers see essential notes, partners can review controlled evidence, and internal materials remain internal.
Publish a snapshot and keep version traces
After publication, keep timestamps, completeness, public fields, evidence archives, record indexes and change history.
Suitable scenarios
The point of this page is to show how the platform helps merchants manage product records clearly.
SME manufacturers
Start with representative products to reduce repeated document requests from customers.
Cross-border sellers and brands
Put product notes, materials, batches, evidence summaries and partner-reviewable records into one entry point.
Customers, channels and platform review
Show key support through public pages and controlled materials without exposing sensitive files.
Data retention and exit
Merchants need not only to publish DPP records, but also to know how data is retained, exported and migrated.
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 by contract or applicable law.
Shutdown or migration contingency
In case of service interruption, migration, domain changes or system maintenance, the platform should prioritize public notices for published DPP records, data export, evidence archive download, record-index re-checking and merchant migration communication.
Compliance wording boundary
You can say records are reviewable, not that the platform has completed external review for you.
GEXYRAL helps merchants build product identity, DPP public pages, evidence archives, machine-readable data, record indexes, signatures and viewing scopes. These support data governance and version review, not market access, testing certification or regulatory conclusions.
No external official conclusion is claimed
No automatic market-access promise
Does not replace test reports
Does not replace legal advice
Next step
Start with one product and create a DPP record customers can understand and partners can review.
Choose a representative product or batch first, complete PID, structured fields, evidence, viewing scopes and evidence pack, then copy the workflow to more products.