Common Issues With ERP and Productivity Software

I’ve seen $10,00,000+ ERPs break down because one warehouse team used the word “Box”… while the other said “Carton.” That’s it. Master data is the real killer in most ERP projects. But nobody wants to talk about it because it’s not “attractive” It’s not the software. It’s what you feed into it. And here's the stuff actually wrecking your ERP: 1. 𝐔𝐧𝐢𝐭 𝐨𝐟 𝐌𝐞𝐚𝐬𝐮𝐫𝐞 𝐫𝐨𝐮𝐥𝐞𝐭𝐭𝐞 – “PCS” vs “Pieces” vs “Nos.” – Finance gets confused. Inventory gets misaligned. 2. 𝐃𝐮𝐩𝐥𝐢𝐜𝐚𝐭𝐞 𝐯𝐞𝐧𝐝𝐨𝐫𝐬 𝐰𝐢𝐭𝐡 𝐚 𝐬𝐩𝐚𝐜𝐞 𝐚𝐭 𝐭𝐡𝐞 𝐞𝐧𝐝 – Vendor A – Vendor A␣ – Congrats, now you have two aging reports and no idea who’s overdue. 3. 𝐒𝐊𝐔 𝐧𝐚𝐦𝐢𝐧𝐠 𝐥𝐨𝐠𝐢𝐜 𝐭𝐡𝐚𝐭 𝐜𝐡𝐚𝐧𝐠𝐞𝐬 𝐛𝐲 𝐭𝐞𝐚𝐦 – Sales calls it “1L Oil Bottle” – Warehouse calls it “OIL1L” – Finance sees two lines and overpays freight. 4. 𝐆𝐋 𝐚𝐜𝐜𝐨𝐮𝐧𝐭𝐬 𝐬𝐞𝐭 𝐮𝐩 𝐛𝐲 𝐝𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐭 𝐩𝐞𝐨𝐩𝐥𝐞 – 4010-Admin vs 401A-AdminExp – Good luck finding out why your reports don’t reconcile. 5. 𝐂𝐨𝐮𝐧𝐭𝐫𝐲 𝐟𝐨𝐫𝐦𝐚𝐭𝐬 𝐭𝐡𝐚𝐭 𝐜𝐥𝐚𝐬𝐡 – “US” vs “USA” vs “United States” – Then one team can’t file GST because the country code doesn’t match the statutory system. You don’t need another ERP module. You need a data governance spine. If you're migrating, consolidating, or upgrading fix this first:  → Unified naming logic → Approved master data owners → Clean-up workflows → Real UOM and GL dictionaries → Vendor & SKU de-dupe policies Your ERP isn’t broken. Your data is wild. And if you don’t fix it, every report, every dashboard, and every decision will quietly rot from the inside. Seen something worse? Drop your horror story in the comments. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 𝐬𝐨 𝐨𝐭𝐡𝐞𝐫𝐬 𝐜𝐚𝐧 𝐥𝐞𝐚𝐫𝐧.

The biggest businesses can get major programmes horribly wrong. Here are 4 famous examples, the fundamental reasons for failure and how that might have been avoided. Hershey: Sought to replace its legacy IT systems with a more powerful ERP system. However, due to a rushed timeline and inadequate testing, the implementation encountered severe issues. Orders worth over $100 million were not fulfilled. Quarterly revenues fell by 19% and the share price by 8% Key Failures: ❌ Rushed implementation without sufficient testing ❌ Lack of clear goals for the transition ❌ Inadequate attention and resource allocation Hewlett Packard: Wanted to consolidate its IT systems into one ERP. They planned to migrate to SAP, expecting any issues to be resolved within 3 weeks. However, due to the lack of configuration between the new ERP and the old systems, 20% of customer orders were not fulfilled. Insufficient investment in change management and the absence of manual workarounds added to the problems. This entire project cost HP an estimated $160 million in lost revenue and delayed orders. Key Failures: ❌ Failure to address potential migration complications. ❌ Lack of interim solutions and supply chain management strategies. ❌ Inadequate change management planning. Miller Coors: Spent almost $100 million on an ERP implementation to streamline procurement, accounting, and supply chain operations. There were significant delays, leading to the termination of the implementation partner and subsequent legal action. Mistakes included insufficient research on ERP options, choosing an inexperienced implementation partner, and the absence of capable in-house advisers overseeing the project. Key Failures: ❌ Inadequate research and evaluation of ERP options. ❌ Selection of an inexperienced implementation partner. ❌ Lack of in-house expertise and oversight. Revlon: Another ERP implementation disaster. Inadequate planning and testing disrupted production and caused delays in fulfilling customer orders across 22 countries. The consequences included a loss of over $64 million in unshipped orders, a 6.9% drop in share price, and investor lawsuits for financial damages. Key Failures: ❌ Insufficient planning and testing of the ERP system. ❌ Lack of robust backup solutions. ❌ Absence of a comprehensive change management strategy. Lessons to be learned: ✅ Thoroughly test and evaluate new software before deployment. ✅ Establish robust backup solutions to address unforeseen challenges. ✅ Design and implement a comprehensive change management strategy during the transition to new tools and solutions. ✅ Ensure sufficient in-house expertise is available; consider capacity of those people as well as their expertise ✅ Plan as much as is practical and sensible ✅ Don’t try to do too much too quickly with too few people ✅ Don’t expect ERP implementation to be straightforward; it rarely is

ERP won't streamline operations effortlessly. Without planning, it creates chaos instead. Most founders assume an ERP implementation will automatically fix revenue leakage and improve decision-making. The reality? Without proper planning, you get tangled data and frustrated teams. I've watched a founder plug in their ERP expecting magic. Instead: → Data became a mess → Employees grew frustrated → Decision-making got worse, not better The gap between expectation and execution comes down to three things: • No clear strategy before implementation • Lack of team buy-in from day one • Underestimating the complexity of system integration ERP systems are powerful tools for reducing revenue leakage and enabling better decisions - but only when you treat implementation as a strategic project, not a plug-and-play solution. The best founders don't assume technology will solve their problems. They build the strategy, align the team, and execute with precision. That's how you turn an ERP from a headache into a competitive advantage.

⚠️ The Biggest Threat to ERP Isn’t Bugs — It’s Excel. Let’s be honest — ERP systems don’t lose to competitors. They lose to spreadsheets. Every transformation project starts with good intentions: “We’ll standardize, automate, and integrate.” Fast forward six months… and there’s a secret Excel file somewhere running your supply chain. That one “temporary tracker” becomes mission-critical. The CFO’s budget forecast? Excel. The operations planner’s safety stock calculation? Excel. The pricing analyst’s margin adjustments? Excel. Before you know it, your million-dollar ERP is feeding data into — you guessed it — a 97-tab spreadsheet with VLOOKUPs older than your intern. Here’s the uncomfortable truth: Excel isn’t the villain. It’s the symptom. It appears wherever ERP implementations fail to align with: ✅ Real business needs ✅ Change management discipline ✅ User trust and usability When users can’t rely on the ERP for real-time answers, they go back to what’s fast, familiar, and dangerous: Excel. So, before you buy another module or integration, ask yourself — Do people actually trust the data? Do they understand the process behind it? Because you don’t fix spreadsheet dependency with technology. You fix it with adoption, communication, and confidence. #GuptaERP #ERP #DigitalTransformation

Every ERP failure starts the same way. Not with bad code. With good intentions. Someone says, “Let’s customize it — just a little.” And that’s how it begins. A field here. A script there. A shortcut that saves a meeting. Six months later, you’re no longer running an ERP. You’re running a museum of exceptions. I’ve seen companies with five identical workflows — all named differently — because no one wanted to touch another department’s setup. By the time leadership realizes it, every process speaks its own dialect. Finance can’t reconcile. Ops can’t trace orders. IT can’t patch without breaking something else. Customization feels empowering. Until it locks you in. We fixed it by banning one-off builds. Every new request had to prove it served more than one team. If it didn’t, it didn’t ship. Within weeks, complexity dropped. Speed returned. And the system started breathing again. Because in ERP, control isn’t freedom. It’s restraint.

Your ERP project is in trouble if you're hearing these 6 phrases. I've sat in enough project meetings to know when things are about to go sideways. These phrases sound reasonable in the moment. But they're red flags that predict problems months down the road. 🗣️ "𝗪𝗲'𝗹𝗹 𝗳𝗶𝗴𝘂𝗿𝗲 𝘁𝗵𝗮𝘁 𝗼𝘂𝘁 𝗮𝗳𝘁𝗲𝗿 𝗴𝗼-𝗹𝗶𝘃𝗲." No, you won't. After go-live, you're in survival mode dealing with urgent issues, not solving deferred decisions. 𝗧𝗵𝗲 𝗳𝗶𝘅: If it matters enough to discuss now, it matters enough to solve now. Document it, assign an owner, set a deadline before go-live. 🗣️ "𝗧𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺 𝘄𝗶𝗹𝗹 𝗳𝗼𝗿𝗰𝗲 𝘂𝘀 𝘁𝗼 𝗰𝗵𝗮𝗻𝗴𝗲 𝗼𝘂𝗿 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀." This sounds like commitment to best practices. But it's actually abdication of responsibility. Systems don't force change. People do. If you haven't planned how those process changes will happen, you're setting up resistance and workarounds. 𝗧𝗵𝗲 𝗳𝗶𝘅: Map the process changes. Train on them specifically. Explain why they matter. 🗣️ "𝗟𝗲𝘁'𝘀 𝗷𝘂𝘀𝘁 𝗰𝘂𝘀𝘁𝗼𝗺𝗶𝘇𝗲 𝘁𝗵𝗮𝘁." Customization isn't always wrong. But when it becomes the default answer to every gap, you're building a maintenance nightmare. Each customization adds cost, complexity, and risk to every upgrade. 𝗧𝗵𝗲 𝗳𝗶𝘅: Ask three questions:   1. Does this support a competitive advantage?   2. Is there a configuration option we're missing?   3. What's the long-term cost of maintaining this? 🗣️ "𝗢𝘂𝗿 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗶𝗹𝗹 𝗮𝗱𝗮𝗽𝘁 𝗼𝗻𝗰𝗲 𝘁𝗵𝗲𝘆 𝘀𝗲𝗲 𝘁𝗵𝗲 𝗯𝗲𝗻𝗲𝗳𝗶𝘁𝘀." Hope is not a change management strategy. If you're counting on people to figure it out on their own, you're underestimating resistance. Adoption doesn't happen automatically. 𝗧𝗵𝗲 𝗳𝗶𝘅: Build change management into the project plan. Identify champions early. Make adoption measurable, not assumed. 🗣️ "𝗪𝗲'𝗿𝗲 𝘁𝗼𝗼 𝗯𝘂𝘀𝘆 𝘁𝗼 𝗱𝗲𝗱𝗶𝗰𝗮𝘁𝗲 𝗳𝘂𝗹𝗹-𝘁𝗶𝗺𝗲 𝗿𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀." Translation: This project isn't actually a priority. Part-time participation guarantees delays, poor decisions, and a system that doesn't match reality. 𝗧𝗵𝗲 𝗳𝗶𝘅: If you can't staff it properly, don't start. You'll spend more time fixing a half-resourced project than doing it right. 🗣️ "𝗪𝗲'𝗹𝗹 𝗰𝗹𝗲𝗮𝗻 𝘂𝗽 𝘁𝗵𝗲 𝗱𝗮𝘁𝗮 𝗱𝘂𝗿𝗶𝗻𝗴 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻." No, you won't. Migration is a data transfer project, not a cleanup project. If your data is messy now, it'll be messy in the new system. 𝗧𝗵𝗲 𝗳𝗶𝘅: Clean your data before migration. Deduplicate. Standardize. Validate. It's the difference between a system you trust and one you question. Every ERP project has problems. The difference between success and disaster is catching them when they're still fixable. And that only happens when someone actually speaks up. What phrases make you nervous in project meetings? Share your red flags in the comment. #ERPImplementation #ProjectManagement #DigitalTransformation

Everyone loves “AI-powered ERP,” but nobody talks about the fact that 60% of companies don’t even clean their master data. It’s 2026, and I don’t understand why we’re still talking about it. As per a report by Gartner, 60–85% of data initiatives fail due to poor data quality. Can you imagine what this can cost? 1) Direct money loss Wrong data leads to wrong invoices, wrong taxes, duplicate payments, and hence thousands of dollars lost. 2) Wasted ERP and AI investment AI-powered ERP systems still depend on clean data. This means you keep paying for expensive software, consultants, and AI tools to generate unreliable insights and unusable reports. 3) Loss of trust and poor decisions When reports are of no use, then leadership spends more time debating numbers than making decisions. So, to avoid this loss in your organisation, you need to work on these: - Your tax logic - Your vendor list - Your data quality - Your cost centers - Your project codes - Your approval flows - Your product and service lists - Your one full cleanup cycle before migration If not done well now, you’ll regret it later on. Because it’s your “data” and your “duty.” Follow Martin Iten for more content like this related to ERP.

ERP Projects Fail for Many Reasons. Ignoring Integrations is the Fastest Way to Doom One. Too often, ERP projects run over budget, take too long and fail to deliver. The culprit? Overlooked integrations. I see this mistake all the time. Companies focus on ERP functionality but forget that no system operates in isolation. Data flows, third-party systems, and automations must be planned from day one—not as an afterthought. That’s why I put together a no-nonsense whitepaper on how to make ERP integrations work instead of becoming a hidden pitfall. 5 Practical takeaways from the whitepaper: 1. Define all data flows at project kickoff – Document dependencies between systems early. Surprises later = delays & cost overruns. 2. Master data first, transactions second – Sync customers, vendors, and products first. If your master data is broken, transactions will fail. 3. Set a realistic integration timeline – Sync integration tasks with ERP rollout. If integrations are late, the entire project stalls. 4. Test with real data, not fake records – Your ERP test system should mirror production. Otherwise, the first real transaction is your actual test. 5. Make integrations visible – Use visual mapping tools to align teams, avoid assumptions, and ensure all critical systems stay connected. Get the full whitepaper here: https://lnkd.in/dfNHA9nN ERP success is not just about the ERP—it’s about how well everything connects. Integrations First. Always. #ERP #Automation #iPaaS #PMO #ProjectManagement

Most ERP, PLM, and MES programs don’t stall because the technology can’t integrate. ☑️ SAP and Oracle integrate. ☑️ Siemens, SAP, and Dassault PLM integrate. ☑️ SAP ME/MII, Opcenter, iBASEt, Delmia (Apriso, Ortems), Rockwell, and IIoT platforms integrate.   ☑️ The APIs work. ☑️ The interfaces fire. ☑️ The data moves.   What breaks is operational truth as work moves from PLM > ERP > APS > MES > the shop floor. That drift usually starts early, during ERP and PLM programs, when product structures, routings, effectivity, constraints, and planning assumptions get locked in before execution reality is fully understood. By the time manufacturing solutions goes live, delivery teams are already compensating, Excel models, side schedules, tribal knowledge, manual reconciliation, all to keep production moving.   That pattern shows up again and again across Systems Integrator-led programs.   It’s an Execution Intelligence problem.   Execution Intelligence is the capability to keep product truth, process truth, and execution truth aligned across ERP, PLM, APS, and MES so plans hold when reality shows up.   In the article below, I break down:   💡 where execution truth actually fractures inside large programs 💡 why APS, OR, and MES don’t resolve it on their own 💡 how stabilizing execution truth early protects ERP and PLM revenue 💡 and how that foundation enables Smart Factory expansion later If you’re selling, running, or delivering manufacturing transformations and any of this feels familiar, this one’s for you....