Dynamics 365 Commerce

LCS should support uploading and deploying multiple CSU extension packages (packages from different ISV/Partners and Customers) and show different packages deployed in the LCS UI.

This will avoid the manual merge of the packages from different ISVs and Partners and enable seamless deployment without involving any Dev persona for upgrade.

When doing discount pricing and campaigns there is a requirement by law in Finland that the end customer needs to be informed what has been the lowest price for the product within the last 30 days before the current discount campaign.

For example the product has a base price of 200 eur, in January the discounted price is 150 eur and in February another campaign kicks in that has a price of 100 eur. In February we should be able to inform customer that the sales price is 100 eur and the lowest price within 30 days is 150 eur.

This kind of feature would be needed in product shelf labels, reports and price inquiry at POS (Scale Unit API).

https://learn.microsoft.com/en-us/dynamics365/commerce/price-report this feature might be close to what is needed, but it is currently limited to 7 days.

The Store Commerce app may get multiple updates / fixes on a single day, but the LCS Shared asset library Store Commerce asset does not include or show release notes behind the Versions view of the said component.

Customer expects that when they are choosing the new Store Commerce App version on LCS, they will have information what has been changed in Store Commerce App 10.0.28 Version 23 and 10.0.28 Version 36 as an example.

Here is what is expected in more details:

• Go to LCS Shared Asset Library (1)
• Shared asset library -- Microsoft Dynamics Lifecycle Services
• Select asset type node Retail Self-service package (2)
• Scroll down to 10.0.28 – Store Commerce line on the list
• Mark the checkbox on this line (3)
• Click on “Versions” on the top of the list (4)
• LCS opens a side dialog containing all of the downloadable links for Store Commerce 10.0.28 app (5)
• For example the customer is using Store Commerce App 10.0.28 version 23 at the moment (released on Aug 31, 2022) (6) and they need to know what has been changed between app versions 23 and 36 (release on September 20, 2022)
• The Release notes column (9) is empty ; that could contain the aggregated release notes containing all of the changes in app 10.0.28
• The general article of the 10.0.28 does not contain detailed information of the Store Commerce App versions (here 10.0.28/23 & 10.0.28/36)
• The customer can download the desired version using the version download link (8), but it’s just the installer, and contains no documentation regarding the contents of the changes in this downloaded version

It can’t be just “download and install the newest version of the app” if customer doesn’t know what the actual difference is between these 2 app versions. 

We, as Microsoft publish new Store Commerce App versions at a fast pace that customer can’t keep up with the new versions if they don’t know what really has been changed in the newer versions.

Lets say,we have registered few mode of Delivery, for example- A,B,C,D,E,F in HQ under Sales and Marketing>>Setup>>Distribution>>Mode of Delivery, There is busines needs that user don't want to see A,B,C, mode of Delivery when they create Inbound/Outbound inventory on POS. They want to see D,E,F only. 

This would help retail staff not to get confused or to spend time on selecting right mode of delivery when they see lot of mode of delivery because some mode of delivery we use in HQ could be specific for some customer group but not for inventory transfer.

The barcode scanning experience should be enabled for order fulfillment operations Pick and Pack.

Scenario:

Sales order for item A, item B, item C, item D.

These items should be picked first, but not packing slip updated yet.

In the store commerce app, order fulfillment operation we want to scan all barcodes for the sales order in random sequence. This should change the line state (inventory transaction status) to picked.

Current option is to select the line and mark it for being picked, but the form is not enabled for barcode scanning.

When you need to scan e.g. 5-20 customized products with unique barcodes per sales order validation through barcode scanning is a must.

Some retailers have a minimum threshold of Loyalty Points that are required to redeem for a fixed reward, e.g. redeem 500 points for $10 off. Additional rewards can be redeemed in increments of 500 points, so if customer wants to redeem 1000 points, they can get $20 off or 1500 points for $30 off. This is fairly common scenario when retailers allow fixed $ amount redemption when customer has accrued/reached a points milestones. This can be a configurable flag on the loyalty points redemption line so that user can set it to fixed points redemption or the standard behavior.

Customers encountered challenges while using the Store Commerce application during inventory counting processes.

The issue arises when scanning items for inventory counts; the application requires the user to manually define the location for each new item being scanned.

While the app automatically associates previously counted items with their existing locations, it mandates a manual location input for each new item added to the inventory count.

This operational requirement significantly slows down the inventory process, especially in scenarios where multiple new items need to be scanned and added.

It disrupts the workflow and increases the likelihood of input errors due to the repetitive nature of the task.

Suggestion: 

The implementation of a feature that allows users to set a default location for inventory counts within the Store Commerce application.

Having a default location would streamline the inventory counting process, reducing the need for repetitive manual entries and thereby enhancing efficiency and accuracy.

Could we please have the ability to add products to a customers wishlist from the POS. This should then be visible in the customer wishlist online. Currently wishlists are view only in the POS, but as part of a conversation between a sales associate and a customer we may want to save items for further consideration/later purchase, so we need a way of saving this for a customer, the wishlist would do this, if we can add to it from the POS

Provide a general parameter to say whether the deposit amount should include shipping charge.

If you now would have 50% desposit and the customer orders something with a shipping charge of 40. He deposit will include 20 for shipping. If the customer cancels his order in time/or later decides to do pickup in store, then you charged him 20 for nothing an a complete refund policy needs to start. 

with this parameter our customers can decide themselves how they handle deposits on shipping charges

From the B2B and B2C Ecommerce there is no possibility for web users to start a return process. Customers may want to return something they bought online for many different reasons, and in the D365 Ecommerce solution, there is no functionality to meet this requirement. In the return policy of our clients, you might need to create returns for customers to return purchased items and refund a customer's payment.