A QR code can lead to the correct product page and still display the wrong product image. The common cause is not scanning but a weak asset supply chain: a filename is mistaken for a product identity, a campaign graphic overwrites a neutral packshot, or an old packaging variant remains available at the same URL.
In July 2026, GS1 ratified the Product Image Standard 5.0. The new major release incorporates the previously separate Sharing/Delivery Guideline into the standard. Capture, storage, naming, metadata, usage rights and technical delivery are therefore no longer split across separate documents. For manufacturers, retailers and operators of QR destinations, this is a useful moment to treat product images as versioned master data rather than decorative files.
What version 5.0 actually changes
The standard is not new product legislation and does not mandate a particular image system. It is a GS1 framework for digital images associated with products and shared between organisations. According to its change log, release 5.0 merges the unique content of the “GS1 Product Image Sharing/Delivery Guideline” into the expanded image standard. Its name, structure and wording were also cleaned up. The GS1 reference directory records version 5.0 as last modified on 17 July 2026.
The important change is therefore less about a new file format than an end-to-end model. An image is not created for only one web shop. It is supplied by an image provider, processed by multiple recipients and potentially delivered through retailers, data pools, product pages, apps or QR entry points. The standard connects asset quality with the way recipients reliably reach the correct file.
Separate the master asset from web derivatives
GS1 recommends storing product images as high-quality, content-rich master files. Formats and sizes for different channels can then be derived from those masters. This prevents every recipient from scaling or editing an already compressed web file again.
In practice, that creates two layers. An approved master asset, such as a high-quality TIFF or another suitable source format, remains in the internal repository. A delivery layer creates JPEG or PNG derivatives for the web, mobile applications and product-data feeds. A derivative may be regenerated, but its product assignment, validity and source must not change with it.
Filename, product and asset are three identities
The GS1 standard uses structured filenames that can contain the GTIN of the depicted product as well as the type and purpose of the image. At the same time, it makes an important distinction: that filename is not a GS1 identifier for the image file itself. The GTIN identifies the trade item, not the digital asset. Where a non-traded image file is identified as a digital document, the standard points to a Global Document Type Identifier, or GDTI.
This distinction matters for data models. One product can have many images: front, side, package, detail, application, sustainability information or a picture of the printed 2D code. Conversely, one campaign image can depict several products. A long-term system therefore needs more than a relationship saying “product has image URL”.
A dependable asset object needs at least its own internal ID, the associated GTIN or product ID, image type, approval status and version. It may also need a GDTI, language, Consumer Product Variant, viewing angle and packaging state. The filename remains useful for exchange and troubleshooting, but it is not the only source of truth.
Give each image a direct, stable URL
In the Global Data Synchronisation Network model, product images are not distributed as binary files inside the data record. Links to accessible images are exchanged instead. Version 5.0 describes delivery through a shared URL. Each file should be directly accessible; known problems include broken links, corrupted or unsupported files, password protection and pages where a person must navigate manually to find the image.
The same directness matters for QR destinations and product-data APIs. A URL should return one asset in a defined format, not a gallery or sign-in page. The server should provide the correct media type, keep redirects controlled and return the same resource reliably on repeated requests.
This does not mean that a product URL may expose only one image. A GS1 Digital Link resolver can make multiple typed resources discoverable for one product identity. The image resources still need unambiguous destinations. The resolver handles selection and linking; the asset system remains responsible for the file, version and permission.
Metadata determines which image is correct today
Version 5.0 includes an extensive metadata list. It covers fields such as GTIN, product and brand name, image type, filename, creation date, valid-from date, expiration date, version number, legal owner, usage rights, language and quality-assurance date. Alternative text is also included as optional metadata.
Not every organisation needs to populate every field immediately. Five decisions should never live only in the filename: Which product is depicted? What role does the image have? In which markets and languages may it appear? When is it valid? Who may modify or redistribute it?
Start and end dates are particularly useful during a packaging transition. A future image can be distributed before it becomes visible. After expiry, it can be removed automatically from customer-facing views without deleting the historical record. That is more precise than a manual file replacement on launch day.
Usage rights belong in the delivery process
A technically accessible image is not automatically free to use. The standard describes common boundaries: recipients may often resize an image proportionally or convert its format. Changing text or language, using it in the wrong territory, or displaying it before or after an agreed period may be prohibited.
An image API should therefore provide more than the file. It should at least link to a record containing the owner, rights profile, validity and permitted context. A retailer can then check country, language, channel and date before publication. Where rights information is missing, the organisation needs an explicit default policy rather than a silent assumption.
Multilingual delivery is not a late filename suffix
The standard provides language indicators in the filename where an image set is language-dependent. This matters for packshots, instruction images and claims containing visible text. A new language version is a separate governed asset; it should not be produced by automatically editing another language if that would change packaging information or approval status.
Alternative text also depends on context. The GS1 standard lists it as metadata, while the W3C decision tree for text alternatives distinguishes informative, functional, redundant and decorative images. A neutral packshot on a product detail page therefore needs a different treatment from the same image used as a link or displayed next to equivalent text.
An image of a 2D code also needs version control
The standard defines a technical image type for 2D barcodes, including QR codes using GS1 Digital Link URI syntax and GS1 DataMatrix. It gives these images a minimum size of 600 by 600 pixels and a structured naming pattern. GS1 also warns that images of 2D codes may be scanned at any time by partners or consumers and need to remain current when linked content changes.
This is separate from print-quality verification. A high-resolution image does not prove that the actual code will scan on curved, glossy or damaged packaging. The asset process must say whether a file is a production original, a documentation photograph or an illustrative rendering of the code.
A practical acceptance test for image URLs
Approval should cover more than appearance. An automated test can confirm that the URL works without authentication, returns an expected image media type, meets minimum dimensions and does not redirect to an HTML gallery. A hash or version ID can reveal whether the delivered file changed without a new approval.
The business test complements those technical checks. GTIN and product variant must match, type and language must be correct, the validity period must cover the publication date, and rights must permit the target channel. Informative images also need suitable alternative text. For a 2D code, the production sample must be scanned in the real world.
Together these controls create a small but complete supply chain: approved master asset, reproducible derivative, explicit asset relationship, direct URL, machine-readable metadata and monitored validity.
The consequence for QR and product-data projects
The GS1 Product Image Standard 5.0 shows that product images are not attachments to add at the end of a data project. They have their own identity, lifecycle, rights and quality properties. Storing only a file path beside the GTIN loses those relationships at the first packaging, language or campaign change.
QR destinations, product-data feeds and future product passports therefore benefit from an asset registry that publishes images under controls comparable to other product information. The QR code remains the entry point. Whether the correct, valid and usable image appears behind it is decided by a well-operated asset supply chain.
Sources
GS1 Product Image Standard, Release 5.0, July 2026
