top of page

Why is Business Central Picking the “Wrong” Sales Price?

  • Writer: akash shukla
    akash shukla
  • 8 hours ago
  • 2 min read
Hello Readers,
Recently, I encountered an interesting scenario during a client discussion that I believe many Business Central consultants and users can relate to.

The Situation


My client had created a new Price List in Business Central. For the same item and the same validity period, multiple customer-related pricing combinations existed, each with a different sales price.

Sales Price List

When users started creating Sales Orders, they noticed that the price they expected was not being automatically populated on the sales lines. For example, for Item 1908-S, the expected price was 160, and for Item 1925-W, it was 180. However, the system automatically populated prices of 120 and 150 respectively.

Sales order with wrong price

Naturally, the question arose:

"How does Business Central decide which price to use when multiple valid prices exist?"

Investigation


To understand the behavior, I recreated the same scenario in a Business Central sandbox environment. After testing various combinations, I confirmed that Business Central follows a straightforward pricing principle:

"Business Central Always Tries to Find the Best Price for the Customer"
Code logic

When multiple valid prices are available for the same item and date range, the system evaluates the available options and automatically selects the lowest eligible sales price.
In other words, Business Central prioritizes the Best Price for the customer rather than simply choosing the first price record it finds.

Key Takeaway


If multiple sales prices are valid for the same item, customer, and period, Business Central will generally select the most favorable (lowest) applicable price for the customer.

The next time a user says, "Business Central is picking the wrong price," you may want to verify whether the system is actually applying its Best Price Calculation logic.

I hope you found this insight useful and that it helps you resolve similar pricing-related questions in future.


Comments


bottom of page