Dynamics 365 Commerce

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.

Description:

This feature aims to ensure that the cost amount is consistently updated for customer orders in the store transaction form, similar to how it is updated for cash and carry transactions. This will help maintain accuracy in cost reporting and streamline the process for users who need to generate reports and analyze the cost of goods sold.

Currently, the cost amount is not updated for customer orders in the store transaction form, causing significant issues for users. They are unable to retrieve cost details from sales transactions, even after the sales order is invoiced. This inconsistency affects the ability to generate accurate reports and determine the cost of goods sold, leading to substantial business impact.

Business Impact:

• Users cannot determine the cost of goods sold from the retail front.
• Inability to generate accurate sales reports.
• Manual effort required to dig into InventTrans to view cost details.
• Significant disruption in financial reporting and value recognition.

Request:

We propose to ensure that the cost amount is updated for customer orders in the store transaction form, similar to cash and carry transactions.

1. Implement logic to fetch and display the cost amount for customer orders once the sales order is invoiced.
2. Consistency Across Transaction Types: Maintain consistency in how cost amounts are handled across different transaction types (cash and carry, customer orders) and ensure that the cost amount is visible and accurate in the store transaction form for all types of transactions.
3. Automated Updates:

• Automate the process of updating the cost amount for customer orders to reduce manual effort and errors.
• Implement checks to ensure that the cost amount is correctly updated and displayed in the store transaction form.

Benefits:

• Improved accuracy in cost reporting.
• Streamlined process for generating sales reports.
• Reduced manual effort and errors.
• Enhanced financial reporting and value recognition.

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.

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.

If there has only been a login on a store's POS, a transactional statement is created for the store. This statement is empty, and the posting of statements always show 'error' if an empty statement is included in the posting process. These empty statements must be manually deleted, and shouldn't be created at all.

Payment methods are configured per call centre channel to allow processing sales order and take customer payments.

Navigate to

1. All call centre (Retail and Commerce > Channels > Call centres > All call centres)
2. In action pane, Under setup tab and setup group, click Payment methods
3. In the payment methods screen, select a payment method and click Payment transactions.

Notice, that the payment transaction only shows all the payment transactions from store, but it doesnt show sales orders created via call centre thought they are also called Retail sales (Retail sales checkbox is marked yes for such orders).

It would be great if we can see sales orders per payment method used in call centre (like we can see store payment transactions) or have a way to filter out orders paid via certain payment method.