GS1-128 Barcode Data Encoding in Microsoft Office Word Application
We provide structured instructions for encoding GS1-compliant data, configuring character sets, and managing symbol structure for the GS1-128 (a standardized linear barcode based on Code 128 for supply chain identification) symbology in the Microsoft Office Word Application.
What is GS1-128 Barcode Data Encoding?
The GS1-128 barcode data message consists of structured groups. Each group contains a GS1 Application Identifier (AI, a standardized code defining data type) and its corresponding data value. All characters used in AI codes and data fields comply with the GS1 subset of ISO/IEC 646.
An Example:
One group includes AI code (00) and data (395123451234567895). Here, AI (00) represents SSCC (Serial Shipping Container Code) for transport unit identification.
An Example:
One group includes AI code (00) and data (395123451234567895). Here, AI (00) represents SSCC (Serial Shipping Container Code) for transport unit identification.
GS1-128 Barcode Minimum and Maximum Data Length
A valid GS1-128 barcode must contain at least one AI-data group. For a single GS1-128 symbol in the Microsoft Office Word Application, the maximum total data character count is 48.
Note: Exceeding the 48-character limit will generate an invalid barcode in the Word document and cause scanning failure.
GS1-128 Barcode Encoding Character Set
GS1-128 supports the following character types in the Microsoft Office Word Application:
Do not manually add function characters, start characters, or stop characters.
The add-in automatically inserts required structural characters into the barcode. The generated GS1-128 symbol displays correctly in the Word document.
- Data characters from the GS1 subset of ISO/IEC 646
- Four function characters: FNC1, FNC2, FNC3, FNC4 (FNC2 and FNC4 are not used in GS1-128)
- Three start characters and one stop character
- Code set selection and shift characters
Do not manually add function characters, start characters, or stop characters.
The add-in automatically inserts required structural characters into the barcode. The generated GS1-128 symbol displays correctly in the Word document.
Note: Manually typing function or structural characters will break encoding logic and produce unreadable barcodes.
GS1-128 Check Digit Character
Every GS1-128 barcode includes one mandatory check digit for data validation. This check digit is embedded in the barcode symbol but not shown in HRI (Human Readable Interpretation) text.
In the Microsoft Office Word Application barcode settings panel, the Add checksum char option does not apply to GS1-128. The encoder automatically calculates and inserts the check digit before the stop character.
The check digit is properly integrated into the barcode structure. The symbol maintains scanning compatibility in printed Word documents.
In the Microsoft Office Word Application barcode settings panel, the Add checksum char option does not apply to GS1-128. The encoder automatically calculates and inserts the check digit before the stop character.
The check digit is properly integrated into the barcode structure. The symbol maintains scanning compatibility in printed Word documents.
GS1-128 GS1 Data Message Encoding in Microsoft Office Word Application
A GS1 data message includes one or more element strings. Each element string combines a GS1 Application Identifier (AI) and its associated data field.
Example GS1 Data String
(01)99012345678909(15)241015(21)abcThis sample contains three element strings:
Example GS1 Data String
(01)99012345678909(15)241015(21)abcThis sample contains three element strings:
- 01 - GTIN (Global Trade Item Number): Fixed 14-digit product identification code
- 15 - Best Before Date: Fixed 6-digit date in YYMMDD format (example: 241015 = October 15, 2024)
- 21 - Serial Number: Variable-length alphanumeric value (1–20 characters) for unique item identification
- Open the Barcode Settings pane in the Microsoft Office Word Application.
- Locate the Data property field.
- Enter the full GS1 data string with AI codes enclosed in parentheses.
Note: Incorrect parenthesis formatting or invalid AI lengths will result in encoding errors in the Word output.

