-
POS payment to customer account
If you pay to customer account in POS, the sales order is invoiced either by the transactional statement or by the Real-time service. This is not always the preferred result. Customers, both B2B and B2B, often has different demands on how and when to be invoiced. It's therefore a better solution to post a packing slip instead. The invoicing can then be performed by the business rules manually or in batch. Invoicing directly or not could be controlled by a parameter. -
Info codes in call center sales orders and sales quotations
Info codes has been a part of Retail and Commerce since the LS Retail days. However, this has only been a part of the POS, and not HQ. Some Info codes are now implemented as reason codes in the Call center functionality, but that is not sufficient. Its about time that there is one place to register and maintain PopUp's and reason codes in the solution. At present it is necessary to maintain Info codes, Scripts and Attachments (Notes) separately to obtain a reasonable interaction with the user. This is first of all important for customers, but there is no reason why other linked tables shouldn't support the same functionality, like products and tender types. -
Aggregating different barcodes in POS cartview and receipt
In response to https://fix.lcs.dynamics.com/Issue/Details?bugId=583124&dbType=3&qc=54705690f00799ad3645ad0c32b392ac3b2d25136f768813a553744c3281cf74. If it is the same item and same variant, it should be treated as this regardless of the barcode. This is especially important when barcodes include quantity (GS1-128). Wooden cladding or timber framing can be scanned by hundreds of meters on the same transaction. -
Closing a blind closed shift opened by another worker
If a shift is opened by one worker and blind closed by another, the shift must be closed by the same worker that opened the shift, unless the worker has manager privileges. If the worker has permission to manage shared shifts, it should be possible to close a shared shift. -
POS is not using the Credit and collections functionality
The Credit and collections functionality is not triggered by the real-rime service from the POS. Its is only using the legacy credit check and makes no use of the Credit management checkpoints, etc. This prevents us from using this functionality in general because we are using callcenters, POS and ecommerce channels, and all channels must handle the credit checks in the same manner.
-
POS compact design shows all payment methods
A compact design for handheld devices shows all payment methods. In a regular design you can design whatever payment methods you want to display. Not all payment methods are relevant for a handheld device, for instance Cash payment. It should be possible to toggle a parameter in the payment methods, selecting if the payment method should be visible in a compact design or not.
-
Amount paid filter in POS transaction search
It is often necessary to search for the paid amount in the search transaction operation. This is because the customer only has the bank transcript as documentation. If a paid amount filter in combination with a date is possible, there would be a much easier task to find the correct transaction.
-
A partial prepayment in POS stops due to exceeded credit limit
This problem occurs if the Credit limit type is set to Balance+All and the customer is marked with Mandatory credit limit=Yes. If a sales order is created in HQ and partially prepaid in POS, there is a credit limit error, and the transaction is not possible to complete. It should be possible to fulfil a partial prepayment eve though the customer credit limit is exceeded. Prepayment is used to secure a payment of capital goods and is used because the customer has no credit or have exceeded the limit.
-
A partial prepayment in POS stops due to exceeded credit limit
This problem occurs if the Credit limit type is set to Balance+All and the customer is marked with Mandatory credit limit=Yes. If a sales order is created in HQ and partially prepaid in POS, there is a credit limit error, and the transaction is not possible to complete. It should be possible to fulfil a partial prepayment eve though the customer credit limit is exceeded. Prepayment is used to secure a payment of capital goods and is used because the customer has no credit or have exceeded the limit.
-
A simpler price check for call center users
The commerce price simulator is too complicated for regular users to check a price on a product. The price check "Find product price (PriceDiscActualFormPart1)" in the workspace "Sales order processing and inquiry (SalesOrderProcessingWorkspace)" should be extended with the commerce pricing engine if the user is connected to a callcenter.
You’re offline. This is a read only version of the page.
