Dynamics 365 Commerce

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.

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 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.

Idea Proposal: Enhancing Purchase Agreement Selection in D365 F&O

Problem Statement: Customers need the ability to manually select purchase agreements for planned purchase orders during the firming process. Additionally, they require an extensibility point to customize the purchase agreement selection logic.

Solution Overview:

• Identify Relevant Code:Locate the code responsible for automatic purchase agreement selection during firming (e.g., within the PurchAgreementFirmingService class).
• Understand the existing logic that determines which agreement to select based on criteria such as vendor, item, and date.
• Create an Extension Point:Collaborate with the development team to introduce an extensibility point in the code.
• Consider the following options:Event Handler: Add an event handler before or after the assignment of the agreementId variable. This allows custom logic to execute during the firming process.
• Chain of Command (CoC): Extend the existing method using CoC to modify the agreement selection behavior.
• Custom Service: Develop a custom service that handles agreement selection and replaces the standard service.
• Customize Agreement Selection:Once the extensibility point is in place, developers can create custom logic:Manual Selection: Implement a user interface where users can manually choose the purchase agreement during firming, overriding the system’s automatic selection.
• Business Rules: Apply business rules (e.g., priority, preferred vendors) to determine the most suitable agreement.
• User Preferences: Allow users to set preferences for agreement selection.
• Testing and Validation:Rigorously test the customized agreement selection process to ensure accuracy and reliability.
• Validate the solution with real-world scenarios and user feedback.

By enhancing purchase agreement selection, we can empower D365 F&O users to tailor their experience and improve efficiency in procurement processes.

Hi,

We got so many comments from the users that the text and some buttons in MPOS really could be bigger, to help the users to work with the product.

Small text and buttons lead to error when clicking and a hard time reading the instructions in ex pop ups.

The buttons in the left menu (transaction view, home view and products) is most critical since it is very small.

Also over all, all text could preferably be bigger and alsomaybe bold or better applied for the eye to catch.

Is this a possible thing for you to look into?

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

When recalling a quote at POS, there should be the ability to filter on quotes by the status of the quote, for example "Sent" to identify quotes that have been sent, but not yet confirmed. There is currently the functionality to only search by the status of customer orders.