Keep existing numbers
Commodity logos that have been printed, filed, and circulated in channels do not need to be easily overthrown. A mapping can be established first and then public information can be gradually sorted out.
GS1 / GTIN compatible
Mapping PID and DPP
Public QR lookup
There is a product coding system, and it can also be gradually connected to DPP data preparation.
If your company already uses GTIN, SKU, batch numbers or serial numbers, GEXYRAL can help map those existing identifiers to PID product identity, structured DPP records, evidence archives and public QR lookup pages. The platform does not replace GS1 number application, authorization or entity eligibility checks, and it does not pretend that a company has GS1 status. It provides a clear, maintainable and explainable compatibility path for existing identifier systems.
Does not replace GS1 official services
GTIN is not mandatory for all merchants
Run through a batch of products first, and then gradually expand
Why do you need this page?
Merchants are not concerned about terms, but whether existing codes can continue to be used in the future.
Many companies already use internal SKUs, external GTINs, platform product IDs, batch numbers and serial numbers. If a DPP system creates a disconnected identifier set, printing, fulfillment, after-sales service, review and data maintenance all become harder. GEXYRAL’s approach is to let PID handle product identity inside the platform, keep GTIN or company codes in their original business role, and let DPP carry records and evidence through a mapping relationship.
Reduce duplicate QR codes
The same product entrance can enter the PID page, DPP page or compatible paths based on merchant configuration to avoid copying many codes for different systems.
Data can continue to be completed
First disclose the basic identity and explanation, and then supplement the source of the material, test report, declaration document, JSON-LD and Evidence Pack.
Express it more clearly to the outside world
When customers and partners open the page, they can understand what the logo represents, where the data comes from, what content can be made public, and what content needs authorization to view.
three-level relationship
Don't mix PID, GTIN and DPP into one concept.
A truly maintainable design should separate identity, coding, data, evidence and access rights. This is not only convenient for merchants to maintain, but also convenient for customers to understand.
Product identity within the platform
Used to establish GEXYRAL internal product records, code scanning inquiries, risk warnings and historical traces. Even if the company does not have GTIN for the time being, it can use PID to run basic queries first.
The company has standard product logos
Suitable for brands or manufacturers that have acquired and maintained GTIN. The platform only records the logos provided by associated merchants, and does not apply for or prove official qualifications for merchants.
Digital product passport information
Carries structured fields, public statements, material sources, supporting document summaries, access rights, machine-readable data, and Evidence Pack.
Manage granularity
Different companies can gradually access them by commodity, batch or single item.
Not all products need to be single-piece at the beginning. The key is to first identify business needs, printing costs, data maintenance capabilities and customer verification scenarios.
Product/Model Level
It is suitable for goods with relatively stable styles, models and specifications, and is used to disclose basic information, brand information, instructions and general certification materials.
lot-level
Suitable for each batch of raw materials, test reports, production dates or shipment batches of goods, and correlate evidence and records from the same batch.
Serial number/single piece level
Suitable for high-value, strong after-sales, strong traceability or one-thing-one-code scenarios, allowing a single item to have a more detailed life cycle record.
QR code entry
PID, DPP, and GS1 compatible links must be used in layers and cannot pretend to be each other.
The page shown after a scan should match the merchant’s actual enabled capabilities. Products with only PID enabled should enter the basic product record, while products with DPP enabled can enter the digital product passport. If a compatible GS1-style path is used, the page must still explain the source and limitations of the mapping.
Basic commodity identity entrance
It is suitable to first establish QR code public inquiry, product identity, merchant entity and data update time.
Digital Products Passport Entrance
Ideal for displaying structured fields, supporting material summaries, Evidence Pack, access levels and machine-readable data readiness.
GS1 compatible entry
Use this only when the merchant provides a real GTIN and mapping rule. Without GTIN, use the PID lookup entry clearly and do not imply external authorization.
access procedure
It is recommended to conduct a batch of pilot projects first, rather than modifying the entire system at one time.
The focus of the compatibility solution is not to make the page complex, but to allow stable collaboration between coding, data, evidence, permissions and public inquiries.
Inventory existing logos
Sort out SKU, GTIN, batch number, serial number, old QR code and channel product number to confirm which ones need to be retained.
Determine management granularity
Select the right level by product, model, batch or single piece to avoid overdoing maintenance costs in the first place.
Establish a PID map
Establish a one-to-one or one-to-many relationship between the platform PID and the existing merchant numbers, so that the query portal can stably find the correct records.
Supplement DPP data
Fill in public fields, business fields, and controlled fields, and bind supporting materials to key fields.
Test QR code path
After confirming the scan, enter the correct page. Customers can understand the record status and partners can get a summary of the required data.
Gradually expand products
Start with high-frequency exports, key customers or high-value commodities, and then replicate to more commodities and batches after stabilization.
public data
The compatibility portal will eventually fall on "readable, searchable, and maintainable" data.
Whether the entry uses a PID path, a DPP path or a GS1-compatible URL, the page should help visitors understand product identity, data source, publisher, evidence status and available review methods without misleading them into thinking that a technical compatibility path equals official GS1 authorization.
identificationPID/ GTIN / SKU/Batch/Sequence
parsingEnter the corresponding product public record
informationFields, evidence, permissions and update time
checkCustomers, partners or reviewers view according to permissions
boundary statement
GS1-ready does not mean official registration of GS1, nor does it mean automatic compliance.
GEXYRAL can record and display product identifiers, mapping relationships, public records, evidence summaries and DPP readiness status provided by merchants. It does not apply for GS1 numbers on behalf of merchants, does not verify manufacturer eligibility, and does not present technical compatibility as an official external conclusion.
Do not pretend to be the official GS1 service
No substitute coding application or certification
Don't disguise PID as GTIN
No absolute guarantee of authenticity of goods
Next step
Select a batch of products first and run through the PID, DPP data and the existing code mapping.
It is recommended to start piloting from products that already have stable SKU, require export information, and customers frequently check or have more certification materials. Establish a clear public page and data flow first, and then decide whether to expand to the batch level or single item level.