2018-03-20自定义范围前缀DAS2-127

1.png

2.png

3.png

4.png

bindolabs.atlassian.net/browse/DAS2-127

Background

Now we are using hardcode way to handle barcode starting with 2 as embedded barcode product. However, some of retails store like Wine store might use barcode starting with 2 e.g 2015xxxxx as a secondary barcode (the wine year), when user scanning those products with no responses in the result. This issue happens to store House Of Connoisseur (SID24322).

Solution

We will add ‘Custom Define Scale Prefix’ in add-on page / new tab. Which provide an option for clients to choose whether they need to customize the prefix in product’s barcode. If enable this option, client will be able to define two things.

User will see an ON / OFF option to turn on “Custom Define Scale Prefix”

1. Add new Prefix and input prefix e.g. 20 (Prefix is to distinguish it’s scale product or normal barcode product)
   e.g user input 24 as scale prefix, then all barcode starting with 24xxxxxxxx will treat as embedded barcode
2. User can also add as many prefix as user wanted, e.g 20, 21, 22, 23, 24, 24 etc.
   Once user turned on Custom Define Scale Prefix, user can set Decimal place, e.g. 1/2/3/4
   It depends on the prefix and describes how many decimal places are allowed for this barcode’s weight. For example,

e.g 0 decimal places allowed weight (in grams): barcode 241234512345 = 12345.6 g / $12345
e.g 1 decimal places allowed weight (in grams): barcode 241234512345 = 12345.6 g / $1234.5
e.g 2 decimal places allowed weight (in grams): barcode 241234512345 = 1234.56 g / $123.45
e.g 3 decimal places allowed weight (in grams): barcode 241234512345 = 123.456 g / $12.345
e.g 4 decimal places allowed weight (in grams): barcode 241234512345 = 12.3456 g / $1.2345  

1. User can choose up to 4 digits only

Embedded Barcode format:

If disable this option, then the barcode will be normal product barcode.

It's store level setting, default is OFF