Translate GS1 barcode labels accurately by preserving GTIN-14, SSCC-18 and GS1 Application Identifiers such as (01), (10), (17) and (21) across languages. The practical search intent is straightforward: a multilingual packaging, logistics or product-data team needs to describe a scanned label in another language without changing product identity, batch traceability, expiration information or logistic-unit meaning.
The digits inside a GS1 label are not simply numbers that can be styled for a new market. AI (01) identifies a GTIN field; AI (00) identifies an SSCC logistic-unit field; AI (10) marks a batch or lot; AI (17) marks an expiration date; and AI (21) marks a serial number. Changing a code, losing leading zeros or misreading a YYMMDD date can damage the connection between physical goods and digital records.
This guide explains how to translate GS1 barcode meaning, GS1-128, GS1 DataMatrix, 2D Digital Link identifiers, printed human-readable text, batch dates, serial numbers and scanner data. It solves one specialist problem—preserving structured barcode fields in multilingual documentation—without competing with broader translation methods, vocabulary learning or supply-chain systems.
One-minute GS1 translation map
(00) SSCC logistic unit; (01) GTIN trade item; (10) batch or lot; (17) expiration date in YYMMDD; (21) serial number. These parenthesized labels are a human-readable way of showing application identifiers. The actual barcode must follow the correct GS1 syntax, field lengths, character rules and separation requirements. Your translation may change a heading such as ‘expiry date’ into an approved local-language equivalent, but it must not change the encoded field or conflate the identifier with its value.
The most useful mental model
Did you know that a row of apparently ordinary digits can describe entirely different things depending on a short numeric prefix? A string after AI (01) is a trade-item identifier; after AI (00), a different field identifies a logistic unit. AI (17) tells the reader that the following six digits form an expiration date. A translator who guesses meaning from the number alone is likely to produce a fluent error. The field identifier, packaging level and related product master data supply the missing grammar.
A GS1 label may serve several audiences. A scanner reads encoded data under technical rules. Warehouse software associates identifiers with shipments and stock. A worker reads printed text. A consumer reads product information. The translation may affect the latter two experiences, but the first two depend on stable syntax and identity. Good localization therefore separates human-language strings from machine-readable fields and connects them through controlled mappings. Do not let a design change turn an identifier into a slogan.
Another difficulty is that dates and quantities look naturally translatable. A six-digit date might tempt an editor to write a familiar local order, but the date’s meaning depends on the AI. A weight field may encode decimal precision in its identifier. A batch identifier may be alphanumeric, and a serial number may carry leading zeros. These details should be checked against the current source standard, actual encoded symbol and intended market. A label that looks correct in a photograph may still fail a barcode parser or contradict the item master.
Four layers to verify
Syntax: can the barcode be decoded into the intended AI fields? Identity: do the GTIN, SSCC, batch and serial values match authoritative records? Human-readable information: does the printed text express the right field without changing its value? Market compliance: does the consumer-facing wording satisfy the applicable rules and approved claims? These checks have different owners. Passing one does not prove the others passed.
The priority is to preserve traceability and safe interpretation. A translated lot code, a silently reversed date or a case GTIN substituted for a consumer-unit GTIN can break tracking precisely when an organization needs it most. A professional translation record should show not only a bilingual string but also an independently checked decoded value and a link to the source label revision.
Thirty-seven practical GS1 barcode translation cases
1. AI (01) is a field identifier
Source-label situation. A product label displays (01) followed by a 14-digit GTIN. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating 01 as an item number or putting it inside the GTIN changes the parsing boundary. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Explain that 01 identifies the subsequent GTIN data field and preserve its numeric code. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check decoded field against human-readable text and product registry. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
2. GTIN-14 fixed-length field
Source-label situation. The barcode’s AI (01) is followed by exactly fourteen numeric positions. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Deleting leading zeros to improve typography can turn a valid encoded field into a different-length representation. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the full 14-digit field and any validated check digit, distinguishing identity from display formatting. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Compare the raw decoded 14-digit field character by character. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
3. AI (00) and SSCC
Source-label situation. A pallet label has AI (00) followed by its eighteen-digit Serial Shipping Container Code. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Calling the SSCC a product GTIN could make the recipient identify the shipment unit as a saleable item. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Translate SSCC as the logistic-unit identifier and retain the eighteen digits unchanged. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check the actual unit level and supporting shipping documents. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
4. GTIN versus SSCC
Source-label situation. A carton carries trade-item information while the transport unit has an SSCC. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. The same word ‘barcode number’ for both may conceal which physical level is being tracked. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Identify whether each code belongs to a trade item or a logistic unit rather than merging all identifiers. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Trace order, item master and logistic label relationships. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
5. AI (10) batch or lot
Source-label situation. The label contains an alphanumeric batch code after AI (10). The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating the batch code’s letters or treating them as descriptive words could break traceability. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the batch value verbatim, including case and punctuation where applicable. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Match the batch against the manufacturer’s production record. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
6. AI (17) expiry
Source-label situation. The barcode encodes the expiration date in a six-digit YYMMDD field. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Reversing the digits into a locale date without preserving the original can cause an incorrect expiry. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Carry the original YYMMDD representation, then provide an unambiguous localized rendering only after verifying date context. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Compare decoded barcode value and approved human-readable date. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
7. AI (15) best before
Source-label situation. The same product documentation uses AI (15) for best-before information. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Changing best before to expiry can overstate the meaning and change how the date is used. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve the distinct label and ensure the consumer-facing term follows applicable local law and product evidence. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check the encoded AI and authorized packaging claim separately. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
8. AI (11) production date
Source-label situation. A manufactured unit has AI (11) with a YYMMDD date. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Mistaking production date for expiry or sale-by date can reverse product-age reasoning. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Explain what process the date identifies without importing a different date class. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Inspect all date AIs on the label before labeling the field. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
9. AI (13) packaging date
Source-label situation. A shipping label includes the packaging date. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Rendering it as the item’s manufacture or final-use date may be incorrect. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the packaging event distinct from production and consumption-related dates. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Reconcile packaging process record and encoded AI. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
10. AI (16) sell-by
Source-label situation. Some systems distinguish a last-sale date using AI (16). The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. A translation that substitutes best-before or expiration is not safe without the governing product rules. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve the stated sell-by concept and its retailer-facing context. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Compare the field against supplier labeling specifications. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
11. AI (21) serial number
Source-label situation. An individual trade item carries an AI (21) serial value. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Localizing a serial string or stripping zeros can break its uniqueness within the relevant GTIN. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the serial exactly and explain it as an item-level identification component. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check GTIN-plus-serial identity in the tracking system. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
12. Batch versus serial
Source-label situation. The manufacturer has both a shared lot code and individual serial numbers. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Replacing both with an undifferentiated ‘product code’ can defeat a targeted recall or warranty lookup. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Differentiate production grouping from individual-item identity and keep both original codes. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Test retrieval at batch and item levels separately. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
13. AI (02) contained GTIN
Source-label situation. A logistic label uses AI (02) for the GTIN of contained items. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Treating AI (02) as the pallet’s own GTIN reverses the physical relationship. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Explain the contained trade-item role and preserve its required associated data. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Inspect the packing hierarchy and other label fields. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
14. AI (37) contained count
Source-label situation. AI (37) gives a number of contained units in the relevant context. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Calling it a weight or monetary value may cause receiving errors. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the count and its connection to the contained GTIN under the applicable GS1 rules. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Reconcile purchase order, packaging hierarchy and decoded count. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
15. AI (02) with (37) and (00)
Source-label situation. A logistic unit uses the contained GTIN, count and SSCC fields together. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Dropping AI (37) from a translated specification can leave an incomplete logistic-unit description. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Retain all required associated fields and their roles without confusing contained product with outer unit. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Apply the relevant GS1 application-identifier association rules. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
16. Variable-length fields
Source-label situation. AI (10) may be followed by a variable-length batch value. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Assuming every field ends after a fixed number of characters can cause the next AI to be swallowed into the batch. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve scanner parsing instructions and field boundaries, including separator handling where required. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Test with the actual encoded data and decoder output. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
17. Separator rules
Source-label situation. A concatenated GS1 symbol uses separators to disambiguate certain variable-length fields. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Deleting a nonprinting separator from a machine-readable payload while formatting a translation may change field boundaries. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Treat separators as protocol structure, not visual decoration, and describe them in plain language when relevant. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Validate raw data against the GS1 syntax rules and a scanner. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
18. Parentheses are human-readable
Source-label situation. A printed sequence appears as (01) and (17) to show separate fields. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Assuming the parentheses are literally encoded in every machine-readable representation may mislead integration instructions. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Differentiate human-readable interpretation from encoded application identifier elements. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Compare the barcode payload and printed explanation. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
19. GS1 DataMatrix
Source-label situation. The product uses GS1 DataMatrix with structured application identifiers. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Calling it a plain QR code or an arbitrary Data Matrix without GS1 syntax can hide expected decoding behavior. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Name the symbol family actually used and the data syntax present. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check scanner recognition and payload type. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
20. GS1-128
Source-label situation. A shipping case uses GS1-128 rather than a consumer EAN/UPC retail symbol. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating every linear barcode as an identical retail product code hides additional logistic data. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve GS1-128 designation and the application-identifier fields. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Read the actual logistic label specification. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
21. GS1 QR or Digital Link
Source-label situation. A 2D symbol uses a GS1 Digital Link URI that contains item identity and qualifiers. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating or rearranging the URI path can change which item or qualifier the link identifies. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Treat the URI as structured machine data and localize destination content rather than its canonical identity fields. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Resolve and parse the exact identifier URI under the relevant specifications. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
22. Primary-key ordering in URI
Source-label situation. The URI progresses from product identifier to qualifying details such as lot or serial. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. An attractive localized rearrangement of URI components may violate the expected syntax or lookup logic. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve path structure and use a language selection mechanism for pages rather than key reordering. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Test the resulting URI with an appropriate resolver or validator. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
23. GTIN leading zeros
Source-label situation. A system exports GTIN-13 values padded to the 14-position AI (01) format. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Removing zeros from the encoded record because a human catalogue displays fewer digits can corrupt field length. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the standardized field representation, while displaying other formats only with documented conversion rules. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Compare decoded 14-digit value and verified GTIN identity. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
24. Check digit
Source-label situation. The identifier has a calculated check digit used for validation. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Replacing a final digit during translation to match a neighbouring number can create an invalid identifier. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the exact digits and validate with an appropriate calculation or trusted verification tool. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Use a GS1-compatible check-digit test and independent source record. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
25. Variable-measure indicator
Source-label situation. A specification refers to a GTIN indicator or variable-measure configuration. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Treating any indicator 9 as a generic discount or product grade can be wrong. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep the identity and associated measurement-field requirements explicit for the supported use case. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check application-identifier combinations and variable-measure rules. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
26. Weight with 310n
Source-label situation. The label includes a net-weight AI whose final digit indicates decimal places. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Reading 3103 as a literal weight of 3 kilograms rather than an AI with precision semantics changes quantity. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve the full AI and the field’s encoded integer, then interpret decimal placement from the relevant rules. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Recalculate display weight from the encoded field with unit and precision. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
27. Count versus quantity
Source-label situation. The product specification may refer to units per logistic unit, variable count or packaged quantity. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating each as ‘number of products’ without the physical level can cause inventory mismatches. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Attach each quantity to its defined item and packaging hierarchy. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Reconcile the selected AI and master data unit-of-measure. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
28. Human-readable interpretation
Source-label situation. Printed text below a barcode shows decoded GTIN, lot and date labels. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. A translated print layout can look polished while presenting the wrong encoded value. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Cross-check the visible human-readable interpretation against the symbol payload. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Scan the final artwork, not only the draft text. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
29. Barcode artwork QA
Source-label situation. A multilingual redesign changes typography and spacing around the barcode. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Moving text into the quiet zone or resizing a symbol beyond the approved rules may reduce scan reliability. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Treat barcode geometry as a controlled asset and localize accompanying text without disturbing critical dimensions. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Run the required barcode verification and production proof review. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
30. Country prefix misconception
Source-label situation. A reader assumes the first digits of a GTIN prove the product’s manufacturing country. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. GS1 prefix allocation does not by itself establish country of origin. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Translate prefix allocation and country-of-origin claims separately; do not manufacture origin evidence. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Use manufacturer or customs origin documentation for origin claims. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
31. Verified by GS1
Source-label situation. A product manager consults the Verified by GS1 service for brand-owner-supplied identity information. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Calling every registry match a guarantee of product safety, legality or origin overstates what an identity lookup establishes. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Explain the query’s product-identity role and its limits. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Cross-check labeling requirements and separate regulatory evidence. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
32. Expiry and consumer wording
Source-label situation. A packaging team wants a local-language use-by label from an encoded date. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. A direct code-to-text conversion can ignore local legislation, time context and product-specific wording. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Keep encoded data stable, then subject consumer wording to authorized local compliance review. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Compare master data, artwork approval and the applicable local rule. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
33. Multiple GTIN packaging levels
Source-label situation. A single-item pack, inner pack and case may have distinct product identifiers. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating the case GTIN as if it were the consumer-unit GTIN can cause fulfilment or product-listing mistakes. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Record the identification level next to each code and its unit description. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Scan real samples at each level and compare the orderable unit. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
34. Recall by lot
Source-label situation. A company announces a recall for one GTIN and selected lot codes. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating the recall as applying to every item of the brand may wrongly broaden the action; omitting lot codes may wrongly narrow it. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Preserve exact affected identifiers and scope; keep recall instructions under the authorized notice owner. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Cross-check the issuing authority’s current affected-item list. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
35. Language-neutral machine fields
Source-label situation. An integration document has XML or JSON fields holding identifiers and user-facing descriptions. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating machine keys or changing numbers while localizing descriptions risks breaking data exchange. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Freeze API keys and encoded data; translate approved display strings separately. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Use schema validation and bilingual UI tests. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
36. Scanning failure
Source-label situation. A receiving warehouse reports that the translated label’s barcode is not parsed correctly. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Blaming the language alone can hide an encoding, symbology or artwork issue. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Separate machine-symbol validation, syntax validation, data-master reconciliation and language review. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Capture scanner output and compare all layers independently. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
37. SSCC reuse and lifecycle
Source-label situation. A logistics policy includes rules about reusing SSCC values. The surrounding words may vary by language, but the field’s identity and format rules remain central. Read the entire encoded sequence or authoritative decoded output before deciding how to label this value for an operator or consumer.
The error. Translating the rule as permission to recycle codes immediately could create ambiguous shipment records. Even a subtle adjustment can change what a receiving system associates with the physical item. Correct grammar alone does not show that the barcode, product and printed text remain consistent. The translation must be tested against the right level of the packaging hierarchy.
Safe interpretation. Carry the exact policy and effective standard requirements rather than inventing a generic recycling interval. Keep machine identifiers and values untouched while providing a clear target-language label. For a date or quantity, state the meaning established by its application identifier rather than guessing from the digits. When a local requirement affects consumer wording, send that choice through the responsible product-label approval process.
Verification task. Check current GS1 allocation guidance and the organization’s traceability retention rules. Save the original source string, decoded value, approved display text and reviewer conclusion. If the printed label and encoded value disagree, do not reconcile them by improvising a translation; raise a controlled correction request.
Ten-step packaging and barcode translation workflow
Step 1: Read the application identifier before the value
The two-to-four-digit AI identifies what follows and often its field format. The first question is not ‘how should I translate this number?’ but ‘what data field does this code introduce?’ Preserve the code, then apply the approved field interpretation. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 2: Keep the physical identification level
A trade item, a containing logistic unit and the individual serialized item are not interchangeable. Record which unit carries the code before drafting the localized label. A generic translation of ‘product number’ is often insufficient. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 3: Lock identities
GTIN, SSCC, lot and serial codes may have different lengths and formats. Preserve all characters, including meaningful leading zeros and validated check digits. A language editor should not rewrite machine identifiers for typographical elegance. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 4: Interpret dates with the appropriate AI
YYMMDD tells you the encoded format but not by itself which business event the date describes. Distinguish production, packaging, best before, sell by and expiration according to the actual AI and the product’s legal or commercial context. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 5: Recognize variable-length boundaries
Some AIs have fixed fields; others can have variable-length strings requiring precise separation when followed by other fields. Translators working on scanner or ERP instructions should preserve these structural details, not merely the displayed parentheses. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 6: Differentiate barcode carrier from data syntax
GS1-128, GS1 DataMatrix and a GS1 Digital Link URI are not the same presentation. The underlying data meaning may cross carriers, but the exact encoding and reader behavior have to be tested for the delivered artifact. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 7: Translate user-facing language separately
Packaging can show consumer-language words such as lot, serial number, use by and best before while keeping barcode codes invariant. The displayed label must be approved for the market without retroactively changing the machine value. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 8: Verify actual artwork
A barcode that parses in a sample PDF may fail after production if artwork, print quality, contrast, placement or quiet zones are altered. Keep engineering verification separate from linguistic proofreading. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 9: Check traceability relationships
Pair identifiers with the right product, packaging level and source records. A GTIN plus serial identifies an item differently from a GTIN plus batch. Traceability reports and recalls depend on not confusing those relationships. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Step 10: Maintain a sign-off trail
Archive original decoded data, localized artwork, scanner-verification result, applicable GS1 guidance, product-data approval and date of review. When a supplier changes the packaging or data, review again instead of reusing an old translation blindly. Test the reader’s likely action after seeing the new text. A useful translated label allows the same physical item to be identified, traced and handled, not merely described elegantly.
Frequently asked questions
What is AI (01)?
It marks the following GTIN data field, represented in the GS1 application identifier system as fourteen digits. Always use the current relevant GS1 rules and market regulations for a real labeling project.
What is AI (00)?
It marks the SSCC, which identifies a logistic unit and uses an eighteen-digit field. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Are parentheses encoded in a GS1 barcode?
They often help humans read application identifiers in printed interpretation; the machine-readable representation uses its specified syntax. Do not assume printed parentheses are payload bytes. Always use the current relevant GS1 rules and market regulations for a real labeling project.
What does AI (10) mean?
It identifies a batch or lot value, which may be alphanumeric and variable-length within the defined constraints. Always use the current relevant GS1 rules and market regulations for a real labeling project.
What does AI (17) mean?
It identifies an expiration date, encoded in YYMMDD format. Do not confuse it with best-before or manufacturing dates. Always use the current relevant GS1 rules and market regulations for a real labeling project.
What is AI (21)?
It identifies the serial number associated with the particular trade item. Keep the exact character sequence. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Does GTIN always indicate manufacturing country?
No. GS1 prefix allocation is not by itself evidence of where an item was manufactured. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Can I remove GTIN leading zeros?
Not from the fixed-length AI (01) encoded data. Other display formats may use appropriate normalization, but they require a controlled conversion. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Is a batch the same as a serial number?
No. A batch groups production, while a serial can distinguish one unit within a relevant GTIN context. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Can a QR code contain GS1 data?
Yes, GS1 Digital Link can be carried in certain 2D symbols, but the URI structure and applicable encoding rules must be followed. Always use the current relevant GS1 rules and market regulations for a real labeling project.
What is the difference between GS1 and medical-device UDI?
UDI is a regulatory traceability framework using recognized issuing systems in specified jurisdictions. This article instead focuses on the GS1 application-identifier structure common to product and logistics labeling. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Can this guide verify a barcode?
It teaches what to check but does not replace actual scanning, GS1 specification validation, artwork verification or the relevant product/regulatory approval. Always use the current relevant GS1 rules and market regulations for a real labeling project.
Worked example: one product, two packaging levels and an expiry date
Consider a fictional product whose consumer unit has its own GTIN, batch identifier and expiration date, while a pallet carries an SSCC and information about its contained trade items. The product team prepares English and Japanese packaging instructions. A naive translation refers to the pallet’s SSCC as the ‘product barcode’ and then uses it in the catalogue field intended for the consumer-unit GTIN. That is an identity error, not a language preference. The fix begins by drawing a hierarchy: consumer item, case if applicable, pallet. Each identifier is assigned to the correct level. The bilingual terms are then mapped to those fixed meanings rather than guessed from the printing layout.
Next, the manufacturer encodes an expiry date under AI (17). The localized artwork displays a familiar written date while the encoded YYMMDD value remains unchanged. The reviewer confirms that the printed date is the intended calendar date and that it is an expiration date, not the best-before or production date. A different AI would require a different interpretation. The translation does not change the machine data; it helps a reader understand it accurately. If the market requires different mandatory labeling, that is handled as an additional compliance decision with the original source still intact.
Finally, the batch code contains letters and digits. An editor assumes the letters are an abbreviation and translates them, creating a new apparent batch code that does not exist in the manufacturer’s records. A receiving warehouse could no longer reconcile the printed value with the scanner output. Restoring the exact code and translating only the label ‘Batch’ is the right repair. The rule is simple to remember: identifier values are evidence. Their language-independent identity is more important than local stylistic symmetry.
Sources, boundaries and follow-through
Reference GS1 Denmark’s application-identifier table for field formats and meanings and its association rules for required combinations. For two-dimensional product data, see GS1 Finland’s 2D code explanation. For identity lookup context, see GS1 Singapore’s Verified by GS1 overview. Standards and requirements evolve, so verify the current applicable specifications before production. This article is educational and does not certify regulatory compliance, barcode quality or product safety.
Broader translation principles remain under the existing eduKateSG knowledge library, master translation architecture and protected Vocabulary Learning Hub / How English Works ecosystem. This page is a focused field guide for GS1 structured label translation, not a new general hub.