Are there any requirements to define barcode requirements ?

[LesPiles]

Hello everyone!

We just received a non-compliance report from a customer. The customer complains that when reading the bar code, he founds a "+" before the code and there is no "Enter" at the end. This obviously harms its data entry in SAP.

We obviously suspected the configuration of the customer?s barcode reader (or the code itself).



We discovered that there are 2 kinds of Code 39 (Code 39 and Code 39 ASCII) and a we might have mixed the 2 symbologies over time. We?ve looked at the early requirements in the project to find that the barcode was superficially described (simply "use Code 39").

In short, my question is as follows:

Are there specs, a standard (I would expect that there is something for the Automotive Industry) describing in detail the expected results in terms of bar code (symbology, width, height required , etc.)? If so, I would inspire myself with this to make clear how the client wants the code and avoid later problems.



There are plenty of stuff over the net describing bar codes but I've not found anything describing requirements (specs) from a CUSTOMER point of view. (I'm not looking how to represent a bar code).



Thank you in advance


LesPiles

 

[Mark Meer]

...but I've not found anything describing requirements (specs) from a CUSTOMER point of view

A customer requirement is exactly that: customer defined. Unless their requirements reference a particular standard, you won't find a standard that will claim to meet your customer's requirements.

In your case, it appears an unfortunate case of the requirements not being specific enough.
...did the customer approve the requirements? If so, I'd say you are justified in using either the full ASCII or restricted version (as both are technically "Code 39").

 

[Sam Lazzara]

This may not be what you are looking for, but standards for barcode (1D, 2D) verification are described in this article.