Differences

This shows you the differences between two versions of the page.

--- cobi.wms:gs1_barcodes [2022/03/28 17:45] – tkammer
+++ cobi.wms:gs1_barcodes [2022/04/07 14:52] (current) – [Possible formats] tkammer
@@ Line 15: / Line 15: @@
 All three of these formats are supported by COBI.wms, as long as your hardware supports them.
-[{{gs1-128.png|**Example GS1-128**}}]
+[{{gs1-128.png?0x120|**GS1-128**}}]
-[{{gs1-datamatrix.png|**Example GS1 DataMatrix**}}]
+[{{gs1-datamatrix.png?0x120|**GS1 DataMatrix**}}]
-[{{gs1-qr-code.png|**Example GS1 QR Code**}}]
+[{{gs1-qr-code.png?0x120|**GS1 QR Code**}}]
 All three codes above contain the same data.
@@ Line 28: / Line 28: @@
 These characteristics make **GS1 DataMatrix** the optimal choice for modern warehouse applications, but if your scanner hardware is not capable of scanning 2D codes, then you must use **GS1-128**.
+Note that using a modern format like DataMatrix might also make your barcodes incompatible with other, more primitive scanning solutions.  So in case COBI.wms is not the only software you use for scanning your codes, or in case you want to make it possible for your business partners to scan your codes (who might not be using COBI.wms), then you might want to use GS1-128, or not use GS1 at all and instead print separate barcodes for separate pieces of data (like one for item code and another one for serial number) for maximum compatibility with old scanning solutions.
 ===== Supported data fields =====
@@ Line 72: / Line 74: @@
 ==== Not setting GS1 mode ====
-{{ zint-gs1-datamatrix.png?450}}
+{{ zint-gs1-datamatrix.png?400}}
 As already mentioned in the previous section, it's important to tell your barcode generation software that you want to generate a valid GS1 code; it's not enough for the contents to be valid GS1 contents.