If you have spent any time around manufacturing implementations in Dynamics 365 Finance & Operations, you have probably heard some version of this: "Planning is a mess." "The system keeps suggesting the wrong thing." "Production orders are late again." "Inventory says we have it, but we don’t." "MRP is broken." And every time I hear that, I usually have the same first thought: Are we sure this is a planning problem? Or is this a master data problem wearing a planning costume?

The rant “Just update the PO.” Those four words have launched more chaos than any server outage I can remember. Because a purchase order is not a draft email. It is a contract, a planning signal, a receiving roadmap, and an invoice matching anchor. When you casually edit it after the fact, you are not “keeping it current.” You are rewriting history, and every downstream team pays for it in a different way. In manufacturing, this gets ugly fast. Change a date and master planni

Somewhere in every ERP implementation, a well-meaning person says: “Just widen the tolerances so invoices stop failing.” And it works. For about five minutes. Because tolerances are not a technical setting. They are a behavioral policy. They teach suppliers what they can get away with, and they teach your buyers what they no longer have to care about. You might call it efficiency. Your AP team will call it “Tuesday.” Your controller will call it “Why did our material costs cr

If you have ever heard someone say “EDI is just mapping,” you have witnessed the origin story of a future war room. Because EDI is not a connector. EDI is not a one-time technical project. EDI is a living relationship between your business rules and your supplier’s interpretation of them, mediated by a translator, wrapped in compliance timelines, and held together by master data that Procurement swears is clean. The funniest part is that EDI usually does work. It works in the