-
Add pretty price to POS transactions
Suggested by Jon Crespo – New – 0 Comments
In some scenarios it would be interest to apply pretty price to each transaction line in the POS. Or maybe to the total amount of the transaction.
We have some customers that want to use it, and the rounding of the tender type is not enough because they want to get the amount rounded to complace with the Tax Authorities.
-
To make Unit of measure not compulsory on Periodic discount line
Suggested by Nicholas Fook – New – 0 Comments
There should be an option, not to make Unit of measure compulsory for Calculation type = 'Amount off' at Periodic discount line. Else it may impact how the Quantity limit should work, when they are different unit of measure from a product category.
The option could be to make/refer the Unit of measure from product master.
-
Allow partial payments on invoices through POS
Suggested by Ahmed Wafik – New – 0 Comments
Currently it's not possible to make a partial payment on the remaining amount of an invoiced sales order through POS. We should have the ability to conclude an invoice after making a partial payment on POS while leaving an unpaid amount to be paid at a later time.
-
POS: Separate permissions for actions on transfer orders
Suggested by RubĂ©n Garrido – New – 0 Comments
Currently, it is possible to select which POS user profile has permission to create a transfer. If the user has permission, they can create, send and receive transfers related to their store. It would be interesting to have separate permissions for each of these actions, so that a user can create transfers but not send them, for example.
-
Donate the change option
Suggested by Simon Sholl – New – 0 Comments
At a lot of retailers (especially self checkout) an option is prompted at the end asking if the customer would like to donate their change
we can partially acheive this functionality by using an info code linked to a payment type to prompt if you would like to donate change and link it to a service item being added to the basket.
however this could be vastly improved by calculating the round up amounts for card, or change being given for cash
-
Mix and match BOGO discounts that honor customer pricing
Suggested by Brandon Best – New – 0 Comments
D365 is currently missing the capability to use Mix and Match discounts to be leveraged for BOGO scenarios that honor customer trade agreement pricing. With the current setup, a discount trade agreement is overridden by a mix and match discount line set to 0% or $0 off, meaning the customer is forced to pay full price for their "Buy one" item. It would be great for omni-channel and B2B customer mix if we could configure a BOGO retail promotion that honors the customer's pricing for the first item and overrides the price of the second. This could be as simple as a new type of discount group on the mix and match called "unchanged" or "customer pricing" that is treated as a required line that receives no change in pricing.
-
Allow registration of different bank accounts for Retail statements in One voucher
Suggested by Leonardo Villanueva Arce (SONATA SOFTWARE NORTH AMERICA INC) – New – 0 Comments
In General Ledger, when the parameter "Allow multiple transactions within one voucher" is disabled, and there are different bank accounts for each payment method in Retail stores, it does not allow the posting of statements, so it is necessary to turn on the aforementioned parameter in order to record the transactions.
It is proposed that it be possible to record in different bank accounts using the One voucher functionality ("Allow multiple transactions within one voucher" disabled) for the Commerce module, considering that Microsoft suggests the use of One voucher but Retail statements have this limitation.
-
Return Policy for Cancellation of Transaction From the POS
Suggested by Fayaz Rafeeq – New – 0 Comments
The POS currently supports the return policy only for fulfilled or completed cash & carry transactions. If we are doing a return for a customer order via cancellation of the transaction, POS doesn't respect the channel return policy.
As the cancellation of the transaction is also treated as a return from the POS and the amount due is always negative, this should also respect the channel return policy.
-
Archiving cash and carry transactions In the Headquarter from the sales order table list.
Suggested by Huguette Giramata – New – 2 Comments
The cx wants to delete sales order because they manage B2C operations with high volume capacity. However, the system produces an excessive amount of data in the related tables, such as the sales table and transactions. As a result, they would like to remove some of the old sales records to relief the tables that are fed from these tables. Therefore, they would like to use the clean-up function but they are facing an issue with Archiving sales order generated from the MPOS only, while transactions generated from HQ they are able to Archive them where they use the account receivable parameter to enable deleted transaction to be archived in the voided sales order as they don’t want to delete sales order permanently but to archive them. And they are using the cleanup function by enabling first the parameter.
-
Channel Date for Finding Prices (All customers and all sales orders)
Suggested by Alexander KNAPP – New – 0 Comments
In the Price simulator you have the possibility to use the field "Channel Date and time". This date will be used to find prices on a specific date.
It would be great if there is a possibility to make this field (and functionality) also available in All customers and in All sales orders.
Because we have customers who don't accept a price increase right from the start and therefore it will help us if we can insert a date on the customer (and also to be flexible on the sales order) and the sales prices will be found due to this date.
Example: we have a price increase which is valid from 01.07.2023. The customer who doesn't accept the price increase for this date (he accepts the increase only a few months later), will get in All customers the "Channel Date" 30.06.2023. So the system finds the old prices which are valid before the price increase.
