Dynamics 365 Commerce

I would like to suggest adding a configuration option that allows the POS to automatically log off even when there is an active or open transaction.

Business Need:

In our business operations, there are scenarios where it's necessary to enforce an automatic log-off from the POS, regardless of whether a transaction is currently open. Currently, the system only supports automatic log-off when there are no open transactions, which limits our ability to maintain security and compliance in certain use cases.

Having the flexibility to enable automatic log-off even with an open transaction would greatly enhance our control over POS sessions and help us better align with our operational requirements.

Thank you for considering this enhancement!

It would be a very welcome addition if we could provide additional discounts in trade agreements D365 f&o on top of standard discounts based on multiples fixed in unit conversion.

Think piece, box, pallet.

1 piece is discount 10%

1 box being 10 pieces is 10% base + 2% = total 11.8% discount

1 pallet being 100 pieces is 10% base + 5% = total 14.5% discount

Customers order 10 pieces, not 1 box!

When ordered 11 pieces, standard discount of 10% applies.

It must be possible to indicate per item and per unit whether a discount should be calculated in multiples.

This allows you to send customers to packages because there is an advantage for them without having to keep track of it manually.

This is also helpful for purchase.

Advantage Explanation

Use of existing infrastructure Commercial agreements remain central management point

Users understand it Multiple logic is visual and configurable at line level

Flexible at item and unit level You can define different multiples per product or line

Less customization in pricing You do not need to create separate price rules per multiple

Maintainable Functionally and technically scalable

When using the "suggest fulfillment location" function in the Sales Order Details form directly on Sales Order lines, the popout lists the Top 10 available warehouses ordered by aerial distance (km), and each listed warehouse displays the distance (km) to the shipping location. It would be helpful if the popout can also display the ATS (physical available) inventory quantity associated with each warehouse. This would help the user make a more informed decision on where to route an order for fulfillment, without having to first check the inventory availability at each location. For example, it may be more desirable to route an order to a location that has several units of physical available inventory vs. a location with 1 unit left in stock (even if the location with 1 unit is closer to the delivery address)

Aerial Distance is usually not the number one nor only factor in determining which warehouse to fulfill from.

It would also be helpful if using the suggest fulfillment location automatically reserved inventory at the selected warehouse. By default, if DOM hasn't run on the order yet, when using suggest fulfillment location, the inventory is not reserved.

Currently, self-checkout on Store Commerce does not support changing the UI language. In countries such as Spain, France, or Germany, many customers are monolingual native speakers, while a significant number are tourists or non-native speakers. This creates a major business challenge, as many self-checkout users may be unable to understand the UI or on-screen instructions.

To address this, we require a self-checkout feature that allows customers to select their preferred UI language directly at the terminal. This capability is essential to provide an inclusive and user-friendly experience for all customers, regardless of their language background.

In 10.0.44 we got the feature "Approved customer lists". But it does not with Commerce/eCommerce. Why ? We need it for Commerce/CSU also.

It would be beneficial to introduce an option that allows the system to intelligently distinguish between manual entry and barcode scanning, and respond accordingly:

• When the item is entered manually (ItemID):
• The system could display a screen that enables the user to manually input the product’s weight.
• When the item is scanned using a barcode that includes embedded weight information:
• The system could:
• Automatically extract and apply the weight from the barcode.
• Skip any manual weight entry or confirmation prompts.
• Prevent the user from modifying the quantity, thereby preserving the integrity of the scanned data.

This enhancement would streamline operations, reduce the likelihood of manual entry errors, and ensure consistency in how product weights are handled across different entry methods.

The current out-of-the-box application allows us to review credit card transactions for online and in-store customer orders through the Credit Card History form. This form includes the Adyen Merchant Reference and PSP Number, which we can use to review the Adyen transaction report.

However, we would like to have the same capability for regular retail transactions. Specifically, we propose adding a field in the payment transactions form or the store transactions form to associate the Adyen PSP reference number and the Merchant reference number of that particular transaction.

Currently, businesses are facing a hard time reconciling the transaction reports with Adyen and D365 because of this feature gap

Currently, during system deployments in Dynamics 365 Commerce, the balance inquiry and redemption service for gift cards is temporarily interrupted. This downtime poses a significant operational risk for retail companies, especially those with a global presence across multiple time zones and 24/7 operations.

We propose that Microsoft implement an improvement to ensure continuous availability of this service during deployments, thereby maintaining business continuity and a seamless customer experience.

Problem it Solves:

For a fashion company with international operations, the unavailability of the gift card service during deployments affects both physical stores and the online channel, compromising sales and customer trust. This situation is particularly critical in markets where gift cards are a common payment method.

Benefits for Other Organizations:

This improvement would benefit all organizations using the gift card service in D365 Commerce, not just those in the fashion sector. Retail, grocery, electronics, and other industries with global operations would benefit from greater system resilience and improved customer experience.

Concrete Use Case:

During a scheduled deployment, a company with stores in the Americas, Europe, and Asia experiences failures in gift card redemption on its e-commerce platform, resulting in lost sales and customer complaints. With this improvement, the service would remain active and functional, eliminating this risk.

For Store Managers and Loss Prevention - it's important for a store to have a clear understanding of their entire cash picture at the close of day. Currently, as each shift closes throughout the day, a Z report is generated that shows the over/short for a particular drawer/shift. Therefore, store managers have to collect these Z reports and manually figure out the total over/short for the day across the shifts/cashiers/drawers. They also need to see a total cash and check collected for the day to help them determine their bank deposit amounts. I don'[t believe this information can be easily obtained today by the store manager today unless they hold onto the Z reports of each shift and manually add them together at the end of the day.

While D365 will allow users to see a total cash, check and total over/short on the ERP side (statement posting screens) it's important to note that most store managers do not use the backoffice screens nor have access to the statement posting form as these are finance related functions.

Loss prevention is typically also wanting to be notified by end of day how much total over/short the store had in terms of cash and may want store managers to inform them of this information as part of end of day process - therefore waiting for statement posting and going to finance for the data causes time delays that could impede/delay the investigation.

It does not appear that the POS easily provides the store manager a proper "end of day" cash, check and over/short report - this could essentially be a consolidated Z report that recaps all the shifts closed during the defined "day" and displays the overall/net over/short by payment type for the store for the day.

p.s. - please ensure Ashish sees this :)

Currently, when a cashier scans a coupon or enters a coupon code at the POS, and the transaction does not meet the coupon’s requirements, no message or feedback is provided. Displaying an error or informational message explaining why the coupon cannot be applied would help reduce confusion and save time at checkout.