-
Support Adyen Pay-by-Link feature for Call Center and POS card-not-present scenarios
Suggested by Bryon Williams – Planned – 1 Comments
https://docs.adyen.com/checkout/pay-by-link To support scenarios where we would sell to a customer via an email or phone interaction, selling either out of Call Center or in some cases POS, we would like to be able to leverage the Adyen Pay-by-Link feature via direct integration from F&O. The idea being that we stage the order with payment to be make via payment link, F&O interacts with the Adyen API to generate the link, F&O emails the customer (via an email template), and when the customer completes the payment, the order is updated to show payments satisfied. (or something along those lines). -
Retail periodic discounts calculated on Requested ship date
Suggested by Galia Ivanova – Planned – 3 Comments
Companies often use call center functionality and retail periodic discounts to offer more complex prices and discounts to their B2B customers. In some cases the company policy requires prices and discounts calculation to be based on today's date (this is how the retail periodic discounts work now). But in other cases the company wants to calculate prices and discounts based on Requested ship/receipt date which is currently not supported for call center sales orders. It's good to have an option to set Requested ship/receipt date as a parameter for calculation of retail periodic discounts. -
Retail Sales Price Management - Commerce: Generic currency feature
Suggested by Gerhard RIESER – Planned – 2 Comments
The generic currency feature (and the smart rounding) should also be available in combination with the commerce pricing engine like it is available with the standard price setup in D365. On the trade agreement journal line there is already a toggle "include generic currency" and it is working if the sales order is not a retail sales order (the user is not assigend to a call center).
It would be very helpful to get this feature also for the commerce pricing engine because it would decrease the number of trade agreements and discounts/price adjustments and it would be possible to have a daily update of the exchange rate without the need to update all the trade agreements.
-
Retail discount based on brand
Suggested by Martin Luks – Planned – 1 Comments
We often see a requirement to define retail discounts based on item property, most typically Brand, eventually other attribute / field on item. Example: provide discount 20% on all bags from Mammut. Today this is not possible, the only item relation possible is item or item category (eventually category with exceptions), based on the main retail category hierarchy. -
Default descriptions to Finance postings from Retail & Commerce Payments
Suggested by Kristin Ødegård – Planned – 0 Comments
Related to Retail Stores and Retail Call Centers
When posting payments the default text posted to the financial descriptions are different
Posting text From Stores: SOxxxxxxx, Cash Payment
From Call Centers: Payment for order, SOyyyyyyyyy
This is Microsoft hard-coded and cannot be adjusted without any customizations of code.
The text should be in the same order, preferably with the SO number first, then text .
From a accounting and controlling perspective this will make it more dynamic and better for reconciliation with sorting and also when exporting transactions to Excel you will have better data,
-
Discount can be apply in Unit price rather than line
Suggested by Dhileepan B – Planned – 0 Comments
Presently, In Pos Discount amount is applied on final price i.e., (Qty * unit price= Final price), the Discount amount can be given to each Quantity in the Line Item i.e.,(unit price -discount= final price *qty).
-
MPOS store transfer for batch controlled items
Suggested by – Planned – 1 Comments
Currently, the store transfer functionality for MPOS does not support the transfer of batch controlled items. This poses a huge problem for retail clients who heavily rely on store to store transfers. Even if store employees could select a batch number, they would not know which one to select, so the ideal solution would make the transfer of this inventory possible without entering batch information. Perhaps dropping the tracking of batch altogether at store warehouses.
-
Requested Receipt and Shipment date for ECOM orders.
Suggested by Joseph Youssef – Planned – 0 Comments
The system is addressed to be having the intended behavior of calculation for B2C orders Details for issue 530125 (dynamics.com)
However, using this method of calculation such as the normal Sales order processing calculation methods to consider the Requested Receipt and Shipment date into calculations.
This will be addressed as a valuable addon to the system for businesses that always using Ecommerce orders.
-
Allow setting the number of days to expire credit card authorizations by Card type
Suggested by Kevin Tanferani – Planned – 0 Comments
Currently, a single setting under AR parameters controls the number of days to expire authorizations for all card types. However, card companies have different rules for expiring authorizations. For example, VISA expires authorizations after 7 days while MasterCard allows authorizations to be valid for 30 days.
-
B2B ecommerce - ability to choose shipping date at the time of order checkout
Suggested by Pawan Deep Singh – Planned – 0 Comments
We would like to have one functionality in the B2B e-commerce website at order checkout, where the customer can choose the requested ship date. This field value should be mapped to the D365FO Sales order header field – requested shipping date. Currently, it is by default mapped to the order creation date.
Reason for an idea – Our customer wants to place future orders from B2B e-commerce website.
You’re offline. This is a read only version of the page.
