Save a GS1 Digital Link as a dated source
Separate the identifier encoded in a GS1 Digital Link from the web page it actually opens, and preserve both in a dated note.
A code on a food pack opens a web page. You now have two pieces of evidence: the address read from the code and the destination shown by the browser. Saving only a page title loses the connection between them, especially if the destination changes later.
Read a bounded syntax example
The GS1 Digital Link URI Syntax standard shows how identifiers can be represented in a web address. Consider its example structure https://brand.example.com/01/09520123456788/10/ABC123. This is a documentation example, not an operating food-information service or a verified product page.
| Part | Meaning in this example |
|---|---|
| brand.example.com | The example web domain |
| 01 followed by 09520123456788 | The GTIN field and its 14-digit representation |
| 10 followed by ABC123 | A batch or lot qualifier |
The standard's current URI format uses a 14-digit GTIN representation, including filler zeroes for shorter GTIN formats. Keep the original address exactly as captured. Do not delete the lot qualifier or the initial zero while creating a shorter note.
Record the visit as a separate observation
For an actual package, create a record with these fields:
- Package identity and the photograph that shows the code.
- Original decoded address, if the scanning workflow exposes it.
- Parsed identifier fields, with uncertain fields marked unresolved.
- Final browser address and the page title actually displayed.
- Access date and time, plus a separate publisher update date if one is shown.
- The specific ingredient or nutrition section used, including its product and serving context.
If the browser exposes only the final page address, say that the original encoded address was not captured. Do not reconstruct it from the product name. If the page fails to load, save the observed error and time rather than describing an unseen destination.
A recognizable address is not a content guarantee
GS1 explicitly cautions that an address following this syntax must not automatically be assumed to point to a conformant resolver. Even where a resolver is involved, reading an identifier and reading the linked content are separate operations. The identifier alone does not supply a nutrient value or prove that the destination matches your package version.
When revisiting a page, retain the earlier observation if the destination or its content changes. Compare the full product, market and quantity details before updating your working record. This workflow records what you could actually inspect; it does not certify the website, authenticate the food or implement a complete GS1 parser.
For your next ingredient-label check, explore Ingredi AI through the official Apple listing or official Google Play listing. Keep the package and source note available while checking any captured result. Digital Link decoding or resolver support has not been verified for the app by this guide.