The best manufacturing ERP for mixed-mode manufacturers

SAP's manufacturing lesson for S/4HANA Cloud Public Edition names the production version as the record that states which bill of material is used with which routing or master recipe for a lot-size range and a validity period, and it describes MRP planned orders that are converted to production orders or process orders or loaded onto production lines in repetitive manufacturing. That is why we name SAP S/4HANA Cloud Public Edition the best manufacturing ERP for a mixed-mode manufacturer that gives those documented links and planned-order paths for discrete, process and repetitive work first priority, provided the quote confirms the Public Edition scope items it needs and the project-stock flow. SAP's support note on project stock ties sales delivery from project stock to a named scope item, so ask for that line on the quote.

Microsoft Dynamics 365 Supply Chain Management is the better pick when lean flow is central: its mixed-mode planning documentation sets the supply policy by product, item dimension, site and warehouse, with kanban, production order and batch order among the choices. Production orders and kanbans cannot supply Formula, Co-product, By-product or Planning-item types. IFS Cloud is the better pick when the product is a project deliverable, because a setting on the project item chooses project-specific operations and work in process for its shop order.

What a mixed-mode manufacturer should weigh in an ERP

Logic Unit's ERP selection checklist for manufacturers asks buyers to document whether operations are discrete, process or mixed-mode and to map the combinations of production and order types by site and product, and the ERP Research buyer guide ties the choice of system to the production model. SAP's Public Edition lesson names a leading document for each method: the production order, the process order and the planned order on a repetitive line. Microsoft's production process overview defines the production order, the batch order, the kanban and the project as its order types and says all of them can occur in the end-to-end production of one finished product. IFS documents the manufacturing shop order as its execution record, created from kanban, batch balancing and project deliverables among other sources. The vendors name their execution records differently, so your map tells you which record to ask each one to demonstrate.

SAP's support note for Public Edition says sales delivery from project stock is supported only within scope item 6GD. The IFS Master Agreement makes the signed Order Form the place where the purchased offering, the deployment model and the entitlements are set, and Microsoft documents project production orders in its stock-based Project Operations documentation. Logic Unit's checklist asks the buying team to account for licenses, modules and users. Ask each quote to name the applications, the mode scope and the roles proposed for every production method on your map.

Microsoft's mixed-mode planning page lets the planner choose a supply policy by product, item dimension, site and warehouse, and its multisite planning page makes the site dimension mandatory and keeps the site unchanged while lower-level demand is exploded. SAP's lesson links the bill of material to a routing or master recipe through the production version. IFS keeps product structures and recipe structures as different records for different part types, and its production line documentation says MRP stops exploding demand at a production-line part before the line creates component shop orders or requisitions. Each vendor documents its own mechanism, so ask each one to run your own handoff in the demonstration, with the output of one order consumed by an order of another type.

GS1's Global Traceability Standard distinguishes identification at part level, at batch or lot level and by serial number, and says the relationship between the inputs and outputs of a transformation needs to be recorded. SAP's batch tracing lesson describes a Batch Information Cockpit that traces backward from a finished batch to the vendor and forward to customers. Microsoft's item tracing function works per legal entity, and its trace details show co-products and leave by-products out. IFS documents multi-level tracked structures on shop orders. Use the GS1 wording to set your own test: pick a lot that is made on one order type and consumed on another, and ask each vendor to trace it in both directions.

SAP documents its cloud editions in different objects: Public Edition through Best Practices scope items, and Private Edition through a Feature Scope Description for the 2025 release that places production and process orders, repetitive manufacturing, Kanban and project pegging in its Enterprise Management chapter. Microsoft states a version requirement: lean support in Planning Optimization needs Supply Chain Management 10.0.46 or later with the feature turned on. The IFS documentation is written for release 26R2, and the IFS Master Agreement separates SaaS, software with IFS Cloud Services and on-premise deployment. Confirm that the edition, version or deployment on the quote is the one the demonstration ran on.

SAP, Microsoft Dynamics 365 and IFS on mixed-mode production

SAP S/4HANA Cloud Public Edition: production versions and planned-order paths

The material master in SAP's Public Edition manufacturing lesson holds the MRP type, the lot size and the procurement data, and the production version adds the pairing of a bill of material with a routing or a master recipe. The lesson says planning, meaning demand management and MRP, feeds all the production methods it covers. Planned orders from the MRP run then become production orders or process orders, or they are loaded onto a repetitive line.

SAP's training example in that lesson is a bike company that uses the production order, the process order and repetitive manufacturing in parallel in the same plant. Bikes are assembled on production orders. Paint goes through process orders and wheel assemblies through repetitive manufacturing. Ask SAP to rebuild that example with your own materials and plant in the Public Edition scope it proposes.

Project production is a separate Public Edition scope item, and its purpose topic describes an engineer-to-order flow that links sales order items to project WBS elements, with project production orders supported by project-stock components. SAP's support note lists what sales delivery from project stock takes: the scope item is activated, the material strategy group is set to E2, the WBS element is assigned to the sales order item, and the sales order is created after the material master is updated. Have the quote name that scope item, and ask SAP to run the project-stock flow beside your other orders in the demonstration.

SAP's batch tracing lesson describes a Batch Information Cockpit that traces backward from a finished batch through intermediate batches to raw ingredient batches and the vendor, and forward from a raw batch to process orders, product batches, deliveries and customers. The batch management scope item describes batch derivation, which transfers or displays the data of component batches on produced batches, and the co-product and by-product scope item covers goods receipt for the main product, co-products and by-products on process orders. If a co-product batch or a serial-numbered part crosses into one of your discrete production orders, bring that case to the demonstration and ask for the trace in both directions.

Ahlstrom, a maker of fiber-based specialty materials, rolled out S/4HANA Public Cloud at one of its smaller factories with partner Vincit, SAP's Africa News Center reports. The post says the model can be reused at Ahlstrom's other factories.

Recipe and formula development sits in the Enhanced LoB Functions chapter of SAP's Feature Scope Description for S/4HANA Cloud Private Edition, alongside Manufacturing for Production Engineering and Operations. The document's license note marks features outside Enterprise Management for a separate-license check with the SAP account executive. The project-stock support note is written for Public Edition, so a Private Edition buyer needs the project functions confirmed from the Private Edition document and quote.

Microsoft Dynamics 365 Supply Chain Management: supply policy for each product and site

Supply policy in Supply Chain Management is a choice among kanban, production order, purchase order, batch order and transfer order, and Microsoft's mixed-mode planning page says it is made per product, item dimension, site and warehouse. The choice is set on the default order settings and item coverage pages, and the default order type controls which order master planning generates. Microsoft's examples have production orders sourced from kanbans and a batch order that requires a product supplied by transfers or by kanbans.

Process manufacturing in Supply Chain Management needs a production type of Formula, Co-product, By-product or Planning item, and the same page says kanbans and production orders cannot be used for those types. A batch order's ingredient is a separate decision: Microsoft's formula documentation says pegged supply on a formula line creates a batch order, production order, kanban, transfer order or purchase order for the ingredient, decided by the default order settings and the ingredient's production type.

Planning Optimization considers lean demand and supply such as kanbans through a lean-production feature that has to be turned on in feature management. Master planning treats the site dimension as mandatory and keeps the site the same while it explodes lower-level demand, so run the demonstration with the sites and warehouses your plant uses.

A project is an order type of its own in Microsoft's production process overview, listed beside the production order, the batch order and the kanban. Project production orders are documented in Microsoft's stock-based Project Operations documentation. Ask Microsoft's quote to name the applications and roles it proposes for that project work.

Microsoft's tracked components feature has workers register the batch and serial numbers of consumed components and associate them with the batch and serial numbers of the finished products on production orders. Its item tracing function works per legal entity; co-products appear in the trace details and by-products are not included. A plant that sells or reuses a by-product should bring that lot to the demonstration.

Taylor Farms, a producer of ready-made salads, replaced an on-premises Microsoft system with Supply Chain Management and Finance and moved its planning to a single item master, according to Microsoft's customer story.

IFS Cloud: shop orders that carry project operations and recipe structures

A setting on an IFS project deliverable item controls whether its project-specific operations and work-in-process products are used, or the standard manufacturing versions. A project-linked shop order cannot be released until its project activity is in Released status, and after release its committed cost and hours are posted to the project.

IFS documents the manufacturing shop order as its execution record for work created manually or from requisitions, batch balancing, customer orders, project deliverables and kanban. The same order can produce the main part with secondary outputs.

Recipe structures are the IFS alternative to traditional product structures: ingredients are entered by weight or volume, and the structure is created for an inventory part of type Manufactured Recipe. Product structures are created for parts of type Manufactured. A plant that needs recipes and project deliverables together should ask IFS to run a project item whose shop order consumes a recipe-made part.

MRP in IFS stops exploding demand at a production-line part. The line then creates component shop orders or requisitions, and normal planning continues from there.

IFS can create a tracked structure for a multi-level lot-tracked or serial-tracked parent, and receipt waits until the component assignments are complete. Its lot tracking documentation pairs the lot number with the part number and does not tie it to a site, and the same lot identifier on two different parts does not connect them. Co-products and by-products can have lot reservations, and a site setting decides whether they get dedicated lot numbers or the shop-order lot number.

Rodda's, a cream producer, replaced its legacy ERP with IFS Cloud, and the IFS customer story says staff see live data on the progress of shop orders. The IFS Master Agreement puts the purchased offering, the deployment model and the entitlements in the signed Order Form, so ask to see recipes, project deliverables and kanban named there.

Which manufacturing ERP should a mixed-mode manufacturer choose?

SAP S/4HANA Cloud Public Edition is our pick for the mixed-mode manufacturer whose first priority is a documented link from each bill of material to its routing or master recipe and a documented path from planned order to production order, process order or repetitive line, provided the quote confirms the Public Edition scope items for those methods and the project-stock flow. That buyer's deciding factor is how plant, plan and item behave, and one SAP lesson names the record and the conversion paths for discrete, process and repetitive work.

Microsoft's supply policy by product, site and warehouse and its lean support in Planning Optimization are documented controls too, and for a plant organized around kanbans they come first. We put SAP first for the buyer described above because that buyer starts from the production version and the planned order, and both are named records in SAP's Public Edition lesson.

Dynamics 365 Supply Chain Management is the better pick when lean flow is central and you want the supply policy set product by product, the way Microsoft's examples have kanbans supply a production order or a batch order's ingredient. Check your item list first, because production orders and kanbans cannot supply items of the Formula, Co-product, By-product or Planning-item types.

IFS Cloud is the better pick when what you sell is a project deliverable and the shop floor has to follow the project: the project item decides whether project-specific operations and work in process are used, and the released shop order posts its commitments to the project. Its recipe structures, with ingredients by weight or volume, are a separate capability to add to the same demonstration.

Other manufacturing ERP providers