/
GS1 Vendor Label Configuration

GS1 Vendor Label Configuration

[ 1 How WMS+ Parses GS1 Barcodes ] [ 2 Identifier Recognition and Field Mapping ] [ 3 Admin Setup & Best Practices ]

WMS+ can extract data from vendor-supplied barcodes using GS1 Application Identifier (AI) parsing. It allows batch information, such as lot number, expiration date or weight, to be pulled directly from printed labels during receiving, without manual input.

The following guidance outlines how to configure AI parsing in WMS+, explains how the Simplate engine processes barcode segments, and identifies the GS1 AIs that are commonly used. To ensure clarity, this section focuses specifically on vendor-side label scanning, not internal label generation or batch attribute mapping. Next, we outline how the WMS+ system utilizes these configurations during the receiving process.

How WMS+ Parses GS1 Barcodes

When a barcode is scanned during a receiving process, WMS+ reads the AI structure encoded in the barcode. Each Application Identifier defines the type of data that follows (e.g., batch number, expiry date). WMS+ uses Simplate syntax to extract values based on these identifiers and insert them into the correct fields in the batch entry screen.

Parsed values can be assigned to standard fields (like Lot Number or Expiration Date) or user-defined fields (UDFs), depending on how the receiving screen is configured.

AI Code

Description

Format

(01)

Global Trade Item Number (GTIN)

14-digit numeric

(10)

Batch/Lot Number

Variable length

(11)

Manufacturing Date

YYMMDD

(13)

Packaging Date

YYMMDD

(15)

Best Before Date

YYMMDD

(16)

Sell By Date

YYMMDD

(17)

Expiration Date

YYMMDD

(21)

Serial

Variable-length, up to 20 alphanumeric characters

(30)

Quantity

Variable, terminated

(31XX)

Weight in KG

6-digit number with decimal position defined by AI (e.g. 3102 = 2 decimal places, so 001234 = 12.34 kg)

(32XX)

Weight in LB

6-digit number with decimal position defined by AI (e.g. 3203 = 3 decimal places, so 000875 = 0.875 lb)

(240)

Item Code

Up to 30 alphanumeric characters (e.g. FF-BRIOCHE-CASE)

WMS+ expects GS1-formatted data using the correct structures. For example, an expiration date should be formatted as YYMMDD, and a net weight should use a decimal structure defined by the AI suffix (e.g. 3102 means two decimal places).

Identifier Recognition and Field Mapping

WMS+ can match scanned barcodes to items using either of the following identifiers:

  • GTIN (01) – Must be registered in the Bar Codes tab of the SAP Business One item master.

  • ItemCode (240) – Used for internal barcodes. If the ItemCode is followed by other elements, it must be terminated with a Function Code 1 (FNC1) character.

If no match is found, WMS+ will not identify the item.

The following process settings also affect how GS1 values are parsed (Admin Panel → Common Configuration → Process Settings):

  • Ignore GS1 Batch Number: Disregards AI (10) values.

  • Ignore GS1 Quantity/Weight: Disregards AI (30), (310), or (320) values.

  • Use Weight Over Quantity in GS1: Gives priority to AI (310)/ (320) weight values instead of quantity.

Mapped barcode values will populate batch fields in WMS+ in two ways:

  • Core AIs are always populated by default: Lot Number (AI 10 or AI 21), Manufacturing Date (AI 11), Expiration Date (AI 17), and Quantity/Weight (AI 30, 31XX, 32XX). For catchweight items, both Quantity and Weight are parsed and stored.

  • All other AIs require mapping in the SEM Receiving Procedures table. Without this mapping, the values may appear for reference in WMS+ but will not be stored in SAP Business One. For details, refer to Batch Attribute and Simplate Mapping.

Admin Setup & Best Practices

  • Register GTINs or ItemCodes in the Bar Codes tab of SAP Business One.

  • Define visible batch fields using the SEM Receiving Procedures configuration table.

  • Apply Simplate expressions to auto-fill fields during scanning.

  • Use the {{$$}} token to test mappings and verify data context.

  • Test barcode samples in a staging environment before production use.

  • Maintain a reference list of AI tokens used by each vendor.

  • Ensure scanning hardware supports required symbologies (e.g., Code128, Datamatrix).

  • Confirm all barcode data is parsed by the scanner, as WMS+ does not interpret symbologies directly.

  • Periodically review vendor label formatting to ensure GS1 compliance.

  • Configure fallback logic in Simplate expressions to handle missing AIs.