Skip to main content

Search

Search

Change Symbology Based On Data Field Contents

Comments

3 comments

  • Avatar
    Legacy Poster

    I think I'm confused. An EAN-13 code with a leading zero is the exact same as a UPC-A barcode without the leading zero. Therefore, unless your source of data is inconsistent, you should only require an EAN code if you have a full 12+1 (Check Digit) value coming in? Which should be easy to filter for?

    0
  • Avatar
    Legacy Poster

    Ha.  You think you're confused.  It seems I need to learn more about barcode symbology.  Thanks for the help. 

    0
  • Avatar
    Legacy Poster

    Guru is right.  GS1 understands all product numbers (item, inner pack, case, pallet, etc.) as GTIN (global trade item numbers).  Everything has a 14-digit code.  Bananas, for example, are only to be sold at one level, the POS level.  That gets the last 12 or 13 digits of the GTIN.  12 for UPC, 13 for EAN.  The two digits (or one for ean products) are used for the other packaging level.  So a bunch of bananas might have upc number of 11223344556X, where X is the check digit.  The EAN would likely be 011223344556X and the box of bananas 1011223344556X, and the pallet of bananas 2011223344556X.  Scanners that read UPC should read the EAN, so it won't really matter which one gets used.  Making sure you have the right "base" GTIN plus the correct check digit is important.

    0

Please sign in to leave a comment.