Amr Mohamed

When print management for a specific vendor is configured to send an email once a PO is confirmed, a confirmation journal has to be generated so the email can be sent by enabling the following toggle button when generating the confirmation "Use print management destination".

However, when a PO is confirmed in POS, it does not generate a confirmation journal, so the email is not sent.

We suggest giving the option of generating a confirmation journal while confirming a PO in POS to honor the print management settings for sending emails etc.

Our customer has a specific request regarding the handling of loyalty payments in customer orders.

Currently, when a customer order is created and includes loyalty payments, the corresponding vouchers are automatically posted to the account of the customer who made the transaction.

However, the customer proposes a change:

they would like to have a feature to make all loyalty payments to be posted to the default customer account.

The reason behind this request is to reduce the volume of transactional data in the system.

At present, the system aggregates the posting of transactions, consolidating them into a single sales order for each customer.

In the case of loyalty payments, where the sales and payment are posted with the Customer Account, this increases the volume of transactions, which could potentially impact system performance.

The customer's proposed change aims to mitigate this potential performance issue by consolidating all loyalty payments under the default customer account.

Customers encountered challenges while using the Store Commerce application during inventory counting processes.

The issue arises when scanning items for inventory counts; the application requires the user to manually define the location for each new item being scanned.

While the app automatically associates previously counted items with their existing locations, it mandates a manual location input for each new item added to the inventory count.

This operational requirement significantly slows down the inventory process, especially in scenarios where multiple new items need to be scanned and added.

It disrupts the workflow and increases the likelihood of input errors due to the repetitive nature of the task.

Suggestion: 

The implementation of a feature that allows users to set a default location for inventory counts within the Store Commerce application.

Having a default location would streamline the inventory counting process, reducing the need for repetitive manual entries and thereby enhancing efficiency and accuracy.

In customer's business, we often need to apply discounts to fresh products near their expiry date.

These discounts are applied at the point of sale by overriding the total price for a specific quantity of a product.

However, the current price override operation in Dynamics 365 Commerce only allows us to override the unit price, not the total price for a specific quantity.

This behavior does not align with customer's business process and results in incorrect pricing at the point of sale.

We request a feature that allows the price override operation to apply to the total price of a specific quantity of a product, rather than the unit price.

This feature would greatly improve our pricing flexibility and accuracy at the point of sale.

Example:

If you are selling ginger for 9.95 a kilo, and customer is buying 400 grams, so that's going to be 3.98, so 50% discount on that would be 1.99, so the cashier tries to override the price in the cart to be 1.99, but when he does that, it's the unit's price that's what's overridden, so the price in the cart will be 0.796 which is 1.99*0.4, instead of being 1.99 directly. 

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.

In few scenarios, a single serial number is used for the same product but with more than 1 item.

In some scenarios, it is needed to sell 50 units of each item in a single transaction at the POS.

However, this requires excessive scanning, which is not ideal for a retail environment.

As per "Work with serialized items in the POS - Commerce | Dynamics 365 | Microsoft Learn" document:

“When selling or fulfilling serialized products through the POS application, a quantity of "1" is enforced for the serialized items on the sales transaction. This is a result of how the serial number information is tracked on the sales line. When selling or fulfilling a transaction for multiple serialized items through POS, each sales line must be only configured with a quantity of "1".”.

This is a feature request to have a feature to allow customers to increase the quantity of serialized items in the POS cart if the feature is enabled.

In specific business scenarios, customers want to limit the earned loyalty points per card per month to a specific number.

For example, a customer can only earn 1 million points per month, without expiring.

This is crucial to prevent loyalty fraud, manage financial liabilities, and encourage redemption.

Objective: To enhance the security, efficiency, and customer service of return transactions in cash-and-carry stores by requiring valid customer details (contact number and email) for all return orders.

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 return order transactions in cash-and-carry stores. This feature will ensure that every return transaction is associated with a verified customer, thereby improving the overall return process.

Justification:

1. Customer Verification: Ensures the identity of the customer making the return, reducing the risk of fraudulent returns.
2. Return Tracking: Maintains a detailed record of returns associated with specific customers, aiding in inventory management and return pattern analysis.
3. Enhanced Customer Service: Enables the store to provide better customer service by notifying customers about the status of their return 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 returns, ensuring adherence to consumer protection laws.

Implementation Details:

• Modify the return order 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 return transaction record.

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

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.