Dynamics 365 Commerce

The Retail and Commerce module provides a common setup using an Offer Id for Price adjustments and discounts allowing one or more to apply to the same transaction sales line depending on the setup. However, when retail sales transactions are viewed the applied Price adjustments are not visible at all to explain how the sales price was altered from the base Item price. All other applied discounts are visible by Offer Id so that they can be surfaced in downstream reporting.

It seems like an oversight to not do the same for Price adjustments given the identical nature of their setup.

Gap Description:

Currently, there is no standard entity available for bulk importing/exporting IP address configurations for registers in D365 HQ.

Current Problem:

When a company uses Adyen Terminals as its payment provider, it is necessary to set up the IP addresses for each terminal. If the company has multiple stores and registers, manually modifying the data for each register becomes quite challenging.

Recommendation:

It would be beneficial to provide a standard data entity that allows for bulk importing of this information, as it is commonly required by businesses in the retail & commerce area.

Navigation:

Retail & Commerce > Channel Setup > POS Setup > Registers > Register > Under Hardware > Configure IP addresses

Description

Please add the ability to attach the receipt as a PDF file to the receipt email sent from Dynamics 365 Commerce.

The PDF should be an exact representation of the printed POS ticket, including layout, branding, totals, tax details, and footer text.

Business Need

Many of our customers require a formal, printable receipt for:

• expense notes
• reimbursement workflows
• travel and expense systems
• bookkeeping and accounting processes
• VAT and audit documentation

The current receipt shown inside the email body often confuses customers, and many expense systems do not accept email-embedded receipts as official documents. These customers specifically need a PDF file that looks exactly like the receipt they would receive in-store.

Requested Functionality

• Add a configuration to enable “Attach PDF receipt to email”.
• PDF should use the same layout as the store’s printed POS ticket.
• The PDF should be attached in addition to the HTML email receipt (unless disabled by the retailer).
• Should work for Store Commerce, CPOS, and Tap to Pay workflows.

Benefits

• Provides customers with a universally accepted, standardized receipt format.
• Reduces confusion caused by HTML-only receipts.
• Supports compliance with expense management and bookkeeping requirements.
• Aligns Commerce with common industry practices where PDF receipts are standard.

Digital Asset Management in D365 Commerce Site Builder lacks the search, filtering, bulk operations, and validation capabilities required for efficient maintenance of product media at scale. As a result, tasks such as identifying products missing images, replacing outdated assets, ensuring quality standards, preventing broken media links, and cleaning up unused files become highly manual and error-prone.

This gap reduces productivity for merchandising and content teams, impacts time-to-market for new products, and increases the risk of poor customer experience (e.g., missing or low-quality product images in the storefront). To address this, we propose a set of targeted improvements

:

• Robust search and filtering (including “products without images”)
• Bulk upload, bulk tagging, and bulk replacement
• Dashboards for missing or low-quality media
• Metadata, tagging, and version control
• Media quality validation and AI-assisted automation
• Orphan asset detection and cleanup tools
• API and integration enhancements for PIM/DAM connectivity
• 
  

Together, these improvements will reduce manual effort, increase data quality, improve storefront consistency, and significantly streamline ongoing product media maintenance in D365 Commerce.

Currently, custom controls are supported on larger display versions (desktop/tablet) of POS views but not on mobile views. This creates an inconsistency in behavior between phone and tablet/desktop devices. Extensions targeting CustomerAddEditView do not apply to CustomerAddEditViewPhone because these are separate views with different schemas. As a result, critical custom fields required for customer creation and editing are unavailable on mobile devices.

Suggested approach is to enable support for custom controls on mobile POS views, similar to what is available for desktop/tablet views. This would allow extensions targeting CustomerAddEditView to also apply to CustomerAddEditViewPhone, ensuring consistent functionality across all device types.

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.

In eCommerce, it would be nice to have a "alert me when back on stock" feature, where the eCommerce user can receive an email when the goods are back on-hand. We see this feature available in many other eCommerce solution, and this is a requested feature.

Currently While Deploying Package in D365 Commerce LCS Page along with the Scale Unit it only Shows InProgress and User have to Click on each Scale Unit to check the Step at which Package is running.

If we can show Step Number of Package Deployment along with In Progress it will be easy and convenient for the User.

Thanks

Ayush Jaiswal

9986622407

The current functionality for Self-checkout does not have the capability of sending email receipts to the customer. From a user experience perspective, this would prove invaluable to best service the customer on their terms.

This would use the standard email logic that the POS already uses, just extending the logic to a register marked as self-checkout.