Dynamics 365 Commerce

With self-checkout being all the rage, many retailers with loyalty programs will want to make it simpler for a customer checking themselves out to add their loyalty information to a transaction.

With current functionality, the customer would need to add themselves to the transaction, and remember to do so. The only standard function that could be done is an info code that prompts the customer to add themselves.

A more streamlined approach to this would be to allow an operation to be triggered from an info code subcode (where we can currently trigger another info code or a product). This would allow the following scenario:

• Info code prompt: Are you a loyalty customer?
• Subcode 1 = Yes, trigger function = Operation, Operation = Add customer

Many other possibilities are opened with this functionality, but from an SCO perspective this will be extremely helpful to have customer-prompted operations.

At present there is no option available for B2B customer to perform a return from the D365 commerce web shop. For performing a return the customer need to reach out to then seller on email or on a call and then a return order is created on the D365 F&O. To avoid this cumbersome process then customer wants to perform a return on the B2B site itself. Also they want to see the credit note information under the My Account section for the returns they have performed from the B2B site. Looking forward to have it on the next release to make the website more user friendly for customers.

In the current Dynamics 365 Commerce loyalty functionality, loyalty points redemption is treated as a payment method, reducing the balance due on the transaction. While this may align with U.S. tax practices, it creates a serious compliance issue in EU and Nordic markets.

In many jurisdictions – including Norway – VAT is calculated before payments are applied. Therefore, when loyalty points are used as "payment," the system calculates VAT based on the full sales amount, even though the customer has effectively received a discount. This leads to:

• Incorrect VAT reporting (VAT is overstated).
• Reduced margins for the retailer (VAT paid on value not received).
• Possible compliance risk during audits.

Requested feature:

Introduce a configurable option (via loyalty setup or Commerce functionality) to allow redeemed loyalty points to be applied as a discount, either:

• As a manual order-level discount; or
• As a calculated loyalty discount line item before VAT calculation.

This would:

• Ensure VAT is calculated on the actual revenue received.
• Align D365 Commerce with EU tax requirements.
• Offer greater flexibility for international retailers.

Current workaround:

This requires custom development using POS triggers or CRT extensions to convert loyalty redemption to order discounts. Such workarounds introduce maintenance overhead and inconsistent behavior across channels.

Business impact:

For retailers operating in the EU, this is not just a feature request – it is essential for correct financial reporting and compliance.

We used MPOS with a Windows Kiosk account locked down to just run MPOS. When we upgraded to Store Commerce, we lost the option to add the Store Commerce App in the Windows Kiosk mode drop down set up. Can we get this re-added so we can move away from everyone having to log into Windows with their AAD account? We manage 850 registers.

The "transaction time" is not available on the SalesTransactionsV2 entity and the RetailTransactionSalesLineV2 table. It is an important information that is needed for analysis when checking out sales per item with relation to the transaction time each sales occur,

Customer can enjoy Trade agreement prices on B2B and BC2 E-commerce, defined in back office specific to individual customer or any group of customers. But on Product List Page (PLP), Price filter only use the product Base price to show "Minimum" and "Maximum" values

For Example minimum base price for a product is $ 5 to a maximum of $ 250, on PLP price filter will show the slide bar from 5 to 250.

If customer has a special price based on their trade agreement, and if Minimum price for a product is starting from $ 1 to a maximum of $ 100, Price filter should adjust accordingly and show from 1 to 100 but currently it will keep using the Product Base price and still show 5 to 250 which a really bad user experience.

The Idea is while excluding products or categories inside the assortments it should be removed also from the retails offline database specifically from ECORESPRODUCT table instead of removing it from the view level only.

Customer is able to apply a price override in a call center order, and they are using the override permissions and order price control settings, however, the price override is not tracked in any reports. they do not see it in order events, marked as a price override in customer service or in the price override report. so please consider to activate this behavior so the customers can track easily the price override on the call center

Process a POS sales order that has broker commissions created from a broker contract. Broker commissions created against sales order line/s. Broker claim created on sales order invoice update.

Process a POS return (using the receipt number or via the journal view in POS) for the previous sales order.

Expected result: The broker commission should also be reversed against the negative sales order line.

Actual result: No broker commissions are created at all for the return.

This would be a useful feature especially considering there is a valid business case for it: We have a customer who are planning to go live soon, and this enhancement would be of great value.

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.