Shafeeque P. Lead Consultant

Unlike price check screen in EPOS in 2012 R3, the barcode input stays on the text box even after the result is displayed on screen in MPOS. To check the price for next item, the users needs to manually clear the bar code of previous search.

Most of our customers who move into Dynamic 365 Commerce from other platforms(Magento/Shopify) wants to show the product images on the email notifications send to customer. This is seen as default functionality in any ecommerce platform.

Currently product images uploaded to the Site Builder have the public URL of the format https://images-us-prod.cms.commerce.dynamics.com/cms/api/xxxxxxxxx/imageFileData/yyyyyyy4w?pubver=1 . If this can be provided in the format https://blog.shafeeque.in/wp-content/uploads/Products/14000000002400_000_002.png (pointing to the image file), the service can be reused to show images on CPOS,MPOS and Store App.

If a user tries to create a customer profile with email ID/phone number that already exists in channel DB. The system should show a warning/message a customer profile already exist with the same information. This will avoid customer profile duplication to a very large extend.

When a sales order is created from Dynamics 365 Commerce, the warehouse field on the sales order header is inherited from the Ecommerce warehouse. Once the order is processed by DOM, the warehouse is updated on the sales order lines based on the DOM rules. However, the warehouse on the sales order header remains unchanged.

If the warehouse on the header can also be updated, this will ease lot of efforts for security configurations and reports.

Note: I understand the fact that with DOM, you can fulfill once SO from multiple warehouses.

Currently, not much placeholders are available for Commerce transaction events notification email templates. It will be good to have an option to attach the sales order invoice in PDF which will be generated from SO invoice function.

Currently when a product is created as Product Master, the define media template option generates two kinds of URL to upload the images.

1. 1-5 base images that will show up on the PDP by default even if you haven't selected ant size, color, Style and Size.
2. 1-5 images for each combination of variants.

In most of the cases, we use the same image for a shirt that is black in color irrespective of the sizes. With the current design we are forced to upload the same image in different file names so that the images will show when a customer selects different sizes of black in Ecommerce. Instead, if we had option to upload generic image for each color of a product like we have in option 1, it will save some man power required to maintain the same file for multiple sizes and also save storage space.

Currently, for a product with 5 colors and 5 sizes, we are forced to upload 5x5x5 images so that all images will show for size/color combinations. If we bring the above change, it can be brought down to 25 which is a huge improvement.

Adding the navigation hierarchy to the transaction screen will be really helpful for quick-service restaurants.

• Users will be easily able to navigate the menu and see the cart update as they add items. Using button grids and configuring the images is very time-consuming.
• Adding functionality to add the products to the transaction screen (without going to the product detail page) will ease the ordering process.

f anyone from the engineering team is here. All of us will be grateful to you if you can add some more columns (Account Num, Sales Order Number, Transaction Time) to the online store transaction view. The form doesn't support saved views. The current columns (store name and date) are of no help.

https://www.yammer.com/dynamicsaxfeedbackprograms/#/Threads/show?threadId=1966625555120128

Customers would want to discover a product based on multiple factors like category, brands, etc. While this can be achieved using navigation hierarchy by creating 1st level node named "brand" and listing all the brands under it, it requires a lot of manual work. In most cases, the brand is listed as an attribute, and maintaining the same as product category assignment requires manual work.

Like other CMS, it will be good to have the option to create a Product List Page based on an attribute (that is PLP for each brand) which can be addressed using a direct URL. Automatically generating a navigation menu-like structure will make life a lot easier for content managers.