@timshuwy is correct, but I’ll restate it as ‘landed and std cost are not mutually exclusive, it’s that landed cost transactions do not affect the std cost as they will affect the avg/last cost.’
The system maintains avg and last costs with every cost transaction, regardless of cost method on the part. As stated, std cost is set by you and the system will never alter it - you have to change it.
@Mark_Wonsil is also correct in that you could alter the burden values to compensate for additional cost. We did this for years where a cost accountant would review all receipts for the week, slice and dice the freight costs (that we paid for delivery) and alter the burden (or std) costs manually for those parts based on a series of rules.
It wasn’t until about a month ago that we were reverse engineering his macro-laden XLS workbook that I realized that he was really just doing some complicated version of AVG costing. So I called them all together to do a mathematical proof to show they were just AVG costing, and ask that we convert all those parts to AVG costing and start doing landed cost transactions. We could save a whole day per week in productivity. We are currently in a middle of a large volume test in the Test DB to let them prove to themselves that I am correct 