Dynamics 365 Commerce

Hi,

We got so many comments from the users that the text and some buttons in MPOS really could be bigger, to help the users to work with the product.

Small text and buttons lead to error when clicking and a hard time reading the instructions in ex pop ups.

The buttons in the left menu (transaction view, home view and products) is most critical since it is very small.

Also over all, all text could preferably be bigger and alsomaybe bold or better applied for the eye to catch.

Is this a possible thing for you to look into?

As a partner, allowing read access to the customer environment Channel databases would enable more rapid support for the customer problem scenarios in multiple levels:

- validate Channel database SQL schema regarding new or deleted fields

- validate data problem scenarios when data on POS does not seem to reflect the correct data structures

- validate download & upload issues

- valildate missing or invalid data

- validate P-job runs

- validate individual job runs

- validate POS generated data

- validate transactions, lockdowns and shift issues

And most of all, allowing accesss would increase the issue solving productivity, and decrease the throughput of support issues and the total costs of Microsoft and partner support, since we could quickly investigate ChannelDB issues without first contacting Microsoft. 

Regarding minor issues, ticket-by-ticket-based ChannelDB problem solving involving MS support is highly inefficient action and prevents us from serving and supporting our customer base properly. 

When using EntraId single signon for Store Commerce in combination with shared installation (Multi user, --UseCommonApplicationData) there are two main challenges we need to handle:

- Adding users to the local security group RetailChannelUsers is a challenge when installing in userspace since we cannot easily add all users that need to use the computer to that local security group. Using group policy is not always possible due to security setup so a way to add users centrally in HQ and allow for replication to the local group or similar using Entra ID groups would be preferred.

- Automatically killing or otherwise handling the requirement to have only one instance of the Store Commerce application running is a challenge since users are not always clear that they need to shut down the application when locking the screen temporarily. Either allowing users to terminate the running instance or otherwise allowing multiple users to use the same device using entraid without needing to reboot the computer would be needed.

While creating a customer in store commerce app these constraints needs to be added:

Phone numbers: It allows adding characters and special characters -> Customers wants the phone number field to only add numbers.

Customer Name: It allows adding numbers and special characters -> Customer wants the name to only allow characters.

Customer Email: It allows adding anything if it has these two sympols "@", "." -> Customer wants it to validate if the email is correct

Currently To request a full or partial return of a sales order from a B2B and B2C e-commerce site, it is necessary to enable a Call Center channel within the headquarters to process returns. In electronic commerce, there is no direct possibility of issuing a return; The process must be managed through a Call Center, but it will be a better option to perform this directly from the B2B and B2C e-commerce sites as per some customers' process does not match the call center return process.

Let's dive into the business scenario:

A restaurant experiences high customer traffic, with orders placed online or via phone and picked up at the restaurant. The current process is as follows:

1. A customer places an order online or through a call center.
2. The customer arrives at the restaurant to pick up the order.
3. The cashier recalls the order, selects it, and clicks "pick up."
4. The cashier must manually select all items in the order, as there is no scenario involving directly going to cart with all items.
5. Due to the high volume of orders, cashiers sometimes miss selecting an item, leading to inventory and financial discrepancies because of partially fulfilled orders.

The feature request is to implement functionality that allows cashiers to skip the item selection step and directly add all items in the order to the cart.

This would streamline the process and help fulfill more orders efficiently during peak times.

This is related to issue#614899, 615115 

For items that is marked as auto report as finished to automatically create a BOM journal on processing statement posting,

The issue is when those items are returned the system is not returning the stocks directly, it is trying to process the auto report as finished by creating BOM journal again so it is failing to do so with, it should only return the stock.

There are two scenarios when Batch number for Return transactions are not taken from sales transaction:

1. When return transaction is registered in POS without reference to sales transaction
2. When return transaction is registered in POS with reference to sales transaction but both transactions are posted in the same Statement

In both two scenarios when Batch number for return transaction is not taken from sales transaction there is required to setup Batch number group in Released product to enter new Batch number from sequence.

It is standard behavior but in effect it generates many new not necessary Batch numbers.

It would be better to use Default Batch number instead Batch number from sequence in such case like it is for cash&carry sales transaction.

Repro steps with 2 scenarios:

1. Register Return product operation in POS for Item with Batch number tracked (no reference to sales order),

• Upload by P job to HQ,
• Run Validation of retail transaction,
• Calculate and try to Post Statement

1. Register Sales transaction in POS for Item with Batch number tracked,

• Go to Show journal and select new created sales transaction,
• Register return transaction,
• Upload by P job to HQ,
• Run Validation of retail transaction,
• Calculate and try to Post Statement

In both cases there is presented error message in Statement:

While processing the state Customer order invoiced, generic exception encountered in retail statement xxx post aggregate controller while aggregating the transactions: 

Posting Posting Sales order: yyyy Item: zzz Batch number group is not specified on item and can therefore not automatically be created 

Posting Posting Sales order: yyyy Item: zzz Inventory dimension Batch number must be specified. 

Posting Posting Sales order: yyyy Item: zzz Update has been canceled. .

It would be better to assign Default Batch number id for return transaction instead of generating new ones from sequence number

CST is requesting to have the ability in the system to allow a default descriptions for Customer - Payment, Ledger

Objective: To enhance the security, tracking, and customer service of gift card transactions by requiring valid customer details (contact number and email) for all transactions involving the issuance or redemption of gift cards.

Feature Description: Implement a feature in the Dynamics 365 Commerce Point of Sale (POS) application that mandates the collection of valid customer details (contact number and email) for all transactions involving the issuance or redemption of gift cards. This feature will ensure that every gift card transaction is associated with a verified customer, thereby improving the overall transaction process.

Justification:

1. Customer Verification: Ensures the identity of the customer involved in the gift card transaction, reducing the risk of fraudulent activities.
2. Transaction Tracking: Maintains a detailed record of gift card transactions associated with specific customers, aiding in tracking and managing gift card usage.
3. Enhanced Customer Service: Enables the store to provide better customer service by notifying customers about the status of their gift card transactions or any issues that may arise.
4. Marketing and Communication: Allows the store to use the collected contact information for marketing purposes, such as sending promotional offers or updates about new products and services.
5. Compliance and Reporting: Helps in complying with legal requirements for collecting customer information for financial transactions, ensuring adherence to consumer protection laws.

Implementation Details:

• Modify the gift card transaction workflow in the POS application to include mandatory fields for customer contact number and email.
• Validate the entered customer details to ensure they are in the correct format.
• Store the customer details securely and associate them with the gift card transaction record.

Impact: This feature will enhance the security and efficiency of gift card transactions, improve customer service, and provide valuable data for marketing and compliance purposes.