Maciej Ramus
On Friday at 2:30 PM, the purchasing director of a manufacturing company in Greater Poland discovers that the file “dostawcy_master_v22.xlsx” on the network drive has two versions being edited in parallel. One has been opened for three weeks at the Poznań branch. The other at headquarters. There's no such thing as a merge conflict in Excel, so one will simply overwrite the other. Three months of manual work by a buyer in Silesia will be gone the moment someone clicks save.
It's not a made-up story. This is a scenario that repeats in medium-sized Polish production companies about once a quarter. And this is not the biggest problem with Excel as a supplier database. This is only the first sign that it is time to seriously consider changing the tool.
This article is not an attack on Excel. Excel is a great tool if you know where its field of application ends. Below, I break down seven specific moments when vendor management in Excel stops working. They do not all have to occur at the same time. But if you recognize three, migrating to a dedicated system should be on your list of operational priorities for the next six months.
Why Excel still dominates supplier databases
It is worth starting with an honest answer to the question why, despite dozens of dedicated systems on the market, Excel is still the standard in most Polish manufacturing companies. The answer is simple: because it is everywhere, everyone knows how to use it, and at the beginning it is enough.
When a company starts, it has 10-15 suppliers. The supplier knows each of them personally. Excel with their contact details, current prices and notes is enough. Implementation of the system requires investment, configuration, training. Excel is free and „starts tomorrow”.
The problem is that the scale changes more quietly than most companies notice. The number of suppliers is growing, the number of components is growing, the supply team is growing. Excel scales linearly with the number of suppliers, but the operating cost of handling this Excel scales exponentially. When the company gets its bearings, it already has 80 suppliers, three suppliers and five versions of the same file.
7 moments when Excel is no longer enough
The following symptoms appear in companies that have crossed the Excel operating threshold but are not yet aware of it. Each of them separately looks like a nuisance that „you have to survive somehow”. Together, they create a bottleneck that costs the company real money.
7 moments when Excel with suppliers begins to harm the company
Not all at once, but three is enough to start planning a migration.
One supplier works on „dostawcy_v14.xlsx”, the other on „dostawcy_final_ostateczna.xlsx”, which he received by e-mail three months ago. Someone refreshed the prices of steel, but forgot to send it to the rest. The result: two people price the same project with a different cost base, the result differs by 12 percent.
Risk of loss of marginYou want to see if Supplier X raised prices by 8 percent last year. You open Excel and see the current price. Previous? Maybe in an e-mail from August, maybe in a cloud backup. She's usually nowhere to be found. Without price history, you don't negotiate, you just accept what you get.
Lack of negotiating leverageWojtek from procurement knows that the motorcycle from supplier A must be ordered 3 weeks in advance, because they have problems with logistics. That supplier B does better quality, but is sometimes late. That supplier C issues invoices with a 60-day deadline only for orders over 20,000 PLN. It is not in Excel. When Wojtek goes on vacation or changes jobs, this knowledge disappears.
"Ryzyko personalne.For each new customer inquiry, you select 5-8 suppliers matching the set of components from Excel, copy emails to recipients, enter the subject, paste the specification. Working hours per RFQ. With 200 inquiries per month, it is 200 hours, i.e. 1.25 full-time only for sending e-mails.
Hidden operating costEach supplier responds in a different format: one in PDF, the second in an email with a table, the third in an Excel attachment with its own column layout. Someone has to standardize it for comparison. The same work repeated several times a month. And only then do you have the answer to the question of who is the cheapest or the fastest.
Wasted analytical timeExcel will tell you who is in the database and what the last price is. It will not tell you that supplier A missed the deadline 3 times in the last 12 months, that supplier B returned two batches due to quality, that supplier C has the highest prices but the lowest advertisability. Without this ranking data, you choose „after acquaintance”.
Decisions without dataThe customer requires that all critical components come from suppliers with ISO 9001 current on 2026. You send people to search folders, e-mails, files with certificates. In the system with the supplier database, it is a filter, in Excel it is a project for a week. You have a similar problem when a customer suddenly asks about the origin of the material (EU Deforestation Regulation requirements, conflict minerals, EUDR).
Compliance riskIf you recognize at least three of these moments in your company, you are at the threshold where it starts to cost more to maintain Excel than to implement the system. The good news is that you don't have to immediately go for a full-size SaaS platform with a license for €3,000 per month. The basic version of the system, which solves 80 percent of these problems, can be built as an internal tool within a reasonable budget.
Excel vs system in six dimensions
Below is a table compiling six dimensions in which the difference between Excel and the system is immediately felt by the end user. It is not about functions from a spreadsheet, of which there are, of course, more in Excel. These are the operations that consume the most time in the daily work of supplies.
Excel vs Supplier Management System
Six dimensions where the difference is immediately visible
The last dimension deserves attention: the certificate audit. In 2026, after EU regulations on material origin came into force (EUDR, conflict minerals, carbon footprint), compliance audits from clients are becoming routine. A company that can't generate a report on “which of our suppliers have a current ISO 9001 and where critical materials come from” within minutes gets eliminated from tenders at the pre-qualification stage.
The supplier database as a layer of the quoting architecture
Migrating from Excel to a system has one more aspect worth thinking about at the start. The supplier database isn't an island. In a well-designed quoting process, it's one of four layers that have to work together: the Product configurator, the CPQ engine with a BOM generator, the supplier catalog and the quote engine. We described this architecture in detail in a separate article on quoting architecture in non-serial manufacturing.
The key takeaway from that article: the supplier database is exactly the layer worth starting the whole architecture rollout with. Not because it's the most important. Because it delivers value immediately, even without the other layers. Simply having an organized database with price history and ratings changes how procurement works within a week.
When you add system CPQ, your sales team starts getting an automatically calculated base price based on current supplier terms. When you add a configurator, the client starts submitting inquiries on their own in a format that flows through the entire chain without manual intervention.
What migrating from Excel to a system looks like in four steps
Step 1. Import your current database from Excel. You start with what you have. Even an imperfect supplier database in Excel is a better starting point than building from scratch. The system imports the file, maps the columns to the base structure, and flags gaps (e.g. suppliers without a tax ID, components without a price). This step takes from a few hours to a few days, depending on how clean the current Excel file is.
Step 2. Parallel operation for 4-6 weeks. Buyers keep using Excel for day-to-day tasks, but every operation (price update, new supplier, new supplier quote) is entered into the system in parallel. It's a calibration period: you check whether the system covers all real use cases and add any missing fields.
Step 3. Cutover. You set a date from which the system is the single source of truth. Excel goes read-only, as a historical reference. Important: the first 2-3 weeks after the cutover require patience. There will be cases where a buyer wants to “quickly” go back to Excel because the system doesn't show something. Stick with the cutover, but collect those cases as a list of improvements.
Step 4. Expand with auto-RFQ and ranking. Once the database is live, you add the automation layer: the system sends inquiries on its own to the 3-5 best suppliers per component, collects responses and builds a ranking on data from the last 12 months. This step requires a mature database with good history, so it's usually done 3-6 months after the system goes live.
When Excel is enough and migration isn't worth it
Not every company needs a system. Excel is enough if three conditions are all met: the number of active suppliers doesn't exceed 20-25, procurement is handled by one person (so there's no version sync problem), and there's no regulatory requirement for supplier compliance audits.
It's also worth remembering that even for such companies there are inexpensive hybrid solutions: Excel as the main tool plus a simple dashboard in Airtable, Notion or Google Sheets for sharing with the rest of the team. It's not a full system, but it solves the most annoying problem: parallel versions of the file.
We see a similar pattern when rolling out automation at wholesalers. We wrote about it in article on automation in wholesale: not every process needs to be automated right away, but you need to know the point at which manual handling starts costing more than building a system.
Summary
Excel as a supplier database works well until the company crosses an operational threshold. That threshold isn't a specific number of suppliers, but a set of symptoms: circulating file versions, no price history, knowledge in one person's head, manual RFQs and comparisons, no ratings, nightmare compliance audits. Three of these seven symptoms at your company mean it's time to plan a migration.
Migration doesn't have to be a revolution. It starts with importing what you have and running in parallel for a few weeks. A supplier database as a system is also the best first step toward building a complete quoting architecture, to which you'll eventually add a configurator, CPQ and a quote engine.
If you want to talk about what the migration would look like at your company and where to start, write to us via the contact form. Three pieces of information are enough: how many suppliers you have, how many people handle procurement, and what your biggest pain point with your current Excel is.
Frequently asked questions
Is a supplier management system the same as an ERP?
No. ERP handles operations after the purchase decision is made (order, warehouse, invoice). A supplier management system works before that: it relies on price history, quality ratings, RFQs and choosing the optimal supplier. In a well-designed architecture these two systems are integrated, but they have different jobs.
How many suppliers in the database signal that Excel isn't enough?
Above 30 active suppliers you start feeling the limitations. Above 100, Excel is an operational bottleneck. But the number isn't the only criterion. A company with 20 suppliers critical to production continuity needs a system more than a company with 150 suppliers of non-critical components.
How much does implementing a supplier management system cost?
A basic version (a database with price history, a filtering panel, simple RFQ via a form) can be built as an internal web tool for PLN 20k to 50k. A full-featured system with automatic quote aggregation, integrations with supplier systems and a rating module is an investment starting at PLN 80k. Off-the-shelf B2B SaaS products start at EUR 500-1,500 a month.
Does migrating from Excel to the system require stopping procurement work?
Not if you do it in stages. You start by importing your current supplier list from Excel (even an imperfect one) and running the system in parallel. For 4-6 weeks both versions exist, then you gradually phase out Excel. The key is for the system to fill in the data missing from Excel (price history, ratings), not just replicate the file's structure.
Can the system be connected to a Product configurator and CPQ?
Yes, and that's exactly the point. A sensible quoting architecture in custom manufacturing connects the Product configurator (what the client wants), the CPQ engine with a BOM generator (what we need to order) and the supplier catalog (from whom and at what price). We described this architecture separately, explaining which layer is worth starting the implementation with.
