Product identity code
Create identifiable records for products, batches or individual items, with support for QR public lookup.
Terms · Service Terms
Before using GEXYRAL, please understand the platform capabilities and data responsibility boundaries.
GEXYRAL provides merchants, brands, cross-border sellers and manufacturers with product identity codes, QR public lookup, DPP data preparation, supporting-material archiving, machine-readable data and Evidence Pack exports. The platform helps data be recorded, displayed and checked more easily, but does not replace testing, certification, regulatory registration or legal conclusions.
01
Platform service scope
These capabilities help merchants turn scattered product information into records that can be displayed, checked and continuously maintained.
Digital Product Passport data preparation
Organize product data around structured fields, data completeness, access scope and later disclosure needs.
Supporting material archiving
Archive indexes of supporting materials such as test reports, certificates, manuals, authorization documents and batch data.
Evidence Pack and snapshot export
Export field snapshots, evidence indexes, Manifests and related records when communication, audit or re-checking is needed.
Merchant responsibility
Merchants, manufacturers or publishing entities are responsible for the truthfulness of the data.
Merchants, manufacturers, importers or other publishing entities are still the responsible economic operators for product information, certification materials, statement content, product compliance and accuracy of external disclosure.
Merchants should ensure that uploaded or entered product names, models, batches, ingredients, origins, test reports, certificates, authorization documents, manuals, images, statements and other data are true, accurate and complete, and that they have the right to display them publicly or authorize relevant parties to view them.
Platform boundary
The platform provides technical record capabilities and does not replace legal conclusions.
As a technical service provider, the platform is responsible for providing recording, version, access control, export, signature and re-inspection capabilities; technical verifiability does not mean legal characterization and does not replace testing, certification, regulatory registration or legal opinions.
Public pages, QR lookup results, risk notices, DPP summaries, machine-readable data or Evidence Packs viewed by consumers or partners are only for understanding and auxiliary verification of product data. They do not constitute an absolute guarantee of authenticity, quality, lawful circulation or compliance status.
02
Rules for public lookup, QR codes and DPP pages
The platform encourages making necessary product data available to consumers, but disclosure does not mean all backend data will be shown externally.
Lookup results are based on what the page shows at that time
Product data may be updated as merchants supplement, correct, review, archive or change publication status. Users should pay attention to the update time, status notices and data completeness shown on the page.
Do not treat QR results as absolute identification
QR public pages help users view product records, entity information, evidence summaries and risk notices, but they are not equivalent to third-party testing, judicial appraisal, regulatory conclusions or brand commitments.
Abnormal information should be judged together with the physical product and transaction context
If repeated scans, high-frequency access, missing data, abnormal status or unclear sources appear, users should further verify with the seller, platform, testing agency or relevant entity.
Abuse of lookup and crawling is prohibited
The lookup service must not be used through malicious requests, bulk crawling, credential stuffing, bypassing access restrictions, forged authorization or other methods that affect platform stability or merchant rights.
DPP data governance
DPP data is disclosed by access tier; not all data is public.
DPP data is graded according to disclosure, consumer, partner, reviewer and internal data. Public information can enter the public page and disclose machine-readable data; consumers, partners, and reviewers need to be authorized to view; internal information does not enter the public page, disclose machine-readable data or general public evidence packages.
Can be included on public pages and in public machine-readable data.
Extended information authorized for consumer viewing.
Authorized data for partners, channels and trade communication.
For audit, regulatory or high-permission review scenarios.
Internal data, not included on public pages or normal public outputs.
03
Evidence Packs, Manifests, signatures and re-verification
These capabilities help prove “what data the platform recorded at a certain time,” rather than directly replacing certificates or test reports themselves.
Evidence Pack
The evidence package is used to organize field snapshots, supporting material indexes, timelines, audit summaries, data lists, and signature records. It is used to review data versions and evidence indexes, and is not equivalent to test reports, certification certificates or regulatory conclusions.
Manifest and signature
The platform will sign and mark the data list, DPP release data snapshot, machine-readable data snapshot, evidence package or export task record. The verification key is kept by the platform according to security requirements and is used for subsequent review of whether the data has been changed.
Registry integration pre-check
Registry-ready means that the platform has completed pre-inspections of fields, evidence, machine readable, Manifest, signatures, access rights, and export capabilities; it does not mean that external Registry registration, regulatory access, or official confirmation has been completed.
04
Accounts, merchant portal and data maintenance
The merchant portal is used to maintain product records and DPP data. Accounts, permissions and data changes should be handled by authorized personnel.
Merchants should properly manage account permissions
Merchants should protect login accounts, operating permissions and authorization credentials to prevent unrelated personnel from changing product data, exporting Evidence Packs, publishing DPPs, adjusting access tiers or viewing non-public data.
Data changes affect public display
When product data, supporting materials, structured fields, publication status or access scope changes, public pages, machine-readable data, Evidence Packs or later exports may change accordingly.
The platform may restrict abnormal access for security reasons
For abnormal requests, malicious crawling, attacks, forged authorization, abuse of integration capabilities, actions affecting system stability or infringing others’ rights, the platform may restrict access, suspend capabilities, retain logs and take further measures.
Merchant exit and data migration
When a merchant quits, you can export Evidence Pack, public field snapshots, field lists, evidence index, Manifest, signature records and access log summaries first. The platform can assist in migration, but does not guarantee the import results of third-party systems.
Service continuity
Service continuity, maintenance and emergency notices
In the event of service suspension, migration, domain name adjustment or system maintenance, the platform should give priority to ensuring the public access prompts, data export, evidence package download, Manifest re-inspection and merchant migration communication of the published DPP.
The platform maintains DPP structured fields, evidence index, access logs, export records, Manifest, signatures and version history based on business continuity, audit traceability, and security needs. The specific retention period can be configured by the platform in the background and can be adjusted according to contract or applicable legal requirements.
Responsibility boundary
In simple terms: the platform records data clearly; merchants are responsible for the truth and reliability of the data itself.
GEXYRAL’s value is to make product identity, data versions, supporting materials, access scope and verifiable records clearer. Users should still make comprehensive judgments based on transaction sources, physical products, seller commitments, test reports, after-sales evidence and applicable laws.