Your ERP Knows a Lot. It Just Doesn’t Know Everything.

We often talk about the ERP as if it were the brain of the supply chain.

And, to be fair, it knows a lot.

It knows what we ordered.
What we produced.
What we shipped.
What we invoiced.
How much inventory we have, or at least what we think we have.

But here is the uncomfortable truth: Your ERP probably doesn't know everything you need to know about your supply chain.

And that is not necessarily because your ERP is bad, it is because the supply chain doesn't happen entirely inside your ERP.

A logistics provider might know the actual delivery date.
A warehouse might know when the truck actually arrived.
A supplier might have a better view of when an order will really be ready.
A carrier might know that a shipment is delayed because of a capacity issue.

And somewhere in the organization, someone probably knows all of this because they received an email about it.

There is a surprising amount of supply chain information living outside the ERP.

In Excel files.

In emails.

In PDFs.
In supplier portals.
In logistics provider systems.
In Teams messages.
And sometimes… in someone's inbox.

So how do we bring all these pieces together?

Not necessarily by putting everything into the ERP, instead, we can build a layer around it that connects the different sources of information.

For example, your ERP can remain the source for orders, products and shipments, while logistics providers send delivery information through EDI, APIs or standardized files.

That information can then be collected in a common data platform, transformed into a standard format and matched back to the relevant ERP transactions. Suddenly, an order in your ERP isn't just an order anymore, it can be connected to the shipment, the carrier, the delivery date, the quantity delivered and ultimately the customer experience.

And the same principle can work upstream.

Supplier confirmations can be connected to purchase orders, manufacturing data can be connected to production orders, warehouse events can be connected to shipments wtc.

Different systems don't necessarily need to speak exactly the same language.

What matters is having a common data model and a reliable way of connecting the dots.

This is where technologies such as APIs, EDI, middleware and data platforms become interesting, not because we need more technology for the sake of technology, but because they help us answer a much more important question:

“What is actually happening across my supply chain?”

And there is another important piece to this puzzle: standardization.

If 20 logistics providers send you 20 different Excel files, simply collecting the files isn't enough.
One might call it Delivery Date, another might call it Actual Date, another might call it POD Date, and another might simply call it Date.

Before you can build a meaningful KPI, you need to decide that these represent the same business concept and transform them into a common standard, only then can your ERP data and external data become part of the same story.

The result isn't necessarily one gigantic system containing everything, it's something arguably more useful; one connected view of the supply chain.

Your ERP remains incredibly important, but it doesn't have to know everything, it just needs to know its part of the story and be able to connect with the systems, partners and people that know the rest.

Because ultimately, visibility doesn't come from having more data it comes from connecting the data you already have, and sometimes, the most valuable piece of information in your supply chain isn't sitting in your ERP at all.

It might be sitting in an Excel file someone just emailed you.