GS1 DataMatrix vs DataMatrix: What Is the Difference?

DataMatrix is a barcode symbology; GS1 DataMatrix uses that symbology with GS1 identification rules. The two can look alike while returning data that a receiving application interprets differently. Choose according to the receiving workflow, rather than the appearance of the square.

The practical difference

A plain DataMatrix can carry a value such as DEMO-PART-2048. Your application decides whether that value is a part reference, a document number, or something else.

GS1 DataMatrix uses an initial FNC1 symbol character and structured Application Identifiers (AIs). An AI states what the following data represents. For example, (01) identifies a GTIN, (10) a lot, (17) an expiration date, and (21) a serial number.

Follow one example from label to reader

Consider this illustrative human-readable interpretation (HRI):

(01)09506000134352(17)271231(10)DEMOLOT7(21)DEMO0001

Here, 09506000134352 is example identification data, 271231 represents 31 December 2027, DEMOLOT7 is the lot, and DEMO0001 is the serial. Replace all example values with your controlled product data before use.

The parentheses make the AI boundaries readable to a person. They are not literal parentheses encoded around each AI. A separator is also needed between this variable-length lot and the serial that follows it. See the AI field guide for the field-by-field explanation.

Putting the visible HRI text into a plain DataMatrix encoder does not establish the GS1 structure. Likewise, drawing a caption under a code does not change its encoded content.

What a decoder can tell you

A reader may describe both symbols as DataMatrix. Depending on configuration, it may expose a GS1 symbology identifier and show a group separator as an invisible control character. A format label by itself is therefore not a complete data validation result.

Decode your exported image with the DataMatrix decoder. Compare the exact GTIN, dates, lot, and serial with the source record. If fields merge, use the FNC1 troubleshooting guide.

Choose the workflow you actually need

• Use a plain DataMatrix workflow when the receiving system expects your own unstructured value.
• Use GS1 DataMatrix when the receiving process requires GS1 identifiers and attributes.
• Check the required carrier with your trading partner or applicable sector specification.

The UDImaker GS1 DataMatrix generator uses structured GS1 fields rather than arbitrary plain DataMatrix text. Design the surrounding label, export with a verified account, and test an actual print. Reading an image checks its decoded data; it does not grade physical print quality.