Dynamics 365 Commerce

Wish there is an option to easily access the enterprise portal and easily request eligible courtesy prices at own consumer request at will (e.g. based on loyalty points, privileges, invoices or POs policies basis.)

Currently, if a customer scans an extra item while the payment screen is active on self-checkout, the item remains in the cart and is processed after payment. This can lead to confusion and missed charges. The proposed change is to block all item scanning during the payment process, ensuring that no new items can be added once tendering has started. This will improve transaction accuracy, reduce errors.

We need API-level support in Site Builder to automate the maintenance of product images in the media library.

Our media library currently contains more than 55,000 images. These have been manually uploaded over time, and many are now outdated. With the volume of products we manage, manual updates are no longer sustainable.

We regularly receive feedback from customers and suppliers when old or incorrect images appear in the webshop—for example, seasonal packaging from previous years still being displayed. While we update these manually when discovered, the current process does not scale.

Our external image bank provides event-based alerts whenever product images change. To respond to these updates automatically, we need Site Builder to expose APIs that allow external systems to interact with the media library in a controlled and supported way.

Specifically, we need API capabilities to:

1. Check whether an item currently has an image stored in the media library (for example by searching for filenames that include the item number).
2. Retrieve the last-modified timestamp of an existing image (filename-based or metadata-based).
3. Delete image files associated with a specific item (filename-based deletion is sufficient).
4. Upload and publish new image files with defined metadata.

With these capabilities, we can implement a fully automated process where product images are kept up to date the moment they change in our external image bank. This would ensure accuracy, reduce manual workload, and prevent outdated visuals in our webshop.

Adding API support for these operations in Site Builder would bring Dynamics 365 eCommerce in line with industry expectations for automated product content maintenance.

Thank you.

Currently, the Store Commerce app for iOS does not properly account for the Dynamic Island (camera notch), which causes the layout to shift downward. As a result, the operation bar ends up below the visible area of the screen. Microsoft’s initial workaround was to make the application scrollable, but this makes day-to-day use tedious and inefficient.

As with all other iOS apps, the header content should be adapted to accommodate the Dynamic Island. This is particularly relevant now that the new Tap to Pay feature works so well on iOS. 😄

Interestingly, the app functions perfectly on an iPhone SE (which has no notch), but since these devices are no longer in production, this isn’t a viable long-term solution.

I recently submitted a support case for this issue, but it was flagged as working as designed. I understand that maintaining uniformity with CPOS may be a factor, but since the product is marketed as being OS-independent, I believe this inconsistency should be addressed going forward.

This is therefore a feature request directed toward Microsoft.

Currently, when advanced tax calculation is turned on in Globalization Studio, F&O recalculates taxes during invoicing, overriding any tax values applied at POS (including exemptions). The “Don’t recalculate tax” parameter seems to be overridden as well.

What I think should enhance this is to add configuration option or parameter that allows POS-originated transactions to retain their tax values during invoicing, even when advanced tax calculation is enabled. Or make it so that Don't recalculate in Commerce Parameter is honored even when Advanced Tax Calculation is enabled.

Hi all, if we start an inbound operation on POS, we have the option to create a new purchase order. We don´t need that function and want to disable it for our users. So we withdraw the permission from the users.

Unfortunately the check for the permissions is at the end of the process (when you want to confirm the new purchase order) and not at the beginning.

So it would be great, if the permissions of the user would be checked right after the click on "New purchase order".

Actual behaviour:

• Start new inbound operation
• Create new purchase order
• Select vendor
• Click confirm
• Message "Manager-Sign in" is required

Desired behaviour:

• Start new inbound operation
• Create new purchase order
• Message "Manager-Sign in" is required

Best regards

Hello Team

Requirement: Enhancement to Threshold Discount Application Logic

Current Behavior

In the current (OOB) implementation of threshold discounts, the discount is applied to the most expensive products in the transaction once the threshold condition is met.

Expected Behavior

Business requirements dictate that threshold discounts should instead be applied to the least expensive products in the transaction, ensuring that promotions are consumed starting from lower-value items.

Attempted Approach

We attempted to achieve this behavior by extending the CalculateDiscountsServiceRequest, but this did not resolve the requirement.

Requirement / Request

1. Confirm whether there is an existing extension point in the threshold discount functionality that allows customizing which products the discount is applied to (most expensive vs. least expensive).
2. If such an extension point is not currently available, we request that Microsoft:

• Expose an extension point in the discount calculation pipeline that enables custom logic for determining the product prioritization order for threshold discounts.
• Or provide guidance/recommended approach for implementing this expected behavior in a supported way.

Business Justification

Applying threshold discounts to the least expensive items is a critical business requirement for the retailer’s promotional strategy.

Thanks

Deepak Poddar

We would like to give feedback on lack of release versions notes/documentation that comes with D365 F&O releases. We have observed that not all changes introduced in a version are documented in the release notes - especially when relating to the critical area of Commerce / Payments, which results in business impact and even financial loss.

1. For example, in v42 / v43, Microsoft internally introduced a new flight called “RetailSavePaymentCaptureTokenFiledValueInCustomerOrderPropertyFlight” (This flight changes the AUTH request to CAPTURE request). This flight was enabled by default when the system was upgraded from v41 to v43. As a result, our asynchronous customer order logic was heavily impacted. Only after multiple calls and meetings with Microsoft did we learn from Microsoft had introduced this flight in v43 — yet it was not mentioned anywhere in the release notes. As a result v43 was delayed for us by 2-3 months.

2. Now, after the v45 upgrade, we are once again facing issues with asynchronous customer orders. We are still analyzing what changes may have been introduced, but this uncertainty makes it difficult for us to take proactive action. Just to share some figures around sales from such orders - In upcoming peak sales period (Nov through Dec to early Jan) forecasted sales is 1 million GBP per month from asynchronous customer orders (also called shop mail orders) where customer places an order in store to be delivered by the Distribution Centre.

3. After upgrading from v43 to v45, we started facing an issue with the token scope in the CreditCardCust table.

In v45, the system is now sending the value as non-recurring instead of unknown. This behavior started only after the v45 upgrade, even though we are not using the non-recurring feature.

As a result, our Async Customer Orders are failing because we cannot use duplicate UniqueCardId, and the system is unable to create Async orders.

To validate this, we installed v44, where the token scope still appears as unknown and the system is able to create Async Customer Orders without any issue. From our side, we are unable to identify what changes Microsoft has introduced in v45 that caused the token scope to appear as non-recurring. If this issue was related to our code customization, the same behavior should also have occurred in v44, which is not the case

4. Each release upgrade is getting increasingly challenging due to lack of information provided in release notes, particularly in the store commerce area – this has been flagged to Microsoft on a number of occasions but there has been no improvement. For this reason we have to do a full POS regression test each time as we don’t know what has changed.

Since version 41, changes have been made in the area of payments which is critical, the documentation is poor, response from MS on issues logged is very slow and this is a difficult area to troubleshoot as we need to do physical testing with cards and involve our payment provider, elongating the time to resolve issues.

We feel it would be highly beneficial if the release notes contained complete and transparent details of all changes (including new flights and feature toggles). This would allow us to properly assess the impact in advance, plan mitigation steps, and avoid disruption to customers operations.

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

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