In most production plants, the supply chain still runs on emails, phone calls and Excel spreadsheets. A purchase order goes out by email, the supplier confirms a date in a reply, someone retypes it into the ERP, and stock levels live in a separate file that was accurate yesterday. For a head of procurement or supply chain, that means one thing: decisions get made blind, and every missing component threatens to stop the line.
In our experience, the ERP itself is rarely the problem. The problem is the layer around it: the portal where suppliers enter confirmations themselves, the dashboard that shows stock in real time, and the integrations that tie it back to production. We don’t have a case study here that we could point to, but we have something more concrete: the people and skills that build these systems, plus real experience in industrial and Industry 4.0 projects.
Why is a manufacturer’s supply chain so opaque?
Because the information is scattered and no one sees the whole picture at once:
- orders circulate in email, so only the person on the thread knows the status,
- supplier confirmations arrive in different formats and at different times, often as a PDF,
- stock levels sit in a spreadsheet or the ERP, but not in real time,
- demand forecasts rest on gut feel and last year’s history.
The result is always the same: excess stock at one end and shortages at the other, because no one has a single, current view.
What is a supplier portal and what should it cover?
A supplier portal is a shared place where the manufacturer and its suppliers work on the same data instead of exchanging emails. We most often build in it:
- orders visible to the supplier the moment they are issued,
- date and quantity confirmations entered by the supplier themselves,
- documents (specifications, certificates, delivery notifications) in one flow,
- statuses and notifications when something changes or slips.
With that, procurement stops being a manual relay for information, and data enters the system once, at the source.
How does supply chain software support planning and demand forecasting?
Planning is worth only as much as the data behind it. So we build supply chain software around planning:
- a demand forecast based on sales history, seasonality and open orders,
- material requirements planning tied to the production schedule,
- “what if” scenarios for changes in demand, dates or suppliers,
- alerts when the forecast drifts from the real order inflow.
The point is not a perfect forecast but reacting to deviations faster, before they turn into a stoppage or dead stock.
How do you deliver real-time inventory visibility?
Inventory visibility is the heart of the whole problem. Without it, planning is guesswork. We build it so that a single dashboard shows:
- stock across all locations (warehouses, line-side buffers, supplier-held stock),
- goods in transit and expected delivery dates,
- minimum levels and reorder points with an automatic signal,
- gaps between system and physical stock, before they grow.
When a head of operations sees one current picture of stock, they stop firefighting and start managing risk ahead of time.
How do you integrate this with ERP and MES without creating another island?
A new portal or dashboard only makes sense if it plugs into existing systems rather than sitting next to them. So we always start the project from integration:
- the ERP as the source of orders, part numbers and stock,
- MES and production systems as the source of consumption and production progress,
- an API and data-exchange layer instead of manual export to files,
- a consistent data model, so a part number and a supplier mean the same thing everywhere.
This is usually where a project is won or lost: integration, not the interface. A pretty dashboard on inconsistent data is just prettier chaos.
Which skills do we provide for a project like this?
We shape the team around the specific scope, not “just in case”. For a supply chain project we most often provide:
- an architect and backend developers (e.g. Java, .NET) for logic and integration,
- frontend developers for the supplier portal and inventory dashboards,
- integration and data specialists connecting ERP, MES and warehouses,
- DevOps for deployments, cloud and maintenance.
These are the roles that actually build such systems, and that we can spin up as team augmentation or a dedicated team.
When is it worth adding an AI layer to forecasting?
An AI layer is an option, not a starting point. It makes sense only once the data is clean and flows in regularly. Then we can add:
- demand-forecasting models more accurate than simple extrapolation,
- anomaly detection in deliveries and consumption,
- stock-level recommendations for specific part numbers.
Our AI and Data competence is real (within the RITS Group we have delivered GenAI, RAG and LLM projects), but to be honest: we have not yet deployed AI on a factory floor. So we treat it as a next stage, added on a stable data foundation, not a promise at the start.
What are the most common pitfalls in these projects?
We see them over and over, and it pays to know them upfront:
- starting from the interface instead of integration - you end up with a beautiful dashboard and no data,
- a portal suppliers won’t use, because it’s harder than email,
- no single source of truth for part numbers and stock,
- a forecast with no owner - nobody acts on the alerts,
- an “everything at once” project instead of one process taken to the finish line.
That’s why we hold to a narrow, working scope before we extend the system to new areas.
How fast can a team join the project?
Speed matters, because the supply chain won’t wait. Our recruitment usually closes in about three weeks, stretching to two months only for non-standard requirements. As a nearshore partner from Poland we work in a close time zone, so the team joins your working rhythm, code reviews and meetings with procurement and production without a long ramp-up. We verify skills before the start, so no time is lost picking people on the fly.
How do we do it at RITS?
We do it as a nearshore partner from Poland that delivers skills, even where we don’t yet have a case study in this specific area:
- we provide a team or individual specialists who build portals, integrations and dashboards,
- we start from integration with ERP and MES, not from the interface,
- we rely on real experience in industrial and Industry 4.0 projects,
- we add the AI layer optionally, once the data is ready.
Most often we do this as team augmentation or a dedicated team, and for a new solution from scratch, as custom software built by our team.
Where to start?
Start from the single most painful process - usually that is supplier order confirmation or visibility of critical-component stock. Take it to the finish line, connect it to the ERP, and only then extend. We covered the differences between engagement models in our article on IT engagement models.
Want to give your supply chain a supplier portal and real inventory visibility? Let’s talk - we’ll match a team and an architecture to your systems.