Dynamics 365 Commerce

There should be an option, not to make Unit of measure compulsory for Calculation type = 'Amount off' at Periodic discount line. Else it may impact how the Quantity limit should work, when they are different unit of measure from a product category.

The option could be to make/refer the Unit of measure from product master.

When creating buyer's push orders for warehouse in other legal entities (for example from DC legal entity to Store's legal entity), standard D365 takes the first intercompany customer-vendor relation that has been created.

But in a multicompany store setup, there will be a intercompany customer-vendor relation per store to enable correct manuel creation of replenishment orders from DC to store A, B or C in retail company (by using IC customer A, B or C).

But with buyer's push, this can't be configured resulting in incorrect intercompany customer-vendor that are taken.

IDEA:

Setup table with company - customer - vendor - company - warehouse that would be used by buyer's push when creating orders.

Product images should be shown in the body of emails sent to customers. This was possible to do before Omnichannel Media was released by Microsoft.

The method was to add a HTML string to the email template and use to use the search file name API or the legacy file name convention.

The Omnichannel Media feature changes the URL structure for product images which means we are not able to pull product images into the body of any email (Order conf, order shipped etc)

I would like to suggest that initial loyalty balances can be imported into the system without customization, right now the initial balances can't be imported directly into the system, they are in the posted status but not being reflected in the loyalty adjustments, for now creating a custom entity seems to be the most viable solution.

Create Security Groups in AAD:Go to the Azure Portal.Navigate to Azure Active Directory > Groups.Create a new security group for each brand and add the respective administrators to the group.Assign Security Groups in Site Builder:In the Commerce Site Builder, select the site for the brand.Go to Site Settings > Staff.Add the security group for the brand to the site. This will restrict access to the site to members of the security group.Verify Access Control:Ensure that administrators can only access their designated brand's site and cannot see or manage other brands' sites.

Example:

Create Security Groups:

Brand A: BrandA_Admins

Brand B: BrandB_Admins

Brand C: BrandC_AdminsAssign Security Groups to Sites:

For Brand A's site, assign the BrandA_Admins group.

For Brand B's site, assign the BrandB_Admins group.

For Brand C's site, assign the BrandC_Admins group.Configure Site Settings:

In Site Builder, go to Site Settings > Staff for Brand A's site.

Add BrandA_Admins to the site.

Repeat for Brand B and Brand C with their respective security groups.

This is basic requirement for every industry, users control magnesium be available in his control, no need to depends on other source,

Need to build new functionality (provision) for Non uses D365 from some days (10-15 days) as per customer convenient) those users need to auto disable in F&O, (D365 ERP)

Description:

Currently, the POS system does not mark receipts as "Duplicate" or indicate the reprint date and time when a customer requests a receipt reprint. This leads to confusion for cashiers and store staff, as they cannot differentiate between an original and a duplicate receipt.

Problem Statement:

• Customers frequently request receipt reprints, but the system does not log or flag these reprinted receipts.
• There is no available feature in the Store Commerce App Receipt Designer to display the reprint date and time.
• Store staff need a clear way to identify whether a receipt is original or a duplicate, ensuring accuracy in record-keeping and preventing misuse.

Proposed Solution:

• Implement a "Duplicate Receipt" flag on reprinted receipts.
• Add the date and time of reprint on the receipt.
• Enhance the Store Commerce App Receipt Designer to include these details.
• Ensure the cashier and store staff can easily differentiate between original and reprinted receipts.

Business Impact:

• Improves transparency in transactions.
• Reduces disputes related to duplicate receipts.
• Enhances operational efficiency for store staff and cashiers.

This is a much-needed enhancement for retail operations, and we strongly recommend Microsoft to consider implementing this feature.

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.

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.

To harmonize the way D365 POS and D365 Call Center are applying currency rounding rules. In Call Center the Price Rounding Rule, which is set up at currency level, is used for the rounding of the unit price of a sales transation and the General Rounding Rule, which is set up at currency level, is used for therounding of the amounts (line, total, ...). In POS the Price Rounding Rule only is used for the rounding of all (unit prices and amounts) and also the number of decimals displayed on POS forms for prices and amounts is driven by the number of decimals in the Price Rounding Rule. This is creating an inconsistent behavior within the D365 Commerce (Call Center and POS) solution expecially for customer who wants to extend (by EDT extension) the number of decimals used for unit prices (e.g. from 2 to 4) but keeps amounts with 2 decimals and apply a different rounding rule for the unit price and for the amounts.