Barcoding: Mind Your “(” and <GS>

Getting GS1-128 right with (93) and (10) – A personal Rant!

The Frustration: When Formatting Breaks Everything

When GS1-128 barcodes fail, it’s rarely because of hardware or software—it’s usually formatting.

In this particular Example, Two fields that cause a lot of trouble?

👉 (93) – Item Number
👉 (10) – Lot / Batch Number

Both are variable-length fields. And that means one small, invisible detail can make or break your barcode:

👉 The Group Separator <GS>

The Parentheses Problem

You’ll often see data written like this:

(93)ABC123(10)LOT789

But those parentheses are only for humans—they are not encoded in the barcode.

The actual data looks like:

93ABC12310LOT789

If parentheses accidentally get encoded, your data will scan incorrectly.

 Where Things Go Wrong

Because both (93) and (10) are variable length, the scanner can’t tell where one ends and the next begins—unless you tell it.

That’s what <GS> does.

✅ Correct

93ABC123 <GS> 10LOT789

❌ Incorrect

93ABC12310LOT789

Without <GS>, the scanner may read everything as (93), and (10) gets lost.

 Why It Matters

This isn’t just a technical detail—it shows up fast in operations:

• Failed scans at receiving
• Incorrect data in WMS/ERP
• Traceability issues
• Manual rework

And the tricky part? The barcode usually looks fine.

Best Practices

• Keep parentheses out of encoded data
• Treat (93) and (10) as variable length—always
• Ensure <GS> is inserted between them
• Test with real scans, not just visual checks

Final Thought

In GS1-128:

👉 ( ) are for humans
👉 <GS> is for systems

When you’re working with (93) and (10), that invisible separator is doing all the heavy lifting.

Miss it—and everything downstream starts to fall apart.

4136B Jersey Pike, Chattanooga, TN 37421

Phone (423) 855-1822 | Fax (423) 499-6317

sales@barcominc.com