A process manufacturing ERP runs production from formulas instead of bills of materials, and its core requirements come down to three things: managing your recipes properly, tracking every batch from ingredient lot to finished goods, and keeping the records auditors and regulators ask for without anyone rebuilding them by hand.
Most processors start looking because something has changed. An old system is going out of support, the FSMA 204 traceability deadline is getting closer, a new plant or acquisition needs integrating, or an audit turned up gaps. The everyday problems tend to be the same everywhere: formulas kept in spreadsheets, yields nobody measures, lot traces done from paper batch sheets, and batch costs that only become clear weeks after the product has shipped.
This guide is for food, beverage, chemical, pharmaceutical and agricultural processors. It covers the process manufacturing ERP requirements that matter most, where general-purpose systems fall short, and how to set up the project so you can show it paid off.
Why can’t a standard ERP handle process manufacturing?
A standard ERP is built around bills of materials and countable parts, and process manufacturing doesn’t work that way. You mix, blend, cook, react or ferment ingredients into something that can’t be taken apart again. Output is measured by weight or volume, ingredients vary from one lot to the next, and a single run can produce more than one product. Here’s where the difference shows up day to day.
| Situation | What a BOM-based system does | What process manufacturing needs |
|---|---|---|
| An ingredient arrives at 92% strength instead of 95% | Uses the standard quantity | Adjusts the quantity to hit the target potency |
| One batch yields a main product plus a sellable side stream | Records one output | Records co-products and by-products and splits the cost |
| Product is sold by the case but invoiced by actual weight | Tracks one unit of measure | Tracks both units (catch weight) |
| A batch yields 96% of the expected quantity | Treats the shortfall as an inventory error | Records yield loss and reports the variance |
| Ingredients and finished goods expire | Ignores dates | Tracks shelf life and picks first-expired, first-out |
| Demand calls for 750 liters from a 500-liter recipe | Multiplies quantities | Scales the formula within vessel sizes and rounding rules |
If you’re weighing both sides, our look at how Business Central handles discrete manufacturing covers the other half of the comparison.
Recipes and formulas
Everything else depends on the formula. If recipes aren’t controlled, scaled and costed properly, every batch record, inventory count and compliance report built on top of them carries the same mistakes. Four areas deserve a close look.
Formula versions and approvals
Every formula should live in the ERP as a controlled record, with versions, effective dates and a sign-off before anyone can use it. Planning and the plant floor should only ever see the approved, current version.
Formulas change all the time. A supplier changes, a cheaper ingredient gets approved, or a customer asks for a reformulation. Each change should go through a request and approval step, and old versions should stay on file so you can show which recipe made any batch, even years later. If your recipes currently live in spreadsheets and get retyped into the ERP, that’s the first thing to fix.
Scaling, yield and potency
You should be able to scale a formula to the batch size you need, plan for realistic yield, and adjust ingredient quantities based on the measured strength of the lots you’re actually using.
Scaling has real-world limits: vessel sizes, minimum batch quantities and rounding rules. Yield matters because every process loses something, so planning for 100% means coming up short. Potency matters in pharmaceuticals, nutraceuticals, chemicals and some foods, where the active ingredient varies by lot and the formula has to compensate. None of this should depend on an operator with a calculator at the start of each batch.
Co-products, by-products and cost allocation
A batch often makes more than one thing. The ERP should record every output, not just the main product, and split the cost across them in a way your finance team can stand behind.
Cheese making also produces whey. Milling produces flour and bran. A chemical reaction might give you a secondary product you can sell and a waste stream you pay to dispose of. Co-products have value and should carry part of the batch cost, while by-products may be sold, reused or scrapped. If all the cost lands on the main product, its cost is overstated and your margins on everything else are guesswork.
Units of measure and catch weight
Many process products are stored, sold and priced in different units. Catch weight items, where each unit’s actual weight varies, are the most common example.
Meat, cheese, produce and a lot of bulk goods are counted in cases or pieces but invoiced by what they actually weigh. Chemicals might be bought by the drum, used by the kilogram and sold by the liter. The ERP needs to carry both quantities on every transaction, from receiving to invoicing, so inventory values and customer bills both come out right. Writing weights on paper at the dock and correcting invoices afterward stops working once volumes grow.
Running batches
With formulas under control, the next job is turning them into batches the plant can actually run, tracking every lot that goes in and comes out, and knowing what each run cost. These are the areas where spreadsheets tend to creep back in.
Scheduling around cleanups and changeovers
Batches should be sized to your equipment and scheduled in an order that keeps cleaning and changeovers to a minimum. In a process plant, the sequence often matters as much as the quantity.
Running an allergen-free product after one with peanuts, or a light color after a dark one, means a full clean-down. Good scheduling groups compatible batches, respects vessel and line capacity, and shows what’s in progress across multi-stage work like mixing, filling and packing. In a lot of plants the schedule still lives on a whiteboard because the ERP can’t handle those rules.
Lots, shelf life and quality holds
Every ingredient and finished lot should carry its expiry date, quality status and measured attributes, and inventory should be picked first-expired, first-out (FEFO).
Batch attributes record what a lot actually is: moisture, fat content, pH, viscosity or active-ingredient strength. They let you match lots to customer specs and feed the potency adjustments in your formulas. Lots on hold or past their date should be blocked automatically, so planners and pickers can’t use them by mistake.
Knowing what each batch really cost
Each batch should be costed from the actual ingredient lots, labor, machine time and overhead that went into it, with yield and cost variances reported against the standard.
Ingredient prices move, especially for commodities, and yields shift with raw material quality. Standard costing tells you where production drifted from the plan, and actual batch costing tells you what each run really cost. Most processors need both, plus co-product allocation, so finance and operations work from the same numbers instead of rebuilding costs in a spreadsheet at month-end.
Compliance: FSMA 204, Part 11 and GMP
Compliance in process manufacturing mostly comes down to recording the right facts as work happens: which lots went into which batch, who approved what, what the tests showed, and where the product went. When the ERP captures that along the way, an audit or a recall means running a report instead of digging through paper. Here’s how the main regulations translate into what your system needs to do.
| Regulation | Applies to | What your ERP must support |
|---|---|---|
| FSMA 204 Food Traceability Rule | Companies that manufacture, process, pack or hold foods on the FDA’s Food Traceability List | Traceability lot codes, key data elements at each critical tracking event, and records the FDA can receive within 24 hours |
| 21 CFR Part 11 | FDA-regulated companies keeping required records electronically | Secure audit trails, electronic signatures, access controls and a validated system |
| Current Good Manufacturing Practice (21 CFR 117 for human food, 111 for dietary supplements, 211 for drugs) | Food, supplement and pharmaceutical manufacturers | Controlled formulas, complete batch records, quality release before shipment |
| OSHA Hazard Communication (aligned with GHS) | Chemical manufacturers and distributors | Safety data sheets and hazard labeling tied to each product |
Tracing lots in both directions
You should be able to trace any finished lot back to every ingredient lot and supplier, and forward to every customer who received it, in minutes. That two-way trace is at the heart of FSMA 204 and of any recall.
A mock recall is the quickest way to check. Pick one ingredient lot and time how long it takes to list every affected batch, shipment and customer. If someone has to pull paper batch sheets, or the trace only works backward from finished goods, the traceability isn’t really in the system.
FSMA 204 traceability
If you handle foods on the FDA’s Food Traceability List, you need traceability lot codes and specific data recorded at each step, such as receiving, transformation and shipping, and you must be able to hand those records to the FDA within 24 hours. The original compliance date was January 20, 2026. The FDA proposed moving it to July 20, 2028, and Congress has since told the agency not to enforce the rule before then.
Many food companies are using the extra time to get their systems ready, and for good reason. Large retailers are already asking suppliers for this data, and capturing it reliably depends on receiving, production and shipping all running in the same system.
Part 11, electronic signatures and quality control
If you’re FDA-regulated and keep required records electronically, 21 CFR Part 11 expects secure audit trails, controlled access, and electronic signatures that carry the same weight as handwritten ones. Look for signature prompts on formula approvals, quality results and batch release, and a full history of who changed what and when.
No software is “Part 11 certified.” The system supplies the controls, but you still validate it and follow your own procedures. Ask any vendor or partner how they support validation and who writes the documentation.
Quality control should run in the same system too: inspection plans at receiving and during production, certificates of analysis, nonconformance and corrective action (CAPA) records, and automatic holds on lots that fail. When test results sit in a separate spreadsheet, releasing a lot means updating two places, and sooner or later the two disagree.
Key deadlines for process manufacturers
These are the dates that most often start a process manufacturing ERP project:
| Deadline | Key date |
|---|---|
| FSMA 204 Food Traceability Rule | FDA will not enforce before July 20, 2028 (FDA) |
| Microsoft Dynamics AX 2012 R3 | Extended support ended January 10, 2023 (Microsoft) |
| Microsoft Dynamics NAV 2018 | Extended support ends January 11, 2028 (Microsoft) |
| SAP ECC 6.0 | Mainstream maintenance ends December 31, 2027; paid extended maintenance runs to December 31, 2030 for enhancement packages 6-8 (SAPinsider) |
| Microsoft Dynamics GP | Product and regulatory updates end December 31, 2029; security patches end April 30, 2031 (Microsoft) |
Other deadlines come from inside the business: an acquired plant to integrate, a new line or site, or a customer audit that exposed traceability gaps.
If you’re facing a fixed date, start early rather than squeezing the evaluation. Most of the schedule risk sits in cleaning up formulas, lot data and quality specs, and in moving years of recipe history, and none of that goes faster under pressure.
Numbers to track before and after go-live
A new ERP should improve numbers your leadership team already watches. Pick two or three, write down where they stand today, and make them the measure of success.
| Measure | What a well-run ERP changes | How to baseline it today |
|---|---|---|
| Batch yield variance | Actual yield is recorded for every batch and compared with the formula | Average gap between expected and actual yield |
| Time to complete a mock recall | Forward and backward traces run from the system | Hours to list every lot, shipment and customer affected by one ingredient lot |
| Expired and written-off inventory | FEFO picking and expiry alerts keep old stock moving | Write-off value as a share of inventory |
| Inventory accuracy | Every movement is recorded by lot as it happens | Compare a cycle count against system quantities |
| Days to close the month | Batch costs post as production is reported | Days from period end to final statements |
| Batch release time | Quality results and approvals sit on the lot record | Hours from batch completion to release |
Put the baseline and target for each one in the statement of work for the first phase. That keeps everyone focused on results and gives your CFO a straightforward way to judge the project.
Things to question in a proposal
Some of the most useful signals come from how a vendor or partner plans the project:
-
- Formulas stay in spreadsheets “for phase two.” If recipes aren’t controlled in the ERP, neither is anything downstream of them.
-
- Compliance is “a report we’ll build later.” Traceability depends on capturing the right data at receiving, production and shipping from day one.
-
- Their references are in a different process industry. Food, chemicals and pharmaceuticals have different rules. Ask for references in yours.
-
- Validation isn’t in the plan. Regulated manufacturers need validation documentation and testing. Leaving it out makes the quote look smaller than the project.
-
- The quote leaves out modules you’ll need. Quality, formula management extensions, warehouse and lab integrations are common add-ons.
-
- Nobody can say who supports you after go-live. Ask for the support model, the named team and the service levels in writing.
How to compare vendors
-
- Define your products, regulations and baseline numbers. List the product families that drive revenue, the regulations you answer to, and the measures from the table above that reflect your biggest problems.
-
- Test each system on your own work. Give each vendor one real formula, one real ingredient lot and one real customer order. Have them produce the batch, cost it, release it through quality, ship it, and then run a forward and backward trace.
-
- Score every vendor on the same weighted scorecard. Weight the criteria by what your operation depends on, and score each vendor as soon as you’ve seen it handle your data.
-
- Check references in your industry and size band. Speak with two or three processors who make products like yours, ideally ones who went live in the last two years, and ask what happened after go-live.
-
- Ask for a fixed-scope first phase. It should name the delivery team, the milestones and the target numbers it will move.
-
- Price three years, not one. Include licenses, implementation, extensions, integrations, validation, environments and storage, training and post-go-live support.
Example scoring for a food manufacturer
Here’s how a mid-sized food manufacturer might weight its process manufacturing ERP requirements. A pharmaceutical or supplement maker would put more weight on electronic signatures and validation, and a chemical producer on potency, units of measure and hazard documentation.
| Criterion | Weight |
|---|---|
| Formula control, scaling and yield | 20% |
| Lot control, shelf life and traceability | 20% |
| Quality control and compliance records | 15% |
| Batch planning and scheduling | 15% |
| Batch costing and co-products | 10% |
| Integrations (scales, labeling, EDI, lab) | 10% |
| Partner experience and support | 10% |
Keep the budget honest, too. In Panorama Consulting’s 2026 ERP Report, more than a quarter of organizations went over budget, often because technical requirements surfaced late. Testing each system on your own formulas and lots is the cheapest way to find them early.
Do you need a LIMS or MES as well as an ERP?
Some operations do. A process manufacturing ERP should run formulas, batches, inventory, quality and finance, but a specialist system is worth adding in these situations:
-
- Laboratory information management system (LIMS) when you run high volumes of lab tests, stability studies or complex sampling plans.
-
- Manufacturing execution system (MES) or electronic batch records when operators need step-by-step instructions, weigh-and-dispense control or equipment-level data capture.
-
- Process historian when you need continuous sensor data from reactors, ovens or fermenters.
-
- Label management when you print regulated labels in many formats and languages.
If any of these apply, ask how the ERP will exchange data with the specialist tool before you choose. That integration is usually where the cost adds up.
Is Copilot worth it for process manufacturers?
It can be, as long as you judge it like any other feature: ask to see it working on a process you’d already pay to improve, and measure it against a number you already track. In process manufacturing, useful examples include forecasting demand for short-shelf-life products, spotting batches whose yields are drifting, and following up with suppliers on late or out-of-spec deliveries.
The results depend on the data underneath. If formulas, lots and quality results aren’t in one system yet, that’s the place to start.
Business Central or Supply Chain Management?
For regulated, multi-plant or potency-driven operations, Supply Chain Management is usually the better fit. Business Central with a process extension suits single-plant processors with simple recipes and lighter regulation. Here’s what each one brings.
Dynamics 365 Supply Chain Management has process manufacturing built in. Formulas and formula versions must be approved before use and can include co-products, by-products and catch weight items. It also supports batch attributes, potency-based batch balancing and formula change management. Its advanced quality management features, including electronic signatures, are designed to help manufacturers meet FDA requirements such as 21 CFR Part 11 and cGMP. It can run discrete and process production side by side for mixed-mode plants, too. Folio3 implements it as a process manufacturing ERP for food, chemical, pharmaceutical and nutraceutical plants.
Dynamics 365 Business Central is built around discrete manufacturing. Process capabilities such as formula management come from ISV extensions on top of its core, which works well for many small and mid-sized food and beverage producers with lighter regulatory requirements. Our guide to Business Central shop floor data collection covers where that approach reaches its limits.
How to tell which one you need
Mistakes happen in both directions. Some companies stretch Business Central with heavy customization to act like a regulated process system, while others buy Supply Chain Management for a single plant with simple recipes. These signals usually point the right way:
| Signal | Usually points to |
|---|---|
| One plant, simple recipes, light regulation | Business Central with a process extension |
| Potency-adjusted formulas, co-products or catch weight at volume | Supply Chain Management |
| 21 CFR Part 11 electronic signatures across quality and release | Supply Chain Management |
| Several plants, entities or countries | Supply Chain Management |
| Discrete and process production in the same operation | Supply Chain Management |
| Replacing Dynamics GP or NAV in a small food business | Business Central with a process extension, in most cases |
| Replacing Dynamics AX 2012 or SAP ECC | Often Supply Chain Management, depending on size and complexity |
Where to start
Of all the process manufacturing ERP requirements in this guide, three matter most day to day: controlling every formula, knowing what each batch produced and cost, and showing auditors or regulators the records when they ask. Work out which of those causes you the most trouble today, weight your evaluation around it, and ask every vendor to prove it on your own formulas and lots. Choosing a partner who already knows your industry’s rules matters as much as the software.
Folio3 Dynamics has spent more than 20 years implementing Microsoft Dynamics for food, agriculture, chemical, pharmaceutical and mixed-mode manufacturers. A good first step is our ERP Complexity & Value Assessment. We map your formulas, production model and current systems, recommend Business Central or Supply Chain Management, score your data readiness, list the integrations involved, and lay out a phased roadmap with the numbers each phase should move. Request an assessment or explore our process manufacturing practice.
Frequently asked questions
Short answers to the questions process manufacturers ask most often when evaluating an ERP.
The basics
A process manufacturing ERP runs production from formulas and recipes instead of bills of materials. It handles batch orders, variable yields, co-products, potency, catch weight, shelf life and lot traceability, and links them to quality control and financials in one system.
The core requirements are formula management with versions and approvals, batch scaling with yield and potency adjustments, and handling for co-products, by-products and catch weight. Add lot control with shelf life and FEFO picking, batch costing, and the traceability, quality and electronic records that regulations such as FSMA 204 and 21 CFR Part 11 expect.
Batch manufacturing is one type of process manufacturing, where product is made in finite lots from a recipe. Process manufacturing also covers continuous production, such as refining, extrusion or bottling lines that run without stopping. Batch and process manufacturers need almost the same ERP capabilities, so the same shortlist usually applies.
A bill of materials lists countable parts that are assembled and can usually be taken apart again. A formula lists ingredients in quantities or percentages that are transformed into something new, often with expected yield, scaling rules, potency adjustments and more than one output.
Catch weight describes products counted in one unit, such as cases or pieces, but priced or invoiced by actual weight, which varies from unit to unit. Meat, cheese, seafood and produce are common examples. The ERP must track both quantities on every transaction.
Compliance and choosing a system
If you handle foods on the FDA’s Food Traceability List, you need traceability lot codes and specific data recorded at critical tracking events such as receiving, transformation and shipping, and the ability to give the FDA those records within 24 hours. The FDA will not enforce the rule before July 20, 2028.
No software is compliant on its own. An ERP can provide the controls Part 11 expects, including audit trails, access controls and electronic signatures, but you still need to validate the system and follow documented procedures.
Business Central with a process extension suits single-plant processors with simple recipes and lighter regulation. Supply Chain Management suits potency-adjusted formulas, co-products and catch weight at volume, 21 CFR Part 11 requirements, multiple plants or entities, and mixed discrete and process operations.
Plan for longer than a comparable discrete project. Formulas, lot data and quality specifications all need cleaning, and regulated manufacturers must add system validation. A fixed-scope first phase covering formulas, batches, inventory and financials shortens time to value.
