Dynamics 365 Commerce

Store commerce gives the opportunity to create a Purchase order From POS, so why don't close the full cycle by creating a returned order to the Vendor?

It will be good to have the option to copy the button properties of an existing button while creating a new one. An option to define the button color and appearance properties at a grid level can really help configure buttons fast.

Recently, Microsoft added a new Retail device type was added. The Store Commerce App. When users in D365 F&SC go to the 'Devices' form and add a new record they need to select what device type the device record is. ModernPOS, CloudPos, StoreCommerce, ect.

The only way to add the new drop-down option 'Store Commerce' is to go to the Commerce Parameters form, and then click on the 'initialize' button on the 'general' tab. While this work, pushing this button in production is a high impact. It creates seed data, if it doesn't exist. If a client removed any of this seed data in their system, this button would re-create this un-needed data in production, along with inserting the new 'store commerce' record into the RetailDeviceTypes table.

There exists a RetailDeviceTypes form that does allow users to create and delete records. However, whenever a new record is created, the 'Type' field is not shown. If you add it with personalization, the field is un-editable.

Suggestion: Allow the 'Type' field on the RetailDeviceTypes form to be editable so that a user can manually add the 'Store Commerce' record, instead of letting the 'initialize' button create it, along with potentially other records that they do not want.

When enabling the fiscalization module in Dynamics 365 Commerce, a Connector Technical Profile must be configured in HQ. Selecting Local as the Connector Type and setting the Connector Location to Local causes the sequential number to fail due to a limitation in Pos.Core.js. The standard code only checks for Internal connectors and omits Local, breaking number sequencing required for legal compliance in some countries.

To work around this, we extended applicationStartTrigger to include Local in the connector type check. However, this logic should be part of the standard code.

We request an update to Pos.Core.js to support both Internal and Local connector types, ensuring correct sequential numbering and compliance.

There are often times where products are only available during certain periods in time.

For example during the Summer season an assortment of summer products are available. During the Winter something different. It's cumbersome to constantly have to set expirations on assortments that are going to be re-used again and again.

We would like to setup Assortment Periods where the expiration is based on a reoccuring timeline instead of static dates. For example I would like to assign a Period called 'Summer' with a static date range (no year) so that from 5/1-8/31 yearly this assortment of products are available. The same for each season etc.

Currently in POS D365, we are able to edit the quotes by using the "Recall order" operation but not able to cancel the quotes. The "Cancel quote" operation should be implemented in POS so that user can cancel the quote just like what we use to do in D365 F&O in "All quotations" form.

Please make the width of the base dialog, that we use to create custom messages and modal dialogs, as a parameter, so we can make it wider, when needed.

Using the transaction comment operation at POS, the user can fill in both the customer reference and customer requisition fields. Both fields flow over and populate on the F&O sales order, but the customer requisition is not available on the POS receipt. The "transaction comment" receipt designer field only pulls the customer reference onto the receipt. We would like there to be another receipt field or have the existing transaction comment receipt field also include the customer requisition field on POS receipts.

i want to exclude discounted products from loyalty programs so customer should not earn points for discounted products

We would like an automated email notification for cash & carry validations errors.

We want to receive an email notification if there are any D365 Commerce POS transaction with an error.

This allows us to no longer need to review Store Financials daily to confirm there's no error.