The POS Master database and POS Import process handle the "Lowest price last 30 days" field to ensure the correct data updates in the SQL database. This allows EG POS to calculate accurate discounts for items with campaign or member prices during sales.
Handling of deleted/deactivated items has been improved in POS Import. Only the item data is inserted into staging tables and all related data are skipped.
Support for handling the externalOfferNo exported from Promotion module has been added to POS Import. The externalOfferNo should now be saved in the dbo.discountgroup, if present.
Quantity can be imported on GTIN's when importing items from Item Management. This will be used in EG POS to be able to sell predefined quantities of an item by scanning a barcode. This can for example be used to sell D-packs by scanning the D-pack barcode in POS. In the database, the quantity is saved on the dbo.ItemIdentity table. Quantity = NULL means we always sell 1 in POS like before.
Quantity can be imported on GTIN's when importing items from Item Management. This will be used in EG POS to be able to sell predefined quantities of an item by scanning a barcode. This can for example be used to sell D-packs by scanning the D-pack barcode in POS. In the database, the quantity is saved on the dbo.ItemIdentity table. Quantity = NULL means we always sell 1 in POS like before.
Bundles can be imported from Item Management and sold in POS.
The price set on the bundle item will be used when selling the bundle in POS. The difference between the sum of the price of the items in the bundle and the bundle price will be set as bundle discount. The sum of the price of the items in a bundle must be lower than or equal to the price of the bundle.
Attributes 'Duty free', 'Sealing bag', 'Restricted', 'Origin' and 'Weight control' are visible in item details, and are exported and imported by both JSON and Excel files. Origin and weight control can be defined as store local values.
'Distribute discount' that is included in the Mix 23: "Buy N items and get a discount in % on the M cheapest items" is supported by POS Import. By selecting 'Distribute discount', discount can be spread evenly on every item in the receipt that is in the offer.
Each time POS API is released, any new permissions will be added automatically to User Management so it can be used in user roles to give permissions to cashiers. Support for importing all of these new permissions has been added to POS Import and POS Master. database.
Support for handling multiple assortments codes set on the item in the Item Management module has been added to POS Import.
Info
title
Note
Deletion of assortment codes exported per profile is not supported since we are not able to track the deletion. The event is not exported from Item Management module
POS Import v. 4.0.58
Status
colour
Green
title
released
Support for Special Group of item from Item Management
To reduce the size of the staging.FlatJSON table, support for saving compressed POS configuration data in the database has been implemented in POS Import. The data is decompressed while entries are processed by the FlatJsonExecutor job from POS Import package.
Info
title
Required
POS Master v. 3.0.0.134 or higher.
Add support for "Number of times the mix can trigger" for Mix 28
Support for "Number of times the mix can trigger" for Mix 28 has been added to POS Import, which sets the maximum number of time the offer can be used.
POS Import v. 4.0.57
Status
colour
Green
title
released
Import Supplier Details Changes from Item Management
Support for importing country-specific item group text is added to POS. This will enable showing the item group text in the language of the country the cash register is in.
The weighted cost price of an item per store is imported to POS. The weighted cost price is now used regardless of the price is used in the sale (normal, campaign, member, mixmatch). If there is no weighed cost price, the normal net cost price is used.
If an offer is created for a specific customer group, the offer should only be applied in the POS when a customer belonging to that group is added to the receipt.
Info
title
Required
POS Master v. 3.0.0.123 or higher.
Import of reason/actions codes from Inventory Service
Support for country-specific item texts from Item Management has been added to POS Import. Changes are also required in POS Master database to be able to use the new data.
Alphanumerical customer numbers exported from Chain Web will be imported to POS.
Expand
title
Configuration
BatchLoader config
New parameter in the BatchLoader config with the default value set to False: "useExternalCustomerNumberAsMain": False
If an external customer number is not present and the parameter is enabled, the main customer number will be used instead.
Info
Note:
If the customer is already present in the POS Master database and contains the external customer number field, and if the "useExternalCustomerNumberAsMain" is enabled, another instance of the same customer will be created with the external customer number. Thus, it is important to clean up old customers when switching to alphanumerical customers (external customer numbers).
The performance of the SQL Stored procedure used by POS Import to find stores with un-processed data in POS Master staging tables has been improved. The procedure could previously use up to 30 seconds and result in timeout. It should now finish in less than 1 second.
If, for some reason, the procedure does not respond within 25s, all stores will be processed.
Support for "Can be sold" flag exported from Item Management module has been added to POS Import. "Can be sold" = false flag from Item Management is now imported as stopcode = 3 in POS Master (FlatVPI table). Hard-coded stop reason "Not ready for sale".
Required: POS Master v3.0.0.99 or higher