Dynamics 365 Commerce

The demand for self-checkout is increasing massively worldwide. Self-checkout provide a better customer experience and can provide a better efficiency in terms of shorter lines and a faster checkout, especially for supermarkets and grocery stores, but also for fashion retailers and others. With self-checkout store staff can manage more than one cash register at the time and by doing this provide a way for staff to spend more time helping customers out on the store floor. Dynamics 365 is supporting parts of the functionality and setup required to handle this but the POS has limitation in setup and customizability to support self-checkout scenarios. We wish for Microsoft to include a POS version designed for use in self-checkout scenarios with ability, including, but not limited to, scanning bar codes, manual input of items, weighing item, using coupons, and paying with various payment methods. For Microsoft to include a POS that is designed for self-checkout would provide an even bigger advantage for Dynamics 365 as opposed to what competitors are offering.

Retail staff want to get visibility of a store's contact phone number within POS.

It seems like the logical place to do this would be on the location details screen, accessed from (e.g.) the Inventory lookup form by clicking on Show store location button.

Here we see a location map, store name, address, opening hours, virtually everything you'd want to know about the store, so this logically would be where the phone number should be displayed.

• a staff member has the customer standing in front of them
• they have no stock
• they've done an inventory lookup and found a store(s) with stock of the item
• they wish to call that store to confirm they really have the item

It seems odd to surface so much other information about the store, but not this.

Would seem fairly easy to display any contact information record of type Phone, that is Primary, from the Operating unit, with little or no CSU modification, and only having to enhance the POS screen.

Distributed Order Management - Wholesale (non-direct to customer) Related Requirement (1) Factor “Requested delivery date” & ATP & Customer Priority in DOM processing​ (2) Expand to non-Retail orders (3) B2B capabilities (4) DC Fulfillment

Possibility to create mix and match discount with discount amount on a specific line.

Specific examples are:

• Buy item X and get Y SEK off one item in category Z.
• Buy from category X for Y SEK and get Z amount of a specific item.

Hej,

We are planning to go live with the new B2B Commerce solution in Q3 2023.

As adressed before we urgently need a text field in the checkout, where our customers can leave a comment before finally placing an order. The comments our customers add to their orders today vary a lot and have different lengths so it should be possible to type at least 500 characters. The comments need to be highlightet somewhere in d365 backend for the customer service team once an order placed in the webshop arrives so the team can take action.

Going on with the Commerce solution the future solution should look like: if an order has a comment the order should be ‘stopped’ and not automatically create a load to get packed and shipped. This is a future scenario – I just want to mention it now so it can be thought in…

THank you

CHristina

Today a parameter exists on the customer details form to enable or to disable payments with the payment method "Customer" so that it's booked on the customer balance. However, this parameter only applies on call center sales orders, not on sales made via the POS. As this is an inconsistency from an omni channel perspective. The request is to apply this parameter accross the board, meanig also in the POS. The business scenario is stores where both B2C as well as B2B customer are allowed to purchase goods and where B2B customers are allowed to pay on account but B2C customers aren't.