Encoding parentheses as payload
Parentheses are commonly shown for human interpretation but are not generally encoded as part of the GS1 element string.
GS1-128 is not ordinary text wrapped in a Code 128 symbol. Use structured fields for supported Application Identifiers, review fixed and variable lengths, and let the generator place FNC1 separators where the element string requires them.
Identifier notice. BatchLabel generates the graphical representation of the number provided. It does not sell or assign official GTIN, EAN or UPC codes.
A practical workflow
Choose a supported identifier such as 01, 17 or 10 and enter its value in the dedicated field.
Resolve invalid GTIN/date lengths and confirm where a variable field needs FNC1 before another field.
Generate and test the final sequence with the trading partner or internal system that consumes it.
Avoid rework
Parentheses are commonly shown for human interpretation but are not generally encoded as part of the GS1 element string.
Without a separator, the scanner cannot know where a variable-length value ends before the next AI.
The composer is not a substitute for the current GS1 General Specifications or trading-partner requirements.
Date semantics, units and regulated data still require domain review.
Questions, answered
It uses the Code 128 symbol but adds FNC1 and GS1-defined data semantics. A plain Code 128 generator does not automatically produce a valid GS1-128 element string.
No. The initial composer supports a documented selection of common AIs. Unsupported or industry-specific fields should be handled with authoritative GS1 guidance and explicit implementation.