The operational problem
What slowed orders, approvals, stock information or other work before a system was built.
PROJECT CASE STUDIES
Articles & insights
Engin Sistem documents projects through the operational problem, the system decision and the evidence available after delivery. Some studies keep the client and commercial details confidential while explaining the work itself.
The project studies below are available in English, with links to their Turkish originals. Other technical notes remain in the Turkish archive.
What the project studies cover
The system decision
Why a B2B portal, ERP connection, mobile workflow or another structure was selected.
Scope and evidence
What was delivered, what can be shown and which outcomes are supported by the available project record.
Project catalogue
Read the full English studies or compare them with the Turkish originals.
A Rule Engine for Dealer Campaigns
Campaign terms, discounts and product visibility were applied manually for different dealer segments, creating conflicts between sales channels.
A central rule engine applied pricing, discount, campaign and product-visibility rules according to each dealer segment.
Read the English case study →One Product and Order Backbone for Four Sales Channels
Product information, technical documents and orders were managed separately across four sales channels, repeating the same work.
A central product, document and order backbone supplied the four channels while leaving their customer-facing interfaces distinct.
Read the English case study →A Product Configurator for 180 Combinations
Correct product and material matches among 180 combinations depended on experienced employees and manual checks.
A custom configurator captured the company's selection rules and guided users through four steps, excluding invalid combinations.
Read the English case study →An Industrial Asset Tracking System in Use for 21 Years
Asset locations, movements and expected returns were tracked in separate records and employees' memories.
Each physical asset received one record linking warehouse entry, dispatch, field movement, return and reporting.
Read the English case study →A Portal for Internal Requests and Approvals
Requests and approvals across departments moved through documents, email and messages, obscuring status and responsibility.
A role-based portal kept submission, review, return and approval steps on one record with a history of decisions.
Read the English case study →An Offline Mobile System for Field Teams
Field visits, notes and orders reached the office through separate channels and could stop entirely when connectivity was weak.
A mobile-first field system stored work on the device and synchronized visits, notes and orders when a connection returned.
Read the English case study →One System for After-Sales Service and Spare Parts
Machine orders, spare-part requests, service work and maintenance history were kept in separate records.
A management system connected the after-sales process to shared customer and machine records.
Read the English case study →Serial-Numbered Product and Label Verification
Manually prepared labels could contain capacity, weight, date or serial-number errors, and customers could not check products against a central record.
The system generated standard labels from product data, recorded unique serial numbers and linked physical products to digital verification.
Read the English case study →A Traceable Order-to-ERP Data Flow
Portal orders were entered again into ERP while approvals, transfer and dispatch were tracked in separate screens.
A controlled integration layer validated orders, transferred them to ERP and recorded approval, error and dispatch status on one record.
Read the English case study →Technical Product Reference Matching
Finding the right laboratory product among several references and technical descriptions depended on scattered records and experienced staff.
A matching system related reference codes, catalogue items, technical data and customer requests in one product model.
Read the English case study →A Multi-Level Dealer Portal
Manual pricing, stock and commission handling across a three-level dealer structure caused errors and repeated reconciliation work.
One hierarchical portal combined level-based access, pricing rules, commission calculations and ERP-connected stock and orders.
Read the English case study →Production Planning and ERP Integration
Production plans in Mikro ERP did not stay synchronized with ecommerce and dealer orders, contributing to stock errors and delayed deliveries.
A two-way integration layer sent orders from B2B and B2C channels to Mikro ERP and returned stock and production status.
Read the English case study →A Mobile B2B Ordering System for Jewellery
WhatsApp orders were difficult to scale and track; pricing errors increased, and catalogue and ERP processes were disconnected.
A mobile-first B2B platform brought product catalogues, dynamic pricing, order management and ERP connection into one workflow.
Read the English case study →Browse the full archive
The Turkish archive also lists technical notes and offers filters for sector and system type.
Browse all project studies in Turkish →Considering a similar system?
We can discuss which parts of your operation need to connect and where to begin.
Request a system review →