Document status: DRAFT
Date:
Prerequisites are located in the menu on the left.
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.
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.
Improvements POS
| Module | Description |
|---|---|
| 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. |
| 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. |
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 |
| 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. |