Dynamics 365 Commerce

On the POS there is the option to set up the buttons "View available discounts" and "View all discounts".

If you scan an item that is part of a currently valid promotion and then tap on the "View available discounts" button, the appropriate discount for the item is displayed, but only the name from the "Name" field of the discount from the settings in the back office. 

Although this can be freely selected, it does not usually contain the conditions of the discount described in detail.

On the discount itself, in the "Details" fast tab the "Description" and "Disclaimer" fields, among others, can be filled out.

It would be great if the contents of these fields were also displayed on the POS when a cashier displays a discount.

In the practical example, one of our customers has a big product portfolio. Up to 100 different discount campaigns are active at the same time. These are difficult for a cashier to remember. 

It is helpful here to at least be able to access the discount information.

This would also create a form of communication transfer from the marketing department to the store.

The sealed hardware installation requires the .exe to be run from a terminal with all the data needed whereas the self service installer used a UI to receive the data. The self service installer downloaded IIS and created the necessary Registry keys such as TLS 1.0 Client and Server and TLS 1.1 Client and Server, with the necessary DWORD values. The sealed installer does not do this thus requiring manual addition of the keys and the installation of IIS. Can the sealed installer not be made to do this as well similar to the self service installer.

Background & Business Need

In retail environments, especially at the Point of Sale (POS), predictable credit memo number sequences can pose a significant fraud risk. As highlighted by a customer in a recent support interaction, if credit memo numbers follow a sequential pattern, a cashier could potentially guess and manually enter the next number in the sequence. This opens the door to unauthorized or fraudulent returns.

Proposed Enhancement

To mitigate this risk, we propose enhancing the credit memo number generation logic by introducing a randomized component. 

Benefits

• Reduces the risk of fraudulent returns by making memo numbers non-predictable.
• Enhances security and auditability at the POS.

Customer Impact

This request stems from a real-world concern raised by a customer actively using D365 Retail and Commerce. Addressing this would not only improve security but also demonstrate responsiveness to customer feedback and operational realities.

Payment methods are configured per call centre channel to allow processing sales order and take customer payments.

Navigate to

1. All call centre (Retail and Commerce > Channels > Call centres > All call centres)
2. In action pane, Under setup tab and setup group, click Payment methods
3. In the payment methods screen, select a payment method and click Payment transactions.

Notice, that the payment transaction only shows all the payment transactions from store, but it doesnt show sales orders created via call centre thought they are also called Retail sales (Retail sales checkbox is marked yes for such orders).

It would be great if we can see sales orders per payment method used in call centre (like we can see store payment transactions) or have a way to filter out orders paid via certain payment method.

Current situation:

At the POS in the SCA during the checkout there is a step called "Do you want to email the receipt?"".

In this step you need to enter your email address and there is also a boolean field that must be switched from “off” (default) to “on” to activate the "receipt per email" function.

However, there are two additional buttons in the step: “Send” and “Don't send”.

Both buttons are active and clickable, regardless of whether the Boolean field is set to “Off” or “On”.

Possible outcomes are:

1. Boolean "Off" + "Send" = no email receipt is sent
2. Boolean "On" + "Send" = email receipt is sent
3. Boolean "Off" + "Don't send" = no email receipt is sent
4. Boolean "On" + "Don't send" = no email receipt is sent

One step is redundant here.

Idea:

Remove boolean field.

Leave the “Send” button inactive as long as no valid email address has been entered.

If a valid email address has been entered then the “Send” button can also be clicked.

A format validation is sufficient to validate the email address - anything@something.TLD

Both "Synchronize orders" and "Validate store transactions" jobs allow selection of channels using the hierarchy but can only run for channels in the current legal entity.

This means that you need to create the jobs in the batch queue per legal entity instead of grouping them into e.g. regions or one job for all legal entities.

Objective: To enhance the security, efficiency, and customer service of return transactions in cash-and-carry stores by requiring valid customer details (contact number and email) for all return orders.

Feature Description: Implement a feature in the Dynamics 365 Commerce Point of Sale (POS) application that mandates the collection of valid customer details (contact number and email) for all return order transactions in cash-and-carry stores. This feature will ensure that every return transaction is associated with a verified customer, thereby improving the overall return process.

Justification:

1. Customer Verification: Ensures the identity of the customer making the return, reducing the risk of fraudulent returns.
2. Return Tracking: Maintains a detailed record of returns associated with specific customers, aiding in inventory management and return pattern analysis.
3. Enhanced Customer Service: Enables the store to provide better customer service by notifying customers about the status of their return or any issues that may arise.
4. Marketing and Communication: Allows the store to use the collected contact information for marketing purposes, such as sending promotional offers or updates about new products and services.
5. Compliance and Reporting: Helps in complying with legal requirements for collecting customer information for returns, ensuring adherence to consumer protection laws.

Implementation Details:

• Modify the return order workflow in the POS application to include mandatory fields for customer contact number and email.
• Validate the entered customer details to ensure they are in the correct format.
• Store the customer details securely and associate them with the return transaction record.

Impact: This feature will enhance the security and efficiency of return transactions, improve customer service, and provide valuable data for marketing and compliance purposes.

When the receipt print prompt appears, the focus is currently set to the toggle on/off button instead of the "Print" button.

To improve efficiency, it is recommended to set the default focus on the "Print" button. This adjustment will allow the user to press "Enter" to print the receipt automatically, without needing to click the button manually.

Implementing this change will enhance the cashier's performance by streamlining the transaction process and receipt printing.

Currently on POS side, when store staff counted cash (start amount, bank drop, safe drop, declare tender), it only print the amount. There is no report to view the counted qty info of each cash denomination. So when there is difference, they would be able to know which denomination was counted wrong.

And in D365 financial statements, for cash payment method, there is Cash declaration menu, when I click it, in the opened form, I can see cash denomination list, but no qty or amount logged there. Customer is not happy with that. They would like see the counted qty when they try to check the difference amount.

So on POS side, we want the counted qty and amount of each denomination to be printed as well. And can have a report to view those detail info.

On D365 side, we want the Cash declaration form opened from financial statements (both open and posted) to show counted qty and amount of each denomination.

thanks

Alan

When using a MediaServers created through IIS for all self-hosted environments.

After installing the latest version or any version update, we see that the MediaServer is deleted from the IIS during upgrade. Can you add a way or any workaround to avoid this situation?

The current workaround is to go to each CSU server and manually recreate it, but this is time consuming and isn't very efficient overall.