A supplier’s certificate, inspection record or declaration may carry a document identifier. That is useful for finding the intended file, but the identifier and the document’s substantive authority are different questions. GS1’s serialisation explanation lists the Global Document Type Identifier, GDTI, among keys with an optional serialisation element. This article uses that narrow point to explain document tracking, not to validate a certificate. The source was read on 3 October 2026.

Decide what the record is identifying

A document collection can contain a general form, an individual completed document and a later revision. Before entering an identifier into a supplier evidence file, establish what the issuer says it represents. Do not assume every visible number identifies the exact copy under review. Where an optional serial element is used, retain it with the base value instead of discarding it during import.

GS1 describes serialisation as identifying individual instances. That helps explain why an instance-level reference can matter when many similar files exist. It does not tell this editor which real document a supplier intended to send. The actual issuer’s mapping and the file contents still need to be checked.

Keep identity and authority in different fields

The evidence record can separately hold the supplied identifier, the issuer named on the document, the file title, the relevant product or site, the issue information and the source from which the file was obtained. These fields help a reviewer trace the item without turning its number into a quality badge.

An identifier does not establish that the named issuer approved the document, that every listed activity is covered, or that the document applies to the current shipment. A real certificate question requires an appropriate issuer or scheme check. A shipment question requires an explicit connection to the relevant goods. Do not infer either connection merely because the document is machine-readable.

Handle a changed file as a changed observation

If a supplier resends a file with the same visible reference, compare what changed and keep the earlier observation. The buyer should know whether a corrected name, added site or altered scope appeared later. This is a document-control recommendation, not a rule for issuing GS1 identifiers or a claim about how any particular scheme handles revisions.

For a practical handover, retain the received file and record the date it was reviewed. Ask the issuer or supplier to explain ambiguities in the reference. Do not silently invent an instance number, relabel the file as verified, or treat a successful lookup as acceptance of all its contents. Technical encoding decisions require the applicable current specifications, which this article does not reproduce.

What a useful conclusion looks like

Our editorial judgement is that document identity should make evidence easier to retrieve, while authority and applicability remain separately visible. That reduces confusion between “we can find this file” and “this file proves the required claim.” No actual identifier, supplier certificate or shipment was evaluated here.

The precise identifier meaning, issuer confirmation and transaction connection are Needs editor verification in a live case. The GS1 support explanation is mechanism context, not approval of a supplier. Failed attempts to retrieve other specifications were not used as if their full bodies had been read.

Source: GS1 serialisation explanation. No identifier allocation or compliance service is offered.