The ERP Lessons the Pandemic Actually Taught Us

Everyone's talking about 2020 being the year of remote work. That's not wrong, but it's shallow. What actually happened was that businesses discovered their ERP systems were fundamentally inflexible in ways that wouldn't matter if everything stayed the same—but everything didn't.

I watched this unfold in real time. In March 2020, suddenly every company needed to operate differently. Supply chains rewired overnight. Warehouses reorganized. Finance teams realized they couldn't close the books without physical access to records they thought were "digital." The panic I heard in client calls wasn't about working from home. It was about discovering critical business processes that depended on physical proximity or assumed sequential workflows that no longer applied.

The Real Lessons Aren't About Remote Access

Most ERP implementations assume a linear process: order comes in, materials are allocated, warehouse picks and ships, invoice goes out. COVID broke that assumption the moment it became necessary to process returns differently, manage limited inventory more aggressively, or pivot to direct-to-consumer sales channels overnight.

I remember one manufacturing client in late March who needed to shift 60% of production to a new product line within 10 days. Their ERP couldn't handle it because the entire configuration was built for their existing product mix. Not technically—they had the capability. Organizationally. The ERP reflected decisions made five years earlier about how product should flow through their business, baked in as "the way we operate."

That client had to hire consultants to reconfigure the system mid-crisis. That's not a remote work problem. That's a rigidity problem.

The pandemic also exposed how poor data hygiene becomes a liability at scale. Teams who'd been manually overriding ERP workflows for years suddenly couldn't do that safely when they couldn't gather in the same room to sanity-check things. One food distributor discovered that for three years, their operations team had been using a spreadsheet-based workaround for ERP functionality that didn't quite fit their needs. When everyone went home, that workaround fell apart because it relied on informal knowledge transfer.

What I'm saying is this: the companies that actually thrived during 2020 weren't the ones with better VPN access. They were the ones whose ERP systems faithfully represented how their business actually operated, not how someone configured it five years ago. They were the ones who'd invested in data quality and weren't depending on tribal knowledge to make the system work.

What Changes, What Doesn't

The other thing the pandemic taught us is that operational resilience isn't primarily about technology redundancy. It's about how flexible your core systems are. Companies that could quickly reallocate demand, adjust procurement, or shift fulfillment channels were the ones whose ERP systems could represent those changes without major customization.

I'm not suggesting you throw out your ERP and start over. But I am saying that when you implement or upgrade one, the question shouldn't just be "does it do what we do today?" It should be "how easily can we adapt it when what we do changes dramatically?"

The vaccine rollout starting this month gives us some sense that things might gradually return to a kind of normal—but I don't think the old normal is coming back. The companies I work with now, even as they anticipate offices reopening, are designing operations with the assumption that flexibility is permanent. That they might need to pivot quickly. That distributed operations might become the default again at some point.

That's the real lesson. ERP isn't just infrastructure for running your business today. It's the platform that determines how fast you can change it when you have to.