Small and medium business | Business Central, N...

Prices Changing When You Change A Location Code In Purchase Order

(2) Share

Report

Posted on by RE-15050947-0

hi,

We have a weird event happening.

In purchase orders we have a typed price of £5 in the line which is confirmed with the supplier. We have changed the receipt location and the price has changed to £6 which checking is the last direct price - is this standard functionality? Cant understand how a human entered price would be overwritten by a system

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (8)

Answers (0)

Sort by

Suggested answer

Teagen Boll 3,198 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Yes this is standard functionality. What is happening is when the location is changed your PO line is running validation to confirm the pricing set on the item card or a price list or a SKU and if there isn't a price set then it just uses the last direct price.

I'd recommend you enter location data first before you key in any price data on the line or you could look at using price lists per supplier.

Best,

Teagen Boll

Work: Catapult ERP

Social: LinkedIn

Was this reply helpful? Yes No
RE-15050947-0 26 on at

Like (0)

Report
Copy link

Link copied!

Im struggling to see the logic of why a system would overwrite a price, these items were on order for over a month, the last direct price changed, we wanted to receipt the into our second location as a change post order, and its by chance we notices the price has changed

Really strange

Was this reply helpful? Yes No
Suggested answer

Ahmad Subhani 713 on at

Like (0)

Report
Copy link

Link copied!
Hi,

Yes, this behavior is part of the standard functionality in D365BC. When the location code is changed on the purchase order line, the system revalidates the line pricing. During this process, it checks for any pricing defined:

If no specific price is found for the selected location, the system defaults to the Last Direct Cost.

To avoid unexpected price changes, it’s better to enter the location code before manually updating the unit price on the PO line. Another good option would be maintaining supplier-specific price lists to ensure consistent pricing behavior.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 22,792 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

You consider adding a customization to preserve manually entered prices when only the location is changed.

Was this reply helpful? Yes No
Suggested answer

Grigorios Mavrogeorgis 2,514 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

This is standard Business Central behaviour, not a bug. When you change the location on a purchase line, BC re-validates the line and runs the price finding logic again. Location is part of the pricing context, so the system looks up the price again and replaces your typed £5 with what it finds, in this case the last direct cost of £6.

The problem is that a manually entered price has no protection in standard BC. There is no flag that says "user typed this, leave it alone", so any field change that triggers a price re-find can overwrite it.
Worth checking if the item has a stockkeeping unit or a price list entry specific to the new location.

If you need to keep manual prices safe, either set the price as the last step after the location, or we add a small AL customisation that skips the price re-find when the price was entered by hand.

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards

Gregory Mavrogeorgis

Work: GMSOFT Limited
Blog: Inside Business Central
LinkedIn: www.linkedin.com/in/gregorymavrogeorgis

Was this reply helpful? Yes No
RE-15050947-0 26 on at

Like (0)

Report
Copy link

Link copied!

Thank you for the replies to this post. It just seemed illogical to me.

the location was correct at the point that we placed the order, a month later, we sought to being it into our secondary site. You can imagine from an accounts point of view, the human placed the order at £5, we are looking to not print and automate, if we didnt have a record of the £5 how would we have found this discrepancy as it would have read £6 on the system we would have to rely on the supplier invoice to be correct.

Logically, it just doesnt make sense but i suppose thats BC, it seems to need lots of logical mods unfortunately

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 101,995 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

You can submit this idea to Microsoft.

Missing a feature? Post or vote for ideas on: aka.ms/BCIdeas

PS: Dynamics 365 Business Central: Define default location for sales or purchase

https://yzhums.com/57738/

Thanks.

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 17,623 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Yes, this can happen in standard BC when you change a key field on a purchase line, such as Location Code, because the line is revalidated and BC may recalculate related item/cost fields; for purchases, Microsoft states that Last Direct Cost from the Item Card is copied to the purchase line Direct Unit Cost, so your £6 result fits that logic. Practically, I’d test it by adding/showing Direct Unit Cost, Location Code, and maybe Variant/SKU fields, then change the location again in a sandbox; if the confirmed supplier price was manually agreed at £5, re-enter it after the location change or change the location before confirming the price. It’s annoying, but not random — it’s the validation/recalculation behind the field change.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No