Zero Waste Price Embedded/Weight Embedded Items- Setup and Reader Rules.
This article is a guide to be used for those using Bizerba scales and want to know how to setup the weight embedded products to work with it, in a zero waste scenario. Included in this is also the regular setup of weight/price embedded barcodes.
The setup of an embedded item is primarily done inside of Total Control, the reader rule is setup inside of GPOS however.
To start if you create a new SKU for this product to use, having a multiplier of 1 (For use of 1KG). This is under “General Databases” and then “Stock Keeping Units”.
In Total Control if you go to “General Databases” and then “Products” and edit the product you want to be weight/price embedded.
Firstly, set the “Price embedded” flag to true on the product, like below.
Then set the product to have the SKU you just created above, like a “Single Unit”, the cost of the unit will be the same as the SKU cost.
Enter an SKU cost for the product.
Enter the selling price of the product as a whole, i.e. An entire block of cheese in a 1KG size being £15, the selling price would be £15.
Go to the dropdown selection where “general page” is and dropdown to “pos options”, then expand the “general” tab.
Change the HALO (High Amount Lock Out) to be a value of -1, this will allow the product to be sold at any price, lesser than the selling price or higher, worked out at the point of sale.
Save the product and communicate it down to the till.
On the till you need to minimise/shutdown the software and launch the “Fidelity GPOS Programming utility”, then when prompted to select the ECR database server click “continue”. (This may differ for environments with multiple databases on a till, always check before making changes).
Then go to “Programming” – “System Tables”- “Reader Rules”.
The reader rules here should be checked as per the following guide, however can differ dependent on your setup of the price label and weight label.
The important part of the setup is configuring it to match the code on your labels, remembering that GPOS will strip any leading Zero from the product barcode.
If the scanner you are using is keyboard-wedge then it needs to include a CR (Character Return) in the length, so a barcode of 13 digits needs setting up as 14 in the reader rules to pick it up.
We recommend scanning the barcode into an application like notepad if it is an keyboard-wedge scanner
Any barcodes when scanned into notepad (keyboard wedge) also need to be setup with a “;” in the prefix if this is included when scanned.
If the scanner is not keyboard-wedge then leave it to the length of the barcode, as GPOS strips the leading 0 out then the prefix just needs to include the start of the barcode and if applicable the start of the product. An example of this is “0266309900490” and the product is code “6630”; the prefix would be “26”.
For the BIZERBA product codes it processes the example differently, and would instead read as follows:
It would still have the leading 0 stripped out, but the code of “0266309000490” would instead be looking for a product code of “66309”; the prefix being “26” still.
In this example, Length = 12, Prefix = 26, code start = 2, Code Portion Length = 6, QTYPortionstart = 8, QTYLength = 4
We recommend starting all of the Bizerba product codes with the same start number.
The code portion is the product and way of telling the system to look for the key type of a PLU (keytype 1).
The Amount Portion is the way of the system determining how much to sell the product for, from its selling price and the amount that shows on that barcode. In the example in the linked article, it starts on the 9th number in the barcode, so it would be selling that item for £16.63. See below for further reference, this may vary on your barcode length.
The difference between a price embedded and weight embedded barcode is simply changing the “amountportionstart” to “QtyPortionStart”, using the same principle as the above.