Dynamics 365 Commerce

Steps to reproduce:

1) Open any inventory operation

2) Scan product (add new line)

3) Scan result is Product Master with pre-selected Color dimension

4) Pre selected Color dimension is ignored in variant selection dialog

Method:

Pos.Core.js

GetInventoryDocumentProductWithLocationAndQuantityClientRequestHandler.prototype._getVariantAsync

 var selectProductVariantClientRequest = new Commerce.Products.SelectProductVariantClientRequest(product, undefined, editResult.correlationId, editResult.title);

Undefined value is passed as second parameter to variant selection dialog which ignoring the already selected dimension;

Idea:

To pass selected deimensions instead of undefined value

Customer is using "Replace alternative item defaults on sales lines" feature which is working fine for HQ. 

However, they also want to implement such a feature to work with retail Ecommerce B2B website, not only SCM.

The scenario is that B2B customers buy spare parts or items through the website and due to huge number of parts available sometimes they're not available or there's a replacement. 

If the order is through HQ and the feature is in use, it works fine and we can automatically replace the item if there's an alternative setup for it.

However, if the order is created from the B2B website, the CST doesn't get a notification or a prompt that this item isn't available, or if there's a replacement for it. This has to be done manually from HQ and due to that, sometimes the replacement they get is a complete different item, or a much more expensive item.

So, if we can implement that the same feature for Retail Ecommerce B2B websites that would be great as many business will rely on such feature especially for selling spare parts that has many alternatives.

With self-checkout being all the rage, many retailers with loyalty programs will want to make it simpler for a customer checking themselves out to add their loyalty information to a transaction.

With current functionality, the customer would need to add themselves to the transaction, and remember to do so. The only standard function that could be done is an info code that prompts the customer to add themselves.

A more streamlined approach to this would be to allow an operation to be triggered from an info code subcode (where we can currently trigger another info code or a product). This would allow the following scenario:

• Info code prompt: Are you a loyalty customer?
• Subcode 1 = Yes, trigger function = Operation, Operation = Add customer

Many other possibilities are opened with this functionality, but from an SCO perspective this will be extremely helpful to have customer-prompted operations.

We used MPOS with a Windows Kiosk account locked down to just run MPOS. When we upgraded to Store Commerce, we lost the option to add the Store Commerce App in the Windows Kiosk mode drop down set up. Can we get this re-added so we can move away from everyone having to log into Windows with their AAD account? We manage 850 registers.

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.

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.