To translate GTIN, UPC and EAN barcode information accurately, a translator must separate product identity from the words printed on the package. Retail labels, catalogues, e-commerce feeds, product master data and logistics records can place brand names, descriptions, sizes, Global Trade Item Numbers and barcode symbols in the same record. The human-language content may need translation; the trade-item identifier normally must remain exact. One altered digit can make the target record refer to another product or fail validation entirely.
This guide explains how to translate product and retail data without changing GTINs, UPC-A numbers, EAN-13 numbers, GTIN-14 values or GS1 barcode payloads. It solves one distinct search intent: what does GTIN identify, how do UPC and EAN barcode forms relate to GTIN, which digits must remain protected, why a barcode is not merely an image, and how can multilingual product information stay attached to the same trade item after translation?
The working rule is translate the product description, preserve the GS1 trade-item key, identify the GTIN format and packaging level, and verify the human-readable and machine-readable forms after layout. GS1 uses GTINs to identify trade items; GTINs can appear in 8-, 12-, 13- or 14-digit structures depending on the use case, while UPC-A commonly carries GTIN-12 and EAN-13 carries GTIN-13. The identifier belongs to the trade item, not to the language of the product description. This specialist branch connects to Master Art of Translation, the protected Vocabulary Learning Hub, and How English Works without creating a competing retail, packaging or logistics hub.
GTIN identifies a trade item
GS1 uses the Global Trade Item Number to identify products and services that may be priced, ordered or invoiced. It is not the product name or marketing description. Preserve the GTIN exactly. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is a family of key lengths
GS1 supports GTIN-8, GTIN-12, GTIN-13 and GTIN-14 structures. Calling every code a 13-digit EAN creates format errors. Keep the actual key length visible. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
UPC-A commonly carries GTIN-12
The UPC-A barcode used widely in North America encodes a 12-digit GTIN. Adding a digit because another system expects GTIN-13 changes the displayed key unless conversion is explicitly defined. Preserve the source representation. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
EAN-13 carries GTIN-13
EAN-13 symbols encode 13-digit GTINs. The term EAN often refers to the barcode symbology while GTIN refers to the identification key. Keep key and carrier concepts distinct. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN-14 supports trade-item configurations
GTIN-14 is commonly used for higher packaging levels and logistics-oriented trade-item identification. Copying a consumer-unit GTIN into a case-level field can identify the wrong packaging configuration. Verify package level. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN-8 supports small-item identification
GTIN-8 can be used where packaging space is constrained under GS1 allocation rules. Padding it casually to resemble a longer key can break identity. Preserve the assigned key. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Check digit supports validation
GTIN structures include a check digit calculated under GS1 rules. A valid check digit can catch some typing errors. Validation does not replace product relationship checks. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
A valid GTIN can still be the wrong product
Another item’s valid GTIN will pass check-digit validation. Row shifts and stale templates can therefore survive syntax QA. Confirm brand, variant, size and package level. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is not a SKU
Retailers and manufacturers can assign internal stock-keeping units. SKUs are organization-specific while GTIN is a standardized trade-item key. Keep both namespaces separate. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is not a model number
Electronics and equipment can have manufacturer model numbers beside GTINs. The model family may cover several sellable configurations. Preserve both fields. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is not a serial number
GTIN identifies a trade item class or configuration, not one unique physical unit. Serialized products require another identifier layer. Do not put serial data in GTIN fields. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is not a lot number
Lot or batch identifies production groups. Many lots can share one GTIN. Keep production and trade-item identity separate. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is not an SSCC
SSCC identifies a logistics unit such as a pallet. A pallet can contain products with GTINs. Keep logistics-unit and trade-item identity separate. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GTIN is not a GLN
GLN identifies parties and locations under GS1 standards. A supplier GLN and product GTIN can appear on the same order. Label key type explicitly. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Brand name can be translated or localized separately
Products can have market-specific brand or display names. A name change does not authorize the translator to alter the GTIN. Keep marketing and machine identity separate. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Product description is translatable content
Descriptions explain flavor, size, function, material or use. The translated description should still correspond to the same GTIN. Verify attributes after translation. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Variant matters
Color, flavor, size, count and configuration can distinguish trade items. Dropping a variant word can make two different GTINs look like the same product. Preserve variant meaning. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Net content is another structured field
Package quantity or volume can distinguish trade items. Unit conversion or rounding can make the target description inconsistent with the GTIN. Keep quantity exact. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Package level matters
Each packaging hierarchy can have its own trade-item identity under GS1 rules. Using the each-level GTIN on a case record creates a false master-data relationship. Verify packaging hierarchy. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Indicator digit can appear in GTIN-14 contexts
Certain GTIN-14 constructions use an indicator associated with packaging configurations under GS1 rules. Treating the leading digit as removable padding can change the key. Preserve all 14 digits. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GS1 Company Prefix contributes to key construction
Organizations can create GS1 keys using licensed company-prefix capacity under allocation rules. The prefix is not a translatable country label. Preserve the full GTIN. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GS1 prefix does not prove country of origin
Prefix allocation does not mean the product was manufactured in that country. Translating it as origin information creates false labeling. Use explicit origin fields. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Barcode is a carrier, not the identity itself
UPC-A, EAN-13, ITF-14 and GS1 DataMatrix can carry identifiers. The GTIN is the data key; the symbol is one machine-readable representation. Keep data and artwork layers distinct. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Human-readable interpretation should match barcode data
Printed digits appear near many retail barcodes. A mismatch can cause scanning and manual-entry errors. Decode and compare after localization. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Barcode artwork should not be recreated from translated text
The bars encode the identifier mathematically. Changing nearby wording should not trigger a new barcode payload. Use authorized source data. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Quiet zones matter
Linear barcodes require clear areas around the symbol for reliable scanning. Expanded translated text can crowd the barcode. Protect machine-readable layout space. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Barcode dimensions matter
Scaling or distorting symbols during localized artwork production can reduce scan quality. A visually attractive redesign can become operationally unreliable. Retest final artwork. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Color contrast matters for scanning
Packaging localization can alter background and print colors. Poor contrast can reduce barcode performance. Follow GS1 symbol-quality guidance. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
UPC and EAN labels are often used loosely
Retail teams may call a number UPC, EAN or barcode interchangeably. The underlying key length and symbology should still be identified correctly. Use precise data-field names. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Leading zeros are significant
GTIN representations can contain leading zeros, especially in database normalization contexts. Spreadsheet conversion can remove them. Store identifiers as text. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Database systems can normalize GTINs to 14 digits
Some master-data systems store shorter GTINs in a 14-digit database field using leading zeros. The normalized storage form should not be confused with the printed barcode representation. Label normalization explicitly. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Do not add thousands separators
Locale formatting can group long digit strings. A grouped GTIN is no longer the standard identifier display. Disable numeric formatting. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Do not localize numeral glyphs
Target languages may use different numeral forms in ordinary prose. Barcode keys and lookup systems expect standardized digits. Translate labels, not the key. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Product names can be identical across sizes
Two package sizes can share the same brand and product name while carrying different GTINs. Name matching alone can merge distinct trade items. Check net content and GTIN. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Multipacks can have distinct GTINs
A multipack can be a separate trade item from its individual units. Using the single-unit GTIN for the pack can break ordering. Verify sellable configuration. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Promotional packs can require identity decisions
Bundles and promotional configurations may have GTIN allocation implications. Translators should not decide whether a new GTIN is required. Use authorized master data. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Product reformulation can affect identity governance
Significant changes can have GTIN management implications under GS1 rules. Language editing alone is not a trigger for inventing a new key. Keep governance with the brand owner. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Packaging redesign does not automatically mean a new GTIN
Artwork can change while trade-item identity remains or changes according to GS1 management rules. Translators should not infer key changes from design. Use current source data. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Market-specific labels can share or differ in GTIN according to governance
Products sold in multiple markets can have different packaging and regulatory text. Do not assume language version alone determines GTIN. Verify the actual market master data. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
E-commerce feeds need exact GTIN matching
Online marketplaces use GTINs to match product records. A translated title attached to the wrong GTIN can merge listings. Check product attributes and key together. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Catalogues can contain both SKU and GTIN
Internal SKU helps the seller; GTIN supports standardized trade-item identification. A spreadsheet column shift can swap them. Use explicit headers. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Purchase orders use GTIN for item identity
EDI and procurement messages can reference GTINs rather than translated descriptions. Changing the description should not change the key. Preserve structured order data. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Invoices can repeat GTINs
Invoice lines can identify trade items by GTIN plus quantity and price. A translation should not recalculate or replace the key. Keep financial and item fields separate. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
GS1 DataMatrix can encode GTIN plus additional data
Machine-readable carriers can combine GTIN with lot, expiry or serial information using application identifiers. The full carrier contains more than the trade-item key. Know whether the target field expects GTIN only or encoded element string. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Application Identifiers are machine syntax
GS1 AIs indicate the meaning of following data elements. They are not ordinary parenthetical numbers to translate. Protect the encoded syntax. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Lot and expiry remain separate data elements
A DataMatrix can carry GTIN, batch and date together. Copying the entire string into a GTIN field creates an invalid key. Separate parsed elements. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
OCR is not barcode decoding
Reading printed digits from an image can introduce transcription errors. The barcode itself can provide a stronger machine-readable check. Decode and compare when possible. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Spreadsheets can convert GTINs to scientific notation
Long numeric strings are vulnerable to automatic formatting. Precision or leading zeros can be lost. Import as strings. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
CSV needs explicit schema
A bare 13-digit number could be GTIN-13, GLN or another key. Without namespace metadata, translators can mislabel it. Store key type. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Machine translation should lock GTINs
MT can insert spaces, localize digits or expand labels inside mixed fields. A fluent target can break product matching. Protect identifier strings. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Translation memory can carry another product’s barcode
Packaging text repeats across flavors and sizes. High TM matches can reuse stale GTINs. Populate identifiers from current artwork or master data. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Search-and-replace can alter many products
Bulk digit or punctuation rules can touch every barcode number in a catalogue. One global edit can break thousands of items. Restrict edits to translatable fields. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Worked example: one product, several packaging levels
A fictional beverage has one GTIN for a bottle and another for a case. The target translates flavor and quantity descriptions while preserving both keys. Keep packaging level explicit. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Worked example: GTIN and GLN
A fictional order contains supplier GLN and product GTIN. Both can be 13 digits but identify different things. Use namespace and role labels. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Worked example: DataMatrix
A fictional medical product encodes GTIN, lot and expiry in one GS1 carrier. The target artwork preserves the encoded data and localizes surrounding labels. Verify by scanning. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Error clinic
Common failures include leading-zero loss, GLN/GTIN swaps, SKU substitution, barcode mismatch, package-level confusion and localized digits. These errors can survive fluent product copy. Run dedicated trade-item QA. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Release checklist
GTIN length, check digit, product variant, packaging level, net content, barcode payload and human-readable digits all need verification. Checking only product names is insufficient. Validate both key and product relationship. Treat the product description as translatable, the GTIN as protected, and the product-to-package relationship as something to verify after export. This prevents a correct key from being attached to the wrong size, flavor, multipack or case.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Frequently asked questions
GTIN, UPC and EAN identifier values should not be translated. Users often ask whether UPC and GTIN are the same thing. Explain that GTIN is the identification key while UPC-A and EAN-13 are common barcode carriers/representations for specific GTIN lengths. The practical test is trade-item traceability. A reviewer using only the target should be able to resolve the same product record and understand which packaging level the identifier belongs to.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Connection to eduKateSG architecture
This specialist owner protects trade-item identity rather than broad retail or packaging translation. A new product hub would overlap existing logistics owners. Use this page for GTIN/barcode identity and other pages for shipping, location or customs codes. For structured files, store the GTIN as text with an explicit key type and exclude it from locale formatting, automatic numbering and generative rewriting. Translation can then change marketing language around a stable trade-item key.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Authoritative sources
GS1 General Specifications and GTIN management standards govern the key and barcode use. Local GS1 Member Organizations support allocation and implementation. Verify product keys against authoritative master data. A strong reviewer checks both directions: start from the target product attributes and confirm the GTIN, then start from the GTIN and confirm the same brand, variant, net content and packaging configuration.
Before release, ask what the field identifies: trade item, location, logistics unit, serialised unit or internal SKU. The target should make that scope visible instead of relying on the length or shape of the code.
Reference verification route
For production work, use GS1’s Global Trade Item Number resources, the current GS1 General Specifications and GTIN Management Standard. Local GS1 Member Organizations can support allocation and barcode implementation. The translation workflow should preserve the assigned key and localize only the product information around it.