Dynamics 365 Commerce

Having the ability to manage barcodes for different purposes would help during the receiving process as well as the sale process. This would prevent the POS from scanning a barcode intended for product receipt during the sale process, and vice versa. For clarity, the following business process can be considered:

1. Create two barcodes for a product with the same unit of measure.

2. Identify the purpose of each barcode in the POS operation.

3. During receiving, if the sale barcode is scanned, it should not allow the receipt to be performed.

4. During the sale, if the receipt barcode is scanned, it should not allow the product to be added.

This way, receiving and selling can be controlled with different barcodes, avoiding scanning an incorrect barcode.

Currently, when creating alternative prices through 'Margin Component Price Adjustments' by percentage, the prices often include decimals. This can be problematic for retail and commerce customers who prefer rounded prices for better customer experience and operational efficiency. However, the existing smart rounding functionality is not applied in this scenario.

Integrate the smart rounding functionality into the margin component price adjustments process. This enhancement would make sure that prices are automatically rounded according to predefined rules instead.

Currently, Dynamics 365 provides an option to mandate starting and declaring amounts. However, we propose adding a new parameter in the functional profile to block sales transactions until a starting amount is entered.

Business Justification:

Store personnel sometimes forget to enter the starting amount at the beginning of the day and proceed with sales. As a result:

• When performing the end-of-day process, the initial cash amount is unknown or estimated, leading to inaccuracies.
• This causes discrepancies in the daily statement, requiring finance teams to manually investigate and correct errors—an inefficient and time-consuming task.

Separate form requires for delete privilege in transfer journal/ Movement journal; this is the common requirement.

Add support for shared cache across CSUs. This would help prevent many real-time service calls into back office. Services like Azure cache for Redis, this could help performance in many scenarios.

Hi there, I use the Price Simulator to check whether there are any promotions or markdowns applied to various products, or as a Price check to compare between D365 and our Legacy system.

At the moment, I can only add one product to test at a time.

Is it possible to add a 'Add products' feature like we have in the Discounts module? I'd like to be able to add more than one product at a time to view them quickly.

Or is there a better way to see the current status/price of a list of products in one view?

Thank you

There is a a feature called, "Support the Site and Default order settings on Customer orders", to enable Default Order Settings for select SKUs within D365. In the feature management section, it states that this feature is for Retail and Commerce, stating if "any customer order is created at AX-Call Center & e-commerce. Customer orders created through POS do not respect this setting."

From our findings, the default order settings also impacts manually placed orders from within D365, so it is not just for e-Commerce or Call Center. This heavily impacts our ability to use this feature, since we have many other channels that would be impacted. Furthermore, the reason and importance of this feature for us is to prevent customers from order too much of the same product, which has resulted in customers wiping out all inventory of select SKUs during peak seasons. This directly impacts sales, since our Wholesale locations are then missing key products to sell seasonal products.

There should be a feature for Commerce that is strictly to enable Default Order Settings for select SKUs for Commerce only. This could be a feature that is only available within the Commerce Product or Navigation Hierarchy or the Catalog itself, preventing any impacts to other channels. Currently the default order setting feature lives within the "Retail Released Products" section and impacts the inventory at all our channels.

Released products have Default order setting in which you can define sales order parameters, you can use multiplier "1" to sell whole quantity in increment of 1 but this configuration is not applied to Store Commerce App (POS). This should support to POS as well.

When a POS cashier attempts to checkout a transaction and fails in Online mode due to a network disruption, they are allowed to manually or automatically switch to Offline mode and modify the cart in any ways (add/modify/void sales lines or tender lines) before attempting checkout again. This creates a potential issue, as it’s possible for the Online mode checkout to have succeeded before or during the switch to Offline mode, leading to inconsistent transaction data due to modifications made in Offline mode.

When we create a common list or add metadata in the SharePoint library, we allow all people who have access to the list/SharePoint library the same access to all lines. This means that if we would like people to edit the list, they can add all lines, not just the ones that concern them.

I would like to be able to add access based on the metadata. So, if I have a choice column, I could use it to set access rights. The owner would have access to all data, and then I could add group A that can only edit lines marked under option 1, and group B could edit only lines for option 2.

All of them see each other's lines and have a full overview, but they don't mess with each other's data.