-
Alternative setup of retail quantity discounts
The retail module gives a lot flexibility in the pricing and discounts area and more and more of our customers like to use it. Also existing whole sale customers that are used to work with the trade agreements are embracing this price engine. However the setup of the quantity based discounts is very cumbersome for them, especially is you want to setup prices for a given qty. This is caused by the fact that you have to setup the qty based prices first and then attach the items to it. WHen you want to view what has been setup for a specific item, this is not possible as the item can be in multiple agreements (e.g. if you have different dates or different qty tiers). It would be great if we would be able to set them up in a similar way as the trade agreements, which is per line.... Now you would say, why don't you use the trade agreement discounts for this purpose? Multiple reasons: - It's not possible to setup a discounted price (=net price) - When have an order with multiple order lines with the same item id and different variants the qty's are not summarized when fetching the right tier (this in contradiction with the prices where it does summarize) - Microsoft has made a statement not to use trade agreement discounts when using retail discounts.
-
Blocked free text invoices should be visible in the block management list page
In the new Enterprise credit limit management features that will be released soon, free text invoices should also be visible in the block management list page.
-
Exclude future sales order from credit limit check
It should be possible to setup a timeframe (horizon) and the balance of the orders that are outside this timeframe should not be included within the credit limit check. In some business a part of the sales is done in a preliminary stage called (pre-sales) while other sales is done right now (in season). As the values of the presales is often very high and the delivery will be done after a few month's it influences the order balance right now and causes blocks for in seasonal sales.
-
Exclude disputed invoices from credit limit check
Add the possiblity to exclude the balance of certain disputed invoices from the credit limit check. It could be that a customer is not paying their invoices due to bad performance of your company and during the period of the dispute you do not want to block your customer as a result of your own faults. For that period that you are discussing this invoice you want to exclude it from the balance.
-
Allow creation of a credit note when the credit limit has been exceeded
When you have a dispute with your customer and for that reason the outstanding balances have become due, it could be that your own company has caused the issue and for that reason your customer didn't want to pay. In order to resolve this situation you like to create a credit note or want to take back the goods. In that case you would not want to be blocked.
-
Add credit limit check on sending a quotation
Add credit limit check (warning or error) on sending a quotation in order to prevent this customer to get the impression he can still buy goods
-
Show the project in which a solution is Opened for edit
When you want to edit a solution you have to select a project and only from within this project you are able to edit the solution and publish it. When you come back to the main page of LCS and you select the solution tile, you will see that the solution is opened for Edit but you do not see in which project. As an ISV we have more than 50 LCS projects and when you do not know anymore in which project the solution is set into edit mode you have to go through all 50 project to try which it was. Solution: add a column to the grid so you can see in which project is has set into edit mode. -
Sort alphabetical in AzureDevOps project lookup in Rsat Settings
Currently the lookup of AzureDevOps projects in the Rsat Settings is not sorted alphabetical. As an ISV we have a long list of AzureDevOps projects to choose from, would be great to have them sorted.
-
Automatic update of LCS Solutions from AzureDevOps Release Pipeline
As ISV of multiple products we are missing one major step which prevents us form completely automate our release process. We need an API which can update an existing LCS Solution, which removes models and deployable pacakges and replaces them by the latest ones, adds the released notes and then publish this solution globally. In this way we can fully automate the whole release process from AzureDevOps -
Exclude sales order from credit limit block based on terms of payment
When a customer is over his credit limit or the payments are due the credit limit check will block the sales order. By changing the terms of payment into Cash or Cash on delivery we would like to be able to exclude this order from the credit limit block. In the current solution this is not possible as the exclusion for terms of payment only apply to orders which were blocked due to a terms of payment blocking rule.
You’re offline. This is a read only version of the page.
