Dynamics 365 Commerce

If we do price override after set quantity of weighted products, the override price is considered for quantity before set quantity and is then recaculated accordingly for the units in the basket. The right behaviour should be to override price based on the quantity in basket.

The above applies to some low value low weighted products like Ginger, are purchased in Kilo(Kgs) and sold in Grams (g) in the stores on POS.

But as these products are so low value low weight, we cannot keep the sales unit as grams as it's diffcult to define price per gram.

So the sell trade agreement is defined in KGs and hence,the product is added to POS in KGs...1KG = £9.95

Then we set quantity to the req quantity customer has purchased like 0.3Kg (300 grams) .. 0.3 KG = £2.99

Sometimes these products are on one off markdown to clear stock towards their best before date and we sell these for a giveaway price like £1.

When user overrides the price after setting quantity, the overriden price is considered for the 1Kg instead of 0.3 KG and instead of 0.3 KG being £1, it calculates 1kg = £1 and hence 0.3 KG = £0.3, which is incorrect, we wanted to override 0.3 KG = £1.

It's difficult to calculate how much percentage it is during peak hours to be able to use line discount % function as is prone to manual error.

We did raise this as a bug with Microsoft (2404150050004828), but we were told to raise an IDEA instead.

Hi,

Before Update there were some awesome features in the return function in the dynamics POS.

We would really be happy if they were again implemented.

• The cross box were before still marked so it was very easy to see what products was returned and not. But after update the cross is not there as soon as you choose a new article to return. It is less clear to ony have the 1 number to follow to the right and wishes are to still have all articles cross marked that has been chosen for return :)

Please - looking forward to get this function back again soon!

Adding Application session ID and User session IDs from the client where the transaction was made in separate fields in the transaction tables (for example RetailTransactionSalesTrans and RetailTransactionPaymentTrans) would make support and troubleshooting much easier and quicker.

This way we could look up the IDs from the store transactions form in HQ and not have to rely on that cashier have saved those IDs at the time of the issue or query local event log.

Hi Team

Title:

Threshold discount: Apply Discount to Cheapest Eligible Product in Multi-Item Cart If Threshold Met and Calculation type: Discount lines

Idea Description:

As part of our ongoing efforts to optimize promotional pricing strategies within Microsoft Dynamics 365 Commerce, we propose introducing a configurable setup option for Threshold Discount Calculation Type = "Discount Line". This enhancement will allow for more granular control over discount application based on item-level criteria.

Proposed Enhancements:

Threshold Discounted Line Tab Configuration:

Enable selection of specific items, categories, or product variants to be eligible for threshold-based discounts. Introduce a mechanism to define whether the discount should apply to:

1. The cheapest eligible item in the cart.

Threshold discount tires -Configuration Options:

A toggle or dropdown to select "Apply to Lowest Value Item" or "Apply to Highest Value Item".

Automation & Flexibility:

Once the predefined threshold is met, the system will automatically apply the discount to the selected item based on the configured rule.

"This feature would allow businesses to run promotions like “Buy 3 items, get the cheapest one at 10% off” and “Spend $100, get the lowest-priced item free,” and favoring retailer "

Problem Statement:

The existing implementation applies the discount to the highest-priced eligible item by default and favoring customer

Proposed Solution:

Set up option to threshold discount tires ->Calculation type: Discount lines

require option to Higher and lower value promotion configuration mechanism in Microsoft Commerce

Checks if the cart meets a defined threshold (e.g., total value or item count).

Identifies the cheapest eligible item based on defined criteria (e.g., product category, brand, etc.).

Applies a Calculation type: Discount lines to that item only.

in Store commerce Order fulfillment page should have scan barcode button to Pick / Pack the items, similar to outbound Transfer orders shipping page. on scanning barcode, item should be selected automatically in order fulfillment page for pick or pack operation.

I am seeking support for the Brazilian localization, particularly concerning the NFC-e (Nota Fiscal de Consumidor Eletrônica) on CPOS (Cloud Point of Sale). At present, there is no functionality available to make the necessary calls with the fiscal localization. This support is essential for this region to fully utilize the out-of-the-box capabilities of Dynamics without resorting to custom code solutions. Implementing this feature would significantly enhance the usability and compliance of the system in Brazil, ensuring that businesses can operate efficiently and adhere to local fiscal regulations.

Currently, we can setup manager's override on all Line discount % givem by the cashiers even though their permission says they can give 10% discount as an example.

So, if the POS operations 301 is setup with managers override, if will ask for all Line discount % given by cashier.

We want Cashiers to be able to give the discount defined in the Users permissions but then anything above should ask for the manager's override.

At the moment, when having two different parties of the Role "Customer Person", which are assigned to the same Customer hierarchy (necessary for the access to the Microsoft eCommerce / Online shop) and one of this Customer Person (= Party) is removed from the Hierarchy (the other one is remaining there) a merging of the Parties leads to the error "Cannot edit a record in Customer hierarchy nodes (CustHierarchyNode)”

This behavior has also been raised as issue but not been accepted as it is by design due to the soft delete mechanism of CustHierarchyNode table.

It should be possible to merge these parties to avoid duplicate records in the system. The soft delete function of the CustomerHieraryNode can remain but it must be possible to merge records with this.

Current solution for Tax Exemption where 'price includes sales tax' does not support discounted price.

It is very common in EU, where price includes sales tax, to have price auto discounted for sales promotions using Discount Price method. In such case, if a customer is a VAT exempt or an export customer, deduction of VAT tax is not performed correctly by the system.

A common scenario when retail POS is used for quick service restaurant (QSR) operations is to apply a public holiday surcharge. While Auto charges functionality appears to allow for this to be defined by Item group and even by Retail channel, there doesn’t seem to be any type of date control.

This is clearly a deficiency in using the Retail POS for this type of business who would expect to be able to;

1. Define the Retail Channel(s)
2. Define the Item Group(s)
3. Define the Lines by specifying the rate (usually Percent), GST group and the Date that the charge is applicable for

The Retail POS functionality should calculate the applicable charge only on the Date specified in addition to the normal trade agreement & retail discount calculations. The description of the charge code should be displayed to explain the amount calculated as a separate line on the transaction receipt.