Skip to content
AIDC GORequest a quote

Technical Foundation

GS1 Barcode Parsing: Why Scanned Data Does Not Match Your WMS

By AIDC GO · Published Sep 7, 2026 · Updated Oct 27, 2026 · 3 min read

On this page

Short answer: A GS1 barcode can decode correctly while its fields are parsed or mapped incorrectly by a WMS. Compare the label’s intended data, the application’s received string, the extracted fields and the lookup result. Find the first disagreement before changing the scanner.

Identify the representation being received

Confirm whether the input is a GS1 element string, a scan message, a bracketed display or a GS1 Digital Link URI. These representations need different handling. Human-readable parentheses around Application Identifiers are not encoded as AI delimiters in the symbol.

The GS1 Barcode Syntax Engine documents distinct input forms. Capture the earliest available string and label the observation point. Use an escaped or hexadecimal display when a text box would hide control characters.

Preserve the field boundaries

AI 01 identifies a 14-digit GTIN. AI 10 and AI 21 contain variable-length batch and serial values. A variable-length field followed by another element needs the applicable separator; the last field can end with the message. Consult the GS1 DataMatrix guideline for the distinction between predefined length and fixed length.

For the illustrative fields (01)09521234543213(10)LOT7(21)SN42, a displayed scan message is ]d2010952123454321310LOT7<GS>21SN42. Here <GS> represents one Group Separator character, not literal marker text. Without it, LOT721SN42 can be interpreted as the batch and the serial can disappear. A parser may still accept that unintended result.

Compare output configuration with the WMS contract

Preserve the original received value before applying cleanup rules. Record any prefix, separator conversion, field ordering and submit key. Microsoft’s Dynamics 365 GS1 guidance describes a configured printable separator; another receiver may require the original control character.

Once parsing matches the intended fields, inspect the lookup. Confirm whether the task expects a GTIN or an internal item key, and whether packaging, batch and serial mappings are present. Removing leading zeros or submitting the entire message to an item lookup can change the key.

Keep a focused regression set

Retain a known-good label, the failing label, different permitted lot lengths, an invalid check digit and a valid identifier absent from test master data. For each, specify the expected field values as well as the expected business result. Parser success and item acceptance need separate assertions.

Change one output or mapping rule at a time and rerun the same cases on the intended WMS screen. Send the label format, received representation, expected fields, actual result and configuration versions with your inquiry. This gives the supplier and application team a reproducible mismatch.

Device options for this task

Compare AIDC GO HX-21 and AIDC GO HX-24 as Android PDA Barcode Scanners. Supply representative GS1 labels and the WMS input contract so the exact scanner configuration can be evaluated.

Devices for this workflow

Related guides

Tell us about your project

Send the application, operating system and where the device will be used.

Request a quote