Dynamics 365 Commerce

When recalling a quote at POS, there should be the ability to filter on quotes by the status of the quote, for example "Sent" to identify quotes that have been sent, but not yet confirmed. There is currently the functionality to only search by the status of customer orders.

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. 

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

To better server companies in the industry with a longer sales cycle, the ability to fully service the customer from the POS is essential.

As of current functionality, we can create the quotation and confirm the quotation into a sales order. However, there is no function to either cancel or lose a quotation.

To fully flesh out the solution, parameters could be added for default reason code when the quotation cancelation/loss call is sent to the back office for tracking purposes.

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.

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.

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.

The sealed hardware installation requires the .exe to be run from a terminal with all the data needed whereas the self service installer used a UI to receive the data. The self service installer downloaded IIS and created the necessary Registry keys such as TLS 1.0 Client and Server and TLS 1.1 Client and Server, with the necessary DWORD values. The sealed installer does not do this thus requiring manual addition of the keys and the installation of IIS. Can the sealed installer not be made to do this as well similar to the self service installer.

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.