Document status:
| Status | ||||||
|---|---|---|---|---|---|---|
|
Date:
Prerequisites are located in the menu on the left.
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Increased timeout for price calculation
The handling of possible price calculation timeouts in POS has been improved. If prices can not be calculated within the default timeout period, caused by too many possible mixmatch combinations, POS may perform an extra price calculation when switching to payment view.
| Expand | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
Service orders from Chain Classic and other orders from Chain Web
POS can search for Service orders from Chain Classic while other order types are fetched from Chain Web. This makes it possible to migrate to Chain Web as order master even if Chain Web does not support Service orders.
| Expand | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
Extension in import of campaign group from Chain Classic
There is done an extension in POS Master for import of campaign group from Chain Classic. The extension is related to sales channels, where it's added more mappings.
New mappings:
- 4 Handheld shopping (Datema terminal or mobile phone) -> ShopAndGoMobile + ShopAndGoTerminal
- 5 Mobile phone -> ShopAndGoMobile
| Expand | ||
|---|---|---|
| ||
|
Improvements POS
| Module | Description |
|---|---|
| Coopay | Bonus reward added to purchase summary (RTP-15725) When triggered a mix that results in a bonus reward to member both the name of the mix and the according effect amount, as already written on the printed receipt, is also added to purchase summary and sent to GiantLeap when paid by Coopay. This will make the same information visible in Coopay app. |
| Coupons | Coupon discounts in combination with mix and campaigns (RTP-16387) When combining a coupon discount with a mix where you by x and get one for free, and a campaign on the same item, this could result in wrong price calculation. This has been fixed to the customer does not get too many free items according to respective coupon and mix rules. |
| Electronic items | Norsk Tipping - improved handling of simultaneous requests (RTP-16722) Due to many possible simultaneous requests to Norsk Tipping (Norwegian lottery company) from different CR's / different stores, via one common POS Services instance, the handling of all these requests are improved. This will better secure that game tickets are not unnecessarily removed from receipt due to network traffic. |
| General | Converting of phone number when sending request to storebox (RTP-17289) There has been done changes for sending in phone number to storebox, the phone number is now converted to MSISDN format. This is done by removing "+" and leading 0's before sending a enroll Request to storebox. |
| Loyalty | Use CompanyID ("S-lagsnr.") as fetched from Loyalty database in stead of the one read of from QR code on member card (RTP-16383) When a customer's member card is registered in POS by scanning QR code, and the code contains a tag for CompanyID ("S-lagsnr."), according CompanyID will be fetched from Loyalty database, if available. This will better secure updated CompanyID is used, and correct member bonus is given, in situations where different companies / stores are merged, and "old" member cards are still in use by the customers. |
| Receipt | Mix 24 in combination with line discount (RTP-16737) There has been done a fix for mix 24 in combination with line discount on articles that starts with a 20-code. Earlier when selling an item that had this combination, it would not be visible on the printed on receipt. |
| Receipt journal | Fix for missing payment type in receipt journal (RTP-16889) There has been done a fix for showing payment type in receipt journal, when using e.g. Swish, Ressursbank, Vipps or Instabank. Previously when using any of these payment methods, they would not be visible in receipt journal in Chain Web. |
| Self-service | Age control rejected by staff (RTP-16867) There has been done improvements in self-service when age control is rejected by staff. Previously, when rejecting an age control in self-service, the customer would be sent back to the confirmation page, with the "yes" button deactivated. Now the customer is sent automatically back to the sales view. Light tower flashing red due to pay terminal payment failure (RTP-16801) If a pay terminal payment fails due to e.g. an expired payment card the state of the light tower immediately changes to 'AssistanceNeeded', and the red light flashes. This state is however temporary, and customer may continue a few seconds later, without any need of help. The light tower will then go back to 'InUse' state, and the red flashing light disappears. Previously the light was flashing red until the payment was done and the receipt was finished. Do not fetch loyalty number from CoopKey QR code (digital age control) (RTP-17144) When scanning a CoopKey QR code in self-service POS, used in accordance with digital age control, loyalty number from QR will not be added to receipt. This is due to loyalty number tag in CoopKey QR may have a value even for non members, who otherwise would get member benefits they are not entitled to. Changes have effect when CoopKey QR tag 'B' = '2' only. Messages shown to user when item quantity is limited (RTP-16936) For items which are allowed to be sold only with a limited quantity explaining messages is shown to user. These message texts, shown both in cashier mode and in self service mode, will be different based on the reason why quantities are limited. Item quantity may be limited due to either items are linked to a specific requirement ID, or they may be limited due to containing identical active substances. The latter typically affects medical products. |
Improvements POS Server
| Module | Description | ||
|---|---|---|---|
| POS API | Items blocked for sale and multipack items in POS API (RTP-16210) Items that are blocked for sale will get a specific error code in the response when trying to add an item to the shopping cart in POS API. This makes it possible to show a specific error message in the Shopping app. The response for blocked items will be "<RequirementFaultType>ItemIsStopped</RequirementFaultType>" When adding an items that also could be included in multi pack units, the shopping cart returned from the POS API will contain information about this. The response for items that also is sold in multipacks will be "<IncludedInMultipack>True</IncludedInMultipack>. This makes it possible to automatically show a quantity dialog for these items in the Shopping App. Caching of Klarna merchant key in POS WCF (RTP-17259) Changed MerchantID when order is updated from Web Shop. Loyalty coupons added as tender correctly displayed (RTP-16811) Adding loyalty coupons as a means of payment (tender, not subtotal discount) is correctly displayed in the cart and POSLog XML. | ||
| POS Import | Improvements for mix 35/41 from promotion module (RTP-17229) The following improvements have been done:
| ||
| POS Master database | Fix for method to fetch items with stock from POS Services (RTP-16977) A missing column was added to table SearchItemsWithChangedStock that caused exception when PosServices GetItemsWithChangedStock was called. Replication fail on some unfiltered publications (RTP-16937) A problem that caused some unfiltered replications to fail has been fixed. Import of MBXP items (RTP-16931) Since 'MbxpWeb' is used in the POS Master database, the itemType for MBXPwebsale items in dbo.ExtSaleProvider has to be defined to 'MbxpWeb' as well. When itemType in both POS Master and Item master are consistent, such items are properly imported to POS Master database. Import of campaigns on model+color (RTP-15206) Import of campaigns from the cloud promotion module now support the model+color level. This makes the import much faster than importing individual EAN/GTIN's. | ||
| JournalService | Fix for updating customer order id's in the sequence number table in database (RTP-15986) There is now done a fix related to customer order id's in the sequence number table in the journal database. So now all orders except orders that are created in POS will update the sequence number. Previous the number would be set to the highest number, regardless of where the order was created. This would cause problem when reinstalling POS, because store central database would be updated with this number (and get in conflict with number series from Chain/WCF).
|