PLM for process manufacturers: the complete guide

PLM in process manufacturing

Process manufacturers make products through mixing and reactions, other methods include blending and cooking. This means they manage a recipe and its behaviour. That single difference changes what software has to do.

A formula has percentages that must total 100. Raw materials arrive with supplier declarations attached. The attachments also cover allergen statements and contaminant limits. A finished product carries a nutrition table or an ingredient declaration that has to be calculated from the formula.

The market around this has grown steadily. CIMdata put global PLM revenues at $88.3 billion in 2025, a 9.9% rise over 2024, with Germany alone at $5.8 billion in 2024. Most of that spending still flows to engineering-led industries, so process manufacturers buying today are working in a market shaped by someone else's requirements.

That is important when you evaluate tools. A platform designed for machinery will hold your formula as a bill of materials and leave the hard parts to spreadsheets. You need to follow the money. Recalculating declarations after an ingredient change and tracing which finished goods use a withdrawn additive. Regulatory compliance in product design must also stay inside the same system where the product is designed.

What PLM stands for

PLM stands for product lifecycle management, the practice of holding every version of product data in one governed place from the first concept brief through production. It also covers the delisting.

PLM for food manufacturers is the system that holds recipes and their versions together with raw material data collected from ingredient suppliers. It also holds the specifications agreed with retailers and the artwork copy, along with the nutrition and allergen declarations the label depends on. It calculates data wherever possible, so a change to one ingredient reflows into every recipe and every declaration that uses it. It records who approved what, and when, because an auditor will ask.

A product data has states. A formula moves from a bench trial through a pilot batch and into a signed specification. From there, it becomes a commercial product with a shelf life and a retailer listing. Each state has different owners and different rules about who can change what. Without a system, those states live in file names and personal folders, and nobody can say which version went to the factory.

What PLM holds

PLM holds the data that defines the product and the evidence that it is legal to sell. The list below is the working contents of a mature system for beauty care. It also applies to food and beverage.

• Raw material records. Supplier name and technical data, plus allergen and contaminant declarations. The records also cover country of origin and certification status, as well as the expiry dates on each of those documents.
• Formulas and versions. Quantitative recipes with percentages and process steps. They also record yields and losses, plus the trial history that explains why the current version looks the way it does.
• Specifications. Raw material and intermediate specifications, together with specifications for packaging and finished goods. Each includes tolerances and test methods. It also identifies the party who signed it off.
• Calculated outputs. Nutrition values and allergen cross-references derived from the formula. The formula also determines claim eligibility and cost roll-ups.
• Labelling content. Ingredient declarations in every required language and mandatory particulars. The records link each label version to the formula version it describes.
• Projects and stage gates. Briefs and launch dates, with task ownership recorded alongside the decision at each gate.
• Change and approval history. History shows who changed a value and what it was before. It also identifies who approved it and which downstream records were affected.
• Supplier and customer exchange. Requests sent out for ingredient data and specifications sent back to retail customers in the format they demand.

Process versus discrete PLM

PLM is different for process manufacturing. Discrete PLM assumes a countable assembly of parts. Process PLM assumes a continuous mixture whose properties emerge from its composition.

Formula based PLM handles the right-hand column natively. A discrete platform can be configured towards it, and vendors will tell you so, but the configuration lands on the buyer as custom code that has to be maintained through every upgrade.

What a process PLM contains

A process PLM system holds the formula and specification as governed data and calculates compliance outputs from that data. It routes changes through approval and hands finished information to the systems that need it.

PLM versus ERP

PLM decides what the product is. Enterprise resource planning (ERP) executes and accounts for it once that decision is made.

Both systems hold something called a bill of materials. Both hold item masters. Both can store a recipe. The question is which one owns the record while it is still changing. During formulation work a formula changes weekly, sometimes daily, and it needs trial data, rejected versions and approval routing attached to it.

ERP is built for transactions against a released item, so it treats churn as irrelevant. Put formulation work in ERP and you get either a frozen product record nobody trusts or a flood of item numbers created for experiments that never launched.

So the durable arrangement is that PLM owns the product definition up to release and then hands the released recipe and item data to ERP. The released specification also passes to ERP. There it supports planning and purchasing before production. ERP sends back actual costs and batch results. It also returns supplier performance data.

Where this breaks is at the handover. Both systems claim the item master, while nobody writes down which fields flow in which direction. Within two years, the same product carries two different weights. Data migration is the other pressure point, because the legacy data being moved is worse than anyone admitted during selection.

PLM versus PDM

Product data management (PDM) is a subset of PLM. It stores files and controls versions through check-in and check-out. Governance of the surrounding process remains outside its scope.

PDM grew up in engineering companies to serve computer-aided design. In that setting, the deliverable is a file and the main problem is controlling concurrent edits to the same drawing. It answers where the current version lives and who has it open. That can be useful, and for a small team it is sometimes enough.

PDM treats a spreadsheet of a formula as an attachment and its content as opaque. It leaves nutrition recalculation after an ingredient supplier change and identification of products with a withdrawn additive to other tools. Label-release controls when an allergen statement no longer matches the recipe also sit outside it. All of that needs structured data.

For a process manufacturer the practical test is simple. Ask whether the system reads inside your product data or merely files it. If the intelligence lives in formulas embedded in workbooks, you have document management wearing a PLM name badge.

Many process companies arrive at PLM having built a document library first, on a shared drive or a collaboration platform. Treat that library as the starting inventory for migration.

PLM versus PIM

Product information management (PIM) prepares product information for sale. PLM produces the truth that PIM publishes.

A PIM holds marketing copy and images. It also holds digital assets and the attribute sets each retailer or marketplace demands. It syndicates that content outwards to e-commerce listings and retailer portals. Data pools receive it as well. It is a commercial system, owned by sales or digital teams, and its measure of success is complete, accurate listings across channels.

PLM sits upstream. The ingredient declaration and allergen statement originate in formulation. The same governed formula is also the source of net weight and shelf life. It sets the pack dimensions too. All must be approved before anyone sells against them. When PIM becomes the place where those values are typed in by hand, they drift from the specification, and the label on the shelf stops matching the record in the factory.

Regulated and technical attributes flow from PLM into PIM and are read-only there. Commercial content stays in PIM. Packaging specification management is the usual argument, because a pack has both a technical definition and a commercial description, and both teams believe they own it.

PLM consumer goods projects that skip this conversation end up with two systems publishing different numbers for the same product, and no agreed answer about which one an auditor should be shown.

Who uses PLM

PLM earns its keep across the departments that touch a product before it ships. Each group comes to it with a different question.

• Marketing. Marketing teams translate consumer needs and brand positioning into product briefs. They follow formulation progress against those briefs and use approved product information to prepare launch materials. Their gain is a clearer connection between the product they planned and the one going to market.
• Research and formulation. Formulators build and version recipes while they run cost and nutrition scenarios. They reuse approved bases instead of rebuilding them. Their gain is time recovered from recalculation and reformulation work done by hand.
• Regulatory affairs. Regulatory teams check claims and declarations against the live formula. They use the same formula to check market-specific rules. Under Regulation (EU) No 1169/2011, prepacked food must carry a defined list of mandatory particulars that includes the ingredient list and allergens, and those particulars have to survive every reformulation.
• Quality and food safety. Quality owns specifications and test methods. It also owns supplier documentation. When a raw material is withdrawn, they need the affected finished goods list fast.
• Procurement. Buyers need approved alternatives with their compliance impact already assessed, so a supplier swap does not become a labelling incident.
• Packaging and artwork. Packaging teams work from a specification tied to the formula version, which keeps declarations on artwork aligned with what the plant actually makes.
• Commercial and project management. Category and project leads track launch dates and gate decisions against live product data instead of a separate status deck.

Signs of outgrown spreadsheets

Spreadsheets stop working at a predictable point, and the symptoms are consistent enough to use as a checklist. If more than two of these are familiar, the cost of staying put is already being paid somewhere.

• Declarations are retyped. Nutrition and allergen values are copied from a workbook into an artwork brief. They are then copied into a customer form, so a single ingredient change needs three edits and gets two.
• Nobody can answer the impact question fast. Asked which products contain a specific raw material lot, the business runs a manual search across files.
• Label errors reach the market. Analysis of the FDA Enforcement Report Database by Loftware, reported by New Food in 2025, found label errors caused 45.5% of 2024 US food recalls, with 83.85% of those stemming from undeclared allergens. Grocery Manufacturers Association and Food Marketing Institute research puts the average direct cost of a recall at $10 million.
• Document validity, reviews and retention go untracked. Supplier certificates expire without alerts, document reviews have no assigned owner and retention periods are not recorded. In cosmetics, Article 11 of Regulation (EC) 1223/2009 requires the product information file's contents to be updated as necessary and the file to be retained for 10 years after the last batch of the product was placed on the market.
• Version confusion reaches the plant. The factory asks which recipe is current, and the answer depends on who you ask.
• Retailer forms consume formulation time. Skilled formulators spend days filling in customer specification templates.

Choosing PLM that fits the way you develop products

For a process manufacturer, choosing PLM starts with the way formulas, specifications and product information move through the business. The objective is to connect formulation work, approval and release, with clear ownership of the information used by each team.

The evaluation should therefore look beyond feature lists. How is a supplier change assessed? Which formulas, specifications and declarations need review? Who approves the revised product definition, and how does that approved information reach ERP, labelling and commercial systems? These are the scenarios against which the solution should be tested.

C+P Consulting helps CPG and FMCG manufacturers select, implement and adopt PLM solutions suited to formula and specification based product creation. We focus on addressing the data, process and integration decisions during blueprinting, so that implementation follows an agreed understanding of how the business needs to work.

That means bringing product data ownership, approval processes, migration requirements and system responsibilities into the same discussion. The aim is a reliable product definition that remains controlled as formulas, suppliers and requirements change, supported by processes that people can use in their daily work.

Whether you are moving beyond spreadsheets or reviewing an existing PLM environment, speak with C+P about the requirements, data and processes your next step needs to address.

FAQ

More articles