FREE TOOL / CHESTNY ZNAK / GS1 DATAMATRIX
Chestny ZNAK Code Checker: Find the Codes Excel Broke Before You Print
Check Chestny ZNAK marking codes before you print: see every part of the code, find codes damaged by Excel, and draw a GS1 DataMatrix. Free, in your browser.
Codes
Selected code
LabelInn prints one GS1 DataMatrix per code from the CRPT file, byte for byte, and refuses codes Excel damaged.
A Chestny ZNAK code has to reach the label exactly as CRPT issued it, invisible separators included. This checker reads the code the way a scanner does, shows each part, and tells you when the code is damaged. Paste one code, or open the whole code file: it is read in your browser and never uploaded.
01 / WHAT IT CHECKS
What it checks
- The structure. The code is split into its Application Identifiers: (01) GTIN, (21) serial, then (91) key and (92) signature, or (93) verification code.
- The separators. Between some parts sits an invisible GS character (ASCII 29), shown here as a yellow ⟨GS⟩. A code without them is reported, not repaired: where they were cannot be known for sure.
- Every field. The GTIN check digit, digits-only and length rules, dates, and the GS1 character set.
- The form. Long form (91 + 92) or short form (93), and a signature of unusual length.
A code that passes is drawn as a GS1 DataMatrix: FNC1 first, FNC1 in place of every separator. Download it as PNG or SVG to test your scanner. We decoded symbols from this tool with an independent decoder (ZXing): it returns ]d2, GS1 DataMatrix, and the original code byte for byte.
02 / THE EXCEL PROBLEM
The Excel problem
Open a code file in Excel, save it, and the GS characters can disappear. The result looks almost right: the same digits and letters, run together. A scanner then reads one long serial instead of serial, key and signature, and the code fails verification at the point of sale. Try the "Excel-damaged" sample above to see what that looks like.
The fix is to download the codes again and send the file to the printer without opening it in a spreadsheet. Files that write the separator as \u001d or \x1d, and codes captured with a scanner prefix such as ]d2, are read correctly.
03 / PRINTING
Printing the whole file
This page draws one code at a time. For a production run you want one label per code, straight from the CRPT file, with a record of which codes were printed. LabelInn does that with a "Full GS1 code" field: bind it to the code column and every code is printed byte for byte, with damaged codes refused instead of printed wrong. It arrives with the next app release; tell us about your labels and we will set you up first.
04 / OTHER GS1 CODES
Other GS1 codes
The checker reads any GS1 element string, not only Chestny ZNAK: a DSCSA product identifier with GTIN, expiry, lot and serial, or a case code with a traceability lot code. For those, see DSCSA label printing and FSMA 204 traceability lot code labels.
QUESTIONS / FAQ
Frequently asked questions
How do I check a Chestny ZNAK code?
Paste it into the box above or open the code file. Each code is split into its parts, every field is checked, and codes with a problem are listed first with the reason.
Why does my code say the GS separators are missing?
The code has lost its invisible GS characters, most often because the file was opened and saved in Excel. Download the codes again and do not open the file in a spreadsheet before printing.
Can I generate a Chestny ZNAK code here?
No. Codes are issued by CRPT and contain a cryptographic part only CRPT can create. This tool checks codes you were given and draws them as a GS1 DataMatrix.
Is the code file uploaded?
No. Everything runs in your browser. The only thing loaded from outside is the barcode drawing library.
Does the DataMatrix from this page pass verification?
It encodes the code correctly as a GS1 DataMatrix. Whether a printed label passes depends on print quality and size, so test a printed label with your own scanner or verifier.
KEEP GOING
Related
NEXT STEP / LABELINN
Need to print the whole code file?
LabelInn prints one GS1 DataMatrix per code from the CRPT file, byte for byte, and refuses codes Excel damaged. · Byte-for-byte codes · Damaged codes refused · Every printed code recorded