GTIN: Global Trade Item Number
A practical guide to trade-item identification, packaging relationships, validation and controlled change in regulated manufacturing.

On this page · 12 sections
- 1What a GTIN identifies—and what it does not
- 2GTIN formats: length, representation and application
- 3GTIN structure and check-digit validation
- 4Company-prefix records and allocation ownership
- 5Assessing whether a change needs a new GTIN
- 6GTIN versus SKU, lot, serial, SSCC and barcode
- 7Packaging hierarchy: trade items and logistic units
- 8GTIN, Digital Link and connected product content
- 9GTIN and UDI DI: review by market and product
- 10Integrations, data records and exception recovery
- 11Common GTIN failures and targeted controls
- 12GTIN implementation and review checklist
How does GTIN apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a GTIN identifies—and what it does not
A GTIN (Global Trade Item Number) is a GS1 identifier for a trade item. The name and identification purpose appear in GS1 General Specifications, section 3.3.2. For a manufacturer, the useful starting point is the trade-item record: what packaged product does this identifier refer to?
In practical item-master design, keep identity separate from representation, production history and disposition. The GTIN identifies the trade item; a barcode represents data for scanning. A batch record documents manufacturing activity, while a disposition decision records whether material is accepted, rejected or otherwise controlled. Do not use the identifier itself as evidence of product approval or batch release. These are operational boundaries, not a claim that GS1 identification establishes regulatory status.
For example, consider a manufacturer’s approved item record for a packaged product. That record connects the product description and GTIN to purchasing, labelling and receipt transactions. Staff can use the shared reference to interpret what was ordered, labelled and received, while maintaining production and quality decisions separately. An audit trail can preserve changes to that mapping for later review.
The next questions are therefore practical: which GTIN format applies, which packaging relationship the record describes, whether a proposed change calls for a different allocation, and how downstream systems interpret the value. Resolve those questions before treating a successful scan as confirmation that the receiving system has selected the intended item. Detailed comparisons with neighbouring identifiers belong in the GTIN-versus-lot-and-serial discussion.
02GTIN formats: length, representation and application
GS1 General Specifications 3.3.2 lists GTIN-8, GTIN-12, GTIN-13 and GTIN-14 as trade-item identifier formats. Its AI (01) structure represents each in a fourteen-digit GTIN field: shorter formats receive leading zeroes, while their identifier digits remain intact. The application identifier sits outside that field.
| Format | Identifier length | Representation in an AI (01) field | Application check |
|---|---|---|---|
| GTIN-8 | 8 digits | AI (01) | 000000 N1 N2 N3 N4 N5 N6 N7 N8 | Confirm GTIN-8 is allowed for the intended application. |
| GTIN-12 | 12 digits | AI (01) | 00 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 | Confirm GTIN-12 is allowed for the intended application. |
| GTIN-13 | 13 digits | AI (01) | 0 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 | Confirm GTIN-13 is allowed for the intended application. |
| GTIN-14 | 14 digits | AI (01) | N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 | Confirm GTIN-14 is allowed; field width alone is insufficient. |
Here, N1 through the final N denote the identifier’s existing digits. Spaces and the vertical separator are explanatory notation, not a proposed encoded string. The table deliberately separates AI (01) from the GTIN field so interface designers do not treat the application identifier as part of the product number.
The format list is not blanket permission to use every format in every application. Section 3.3.2 directs application selection to section 2.1 for format rules and mandatory or optional attributes. Treat that as a GS1 specification question, separate from whether an interface can accommodate the digits. For carrier and label design, consult the related GS1-128 and GS1-128 label explanations.
As an interface-control practice, preserve the original representation alongside an explicitly defined exchange representation. Document the source format, padding convention and destination field separately. Treat padding as a representation operation, not as allocation of a new trade-item identity. This makes comparisons reproducible without allowing a receiving system’s field width to determine which identifier format the business may use.
03GTIN structure and check-digit validation
Under GS1 General Specifications 3.3.2, Application Identifier (01) indicates that its associated data field contains a GTIN. Keep the application identifier separate from the identifier value when parsing a GS1-128 scan.
That GS1 technical specification expects application software to verify the check digit to establish correct composition; this is a technical specification expectation, not a statutory obligation applying to every manufacturer. For calculation details, consult GS1 General Specifications 7.9. The example below addresses representation rather than the calculation algorithm.
Worked case: matching a scan to an item record
Assume an approved item record stores a GTIN-12 as N1…N12, and the scanner interface carries AI (01). Each N denotes a digit position, not a literal letter. This comparison concerns identifier strings, not quantities of product; there are no physical units. Assume the scan contains no additional fields or scanner metadata.
- Capture the raw scan unchanged. Display it symbolically as 01 | 00N1…N12; the separator is explanatory, not a transmitted character.
- Parse 01 as the application identifier. Do not include it in the GTIN passed to validation.
- Retain 00N1…N12 as the GTIN field. The GTIN-12 row in GS1 section 3.3.2 shows these leading zeros after AI (01). Run the composition check and record its result separately.
- Convert the stored item-record representation to 00N1…N12 for comparison. Preserve the original values and apply a documented conversion rather than indiscriminately stripping zeros.
- Compare the consistently represented strings. If they differ, retain both values and route the mismatch for investigation rather than changing the item record to force acceptance.
A successful composition check does not establish correct allocation, a match to the intended product, or approval of that product for use. Keep item lookup and product-disposition checks separate, with human approval governing disposition. Use exception-based review to distinguish parsing failures, invalid composition and unmatched records.
04Company-prefix records and allocation ownership
GS1’s GTIN rules address uniqueness, allocation and responsibility for allocation; consult GS1 General Specifications 4.2 for those rules. For allocation governance, use a documented responsibility review rather than treating a digit pattern as proof of authority to assign identifiers.
The following are recommended manufacturer controls, not statements of GS1 licensing requirements. Maintain an allocation register linked to material master data, connecting:
- The recorded company prefix and responsible organisation.
- The trade-item description and assigned identifier.
- The assignment decision, its rationale and the approval record.
- The organisation administering the register, separately from suppliers or service providers entering data.
Make that separation explicit in responsibilities and access arrangements: permission to enter a record should not be treated as authority to decide an allocation. Keep the approving person and decision traceable alongside the entry.
For supplier-provided identifiers, record the supplier item reference, supplied GTIN, package description and confirmation contact before approving a local mapping. Resolve unclear package descriptions with that contact rather than approving a mapping based only on a matching item name.
Before acquiring a prefix or assigning identifiers, check current GS1 membership and allocation terms. For a merger, acquisition or transfer of responsibility, document an ownership review, including who will administer the register and approve subsequent decisions. Do not assume unchanged digits settle allocation authority.
05Assessing whether a change needs a new GTIN
Treat the allocation decision as a controlled assessment against the current applicable GS1 GTIN rules, recording the relevant application and rule reference. The GS1 cross-application index in Table 8-5 identifies uniqueness, allocation and allocation responsibility as section 4.2 topics; that index is not a complete trigger list. Use the following proposed manufacturer workflow within change control, rather than treating it as a prescribed GS1 or regulatory procedure.
- Describe the change. Capture the before-and-after product description, formulation, declared content, packaging configuration and commercial presentation. Treat these as review inputs, not automatic reasons to allocate a new GTIN. Identify affected packages, the market and the proposed effective point so the assessment has a defined scope.
- Assess the applicable rules. Identify the application being evaluated and record the specific rule reference used for each affected trade item. Explain how the proposed change relates to that rule. If applicability remains unresolved, record the open question and assign an owner before approving the identifier decision.
- Approve the decision record. State retain or change, with the rationale, affected relationships, implementation dependencies and named human approval. Keep assignment approval separate from the human decision to release product; neither decision substitutes for the other.
- Coordinate implementation. Plan updates across item masters, packaging records, label templates and trading-partner mappings. Assign owners and an agreed effective point, and check that dependent records reflect the approved decision before putting the revised identification into use.
- Close and preserve history. Retain the approved assessment and historical associations so an investigation can reconstruct which identifiers and records applied before and after implementation. Use an audit trail to document changes and approvals. Assess any proposed identifier reuse separately against the applicable rules.
The resulting record should make both outcomes understandable: why an existing GTIN was retained or why a replacement was introduced, and how that decision reached operational records.
- DefineRecord the trade item, package, market and responsible organisation.
- AssessDocument the applicable allocation rule and proposed change.
- ApproveObtain a named decision with its rationale.
- ConfigureUpdate package relationships, mappings and label references.
- TestCompare captured identifiers with approved records across interfaces.
- DeployCoordinate activation and resolve conflicting downstream mappings.
- MaintainRetain history and investigate exceptions through controlled corrections.
06GTIN versus SKU, lot, serial, SSCC and barcode
These terms answer different operational questions. The comparison below describes common manufacturing and logistics data-model roles, not statutory definitions or a prescribed numbering scheme.
| Term | Operational question | Typical record | Relationship to GTIN |
|---|---|---|---|
| GTIN | Which trade item is this? | Trade-item master | Identifies the commercial item or package being referenced. |
| Internal SKU | Which item does our organisation manage? | Local item master | Mapped to GTIN where relevant; the local mapping need not be identical across organisations. |
| Lot or batch | Which production group is involved? | Batch record or lot record | Adds production-group context to the identified trade item. |
| Serial number | Which individual instance is involved? | Instance or serial record | Adds instance context; retain the associated item identity. |
| SSCC | Which logistic unit is being handled? | Logistic-unit record | Linked contents describe the trade items within that unit. |
| Barcode | What data can be captured from this symbol? | Label definition and scan event | Represents machine-readable data; it is not an interchangeable item-master identifier. |
For implementation, document each identifier’s scope and relationships rather than assuming identical numbering structures or fixed mapping cardinalities. A local SKU lookup belongs in the item-master mapping; a production investigation follows the associated batch record. Logistic-unit handling uses a separate relationship, illustrated by an SSCC pallet label.
Keep the parsed business identifier and the captured barcode payload in separate record fields. Retaining the original scan alongside interpreted values helps distinguish an incorrect item association from a capture or parsing problem. Avoid a generic barcode field that mixes GTINs, lot references and complete scan strings.
For example, assume a warehouse receives a labelled commercial package with linked production and shipment records. A trade-item lookup identifies the package; the associated lot record identifies its production group, a serial record identifies the instance where used, and shipment events establish the movement. For recall readiness, follow those links rather than treating a successful GTIN lookup as a complete traceability result.
07Packaging hierarchy: trade items and logistic units
Model packaging as explicit parent–child relationships, not as a pattern inferred from similar-looking GTINs. Recommended packaging-master fields include the parent and child identifiers, quantity of children per parent, unit of measure, package descriptions, and effective status. Describe what each level contains so that a case, its contents and a shipping unit remain distinguishable in operational records.
Case: a healthcare retail-level GTIN changes
Assume the regulated-healthcare non-retail consumer trade-item application applies, and a retail consumer trade-item GTIN change has already been determined to be required. The GS1 regulated-healthcare packaging provisions expect that change to propagate to all configuration levels above the retail consumer trade-item level. This is a GS1 technical expectation for that application, not a universal legal obligation or a test for deciding whether the original change was necessary.
Recommended records affected: the packaging master, old-to-new GTIN mappings, label specifications and trading-partner item records. Review whether every applicable configuration above the retail level has been addressed, and retain the decision history in an audit trail.
Case: a logistic unit contains matching trade items
Assume the logistic unit is not itself a trade item and its highest-level contained trade items share a GTIN. Under GS1 General Specifications 3.3.3, these are the conditions for using AI (02). Its value identifies those highest-level contained trade items, not the logistic unit itself.
For this case, GS1 expects AI (02) to be processed together with AI (37), with the count appearing on the same unit. AI (02) answers which trade item; AI (37) expresses how many. The count’s unit is the relevant highest-level contained trade item—not an assumed quantity of individual products inside it.
Recommended records affected: the logistic-unit contents record, label data and dispatch or receiving message. Keep the unit’s own identity separate from its contents GTIN. Review the trade-item level and count interpretation during receiving ASN matching, rather than accepting a matching GTIN alone.
08GTIN, Digital Link and connected product content
Within its ASP 2 application context, the GS1 data-carrier note preceding Table 8-5 permits a carrier containing a GS1 Digital Link URI for consumer mobile devices in addition to the selected mandatory point-of-sale (POS) carriers. This GS1 specification provision describes an additional option, not permission to replace those POS carriers.
As a governance practice, keep separate review records for the printed carrier, the parsed identifier and the destination content. Link the records so a reviewer can trace a scanned label to its intended product page. Treat content publication and GTIN allocation as separate decisions: neither approval should be taken as authorisation for the other. Use an audit trail review workflow to retain who approved each change and its scope.
- Match the scanned identifier to the intended product, packaging presentation, market and language.
- Test the intended consumer-mobile and operational scanning environments separately; record which are supported.
- Assign ownership of the destination address, published content and ongoing maintenance.
- Test unavailable and incorrect destinations; define escalation, correction, retesting and a fallback route for users.
These are recommended operational acceptance checks, consistent with data integrity by design, rather than additional GS1 allocation rules. Detailed URI syntax and resolver behaviour are outside this section’s scope.
09GTIN and UDI DI: review by market and product
Review identifier mappings by product and intended market. Use the questions below as an applicability worksheet, not a table of GTIN mandates. Do not transfer conclusions between rows.
For US medical devices, check the current FDA UDI basics for scope and confirm the proposed GTIN-to-UDI-DI relationship before approving the mapping.
| Jurisdiction and product | Applicability question | Identifier relationship to confirm | Review record |
|---|---|---|---|
| US medical devices | Does the UDI framework apply to this product? | Is the proposed GTIN appropriate for the intended DI role? | Product, market, identifier role, conclusion |
| EU medical devices | Which device-identification framework applies? | How does the GTIN relate to the applicable device identifiers? | Device scope and mapping rationale |
| US human drugs | Which product-identification framework applies? | How does the commercial GTIN relate to that framework? | Product scope and identifier mapping |
| EU human drugs | Which product-identification framework applies? | How does the commercial GTIN relate to that framework? | Market-specific scope and mapping |
| US foods and dietary supplements | Which identification framework applies to this product category? | What role does the commercial GTIN serve within it? | Category assessment and relationship |
| US chemicals | Which identification framework applies to this chemical product? | How does the commercial GTIN relate to applicable identifiers? | Product assessment and mapping rationale |
Classify each authority separately: binding legal provision, official guidance, GS1 technical specification, internal procedure or configurable software check. Record the authority, provision where relevant, applicability rationale and review date for every conclusion. Link the decision to data-integrity controls and its audit trail; retain human review and approval rather than treating a software result as a compliance conclusion.
Keep deadlines, exemptions and issuing-agency recognition outside this table’s conclusions. Resolve those separately for the identified market and product; do not assume universal GTIN-to-DI equivalence.
10Integrations, data records and exception recovery
As a practical integration control, agree an interface contract between item-master, manufacturing (MES), warehouse and label systems. Define field representation, package relationships, mapping ownership, effective status and dates, and error handling. Specify which system publishes each value and who approves changes. Reference the validation controls discussed above rather than implementing inconsistent checks at each handoff.
Use the following logical data model to connect identifier administration with transactions. These records need not be separate physical database tables; preserve their relationships regardless of implementation.
| Logical record | Suggested fields and links |
|---|---|
| Trade item | GTIN representation, internal item reference, effective status |
| Packaging relationship | Parent and child trade-item references, quantity, unit |
| Allocation decision | Trade-item reference, change assessment, decision, approver, effective date |
| Partner mapping | Partner reference, trade-item reference, mapping owner, validity period |
| Verification event | Transaction reference, mapping version, check performed, result, reviewer |
For lookup failures, use a controlled recovery sequence to support data integrity:
- Retain the original scan payload and partner reference; route the unresolved transaction for investigation.
- Establish the correct mapping with its owner, preserving the original mapping or recording that none existed.
- Test the correction against the failed transaction and relevant package relationship.
- Reconcile dependent transactions before an authorised reviewer permits the affected flow to resume.
Retain an issue record, affected transaction references, original and corrected mappings, test result and reviewer identity as recovery evidence. Avoid creating a new item solely to clear a failed lookup: resolve the identity question before changing the master data.
Trade Item
Approved identity and package description.
- trade_item_id
- gtin
- gtin_format
- description
- base_uom
Packaging Relationship
Links parent and contained trade items.
- parent_gtin
- child_gtin
- quantity
- quantity_uom
- effective_from
Allocation Decision
Connects the identifier to its approval.
- decision_id
- gtin
- rule_reference
- rationale
- approved_by
Partner Mapping
Connects external references to local identity.
- mapping_id
- partner_id
- external_item_id
- gtin
- mapping_status
Verification Event
Preserves capture, result and reviewer.
- event_id
- gtin
- scan_payload
- check_result
- reviewer_id
11Common GTIN failures and targeted controls
Use this proposed diagnostic matrix to investigate identifier incidents. For the underlying distinctions, refer to the earlier sections on structure, neighbouring identifiers, packaging hierarchy, change assessment and connected content.
| Symptom | Likely failure | Immediate containment | Preventive control |
|---|---|---|---|
| Imported identifier no longer matches | Numeric conversion removed leading zeros | Quarantine import; compare raw payload with stored value | Text-field contract; round-trip test preserving leading zeros |
| Active partner code resolves to conflicting items | Overlapping partner mappings | Suspend affected mapping; identify intended item with partner | Partner-scoped mapping register; reject overlapping active assignments |
| Case receipt produces wrong quantity | Packaging relationship uses incorrect unit of measure | Hold quantity posting; inspect parent–child conversion record | Acceptance test comparing expected and posted quantities and units |
| Printed label identifies previous product version | Obsolete template remains selectable | Stop affected print jobs; segregate suspect labels | Template revision register; test withdrawal and approved-template selection |
| Sites disagree after item change | Incomplete rollout across receiving systems | Pause affected exchanges; compare deployed revisions | Deployment matrix with receiving-system acknowledgements and transaction tests |
| Scan opens another product’s content | Connected-content destination mapped incorrectly | Disable affected route; preserve mapping history | Destination register; scan-to-page test against expected product identity |
Containment is not complete recovery. A corrected display or successful rescan may leave transactions or mappings unresolved. Before closure, identify affected items, partners, labels and transactions; reconcile or reprocess them and retain results. Use the MES–QMS integration incident record to track downstream recovery.
12GTIN implementation and review checklist
Use this suggested acceptance checklist with the earlier sections for the meaning of each check. It is an implementation review aid, not a compliance standard.
Identity and application
Is the approved item description recorded? Are the selected GTIN format, intended application and representation documented against the format and structure checks above?
Package relationships
Are relationship records complete for the affected packaging levels, quantities and logistic units, as discussed under packaging hierarchy?
Allocation decision
Is the retain-or-replace decision rationale recorded, with its reviewer and the allocation criteria considered?
Interface testing
Does a successful interface comparison show agreement between approved master data, encoded content and receiving records? Are change records accessible for audit trail review?
Market-specific review
Is the applicable market and product review documented, including any UDI DI assessment identified under regulatory overlays?
Exception ownership
Does every unresolved issue have a named owner? Are deployment across affected systems and partners, and post-change confirmation, assigned and coordinated?
Checklist completion remains separate from the human approval and release decisions covered above.
Frequently asked questions
Q.Can a supplier's GTIN be used unchanged in our own item master?+
Typically, yes: retain the supplier’s GTIN as an external identifier when it matches the product and packaging configuration you actually receive. Keep your internal material code separate rather than replacing either identifier with the other. In material master data, record the supplier, description, purchasing unit and pack relationship alongside the mapping. A useful incoming inspection check compares the physical label with that approved record before the identifier becomes available for routine transactions.
Q.Does a valid check digit prove that a GTIN belongs to the product on the label?+
No. Treat check-digit validation as an arithmetic screen, not proof of product identity or authority to use the number. An incorrectly selected identifier can still pass that screen. Review the complete GTIN against the approved product description, supplier information and packaging configuration, then compare those records with the actual label. For data integrity, retain the identity-check evidence separately from the format-validation result so reviewers can distinguish a readable number from an approved product association.
Q.Why can the same trade item appear with leading zeroes in a scanner feed?+
A common integration explanation is fixed-width formatting: an interface may pad a shorter identifier with leading zeroes. Investigate the scanner output, barcode parser and receiving field definition before treating the value as a different product. Preserve identifiers as text, and retain the raw scan alongside the interpreted value. When troubleshooting GS1-128 through an MES integration, compare approved test labels end to end; avoid a blanket rule that strips zeroes from every scanned field.
Q.Can a pallet be a trade item as well as a shipping unit?+
A pallet can be managed commercially as an ordered product configuration while also being handled as a physical shipment. Review those roles separately rather than assuming that a pallet label serves both purposes. The GS1 glossary definition of SSCC identifies it as the key for logistics units. Operationally, keep the ordered configuration linked to the specific shipment record. Compare the SSCC pallet label with the receiving ASN, including contents and quantities.
Q.What should reviewers check when a supplier proposes a replacement GTIN?+
Ask what changed, which packaging configurations are affected and how the supplier intends to distinguish old and new stock. Compare descriptions, declared contents, purchasing units and pack relationships before approving the replacement mapping. Use change control to document the reason, effective conditions and affected interfaces. Preserve historical associations instead of overwriting them: recall readiness depends operationally on being able to retrieve transactions under the identifier used at the time, including during stock overlap.
Q.Does a label artwork change always call for a different GTIN?+
No blanket artwork rule is appropriate. GS1 General Specifications, section 3.5.3, recognises consumer product variants where a change does not require a different GTIN. That is not a blanket exemption for artwork revisions. Review whether the revision changes product declarations or merely their presentation, then assess the applicable allocation criteria. Keep the artwork revision, decision rationale and approval in the audit trail, so retaining the identifier is a documented decision rather than an assumption.
Q.Can a GTIN be treated as the UDI device identifier for a US medical device?+
Treat this as a device-identification decision, not a barcode-format decision. For a US medical device, check the current FDA UDI framework for applicable scope before approving a GTIN-to-device-identifier mapping. Review the issuing-agency scheme, device description, packaging configuration and associated device records. Keep device-model identity separate from lot, serial and expiry data during that review. Document the approved relationship in controlled product records, with relevant design-history documentation linked where useful.
Q.How should a warehouse recover when a scanned GTIN has no approved mapping?+
A practical recovery workflow pauses the affected transaction and routes the material to controlled review rather than guessing from a similar description. Capture the raw scan, label image, supplier paperwork and physical packaging configuration. Investigate parsing errors, an unmaintained supplier change or genuinely unfamiliar stock. An authorised reviewer can approve a corrected mapping and test the rescan before processing resumes. Record a deviation when the event meets the site’s procedure, preserving any correction to inventory records.
Primary sources
Explore this topic
GTIN sits inside this topic cluster in our glossary. Every neighbour is one click away.
Want to see how GTIN could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
