One system or several - how to tie production to the back office without re-keying

It's one of the oldest questions I hear from manufacturers - and on industry forums it has been coming back for years. Before I founded GoIDEA, I ran companies for years and bought software for them, so I know the moment well: the warehouse has its spreadsheet, production its own, and sales a third. Below I explain how to approach the choice and how I tie such processes together myself.

Where the question comes from

Most often from one very specific situation: the raw material in the warehouse spreadsheet is there in theory, but ran out two days ago because production drew it for another order and no one recorded it in the same place. Each department works on its own version of the truth, and the areas where they meet are patched over with phone calls, email and re-keying by hand. The more orders there are, the more often something falls through the gaps between these islands.

One big system - when it helps and when it gets in the way

A large, integrated package has one real advantage: everything sits in one database, so the data doesn't drift apart. The price for that can be high in two ways. First, money and time - an ERP for a smaller company often means long months of roll-out. Second, and more important: such a system usually imposes its own way of working, and your processes have to be bent to fit the box. For a company with an unusual way of operating, worked out over years, that can be a step back.

The data bears this out: in Poland only 32.9% of small companies have an ERP system, against 94% of large ones (Statistics Poland, 2025). That gap comes precisely from the barrier to entry - rolling out one big system is simply harder for a small company to carry.

Several separate tools - why “several” alone isn't enough

The other extreme is to leave each department with its own program or spreadsheet and accept the re-keying. Each tool on its own may be good, but as long as they don't talk to each other, you pay a daily toll: someone moves an order by hand from an email into a spreadsheet, someone else copies the stock level into the production plan, and every such step is a chance for a mistake - and for two people to be looking at two different numbers.

The third way: linked tools and a single source of truth

For a company of 20-250 people, the middle path works best. Each piece of information is owned by one system - the stock level lives in one place, orders in one, the customer record in one. The other tools read and add to that information through integration, instead of keeping their own copy. When production draws material, the stock level updates at once everywhere it's needed. That is what a single source of truth means: every number has one keeper, and everyone sees the same one.

How I connect it all in practice

I don't start by replacing everything at once. I take on the one area that hurts most today - usually warehouse versus production - and connect it so the data flows automatically. A program that already works for you and does its job stays; I connect to it through an API or an automation layer (n8n) that moves the data in the background. The first working result usually shows within a few weeks, and I add further areas once the previous one has proven itself.

If your material is also “there in theory” but has run out in practice - let's talk for thirty minutes. I'll show which area I'd start with in your company and what it takes.