Most manufacturers have invested heavily in modernizing their business. Finance has automation. Sales has a CRM. Production has scheduling tools. Warehouse teams have real-time inventory tracking. And then there’s purchasing still running on email, spreadsheets, and, in more cases than you’d think, the occasional sticky note.

That disconnect was the starting point for a recent conversation between Clint McCree, co-founder of SourceDay, Joey Himes of SolutionsX, and Darren of SourceDay, who came together to talk about something that rarely gets the spotlight in ERP conversations: purchasing and the supplier data that flows through it. The challenge is that a single inaccurate purchase order doesn’t stay contained. It ripples outward, touching production schedules, inventory accuracy, customer relationships, and ultimately, the bottom line.

Here’s what they had to say, and what it means for manufacturers evaluating their own systems.

Purchasing Is the Forgotten Function

When Joey Himes sits in ERP sales cycles with manufacturing companies, he hears plenty about long lead times and supplier headaches. But he’s also noticed something telling: purchasing rarely gets its own seat at the table. It’s usually lumped in with inventory control or warehousing, while production, quality, planning, and finance each get dedicated attention.

That gap shows up in day-to-day reality, too. As Darren put it, “digital transformation” for a lot of buyers just means an automated email gets sent to a supplier. Not an actual connected process. What happens after that email goes out is often a black box. Buyers fall back on open-order reports with red, yellow, and green flags, tracked manually in a spreadsheet every morning.

The irony is hard to ignore: you can send a two-dollar payment through an app and track it end to end, yet many manufacturers are issuing hundreds of thousands of dollars in purchase orders that disappear into email with almost no visibility.

A Purchase Order Is a Plan, Not a Promise

It’s easy to assume that once a PO is cut, the hard part is over. But a PO reflects what your MRP or APS system thinks is going to happen, not a confirmed commitment from your supplier. That difference matters more than most planning teams realize.

SourceDay’s own data backs this up. More than half of all purchase orders change somewhere between issue and close-out. Prices shift, quantities shift, and dates shift. Without a digital connection to suppliers, it’s genuinely hard to know who’s driving those changes. Is it the supplier missing a date? Or is it the buyer expediting or deferring? In most cases, it’s some of both, but without accurate tracking, you’re guessing.

Here’s why that matters for planning: MRP and APS systems treat whatever date is in the system as fact. There’s no ambiguity built in. If a lead time is wrong, the system might tell you a part isn’t available when it actually is or vice versa. Even more common: when a PO goes past due without an update, the system assumes it’s arriving right now, because it has no other information to go on. That single assumption can throw off your entire production plan. As Joey summarized it, dates are treated as gospel in these systems. Bad dates in, bad plans out.

The Ripple Effect, Traced to the Shop Floor

The group walked through a scenario that’s painfully familiar to anyone who’s run a production floor. A part doesn’t show up as planned; maybe the supplier never confirmed the order, or an acknowledgment showed a delay that never made it back into the ERP. Production hits a wall mid-process, and the job gets wheeled to the side to wait.

Then the next job comes through with its own shortage. Someone remembers there’s a cart of parts sitting off to the side, checks it, and if they’re lucky, finds the part they need. So, they pull it, keeping that second job moving. The problem: that transaction rarely gets recorded. Now the original job is short a different part, and the cycle repeats.

This is the ripple effect in its rawest form. What started as one inaccurate date becomes a chain of undocumented workarounds that erodes inventory accuracy and job costing, while the people managing it are just trying to keep product moving out the door. Multiply that across hundreds of purchase orders, and it’s easy to see how a single data gap in purchasing becomes a company-wide problem.

When Trust in the System Breaks Down

Perhaps the most underrated consequence of bad PO data is what it does to trust and to how teams behave. When workaround transactions go unrecorded, inventory numbers drift from reality. Buyers start noticing discrepancies between what the system says and what they know to be true, and over time, they stop trusting the system altogether. That’s when work migrates into spreadsheets with manual VLOOKUPs and formulas that are one typo away from giving someone completely wrong information.

Beyond the operational mess, there’s a human cost. Bad data creates finger-pointing. First, it’s the buyer’s fault, and then it’s production’s fault, or it’s the warehouse. Teams that are all working toward the same goal end up in conflict instead. As Joey put it, this friction often isn’t loud or explicit. It just sits below the surface, chipping away at collaboration and efficiency.

The good news is this usually isn’t an ERP problem. Modern systems are capable. It’s almost always a data problem, specifically, a lack of accurate, timely input around supplier commitments and changes.

Where to Start: Practical, Not Perfect

None of this requires ripping out your planning system or forcing every supplier onto the same portal. In fact, the group was clear that a one-size-fits-all approach to supplier technology doesn’t work.

A few practical starting points came out of the conversation:

  • Meet suppliers where they are. A small supplier might be comfortable acknowledging orders over email. A larger one might send a PDF from their own ERP. Others may be ready for a full digital dashboard. The goal is to digitize whatever data each supplier is already providing, regardless of the channel.
  • Start with acknowledgments and changes. Rather than trying to digitize the entire supplier lifecycle at once (acknowledgments, ASNs, barcoding, shipping labels), start with the highest-leverage piece: getting accurate order acknowledgments and confirmed date or quantity changes flowing back into the ERP.
  • Assess your current state first. Look at your open-order report to identify chronic problem suppliers. Check where inventory is inflated to compensate for unreliable delivery. Prioritize based on impact, not size. Sometimes a five-cent part is what’s actually holding up a six-figure order.
  • Build supplier collaboration into your ERP roadmap from day one. Suppliers are already navigating a change when you implement or migrate an ERP. Addressing supplier collaboration at the same time avoids putting them through a second disruptive change later and treats them as the business stakeholders they are.

Making the Business Case

For anyone trying to get leadership buy-in, let the data speak. Executives respond to hard numbers, not anecdotes about a stressful week in purchasing.

That means tracking how often POs require expediting, how often late deliveries disrupt production, and how much time purchasing spends firefighting instead of sourcing better suppliers or negotiating better pricing. It also means connecting PO data issues to costs leadership already cares about like missed early-payment discounts due to uncaught price discrepancies, inflated inventory carried to protect against unreliable delivery, and late penalties or strained customer relationships.

If more than half of your purchase orders are changing after they’re issued, that’s not just a purchasing statistic; it’s a measurable drag on how much strategic work your team can actually do.

The Bottom Line

You can invest in the best MRP, APS, warehouse management, or accounts payable automation solution on the market. But if the purchase order data feeding those systems is inaccurate or out of date, all of it becomes harder to trust. As the group put it, a purchasing problem doesn’t stay a purchasing problem. It becomes everyone’s problem.

Suppliers are stakeholders in your business, whether your systems treat them that way or not. Closing the gap between your ERP and your supplier data is foundational to becoming the resilient, efficient, data-driven organization every manufacturer is working toward.

Thinking about where supplier collaboration fits into your ERP strategy? SolutionsX works with manufacturers navigating exactly this kind of transformation.  Reach out to talk through where your PO data stands today and where it needs to go.

About the Author

Megan Lehmann

Megan creates educational content on ERP, manufacturing technology, and digital transformation. Working alongside SolutionsX's consultants, she helps translate complex topics into practical insights for manufacturers.

in