No UPCE in RMS Label Wizard

Dude! You should not be printing barcodes in upce - it could cause you a LOT of trouble (surprised you haven't had it yet!). UPCE, like UPCA, has a country code and a check digit (a logorithym to see if the barcode is formed properly). My advise to you is to convert ALL your printing to 128A, allowing you to also print alpha-numeric. The present labels you have printed will still read by your scanner (I guess...)

I would agree, If you add the UPC-E to the alias you wont have to relable any of the old stock, Make sure you scan an item into notepad though to see what is actually being scanned by the scanner as it is likely different than what you see on the label.

Jerry;

We've been doing it for years with no problems at all. Although there are 6 significant digits the code is really 8 digits. All UPCE codes begin with zero, and the eigth digit is a check digit based on the equivalent UPCA expansion. The existing labeling program automatically calculates these and prints a correct UPCE barcode. We do not use all the codes, but assign them ending with digits 5 through 9 (plus check digit).

We have products in inventory with UPCE codes printed on the package by the vendor, primarily items like candy and gum. There has never been a conflict. Their codes are always in a completely different numbering sequence.

I've done some experimenting with code 128, but the GS1US standard states only four code types are approved for POS use; UPC-A, UPC-E, EAN-13 and EAN-8. According to their documentation those are the only codes that can be read omnidirectionally, and are therefore the only codes that can be used for POS scanners.

Thanks

Ted

Well, the idea that POS scanners can't read 128's is just silly, no matter who wrote it. I have at least 25 clients that use them regularly. As far as your issue, I don't know what to tell you. I don't see any reference in RMS to UPCE. HOWEVER... IF you are using a real label printer like a Zebra or a Cognitive Solutions, you could create a custom label and hard code the UPC type into the label, as RMS just sends the number to the label. (In the Labels folder) So when you print that label, you get a UPCE no matter what you send to it. Examples: CS: BARCODE CODEUPCE 40 140 70 Zebra: "B350,50,1,1A,3,7,100,B," Each printer has a code that tells it what type of barcode to print, as they are actually rendered in the printer itself. The code can be obtained from the printer's programming manual.

If you need help with this approach let me know. I hope this helps!

I agree with Jerry, We've been using 128A for years and every scanner I've ever owned read them just fine. Craig

We have over 200 clients on RMS and several hundred on another software platform we used to sell and a large majority use some form of 128 wether it be A,B,C and they have no problem at all.

The only time they use anything like UPSa,E is if the barcode already exists on the product we just set it up as an alias.

Jerry;

Yes, we are using a "real" label printer (SATO CL408) and it worked well in our "old" system. And yes, it has a series of commands that direct the printer to place text and bar codes in specific locations on the label. In fact I wrote the program that we have been using. However, the label program in RMS wants only a raster printer. We are using the raster driver provided by SATO, and RMS prints text and UPCA just fine, constructing the image based on information within the RMS label system, and sending it as a raster image.

I'll study the code in one of our custom label definitions to see if any modifications can be placed there.

Again, our goal is to stay with the "standard" features embedded within RMS, and that includes the label program. If it is necessary to use an external program to print labels, that cost will need to be added to the conversion costs.

As far as suitability of code 128 is concerned, the bar code standards group is where I am getting my info. I have a link in one of my earlier posts. We have experimented with code 128, and yes, it seems to scan with no problem. We are using a quality scanner (Symbol). Perhaps problems arise when using lesser quality scanners. I don't know.

We have converted most of the UPCE codes to UPCA (Expanding it using the GTIN rules) and then added the original UPCE as an alias. The problem is that the label program only searches the "lookup" code, and not "alias". The users are entering the UPCE code, not the 12 digit equivalent. It is possible to use the LOOKUP feature and then search both fields. Our users are balking at this as too slow and confusing. Over time as product is sold off the shelf, the new labels which are printed will all be 12 digit. In the mean time ...

The POS finds either in a flash. Too bad the search function in the label program doesn't work the same way.

Thanks for your suggestions. I'll keep searching.

Ted

(SNIP)

Jerry;

Looking into the label definition files there is no description other than "BARCODE". No place to add any "custom code. I suspect the type is derived from the lookup file, where each product has a "barcode:" field. The type of barcode is selected from a drop-down dialog. There are many code types listed there, but not UPCE, and so the label program only knows what was selected there.

Thanks

Ted

(SNIP)

Perhaps you should consider a different printer, might I suggest a Cognitive Solutions BlasterLX Advantage - cheap, reliable, and you could make a custom label to run inside RMS.

RMS supports raster or direct-to-printer label output. Add a Generic Text-only driver to Windows called SATO. Create your label format in Notepad with the appropriate SATO commands. See the sample Eltron or Blaster PCLlabel formats as a guide. Use whatever barcode command your label printer supports. UPCE or UPCA is not appropriate in this case, but you could use them if supported by your SATO printer. Save the label format to the folder Program Files, MS RMS, Store Operations, Labels.

Any of the barcode types listed in RMS will produce a scannable barcode from

128A works best for most RMS users because is handles any ASCII character.

If you want the smallest possible width barcode, try Interleave 2 of 5 with

AutoGen installer:

Thanks for the tip about using a generic text driver. I didn't think Windows would "approve". I'll study the structure of the files you referenced and see what I can put together.

Thanks

Ted