Christian Hattermann

In retail stores with a one-shift system, it would be helpful if there were a systemic routine that checks whether the "start amount" at day start matches the "declare tender" amount at day end of the previous day or whether there is a discrepancy.

In many retail stores, it is common for only one cash register with one cash drawer to be used. This is stored in the safe at the end of the day and used again the following day in the morning. If money goes missing during this time (theft, for example), it can be quickly detected by such a function.

I would locate this function in the functionality profile, where it can be activated and deactivated as required.

On the POS there is the option to set up the buttons "View available discounts" and "View all discounts".

If you scan an item that is part of a currently valid promotion and then tap on the "View available discounts" button, the appropriate discount for the item is displayed, but only the name from the "Name" field of the discount from the settings in the back office. 

Although this can be freely selected, it does not usually contain the conditions of the discount described in detail.

On the discount itself, in the "Details" fast tab the "Description" and "Disclaimer" fields, among others, can be filled out.

It would be great if the contents of these fields were also displayed on the POS when a cashier displays a discount.

In the practical example, one of our customers has a big product portfolio. Up to 100 different discount campaigns are active at the same time. These are difficult for a cashier to remember. 

It is helpful here to at least be able to access the discount information.

This would also create a form of communication transfer from the marketing department to the store.

Current situation:

At the POS in the SCA during the checkout there is a step called "Do you want to email the receipt?"".

In this step you need to enter your email address and there is also a boolean field that must be switched from “off” (default) to “on” to activate the "receipt per email" function.

However, there are two additional buttons in the step: “Send” and “Don't send”.

Both buttons are active and clickable, regardless of whether the Boolean field is set to “Off” or “On”.

Possible outcomes are:

1. Boolean "Off" + "Send" = no email receipt is sent
2. Boolean "On" + "Send" = email receipt is sent
3. Boolean "Off" + "Don't send" = no email receipt is sent
4. Boolean "On" + "Don't send" = no email receipt is sent

One step is redundant here.

Idea:

Remove boolean field.

Leave the “Send” button inactive as long as no valid email address has been entered.

If a valid email address has been entered then the “Send” button can also be clicked.

A format validation is sufficient to validate the email address - anything@something.TLD

During a recent project, this request was made by the customer.

Unfortunately, there is no easy way to set a register to a training mode, e.g. to train employees without making inventory and financial postings.

To do this, a new store with the corresponding setups must first be created at considerable expense in order to then set up a demo register.

I would like to have two simple functionalities here:

1. the possibility to put an existing register in the Store Commerce app into training mode by clicking on a corresponding training mode button to be able to perform training there. Ideally, the visual appearance of Store commerce app should change during training mode so that the training mode is easily recognizable.
2. the possibility to switch a register in the D365 setup to a test mode / training mode via a boolean switch. This allows HQ staff to test their settings on the PROD environment and use an identical POS as the stores (without the detour via the UAT).

In my estimation, all customers with whom I have worked on retail projects with D365 so far would want to use these functions.

So MS, make it happen 8-)

Currently, the procurement hierarchy can only be defined once globally for all LEs, and visibility can only be restricted at the PR level per LE. Catalogues allow for further restriction of visibility, e.g. at department level.

Experience has shown that some procurement category hierarchies are very large and extensive with numerous nodes. It would be helpful here if visibility could be restricted to the PR at user or role level.

When creating a PR or PO and purchasing by procurement category, it can be difficult to find the right category from a long list if the procurement category hierarchy is very extensive.

Keywords can be defined for each category. However, these cannot be accessed directly in the procurement category at line level (of PR and PO) when searching. It only works with the exact name of the category, and even then it is only highlighted in bold in the hierarchy list.

In short, my idea is to enable keyword searches (if they can be defined, why not use them?).