A manufacturing group

01 · Three plants, three separate truths

The manufacturing group ran parallel lines across three plants; the ERP, the production tracking software and dealer communication were disconnected. Dealer orders arrived by Excel and phone, and the production plan was settled manually in a weekly meeting. The same order was typed into three systems by hand.

The result was a friction everyone sensed and no one could measure: delayed approvals, inconsistent stock counts, and the same story retold between sales and production.

02 · The integration layer

Instead of ripping out the existing systems we built an integration layer between them. SAP Business One stayed as the core record; a Node.js service layer bound orders, stock and production status into one event stream. An operations database on PostgreSQL holds a real-time single picture of all three plants.

No team had to abandon the tool it knew; the data simply stopped travelling between teams by hand.

03 · The B2B portal

For dealers we built an ordering portal on Next.js: orders land directly in the system with live stock, price and lead-time data. Role-based access was defined with Auth0; every dealer sees its own contract terms and its own order history.

Within the portal’s first quarter, 92 percent of dealers were placing orders through it. Taking an order by phone became the exception.

04 · One dashboard, a new rhythm

A single role-based operations dashboard was built on Power BI for management and the field; approval chains and exception alerts were automated with n8n. The weekly planning meeting went from 4 hours to 30 minutes, because it is now spent deciding, not gathering data.

After seven months manual data entry was down 78 percent, order approval time fell 64 percent, and stock accuracy climbed above 99 percent.