...
Prerequisites are located in the menu on the left.
Support identical EAN13 items with price or weight in barcode (prefix 20 / 23) to be split in database
(RTP-19515)
Identical EAN13 items with either a price (prefix 20-22) or weight (prefix 23-25) presented in the barcode are historically stored, and found, in database by common prefix 20, and 5 zeros (00000) at the end. Any sale of such items have been stored on this common EAN13 number.
Now it is possible (configurable) to search and sell such items even when they are stored in database with different prefix (20 or 23). When stored as 2 different items they also need to have valid check digits, and not always 0. Sold items will be reported by one or the other EAN13 number accordingly.
| Expand |
|---|
|
| POS Configuration |
|---|
CalculateCheckDigitFor20Codes (default 'False') - if activated, EG POS will in database search for either an item with prefix 20 or prefix 23, with a valid check digit (0000C). Sale will be reported on the same items respectively. If not activated, EG POS will as before search for an item with prefix 20 and 5 zeroes (00000) at the end. Sale will be reported on the same item. Detailed information about solution: - 'CalculateCheckDigitFor20Codes' = 'False'
- Common item in database: 20xxxxxx00000
- Any similar scanned barcode with prefix 20-25 will find this item, an sale will be reported on EAN 20xxxxxx00000
-
- 'CalculateCheckDigitFor20Codes' = 'True'
- Items 20xxxxxx0000C and 23xxxxxx0000C has to be present as 2 different items in database.
- Scanned barcode with prefix 20-22 will find EAN 20xxxxxx0000C, and sale will be reported on this EAN.
- Scanned barcode with prefix 23-25 will find EAN 23xxxxxx0000C, and sale will be reported on this EAN.
|
|
Support Klarna payment capture on delivered web orders
...
