Khaled Mohamed Mohamed Hussein El Tahawy

We propose enhancing the SalesOrders API in Dynamics 365 Commerce to support warranty items for e-commerce. Currently, warranty transactions via API do not register in the RetailWarrantyTransactionSales table. This enhancement would align API functionality with standard behavior

we propose a modification to the 'Change Due' functionality. Currently, the 'Change Due' dialog can be hidden when there is no change due by selecting 'Skip when zero'. However, this setting is overridden if gift receipts are configured to print 'As required'. We suggest a feature enhancement that allows the 'Skip when zero' setting to persist, even when gift receipts are set to print 'As required', thus suppressing the gift receipt prompt during transactions while still allowing gift receipts to be printed from the journal.

The current system design is not aggregating Serialized Controlled items

The "Skip Aggregation" setting is currently enabled for transactions with serialized items to handle scenarios where sales, returns, and subsequent sales occur for the same item.

This is currently creating too many Sales Order for the same serialized items, to mitigate this, a feature can be added to enable/disable the aggregation for serialized items at the customer's control

Recent Purchases in POS Customer Profile should show the exact results as Order History.

Right now, Recent Purchases and Order History in Customer Profile in Store Commerce show completely different results.

It'd be ideal for cashiers to see the recent purchases reflect the order history to suggest to customers products that they may be interested in.

It would be helpful for agents - Salespersons to be notified when they're performing inventory counting in POS and they scan an item to be alerted that this item is not included in the journal.

those operating POS to receive notifications during the process of inventory counting. Specifically, when they scan an item, an alert system could be implemented to inform them if the scanned item is not included in the inventory journal. This feature would enhance the accuracy of inventory management and prevent potential discrepancies between the physical stock and the recorded inventory data.

Accurate Financial Reporting: Ensures that the difference amount accurately reflects the bank drop, improving financial transparency.

Simplified Reconciliation: Makes it easier to reconcile bank drops with counted amounts, reducing errors and discrepancies.

We propose an enhancement to FnO to enable the automatic posting of BOM journals for kit items when a sales order is delivered or invoiced. This functionality should mirror the existing behavior in Dynamics 365 Commerce POS, where the BOM journal posts automatically upon order delivery.

Currently, there is a discrepancy between how BOM journals for kit items are handled in Dynamics 365 Commerce POS and D365 FnO In POS, the BOM journal posts automatically when the order is delivered, ensuring seamless inventory and financial updates. However, in FO, this process is not automated, leading to potential inconsistencies and additional manual work.

Benefits:

Consistency: Aligns the behavior of BOM journal posting across POS and FO, ensuring a unified process.

Efficiency: Reduces manual intervention, saving time and minimizing errors.

Accuracy: Ensures accurate and timely updates to inventory and financial records.

Implementation:

The enhancement should include:

Automatic triggering of BOM journal posting upon sales order delivery or invoicing in FO.

Configuration options to enable or disable this feature based on business requirements.

Support for both call center and non-call center users.

This enhancement will significantly improve the user experience and operational efficiency for businesses using D365 FnO

When a kit item is sold in the POS, system creates a BOM journal and uses the components' stock. However, when the kit item is returned, the system does not create a BOM journal and only returns the kit item to stock, leading to incorrect stock values for the components.

Customer Scenario:

1. A kit item is sold in POS, and the system creates a BOM journal, using the components' stock.
2. When the kit item is returned in POS, the system does not create a BOM journal, and only the kit item is returned to stock.
3. This results in the components' stock not being updated correctly, causing discrepancies in inventory management.

Customer Expectations:

• The system should create a BOM journal during the return process of a kit item in POS to ensure that the components' stock is updated correctly.

DOM allows for the definition of fulfillment location priority rules, which prioritize entire warehouses or groups of warehouses. However, it does not support prioritizing specific locations within a warehouse. This limitation can lead to issues with stock not being reserved at a more granular location level within a warehouse, this is because such specific locations are only supported within advanced warehouse management which is not supported within DOM.

Proposed Solution:

Adjust Inventory Dimensions: Ensure inventory dimensions in DOM match those in the warehouse management system, including specific locations within warehouses.

Use DOM Features:

Configure DOM parameters and fulfillment profiles to reflect accurate inventory dimensions, including specific locations within warehouses.