Service · Software development

Custom manufacturing software development.

Custom software for manufacturing companies: MES, quality and planning modules, operator apps, PLC and SCADA integrations and ETO configurators. Not a replacement for your SAP, Dynamics, IFS or Infor LN, but the specific layer around it that follows your process rather than the other way round.

Software for manufacturing companies is rarely a single package; it is a landscape.

The average manufacturer now runs on a collection of systems that partly overlap and partly leave gaps: an ERP for finance and purchasing, an MES that drives the shop floor, a CMMS for maintenance, a QMS for quality, a WMS for the warehouse, PLCs and SCADA on the plant itself, plus stray spreadsheets for whatever falls in between. For most of these layers a standard package exists that works perfectly well: SAP S/4HANA, Microsoft Dynamics 365, IFS, Infor LN or Plex on the ERP side, Siemens Opcenter, Aveva or Tulip on the MES side.

We do not replace those enterprise platforms. We are honest about that: a working SAP or Dynamics implementation is not worth rebuilding. In manufacturing, we are brought in for the layer your standard ERP does not cover well: an MES layer that fits your specific production process, a configurator for engineer-to-order work, an operator app on a tablet, a quality flow that follows your standards, or a planner that takes your actual capacity and setup times into account.

The result is software that follows your process, not a package you have to bend your process around. Code, infrastructure and knowledge stay within your organisation, and all integrations with your existing ERP, PLCs, IoT sensors and external systems are explicitly designed, documented and tested.

Our position in four points.

Process first
We model your production and quality flow before we design anything
ERP respect
SAP, Dynamics, IFS, Infor and Plex remain the source of truth
OT-friendly
PLC, SCADA and industrial protocols are part of our toolbox
Ownership
Code, infrastructure and knowledge stay within your organisation

The custom projects we build in manufacturing.

Software for manufacturers is a broad field. We are usually asked to help in three patterns, and most projects combine two or more of them.

Engagement 01

MES layer on the shop floor

Production control, andon boards and OEE tracking

A Manufacturing Execution System that fits your process exactly. Production orders from the ERP translated into work orders per machine or workstation, real-time status information via a PLC or SCADA integration, andon boards on the shop floor, and OEE tracking (availability, performance and quality) measured from actual production instead of manual timesheets.

Many off-the-shelf MES packages are designed for one specific type of production: discrete assembly or process industry, not both. For companies somewhere in between, such as batch production followed by assembly, or metalworking with widely varying routings per order, we build an MES layer that follows your actual flow. For the broader context of what we do in software development, see our main page.

Production ordersWork order routingPLC/SCADA integrationAndon boardsOEE trackingReal-time dashboards
Engagement 02

Operator app, quality and planning

Shop floor tools around your existing ERP

Three modules that come back in almost every project. An operator app on a tablet or rugged industrial handheld that lets production staff open work orders, check material availability, carry out quality checks and report deviations, directly linked to the ERP and MES with no Excel step in between. A quality module with First Article Inspection, First Pass Yield reporting, a Non-Conformity Report flow and calibration management. And a production planner that takes setup times, tooling availability and staff capacity into account.

A detailed scheduler alongside your standard ERP is a classic: SAP and Dynamics can create orders and plan them roughly, but for detailed scheduling at machine level, taking into account sequence-dependent setup times, shift patterns and downtime, they often get stuck. We build that layer to your requirements and connect it to the ERP in both directions. For service organisations that need similar field tooling, see also our work on a maintenance management system.

Operator appFAI / FPYNCR flowCalibrationSetup-aware planningCapacity planning
Engagement 03

ETO/CTO configurator and customer portal

Make-to-order and engineer-to-order with a rules engine

For manufacturers that deliver configurable or engineered work rather than stock products: machine builders, special-equipment suppliers, capital goods, custom supply. A product configurator with a rules engine that safeguards valid combinations, automatically generates the BOM and routing, calculates prices and, for engineer-to-order, passes input on to engineering for the specials.

You will often also want a customer portal where end customers can track order status, download technical drawings and manuals, view their order history and, if needed, place new orders based on earlier configurations. For outsourced operations such as galvanising, laser cutting and heat treatment, a subcontractor portal lets suppliers view their part of the order, report progress and upload quality certificates. For the wider enterprise context, see also our enterprise software page.

If you work with flammable substances or your processes generate dust, you need a zone classification with equipment that is permitted in each zone. How to record this and keep it in step with changes to the installation is covered under ATEX software.

Product configuratorRules engineAuto-BOMAuto-routingCustomer portalSubcontractor portal

What you have at the end.

Working software in production, plus everything around it so you can manage and develop it further yourself.

Production + staging

Two environments, in your own cloud or hosted by us. Your choice.

Web and operator app

A planner dashboard in the browser and an operator app on tablet or handheld.

Codebase + docs

Full source code, build instructions, architecture and integration map.

Key-user training

Sessions for planners and production engineers, video for operators.

Management (optional)

Monitoring, backups, security patches and ongoing development.

When custom software pays off in manufacturing.

Four patterns where an off-the-shelf package gets stuck and targeted custom software adds value, based on the projects we see in practice.

Process deviation

Your production flow doesn't fit the standard

Standard MES and ERP modules assume generic discrete or process manufacturing. Hybrid flows, such as batch followed by assembly, highly variable routings or custom components in series production, rarely fit neatly. This often ends in heavy customisation of the standard package, which needs attention again with every upgrade. Custom software in a separate layer, linked to the ERP through a clean API, is then structurally cheaper.

ETO/CTO

Engineer-to-order or configure-to-order work

For manufacturers that design or configure per order, such as machine builders and makers of special equipment or capital goods, a configurator with a rules engine is almost always custom work. The product logic is your own IP and doesn't fit a standard CPQ package built for catalogue products. Custom software makes the difference between quotes in hours and quotes in days.

OT integration

PLCs, SCADA or IoT sensors need to talk to your software

When maintenance or production needs to be driven by real-time data from the installation itself — running hours via PLC, alarms via SCADA, condition via vibration or temperature sensors — standard packages usually stop at a manual import. A custom integration, built on standard protocols such as OPC UA, Modbus or MQTT, provides direct triggers in the right workflow.

Compliance

Specific quality and regulatory requirements

Production under ISO 9001, GMP for pharma, FDA 21 CFR Part 11 for regulated markets, FSMA for food, AMS certification for aerospace or GDP for logistics requires audit trails, electronic signatures and validation flows that only fit standard packages through expensive customisation. Custom software follows your standard instead of a generic implementation.

Modules that appear in almost every manufacturing project.

The building blocks we draw on — the combination and depth differ per project.

Production

MES layer and work order control

Production orders from the ERP translated into work orders per machine, workstation or operator. Routing based on operations, material availability, tooling and staff. Progress status fed by PLC signals or manual updates in the operator app.

Quality

QMS module with FAI, FPY and NCR

First Article Inspection, First Pass Yield reporting, a Non-Conformity Report flow with root cause analysis, CAPA registration and calibration management for measuring equipment. Including electronic signatures where the standard requires them and structured reporting for the auditor.

Planning

Production planner alongside your standard ERP

Detailed scheduling at machine and shift level, taking into account sequence-dependent setup times, tooling availability and staff capacity. What-if analysis for rush orders, automatic rescheduling when a machine goes down, and a two-way integration with the ERP for delivery date commitments.

Operators

Operator app on tablet or handheld

Open the work order, check material and tool availability, carry out quality checks, report deviations and feed the status back. Suitable for industrial tablets and rugged handhelds, with barcode scanning and optional digital signatures.

Maintenance

CMMS and predictive maintenance

Asset hierarchy, preventive schedules based on running hours or condition, and a technician app with offline mode. For predictive maintenance: integration with vibration, temperature and acoustic sensors via OPC UA or MQTT, baseline detection and automatic work order creation when a deviation occurs.

Configuration

ETO/CTO configurator with rules engine

A product configurator that enforces valid combinations, automatically generates the Bill of Materials and routing, calculates prices and, for engineer-to-order, passes input on to engineering. Includes version control per customer configuration and history for repeat orders.

Customer portal

Order status and technical documents

A white-label customer portal where customers track order status, download technical drawings and manuals, view order history, retrieve certificates and test reports and, if required, place new orders based on previous configurations.

Subcontractors

Subcontractor portal for outsourced work

For outsourced operations such as galvanising, laser cutting, heat treatment and surface treatment, a portal where suppliers can view their part of the order, report progress, upload quality documentation and complete work within agreed deadlines.

Integration

ERP integration as the backbone

Two-way integration with SAP S/4HANA, Microsoft Dynamics 365, IFS, Infor LN or Plex via the standard APIs. Clear contracts and documented mappings so your own IT team can keep maintaining the integrations after we step back.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a manufacturing project works.

01Introduction→ 02Process and system analysis→ 03Build in sprints→ 04Rollout and support
Step 01

Introduction

A no-obligation conversation with your production management, work planners and IT. Which bottleneck are we solving, which systems are in place and what does the landscape look like?

Step 02

Process and system analysis

We model your production, quality and planning flows, spend time on the shop floor and in work preparation, and map out your existing systems and integrations. End result: a scope document.

Step 03

Building in sprints

Working modules in two-week sprints. Work planners and operators test from the first pilot workstation, planners from the first sprint. Immediate feedback, immediate adjustments.

Step 04

Rollout and maintenance

A phased move into production: first one line, one hall or one product group, then scaling up. Ongoing support, further development and expansion with new modules.

What we integrate with and build on.

For each project we choose what fits your existing landscape. We're not dogmatic about any one framework or ERP. For the broader context of where this type of project fits, see our main page on custom software development; for the technical work around it, see our API integration page.

Industrial & OT
OPC UAModbusMQTTSiemens S7RockwellSCADA integrationLoRaWANIO-Link
ERP & back office
SAP S/4HANADynamics 365IFSInfor LNPlexAFASExactNetSuite
Stack & mobile
Next.jsNode.jsPythonPostgreSQLTimescaleDBReact NativeSwiftKotlinGCP/AWS

Frequently asked questions.

Do you replace SAP, Microsoft Dynamics, IFS or Infor LN with custom software?
For large enterprise organisations that already run a working SAP S/4HANA, Dynamics 365, IFS or Infor LN implementation, the answer is no. Those platforms have been refined over decades, cover finance, procurement, sales and supply chain broadly, and rebuilding that makes little sense. We are more often asked in two situations: first, by mid-sized manufacturers for whom an enterprise licence is disproportionate and the package doesn't follow the actual shop-floor workflow well; second, to build a layer alongside the existing ERP, such as an MES, a planner or a configurator, while the core stays in the existing system. We advise transparently on which route delivers the most in your situation, even if that means an off-the-shelf package is the better choice.
Build or buy an MES layer: what do you recommend?
For standard discrete or process manufacturing there are good MES packages, such as Siemens Opcenter, Aveva, Tulip and Critical Manufacturing, and they are often the logical choice. We build a custom MES when your production process is hybrid (batch and assembly), when routings vary strongly per order, when you have several production lines with differing logic, or when the integration with your ERP, configurator or quality system needs to go deeper than an off-the-shelf package allows. We are honest about this: for 60% of manufacturers a standard MES is the better route, and we advise accordingly.
How do you handle IoT, PLC and SCADA integration?
Industrial integrations are one of our core strengths. We work with the standard protocols: OPC UA for modern installations, Modbus for older equipment, MQTT for sensor data, and sometimes directly via Siemens S7 or Rockwell APIs. We typically connect via an industrial gateway that separates OT from IT and passes data on to a time-series database. From there we feed your MES, dashboards, predictive models or the ERP. One key principle: we don't touch the PLC logic itself unless strictly necessary. We read along and send commands via pre-agreed command channels, with clear fallback scenarios.
What exactly do you do for engineer-to-order or make-to-order work?
For ETO/CTO companies we build a product configurator with a rules engine that safeguards valid product combinations, automatically generates a Bill of Materials and routing, performs price calculation and, for engineer-to-order, passes input on to engineering for the specific specials. The configurator is connected to your ERP (for master data and order creation), to your CAD or PDM system (for drawings and bills of materials) and often to a customer portal where end customers configure products themselves within agreed boundaries. The product logic itself is your own IP and is modelled explicitly in collaboration with your engineering and commercial teams.
What about our quality and compliance requirements?
A quality module with First Article Inspection, First Pass Yield reporting, a Non-Conformity Report flow, root-cause analysis and CAPA registration is a standard part of our scope. For regulated markets we support audit trails, electronic signatures where ISO 9001, GMP, FDA 21 CFR Part 11, FSMA, AMS certification or GDP require them, and the validation documentation your auditor expects. We are familiar with CE marking in practice and can help think through how software components fit into your technical file.
What determines the cost of a manufacturing project like this?
Scope (which modules: just the operator app, or MES, planner, configurator and customer portal together), integration depth (how many external systems and which industrial protocols), number of sites and users, and the complexity of your product and process logic. A well-defined operator app alongside an existing ERP is a different project from an end-to-end platform with MES, planner, quality module and PLC integrations across multiple sites. After the scope document we give you an honest estimate — no upfront price list, because without your context every figure is a guess.
How long until we can go live?
A well-defined module — for example just an operator app, a configurator or a quality flow — can be in production within a few sprints. A broader project with MES, planner, configurator and ERP integrations takes several sprints. We always work in phases: first the core goes live with one pilot line or pilot product group, then we scale up to the full operation. Only once the core is running stably do we open up the next layer.
Will you work with our in-house IT team and existing ERP supplier?
Almost always. In a manufacturing project we will almost certainly touch your ERP — SAP, Dynamics, IFS, Infor or Plex — and often your CAD/PDM system, MES package or existing integration layer too. We work transparently with your IT team and, where needed, your existing suppliers. Clear API contracts, documented integrations and an incident runbook are standard. Code, infrastructure-as-code and knowledge stay with you, so you never become dependent on a single agency.

Talk to us about your manufacturing software.

A no-obligation introductory call of half an hour. We listen to your production process, your existing systems and the bottleneck you want to solve — and give you useful direction, even if it turns out that an off-the-shelf package is the better route.

Edit content