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 兼容
PID and DPP mapping
QR code public query
There is a commodity coding system, and it can also be gradually connected to DPP data preparation.
If a company already uses GTINs, SKUs, lot numbers or serial numbers, GEXYRAL can help you map these existing logos with PID product identities, DPP structured data, Evidence Pack evidence packages, and QR code public queries. The platform does not replace the official registration of GS1, nor does it disguise the GS1 identity of a company. Instead, it reserves a clear, maintainable, and interpretable compatibility path for existing identification systems.
Does not replace official GS1 services
Not mandatory for all merchants to use GTIN
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 have internal SKUs, external GTINs, platform product numbers, batch numbers, and serial numbers. If the DPP system regenerates a completely fragmented set of numbers, subsequent printing, shipping, after-sales, review and data maintenance will become complicated. The idea of GEXYRAL is that PID is responsible for the identity of goods within the platform, GTIN or enterprise codes maintain the original business meaning, DPP is responsible for data and evidence, and the two collaborate through a mapping relationship.
Reduce duplicate QR codes
The same product entrance can enter PID page, DPP page or compatible path according to 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
Do not 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 enterprise does not have a GTIN for the time being, it can use PID to run through basic queries first.
The company has standard product logos
Suitable for brands or manufacturers that have already obtained 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 impersonate each other.
The page seen by the user after scanning the code should be consistent with the merchant's real opening capabilities. Pure PID users enter the basic product record; products with DPP activated enter the digital product passport public page; when there is a real GTIN mapping, the compatibility path is used.
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 入口
It is only enabled when the merchant provides a real GTIN and mapping rules; PID fallback is explicitly used when there is no GTIN to do not create the illusion of official identity.
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 the SKUs, GTIN, batch numbers, serial numbers, old QR codes and channel product numbers 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 PID mapping
Establish a one-to-one or one-to-many relationship between the platform PID and the merchant's existing number, so that the query portal can stably find the correct record.
Complete 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 you use a PID portal, DPP portal, or GS1 compatible URL, the page should help visitors understand the product identity, data source, summary of supporting materials, update time and scope of access. For system docking scenarios, the platform can output machine-readable data corresponding to public fields, but only output content that is allowed to be disclosed or authorized to access.
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 the product identification, mapping relationship, public information, evidence summary and DPP preparation status provided by merchants; however, it will not apply for GS1 code for merchants, does not prove that merchants have official authorization, and does not replace testing and certification, platform review, regulatory judgment or legal opinion. Merchants are responsible for the authenticity, integrity and scope of authorization of the submitted materials.
Do not pretend to be an 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 mapping of PID, DPP data and existing codes.
It is recommended to start pilot projects with products that already have stable SKUs, require export information, and frequently check by customers or have a large number of 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.