Skip to content
All articles
Guides

One Supplier, Five Names, No Answer

When every site runs its own ERP, one supplier hides under many names. Here is what that costs and how to see the whole relationship.

By Aditya Chavali

The decision nobody can make

A category manager wants to know one thing before a renewal: how much does the whole company spend with this supplier?

The answer should take a minute. In a company that runs several ERPs, it takes a week, and it still comes back wrong. One plant knows the supplier by its legal name. Another uses a regional branch. A third bought from a distributor that was acquired last year and never renamed in the vendor file. The same part carries a different item number at every site.

Each system is correct on its own. Together they hide the one number the negotiation depends on.

How a company ends up with many ERPs

Nobody plans it. It accumulates.

  • Acquisitions. Each acquired business arrives with its own ERP, its own vendor file and its own way of coding spend. Migrating it is a project for later.
  • Sites and divisions. Plants and business units choose systems that fit their operations. Some run on premises, some in the cloud, some in a version nobody wants to upgrade.
  • Separate owners. One system belongs to IT. Another is run by a sales or operations team. Each has its own maintenance windows and its own idea of what a clean record looks like.
  • No shared keys. There is no common supplier number and no common item number across systems. Descriptions are free text. Some sites even buy in a different currency.

The result is a set of systems that each pay suppliers correctly and together cannot describe the company's spend.

What it costs

The cost is not the messy data. It is the decisions that never get made.

  • Consolidation stays invisible. When one supplier appears under five names, each name looks like a small relationship. The leverage of the combined volume never reaches the negotiating table.
  • Price variance hides in plain sight. Two sites can buy the same item from the same supplier at different prices for years, because no report puts the two lines side by side.
  • Dependence goes unmeasured. Supplier concentration is a risk question as much as a savings one. It cannot be answered when the supplier is split across systems.
  • Every answer is a project. Each leadership question becomes a data request to every business unit, a round of spreadsheets and a reconciliation that is out of date by the time it is done.

Why the usual fixes stall

Three answers come up in almost every company. Each one has a place. None of them gets the category manager an answer this quarter.

  1. Consolidate onto one ERP. It is the right long-term goal for many companies, and it takes years. Procurement cannot wait for it.
  2. Clean the vendor master by hand. A team merges duplicates in a spreadsheet. By the time it finishes, new vendors have been added at three sites and the work starts again.
  3. Put a BI layer on top. Dashboards can join the systems, but they show the names as they are stored. Five names for one supplier become five bars on a chart.

The pattern is the same in each case: the fix is a project with an end date, and the data keeps moving after it ends.

What works: one record, then the work

The ERPs can stay as they are. What changes is where the company's view of spend lives.

One Corpus across every system. SpendCraft brings in data from each ERP through connectors or file upload and keeps it as a single, governed record of spend. Vendor normalization groups aliases under one canonical vendor identity, so the legal name, the branch and the acquired distributor resolve to one supplier. Item normalization does the same for the parts and services bought under different numbers and descriptions. Everything is classified into the company's own taxonomy, and it can be reclassified on demand without starting over.

That foundation matters because of what it makes possible next.

  • Caddies work the opportunity. A Savings Opportunity Scan, run on demand, surfaces Supplier Consolidation and Price Variance across every system at once. The Savings Opportunities Caddie lets a category manager pick the ones worth working, add context the data cannot see, and take each to a decision. The Caddie suggests. The user decides.
  • Spaces keep the file. The Supplier dependencies Space shows the suppliers the business leans on most, with concentration described across every site. The Tail and new suppliers Space shows the long tail and the newcomers worth consolidating.
  • Scouts watch what comes next. A Spend Scout watches supplier counts, share shifts and new vendors on each data load, so a fourth name for the same supplier is noticed when it appears, not at the next cleanup.

Every number in this loop comes from deterministic logic. Proprietary AI helps resolve names and classify lines. It never generates a figure. Savings ranges are Min to Max ranges scoped to Processed Spend. Ranges are directional, not guaranteed.

Questions to ask any spend tool

A multi-ERP company can test any spend platform with five questions.

  1. Can it bring in every system as it is today, including the ones nobody plans to migrate?
  2. When it merges vendor names, does each merge show its evidence, and can a person accept or reject it?
  3. Does it normalize items as well as vendors, so the same part bought at two sites can be compared?
  4. Can the taxonomy change later without a new implementation?
  5. When a new vendor name appears next quarter, who notices: the platform or the next cleanup project?

The problem does not care how many systems a company runs. One supplier is still one supplier.

The Savings OS.

See it on your own data.

A Proof of Value works one category or one moment end to end.