Sanka Gopi Krishna Mr.

It will be really useful to have a feature where we can, restrict a regular sales associate to open a 2nd shift on the same business day to avoid discrepancies in statement posting at the EOD and it will not let them declare the tender and closing amount twice.

The current application allows us to limit the printing of certain types of receipts through configuration.

However, for operations such as Declare Start Amount and Tender Declaration, the receipt is printed automatically and cannot be restricted. Adding an option to restrict the automatic printing of the above receipts would be beneficial for clients who use handheld devices and wish to minimize the number of paper receipts printed.

Hello,

Currently, we can only import and submit product reviews and ratings with the PowerAutomate solution provided by MS.

We would like to import additional data along with product ratings and reviews.

1. Upvotes
2. Downvotes
3. Moderator replies etc.

This would allow customers to easily import their legacy ratings and review data into the D365 e-commerce platform.

As more customers adopt omnichannel commerce - including Store Commerce (Retail Channel), E-Commerce, and Customer Service (Call Center App) - it would be beneficial to integrate the Media Library / Omnichannel Media Management feature with D365 F&O Call Center. This integration would ensure that product images uploaded in the standard CMS system are also visible to Call Center users when they query products in F&O.

Pain Point:

Currently, for Call Center users to see product images, the images must be manually imported into D365 F&O using Data Management Framework (DMF). This adds an extra step, especially when the same product is already being used across POS and E-Commerce channels.

Advantage:

By integrating the Media Library / Omnichannel Media Management with F&O, it can also serve as a centralized workspace to assign product media, ensuring a seamless and efficient media management process across all channels.

Currently, D365 provides the option to generate the 'Channel Price Report Job' print archive only. It would be very beneficial to have the capability to choose a print destination for this report. This would enable users to send the generated report via email as part of a batch process. This report contains key information, such as price changes, that must be reported to product managers and the administration team, who can be notified via email.

Gap Description:

Currently, there is no standard entity available for bulk importing/exporting IP address configurations for registers in D365 HQ.

Current Problem:

When a company uses Adyen Terminals as its payment provider, it is necessary to set up the IP addresses for each terminal. If the company has multiple stores and registers, manually modifying the data for each register becomes quite challenging.

Recommendation:

It would be beneficial to provide a standard data entity that allows for bulk importing of this information, as it is commonly required by businesses in the retail & commerce area.

Navigation:

Retail & Commerce > Channel Setup > POS Setup > Registers > Register > Under Hardware > Configure IP addresses

Currently, to convert a quote to a customer order in POS, we have to first recall the quote and click edit order, which then triggers the "Edit Customer Order" operation. Due to this process, we are not able to differentiate the edit customer order operation and sales order creation from quote processes.

Business Requirement:

Cashiers must not be able to edit existing customer orders, but they should be able to convert quotes to customer orders and edit quotes as part of the standard quote-to-order process.

Current Limitation:

Currently, there is no possible way from a standard application to differentiate the processes, since both the process of editing a customer and the conversion of a quote to an order use the same operation 'Edit customer order.'

Proposed Solution:

The system should differentiate between:

1. Converting a quote to a customer order - This should use a separate operation or permission that cashiers can be granted
2. Editing an existing customer order - This should continue with the "Edit Customer Order" permission

Alternatively, provide a separate permission setting like "Convert Quote to Customer Order" that can be granted independently of "Edit Customer Order" permissions.

Additional Context:

Currently, due to this lack of process seperation there is no workaround within the standard configuration to restrict editing customer orders and maintain proper security controls while allowing the quote-to-order workflow to function smoothly.

Currently, discount configurations such as 'Discount compound behaviour' and 'Manual Prices and Discounts' from the commerce parameters form are applied universally across all retail channels within a legal entity, including both B2B and B2C scenarios. This blanket approach limits our ability to differentiate the discounting behavior between these channels, particularly in our operation of separate B2B and B2C call centers.

Current GAP:

In B2B sales, where bulk orders are common, discounts should be based on the original price to make selling easier. In B2C sales, retailers usually want to sell products at the highest price, so using a compounded discount works better.

Given this, the current pricing system doesn't allow for different discount setups based on the sales channel, which makes it harder to use across various channels.

When a loyalty card is issued to a customer in POS, the 'valid from' and 'valid to' dates are proper in HQ, but when viewing the same details in POS, the 'valid from' and 'valid to' fields can show an incorrect date offset by one day in the past.

The problem arises if the customer walks into the store at last date claiming that the particular loyalty card should still be active [which is in F&O], but when it comes to POS, it shows inactive on the customer card, leading to confusion and customer dissatisfaction.

I did log this as a bug 928070, but it was considered as 'by design', hence raising this as a feature now.