GS1 UDI AI parser

FAQ

What are GS1 Application Identifiers in a UDI string?

GS1 Application Identifiers (AIs) tag data elements in a barcode or human-readable string. Common UDI-related AIs include (01) GTIN (UDI-DI), (11) production date, (17) expiration date, (10) lot/batch and (21) serial number. Fixed-length AIs (such as 01, 11, 17) have defined lengths; variable-length AIs (10, 21) run until the next AI or the end of the string.

Does this parser handle FNC1 / scanner strings?

No. It expects the parentheses human-readable form, for example (01)…(17)…(10)…. FNC1-separated scanner output needs different splitting rules. Convert to the parentheses form or use a GS1-aware decoder before pasting.

Is the GTIN check digit re-validated here?

No. This page only splits AI groups. Validate or compute the GTIN check digit with the UDI / GTIN check digit tool before you trust a (01) value for labeling.

How do FDA UDI production identifiers map to these AIs?

When a manufacturer uses GS1, production identifiers such as lot, serial, expiration and manufacturing date are typically encoded with AIs 10, 21, 17 and 11 respectively, alongside the device identifier in AI 01. Exact PI requirements depend on the device and packaging level under FDA’s UDI framework (21 CFR Part 830 and related labeling rules).

What if an AI is unknown to this tool?

Unrecognized AIs are still listed with a generic “AI nn” label and the captured value. Confirm fixed vs variable length against the GS1 General Specifications before relying on the split.

Can I paste spaces or line breaks?

Whitespace is stripped before parsing. Keep parentheses around each AI code. Missing closing parentheses stop the parse at that point.