Engin Sistem
PROJECT CASE STUDY

Production Planning and ERP Integration

A manufacturer connected ecommerce and dealer orders to Mikro ERP production planning, with stock updates and monitored order transfers.

Industry Manufacturing

Problem

Production plans in Mikro ERP did not stay synchronized with ecommerce and dealer orders, contributing to stock errors and delayed deliveries.

System built

A two-way integration layer sent orders from B2B and B2C channels to Mikro ERP and returned stock and production status.

Outcome

The system has remained active for years, connecting sales orders and production planning through Mikro ERP.

We connected a manufacturer’s Mikro ERP production plans with ecommerce and dealer orders so staff no longer had to transfer the same work manually between channels.

Context and operating conditions

The client is a medium-to-large manufacturer selling both directly online and through a B2B dealer network. Mikro ERP was the core production system, but it was not connected to the web and dealer channels in real time.

The problem: disconnected layers

Orders arrived through the website or dealer portal. Central-office staff assembled them in spreadsheets and transferred them to Mikro in the evening.

  • Selling unavailable stock: Online orders could be accepted before production and stock information caught up, leading to cancellations.
  • Manual planning: A production supervisor worked from fragmented spreadsheets to decide what to make.

Why a website change was insufficient

The initial request was to refresh the site and add a stock-warning plugin. A new interface or a stock import once per day would not address the gap between the pace of sales and the pace at which sales information reached production.

We therefore connected the external sales channels to Mikro ERP’s production-planning module through an integration layer. Incoming orders affected stock records; when stock fell below a defined threshold, draft production orders could be created for review.

System architecture

  • Two-way API middleware: Orders from B2B and B2C channels were queued and sent to ERP. Stock and production updates flowed back to the sales channels.
  • Draft work-order trigger: The system considered current orders when stock crossed a threshold and prepared draft production orders in ERP.
  • Transfer monitoring: An order that failed to transfer did not stop the entire flow; the IT team could receive a Slack or email alert identifying the affected order.

Operational result

The Turkish case study reports stock-related online cancellations falling from an 8–12% range to a 1–2% range. The supervisor moved from calculating the production plan manually to reviewing the system’s proposed plan. The system has remained active for years.

The related ERP-connected sales and API-first integration scenarios are currently in Turkish.

Considering a similar system?

Tell us how the process works in your business and where it slows down.

Request a system review

Read the Turkish original →

Measurement preference

Choose whether Google Analytics and Google Ads tags may load in this browser.

Withdrawing permission stops new measurement events. This control cannot retrieve measurements already sent.

Privacy notice