Material Requirements Planning Custom MRP & integration BOM · MPS · MES

Custom MRP system development

Appfront designs, builds and integrates MRP software for manufacturing, food, pharma, automotive, fashion and electronics. We build custom Material Requirements Planning where standard ERP modules fall short, or integrate SAP S/4HANA, Microsoft Dynamics 365, Oracle, Infor, Exact Globe, AFAS, Ridder iQ and Plex with your shop floor, purchasing, supplier portals and MES. BOM explosion, master production schedule, capacity planning, just-in-time, kanban, lot and expiry tracking — all in one controlled production flow.

What is MRP and what does a custom MRP system do?

Material Requirements Planning is the planning engine of a manufacturing company. Based on demand — sales orders, forecasts and the master production schedule — and the master data of your products (BOMs, stock, lead times, lot sizes, suppliers), an MRP calculates which components, semi-finished products and raw materials are needed, when and in what quantity. From this, a structured flow of work orders for the shop floor and purchase orders for suppliers follows. Without MRP, that work lives in spreadsheets and email attachments; with a good MRP, it becomes a controllable dial between sales and production.

An MRP system is therefore not the same thing as an ERP — even though it is built into many ERP suites. The ERP handles orders, stock, purchasing and accounting as a whole; the MRP is the logic that drives the right orders from demand and BOMs. An MES (Manufacturing Execution System) then controls the shop floor and records what actually happens; the MRP supplies the MES with work orders and BOM revisions. A WMS (Warehouse Management System) handles storage and issuing; the MRP says which materials must be available and when. Good integrations between MRP, MES and WMS warehouse software prevent data from becoming fragmented and the shop floor from working with outdated plans — a pattern we still come across often at organisations that have yet to make the move to structured MRP.

Appfront builds both custom MRP software and integrations between existing ERP/MRP platforms and the rest of your IT landscape. In classic discrete manufacturing (mechanical engineering, automotive suppliers, electronics), we often work with or around SAP S/4HANA, Microsoft Dynamics 365, Oracle or Infor LN, with deep BOM explosion and capacity planning. For food and pharma manufacturers, we build MRP flows with multi-level lot and expiry tracking, batch recipes and allergen cascades. For fashion brands with seasonal demand, we build collection-aware MRP that accounts for collection start and run-out dates. This ties in with our broader practice in software for the manufacturing industry and food software.

BOM explosion without the Excel puzzle

Multi-level explosion from finished product through sub-assemblies down to raw materials, automatically checked against stock, open orders and lead times. Work orders and purchase orders roll out in a controlled way, with effectivity dates and BOM revisions that are always correct.

Master production schedule

A structured MPS that brings together forecasts, open orders and capacity headroom. Scenario planning shows what a demand peak or a shift change will do before the MRP explosion runs on top of it.

Lot and expiry tracking

Every raw material and every finished product gets a unique lot number with production and expiry dates. FEFO issuing, recalls and HACCP/GMP evidence all run through a single source — no Excel archaeology when the inspector calls.

Our development process for MRP projects

MRP projects stand or fall with a good upfront analysis: which product domain, which production type (discrete, process, mixed), which existing ERP and MES systems, which compliance context. We follow an approach that brings the complexity of your production into view early and delivers a stable result. From mapping your current planning reality to a phased go-live and ongoing maintenance — every step is aimed at making planning, production, purchasing and quality ultimately work from a single source.

1
Domain analysis

We map out how your production is structured: which product families, which BOM levels, which production type (make-to-stock, make-to-order, engineer-to-order), which suppliers and which compliance regimes are involved.

2
Architecture

We design the MRP architecture (data model, integration patterns, planning horizon, lot sizes) and together decide whether a standard ERP module, an extension of it or a custom MRP fits best.

3
Development

Implementation in sprints with automated tests, structured logging, monitoring and clear demo moments. Along the way, you see working flows in an acceptance environment with representative product data.

4
Go-live & maintenance

A controlled go-live with data migration, stock validation and a safety net for deviations, followed by ongoing management, monitoring and further development in step with your release calendar.

What a custom MRP system delivers in practice

Every MRP implementation is tailored to your product domain, production type and adjacent systems. Below are the features we deliver most often in manufacturing, food, pharma, automotive, fashion and electronics. Whether you're building your own platform, integrating an existing MRP with your ERP and MES, or building in a just-in-time flow with EDI suppliers, our API experience combines here with domain knowledge of production and supply chain data. Also read about our broader approach to smart API integrations.

BOM explosion & netting

Multi-level explosion from finished product down to raw materials, with effectivity dates, alternative parts and scrap percentages. Gross requirements become net requirements after being checked against stock, open purchase orders, work orders and reservations. Changes run through ECO flows, so there are no surprises on the shop floor.

Master production schedule

An MPS layer with scenario planning: forecasts, open orders and capacity headroom are weighed against each other before the MRP explosion runs underneath. Planners can model demand peaks, shift changes and seasonal effects before the MPS is officially published.

Capacity planning

Workstation- and shift-level capacity planning with finite scheduling where it makes sense. Under- and over-capacity become immediately visible per work centre, with bottlenecks and setup times taken into account. CRP (Capacity Requirements Planning) runs alongside MRP so that planning stays realistic.

Lot, batch & expiry tracking

Lot numbers per raw material, semi-finished product and finished product, with production date, expiry date, source batch and supplier. FEFO issuing, automatic rotation, structured quarantine status and recalls that give you answers in minutes, not days. Essential for food, pharma and cosmetics.

Supplier orders & EDI

Automatic purchase orders to suppliers via EDI (EDIFACT, ANSI X12), API or supplier portal. ASN (Advance Shipping Notice) processing, passwordless partner onboarding, lead times monitored per supplier and SLA reporting. Vendor-managed inventory and just-in-time replenishment where it makes sense.

Kanban & just-in-time

Hybrid planning in which classic MRP exists alongside pull-based kanban flows. Visual kanban boards, e-kanban via barcode or RFID, lot sizes per item, and automatic supplier orders at the signal level. Fast-moving stock is pull-driven, longer lead times run through MRP — both in one system without duplicate administration.

MES bridges & OPC UA

Bidirectional integration with MES platforms such as Siemens Opcenter, AVEVA, Rockwell FactoryTalk or GE Proficy. Work orders, BOM revisions and routings flow to the shop floor; reporting on production, scrap and deviations flows back. Machine data via OPC UA and MQTT, with an ISA-95-compliant layer design.

Compliance & traceability

ISO 9001, IATF 16949 (automotive), AS9100 (aerospace), GMP and 21 CFR Part 11 (pharma), HACCP (food) and the EU traceability requirements. Audit trails, e-signatures, batch records and non-conformities are recorded in a structured way and linked to product revisions and supplier batches.

MRP projects in practice

An MRP system works out very differently in each industry. Discrete manufacturing has different planning rhythms from process industry; food and pharma require lot tracking, while fashion requires seasonal MRP. A number of scenarios come up again and again — and for each of them we have proven patterns that take into account the specifics of your product domain, your production type, your compliance context and the existing systems MRP has to talk to. Also read how an MRP works together with PLM systems on the product data side and with WMS warehouse software on the logistics side.

Discrete manufacturing & machine building

Machine builders, OEMs and tier-1 suppliers with deep assemblies, long lead times and mixed engineer-to-order and make-to-stock production. We integrate SAP S/4HANA or Microsoft Dynamics 365 with shop-floor MES platforms and build finite scheduling with setup times and queues per work centre. Part of our broader practice in manufacturing software.

Food & process

Food manufacturers, beverage producers and process industries with multi-level recipes, multi-pack configurations, allergen cascades and strict HACCP evidence requirements. We build rolling MRP with daily re-runs, lot and expiry tracking, FEFO issuing, and integrate with retail EDI for pull-based deliveries. Part of our practice in food software.

Pharma & cosmetics

Pharmaceutical producers and cosmetics manufacturers with GMP requirements, batch records, e-signatures under 21 CFR Part 11, quarantine status and strict deviation management. We build MRP flows in which every batch is traceable to source raw materials, supplier certificates and QA releases, so you are inspection-ready without ad-hoc spreadsheets.

Automotive & mobility

OEMs and tier-1 and tier-2 suppliers in the automotive and mobility sector. IATF 16949-compliant traceability, APQP/PPAP flows with suppliers, just-in-sequence deliveries to assembly lines and vendor-managed inventory with major customers. We often work with Plex, SAP or QAD in this context and build just-in-time bridges to the shop floor.

Fashion & seasonal MRP

Fashion and lifestyle brands with collection cycles, fabric libraries and seasonal demand. We build collection-aware MRP that accounts for collection start and run-out dates, capsule collections, manufacturing locations in Asia and integrations with e-commerce storefronts. Production and purchase orders follow the collection calendar instead of a static annual budget.

Electronics & high-mix

Electronics manufacturers and high-mix, low-volume producers with complex BOMs, alternative components and highly fluctuating supplier availability. We build MRP flows in which component shortages become visible in time, alternative parts are suggested automatically and supplier lead times are tracked realistically per item rather than as a static value.

Hybrid contract & private label

Contract manufacturers and private-label producers who run different product lines for different customers, often with customer-specific recipes or variants of a single base product. We build MRP flows that apply different lot sizes, release procedures and separate traceability per customer contract, without breaking your planning.

Technology we use

MRP projects have no fixed stack. The right choices depend on your existing ERP, the complexity of your production, the compliance context and the type of shop floor (manual, semi-automated, fully automated). We work with the market-leading ERP and MRP platforms where they fit, and build custom MRP on a modern service stack where that sets you apart. We always align the stack with your IT landscape, so your own team can keep managing or extending the solution in the long run. The ISA-95 layer model is our guide for giving planning, execution and machine data each their own role.

SAP S/4HANA & SAP ECC Microsoft Dynamics 365 BC / F&O Oracle E-Business Suite / NetSuite Infor LN & Infor M3 Exact Globe & Online AFAS Profit & Unit4 Ridder iQ Plex & QAD Siemens Opcenter (MES) AVEVA MES Rockwell FactoryTalk GE Proficy REST / GraphQL / SOAP EDIFACT / ANSI X12 OPC UA & MQTT ISA-95 layering PostgreSQL & SQL Server Node.js / Python / .NET / Java Azure / AWS / GCP HMAC webhook validation

Why Appfront for your MRP project?

Appfront combines extensive experience in API integrations and custom software with domain knowledge of production data in manufacturing, food, pharma and highly regulated sectors. An MRP project is not a standalone project: it touches sales, planning, production, purchasing and quality at the same time. We always start with a thorough analysis of your production domain, production type and adjacent systems — an MRP choice has to be technically sound, but it also has to add practical value for the planners, work preparers and buyers who use it every day.

For every integration and every custom component, we write clear documentation and make sure your own team — or a future supplier — can understand and manage what is running. No black box, but transparent code, explicit contracts between systems and clear agreements on monitoring, alerting and maintenance. That keeps you independent and in control of your planning, your production data and your release calendar at all times.

You work with a single point of contact who understands both the technical and the functional side of MRP — someone who can talk MPS cycles with your operations manager, IATF 16949 or GMP with your quality team, and the architecture of the integration landscape with IT. That keeps communication lines short, prevents miscommunication with ERP vendors and speeds up decisions when choices have to be made during the build around data models, planning horizons or lot sizes.

Also take a look at our broader practice around the integrations we build, our work in software for the manufacturing industry and our approach to smart API integrations.

  • Experience with SAP, Dynamics 365, Oracle, Infor, Exact, AFAS, Ridder and Plex
  • Domain knowledge of both discrete and process industries
  • Deep API experience — REST, GraphQL, SOAP, EDIFACT, OPC UA and MQTT
  • ISA-95-compliant layering between planning, MES and machine data
  • MES bridges to Siemens Opcenter, AVEVA, FactoryTalk and GE Proficy
  • WMS integrations for warehouse issuing and stock control
  • EDI with retailers and large suppliers (EDIFACT, ANSI X12)
  • Compliance flows for ISO 9001, IATF 16949, GMP, HACCP and 21 CFR Part 11
  • Just-in-time, kanban and hybrid pull/push planning
  • Secure by default — least privilege, audit trails and signature validation
  • Clear documentation your planners and IT team can read
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive development in step with your release rhythm

Security, compliance and evidence

Production data is sensitive on several levels at once: intellectual property (recipes, formulations, NC programs), customer data in order flows, supplier information and, in some sectors, classified or patient-sensitive data. Appfront builds MRP environments in line with the OWASP guidelines, with encrypted communication, role-scoped authorisations and strict separation of duties between disciplines. Planning sees what planning needs, quality sees the relevant audit data, and an external supplier sees only the parts they are responsible for.

For regulated sectors, we build the evidence chain in from the start. ISO 9001 is our basis for audit trails and non-conformities. IATF 16949 for automotive calls for structured APQP/PPAP flows and advanced shipping notices; AS9100 for aerospace adds configuration management and counterfeit-part prevention; GMP and 21 CFR Part 11 for pharma require e-signatures, deviation management, quarantine status and complete batch records. For food products, we work according to HACCP and meet the EU traceability requirement (Regulation 178/2002): one step forward and one step back on every batch.

We document the data flows between MRP, ERP, MES, WMS and supplier portals so that your processing register, technical file and quality manual are always up to date and you demonstrably meet the applicable standards. Supplier evidence arrives through structured declarations — not loose PDFs that you have to read out manually, but machine-readable data that can be traced back to the source. Also read our information security policy and coordinated vulnerability disclosure policy.

  • OWASP ASVS as the basis for secure development
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least privilege per discipline
  • Audit trails per work order and per purchase order
  • ISO 9001-compliant non-conformity and change flows
  • IATF 16949-compliant APQP/PPAP and ASN flows
  • GMP- and 21 CFR Part 11-compliant batch records and e-signatures
  • HACCP evidence and EU 178/2002 traceability
  • Lot, batch and expiry management with FEFO logic
  • Monitoring and alerting for planning deviations
  • Documentation for your processing register and quality manual

Frequently asked questions about MRP systems

Answers to the questions we get asked most often about custom MRP and MRP integrations.

MRP stands for Material Requirements Planning: a planning method, and the system that goes with it, that uses demand (sales orders, forecasts and the master production schedule) and master data (BOMs, stock, lead times, lot sizes) to calculate which parts and raw materials are needed, when and in what quantity. Work orders and purchase orders with the right start date then roll out of that. MRP is therefore the engine between what you want to sell or produce and the orders that actually reach the shop floor and the purchasing department. Without MRP, this becomes manual work in Excel; with a good MRP, it is a controllable, repeatable process you can simply set running.

For a broad ERP context with finance, HR and logistics modules, an established package such as SAP S/4HANA, Microsoft Dynamics 365 or Exact Globe is usually the right starting point. Custom MRP makes sense when your production domain is so specific that a standard MRP module costs more in configuration and workarounds than a custom solution. Think of a food manufacturer with multi-level shelf life and allergen cascades, a pharma producer whose batch traceability deviates from a standard model, a fashion brand with seasonal MRP and collection-aware capacity planning, or a high-mix, low-volume machine builder where lot size one and kanban exist alongside work orders. We then build an MRP layer that runs alongside the ERP and takes over, or replaces, only the planning logic that is truly distinctive.

We regularly work with SAP S/4HANA and SAP ECC in enterprise contexts, Microsoft Dynamics 365 Business Central and Finance & Operations for the broader mid-market segment, Oracle E-Business Suite and Oracle NetSuite, Infor LN and Infor M3 (mainly fashion, food and discrete manufacturing), Exact Globe and Exact Online, AFAS Profit, Unit4 and Ridder iQ. In heavier production environments we also integrate with Plex (cloud MRP for automotive and discrete manufacturing) and QAD. On the custom side, we build lighter MRP layers with PostgreSQL, a service-oriented architecture and REST/GraphQL APIs, often alongside an ERP that handles the financial and logistics layer.

BOM explosion is the process in which an MRP breaks down the Bill of Materials of a finished product step by step into parts, sub-assemblies and raw materials, and multiplies that by the quantity to be produced. If you want to make 200 units of product A, and each unit contains a sub-assembly B that itself contains three parts C, D and E, the explosion works out that you need 200 Bs, 200 Cs, 200 Ds and 200 Es — minus whatever is already in stock or on order. By comparing this gross calculation with stock, open purchase orders, lead times and lot sizes, the MRP knows at any moment which work order or purchase order needs to start. Good BOM management is therefore the first prerequisite: a wrong BOM means the whole explosion comes out wrong.

MRP plans; MES executes. The MRP generates work orders with a start date, quantity, BOM revision and routing — that is, the sequence of operations and the associated workstations. The MES (Manufacturing Execution System) takes that work order onto the shop floor, controls machines, and records what was actually produced, how much scrap arose and which deviations occurred. We connect MRP and MES via REST or MQTT bridges and adhere to the ISA-95 layer model, so planning, execution and machine data each keep their own role. For machine data itself, we often work with OPC UA for modern shop floors and MQTT for IoT-oriented production lines. We integrate with MES platforms such as Siemens Opcenter, AVEVA, Rockwell FactoryTalk and GE Proficy where these are already in place.

The Master Production Schedule is the intermediate layer between forecasts and MRP. For each finished product and planning period (often a week or a day), the MPS determines how much is planned to be made — taking into account sales forecasts, open orders, available capacity and inventory policy. A good MPS smooths out demand peaks that the system would otherwise translate straight into unfeasible work orders, and prevents yo-yo behaviour in purchasing. We build MPS modules with scenario functionality, allowing planners to compare different demand and capacity assumptions side by side before the published MPS goes into the MRP explosion.

For food, pharmaceutical products and cosmetics, lot and expiry tracking is not an extra but a basic requirement. We build MRP flows in which every raw material, semi-finished product and finished product gets a unique lot number, linked to production date, expiry date, supplier and source batch. In the event of a recall, you can then see from a single screen which batches went to which customers, within minutes. For FEFO (First Expired, First Out) stock allocation and automatic rotation of near-expiry lots, we build the logic into the issuing layer. For pharma, we take into account GMP requirements around audit trails, e-signatures under 21 CFR Part 11 and the validity of quarantine status, and for food, HACCP evidence requirements and the EU traceability obligation (Regulation 178/2002).

MRP integrations almost always combine several protocols. We use REST and GraphQL for modern service-to-service integrations between MRP, ERP, e-commerce, EDI platforms and supplier portals. We regularly come across SOAP services in older SAP and Oracle installations. EDI (EDIFACT, ANSI X12) is still the standard for purchase orders, delivery notifications and invoicing with retailers and large suppliers. OPC UA is the standard for machine data and fits the ISA-95 architecture, and MQTT is used for IoT-oriented production and sensors. For batch exchange with legacy systems, such as old ERPs that still expect flat-file imports, we build secure file transfer with checksum validation. Also read our page on smart API integrations.

Not every product belongs in a classic MRP explosion. Fast-moving items with stable demand often work better through kanban or just-in-time replenishment — a simple pull signal from the shop floor that immediately triggers a replenishment order. We build MRP environments that work in a hybrid way: MRP for the complex, long-lead-time components and kanban for high-volume items. Visual kanban boards, e-kanban signals via barcode or RFID, lot sizes per item and automatic supplier orders make the difference between planning on paper and planning that the shop floor actually follows. For automotive, we build vendor-managed-inventory flows; for food, we often build rolling MRP with daily re-runs.

Compliance is not a separate module but a continuous layer running through the MRP data. For ISO 9001, we record audit trails, change management and non-conformities in a structured way and link them to product revisions. For automotive (IATF 16949), we build in APQP and PPAP flows, supplier-quality monitoring and advanced shipping notices. For pharma under GMP, we provide e-signatures compliant with 21 CFR Part 11, batch records, deviation management and quarantine status. For food, we work according to HACCP — critical control points, sampling flows and allergen cascades — and we meet the EU traceability requirements for food. The aim is always that when an audit lands on your doorstep, you can provide evidence within the required timeframes without anyone having to piece spreadsheets together.

Yes. We are regularly brought in on existing SAP, Dynamics, Infor or Exact implementations where the MRP layer gets stuck somewhere — for example an explosion that runs too slowly, supplier EDI that fails regularly, an MES integration that breaks with every release, or a hybrid kanban/MRP flow that causes stock shortages. We audit the architecture, the API calls, the error handling and the data quality, document the current setup and draw up improvement proposals. From there, we take over changes, extensions and ongoing maintenance, or work alongside your existing ERP partner where that makes sense.

Talk to us about your MRP project

Tell us about your production domain, your current ERP or spreadsheet reality and the systems the MRP needs to talk to — shop-floor MES, WMS, supplier EDI, e-commerce or a PLM layer on top. We are happy to help think through scope, priorities, planning horizon and alignment with your ERP vendor. A no-obligation first conversation will give you a clear picture of the possibilities and the trade-offs that matter within half an hour.

Edit content