Setting Up GS1 Barcodes in D365 SCM (Without Losing Your Mind)

Barcodes: the warehouse equivalent of duct tape. They hold everything together, nobody questions them, and if you get them wrong, chaos erupts.

GS1 barcodes are the global language of product identification — a way for scanners, systems, and operators across the world to speak the same "beep." In Microsoft Dynamics 365 Supply Chain Management (D365 SCM), enabling GS1 means you can scan, parse, and actually make sense of these codes inside Warehouse Management workflows.

This guide walks through setup, the "don’t-click-that" traps, and why GS1 matters if you’d prefer fewer warehouse meltdowns.

Prerequisites: Flipping the Right Switches

Before diving into menus, you’ve got to make sure the right features are on in Feature management:

Mandatory — no opt-out since v10.0.32.

Scan GS1 barcodes

Optional until v10.0.36, then Microsoft said “surprise, it’s mandatory.”

Enhanced parser for GS1 barcodes

These features use Microsoft’s native GS1 parsing engine, aligned with GS1 General Specifications (Release 24, 2024 edition). Translation: yes, they’re legit.

Global GS1 Options: Teaching D365 the Secret Handshake

Go to: Warehouse management → Setup → Warehouse management parameters

1. On the General tab, open the Bar codes FastTab. 2. Define GS1 prefix characters:

3. Define your Group Separator:

`]C1` = FNC1 Character (linear)
`]d2` = DataMatrix
`]Q3` = QR Code
Replace ASCII gobbledygook (ASCII 31, `␟`) with something human-friendly.
Most folks use `~` — and no, it doesn’t stand for “tilde-vision.”

This tells D365 how to split scanned data instead of mashing it into one sad, unreadable blob.

Application Identifiers (AIs): The DNA of GS1

Go to: Warehouse management → Setup → GS1 → Barcode data application identifiers

1. If setup doesn’t exist, click Create default setup. ⚠️ Warning: If you already have custom AIs, clicking this button nukes them.

2. Defaults follow GS1 rules (01 = GTIN, 10 = Batch, 30 = Quantity). 3. Fixed length? Only use where GS1 demands (GTIN = 14 digits). 4. Need custom AIs? Totally fine — just don’t invent ones that break standards.

Example:

Application Identifier = `99`
Fixed length = Yes, 7 characters
Type = Alphanumeric
Name = Production ID

📌 Always sanity-check against the [GS1 General Specs](https://www.gs1.org/standards/barcodes/gs1-general-specifications) before getting creative.

Barcode Data Generic Setup: Making Fields Behave

Go to: Warehouse management → Setup → GS1 → Barcode data generic setup

If nothing exists, click Create default setup.
Don’t overwrite existing setups unless you enjoy rework.
This is where you map device fields → GS1 AIs.

Example custom mapping:

Field = `ProdId`
AI = `99`
Description = Production ID

Now your mobile device knows that when it sees AI 99, it should shove it into `ProdId` instead of, say, `Batch`.

Barcode Data Policy: The Warehouse Rules of Engagement

Go to: Warehouse management → Setup → GS1 → Barcode data policy

Create default setup if missing (again: ⚠️ don’t overwrite).
Add or edit policies.

Example:

Policy Name = `Batch RAF`
Description = Batch Report as Finished
Field value capturing = Save as default
Auto-submit = Yes

**Policy example table:**

| Field | AI | Description | Overwrite? | |---------------|-----|---------------|------------| | InventBatchId | 10 | Batch | N | | Qty | 30 | Quantity | N | | ProdId | 99 | Production ID | N |

Create a menu item so operators can actually use GS1:

1. Name = `GS1 RAF` 2. Title = GS1 Report as Finished 3. Mode = Work 4. Work creation = Report as Finished 5. Barcode data policy = `Batch RAF` 6. Generate license plate = Yes

Drop it into the Production menu, and your floor workers now have scanning superpowers.

Example: ZPL Barcode & Scanning

Here’s an example GS1 QR code string:

]Q399P00103730110TestBatch01

Breakdown:

`]Q3` = QR Code identifier
`99` = Production ID (custom AI)
`30` = Quantity
`10` = Batch

Think of `~` as the traffic cop that separates fields so D365 doesn’t smash them into one confusing blob.

Common GS1 Gotchas (and How to Dodge Them)

1. “No AI Found” error

Likely cause: wrong prefix or missing FNC1.
Fix: Double-check global options and use a GS1 validator before testing.

2. Invalid GTIN length

GTIN = 14 digits. If your UPC is 12 digits, add leading zeros.

3. Custom AI not recognized

Probably overwritten. Re-add it to Application Identifiers and remap.

4. Wrong fields captured

Mis-mapping between AI and device fields. Review generic setup.

5. Worker stuck at “Validate Barcode”

Auto-submit off. Flip it to “Yes.”

6. Scanner adds junk characters

Group separator mismatch or scanner config issue. Align D365 and scanner settings.

7. Performance drags

Too many AIs or old version. Upgrade to v10.0.36+ and streamline labels.

Sample ZPL You Can Actually Use

**GS1 QR Code (Report as Finished)**

^XA
^FO50,50
^BQN,2,10
^FD]Q399P001037~301~10TestBatch01^FS
^FO50,200
^A0N,40,40
^FDProdID: P001037^FS
^FO50,250
^A0N,40,40
^FDQty: 10^FS
^FO50,300
^A0N,40,40
^FDBatch: TestBatch01^FS
^XZ

GS1 DataMatrix and GS1-128 examples work the same — just different prefixes and symbologies.

Quick GS1 AI Cheat Sheet (for when nobody wants to read a 500‑page PDF)

Identification:

(01) GTIN .......... n14 Global Trade Item Number
(10) Batch/Lot ..... an..20 Variable length
(21) Serial No. .... an..20 Variable length

Dates (YYMMDD):

(11) Production date
(15) Best before
(17) Expiration

Quantity / Count:

(30) Variable count .. n..8
(37) Logistic count .. n..8

Weights & Measures:

(310n) Net weight kg (n=decimals)
(320n) Net weight lb (n=decimals)

Logistics / Trade:

(400) Customer PO .... an..30
(410) Ship-to GLN .... n13
(414) Location GLN ... n13

Rules to tattoo on your brain (or just print the cheat sheet):

GTIN must always be 14 digits. Pad with zeros.
Variable‑length AIs need FNC1 separators unless they’re last.
Don’t sprinkle AIs you’ll never use.

Wrapping Up

GS1 in D365 isn’t rocket science — but it is picky. Configure prefixes, map your AIs, and line up policies correctly, and scanning becomes magic. Skip a step, and you’ll spend days decoding “no AI found” errors while workers glare at you.

Do it right once, and GS1 pays you back with faster workflows, fewer mistakes, and less warehouse swearing.