Barcode Scans but the System Rejects It: Encoding vs. Database
A scanner beep only means the symbol decoded. Whether the data is accepted is a separate question.
When a barcode beeps but the application rejects it, the first question is whether the decoded string is what you intended. Scan into a plain text field — Notepad, a terminal, a phone note — and compare character by character with the source data. Hidden differences such as a trailing space, a leading zero, a lowercase letter in Code 39, or a GS/separator character in a GS1 string are common.
If the text matches, the problem is downstream. The database may expect a GTIN with a check digit that your value lacks, a different country prefix, or a product that has not been registered yet. Marketplace systems often validate against a catalogue: a perfectly encoded barcode for a SKU that is not listed will still be rejected.
For GS1-128, check the application identifiers and the FNC1 separators. A variable-length field followed by another AI must be terminated with FNC1; without it the scanner concatenates the values and the receiving system sees one long, invalid field. Some generators insert FNC1 automatically only when you use the bracketed AI syntax, so confirm which input format your tool expects.
Keep the distinction in mind when troubleshooting: the scanner answers «can I decode this pattern?», not «is this value correct for your business?». Test the decoded text first, then compare it with the catalogue or EDI message, and only then suspect the print.
지금 바코드 생성
바코드 생성기