The short answer
A full allergen clean is expensive and sometimes unavoidable. The aim is not to skip it but to schedule it only where the allergen matrix says it is needed, and to order the runs so the number of those moments is as small as the orders allow.
What a clean costs
A full allergen clean takes the line out of production. It uses labour, water and chemicals, it needs a verification before the next run, and it eats into the available hours that the line's efficiency is measured on. A plant that runs five products a day and cleans between every pair loses a visible share of the shift.
The opposite mistake is worse. Skipping a clean that was needed puts an undeclared allergen in the next product. So planners need a rule, not a feeling, for when a clean is required and when a quick wipe-down will do.
A simple rule, and a simple example
Illustrative and deliberately simplified; it is not a recommended allergen policy. Your matrix, your line and your QA team decide the real rules.
The rule used here: a full clean is needed whenever the next product does not contain an allergen the last one did. Going the other way, from fewer allergens to more, needs no allergen clean, because the next product declares what it adds.
Four products: P contains none, M contains milk, N contains nuts and MN contains both.
| Run order | Transitions that need a full clean | Cleans |
|---|---|---|
| MN, M, N, P | MN to M (nuts leave), M to N (milk leaves), N to P (nuts leave) | 3 |
| P, M, MN, N | MN to N (milk leaves) | 1 |
The same four runs, the same line, the same day. The first order cleans three times; the second cleans once. Starting from a product with nothing and building up before stepping down is the pattern. Real lines have complications: wet and dry allergens, the label wording for traces, products that cannot run together at all. But the principle holds: order matters, and a matrix lets you count.
The allergen matrix as a planning input
A matrix lists each product against each allergen. On its own it is a quality document. Used in planning it becomes a table that answers, for any pair of consecutive products, whether the transition needs a clean.
In ManufacturingFlow 365 the allergen matrix is part of quality, and allergens and nutrition roll up through the formula. That matters because a product's allergens are not a separate list someone maintains by hand. If a formula swaps an ingredient, the allergens come from the ingredients that are now in it. A matrix that follows the formula stays correct when the formula changes.
Campaigns and their cost
Putting runs in allergen order often means bundling similar products together in a campaign. That has a price: stock of some products gets built ahead of demand, and a short-shelf-life item may not tolerate waiting. Planning in ManufacturingFlow 365 includes campaigns alongside changeover and allergen rules, so the trade-off is visible rather than argued over in the planning meeting.
The point is not to find an order that cleans least at any cost. It is to know the cost of each choice: clean count against inventory held against orders late. When the numbers are on the table, the arguments get shorter.
A clean is not clean until it is checked
A scheduled clean is a plan. A verified clean is a fact. Planning in ManufacturingFlow 365 includes cleaning verification, so the next run can wait on a recorded check rather than on someone's word that the line is ready.
The cost of that check shows up in OEE, which is also in the planning area. A changeover is lost availability, and the longer the verification, the lower the figure. Seeing the number is the first step to deciding whether a particular sequence is worth it, and whether a longer campaign that saves two cleans is worth the stock it ties up. On the shop floor, a changeover recorded under its own downtime reason, as a short list people will use allows, stops it hiding inside general stoppages.
In Business Central
- Planning with changeover and allergen rules, campaigns, cleaning verification and OEE.
- An allergen matrix in quality.
- Allergens and nutrition that roll up through the formula.
- With MESFlow 365, downtime reasons, so a changeover is recorded as one rather than hidden in the shift.
- Lot genealogy and an electronic batch record with an audit trail, which support traceability.
- A planning scenario in the demo data.
Limits
We do not claim compliance with FSMA, BRC or any other scheme; the apps support traceability and audit trails. The allergen changeover rules and cleaning verification sit in the planning area, and some planning pages have not been run, so ask to see the exact pages you would use. We do not claim that the app orders your runs for you automatically; confirm in the demo how far sequencing support goes. ManufacturingFlow 365 is designed from 63 identified gaps, of which 27 are implemented and 36 partly. Electronic batch record and change approval have not been tested with a second user. The apps have been run in a UAT sandbox with demo data and no live customer is recorded.
See it on your process
Send us your product list and the allergens on it. We will load the rules and look at the transitions together: book the allergen changeover planning scenario.
Keep reading: downtime reasons people will use and a mock recall in 15 minutes.