You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

PLANNED

Prerequisites are located in the menu on the left.

Payment by Walley in EG POS

(RTP-29175)

Walley can be used as payment both in cashier mode and in self-service mode in EG POS. To pay by Walley, customer's mobile phone number needs to be registered manually. Customer may then either follow a link received in an SMS, or scan QR code shown on screen in POS with mobile phone camera, to follow identical link. Payment will then be finished on the phone, and receipt written in EG POS.

Walley payment in cashier mode:

Dialog for cashier to enter customer's phone number:

When phone number is registered the payment process starts, involving mobile phone:

Walley payment as shown on customer screen:

Walley payment in self-service POS:

Dialogue for customer to enter phone number:

When phone number is registered the payment process starts, involving mobile phone:

Printed receipt contains info of Walley tender and according transaction ID:

POS Configuration

New parameter:

'WalleyCardIssuerId' (default 215)
Card issuer used for Walley payments. The matching issuer ID must be added in Reporting database.

Existing parameters:

'ButtonConfig'
Add a new button to pay by Walley using function "Pay with mobilepayment" with argument 'Walley'.

'ShopAndGoButtonConfig'
Add a new button to pay by Walley using function "Pay with mobilepayment" with argument 'Walley'.

'CloudAccessServiceUrl'
Address to CloudAccessService in POS Services. Default address should normally be used.
 
'PaymentServiceMerchantId'
Correct Merchant ID to be used will be supplied by PaymentService DevOps team.
 
'PaymentServiceUrl'
Address that EG POS will use to contact PaymentService in the cloud. Make sure to use the correct address for your environment.
https://paymentservice.lindbakcloud.com should be used for production environments, including EG Demo.
https://paymentservice.egretail-test.cloud should be used for test environments.
 
'PayTerminalVerboseLogging' (default False)
Should be activated, to extend logging to research any problems. 

Putting receipt on-hold for online return

(RTP-26708)

A new POS configuration parameter (AllowReceiptOnHoldForOnlineReturn) is added to be able to control whether a receipt with an online return will be allowed to be put on hold or not. It is also not allowed to do a second online return for an item that has been previously returned, put on-hold, and returned successfully.

Required

POS Master 3.0.0.160.

POS Configuration

AllowReceiptOnHoldForOnlineReturn - Default value = False.

When this parameter is True, it will be allowed to put a receipt with an online return to on-hold. When this parameter is False, it will not be allowed to put a receipt with an online return to on-hold. 


Improvements POS

AreaDescription
Balancing

Shift ID on the receipt (RTP-30055)

After closing current shift, receipt is printed with provided Shift ID on it.


Required

Required Parameter configuration in POS Configuration:

BalanceTransactionType = Shift

Fusion Fuel Integration

Fix for registering drive offs (RTP-30096)

A fuel transaction that was added to a receipt and then removed afterwards, can be registered as a drive off successfully without any errors.

Multiple fuel transaction in a receipt and logging out error fix (RTP-30124)

The support for more than one fuel transaction in the receipt is added, and error while logging out with fuel transactions added to the receipt is fixed. 

Orders

Fix for dispatch orders changing into reserve in store orders (RTP-30480)

Dispatch orders or web orders no longer change into reserve in store orders after picking is finished.

Receipt

Performance in POS is effected when POSAPI in Cloud is unavailable (RTP-30886)

Logic is implemented to handle offline situations from POSAPI.  The timeout value is changed to use the existing 'OnlineTimeout' parameter (before is was hardcoded to 30 sec).

Returns

Online Return Permissions (RTP-30098)

When a cashier  that doesn't have permission processes an online return, a second cashier with the correct permission is required to log in to proceed with the return successfully. 

System

Changes in naming of services and integrations (RTP-27462)

Service/integration names shown in Services/Integration tab in System view have been improved to make them more readable for the users. This only applies only to the services contained in the parameter: ServicesToShowInSystemPanel.

Web orders

"Order from Webshop" button visibility (RTP-30106)

Item that is not in stock in dispatch locations is no longer available for web order in POS and the button "Order from Webshop" is not  visible in Item Search.

Improvements POS Server

AreaDescription
POS Import

Import of item attributes related to duty-free and grocery (RTC-40741)

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.

Required

POS Master 3.0.0.161 or higher.
POS Import 4.0.68 or higher.


Import reason codes for sale transactions (RTC-40477)

Support for import of reason codes for sale transactions is added.

Required

POS Import 4.0.68 or higher.


Overlapping item identities (RTP-30559)

Support for overlapping item identities has been added to POS Import. Now items with overlapping EAN/SKU/Tandem should be properly imported and processed.

Required

POS Master v. 163 or higher.


POS Master

Fix for issue with future price (RTC-41145)

The logic for handling the deletion of future prices has been improved, so that it does not override or delete current price.

Required

POS Master v. 162 or higher.



  • No labels