Allergen Control Management

An allergen-free product is scheduled after a peanut-containing run. The changeover cleaning is done. Or is it?

Allergen cross-contact in food manufacturing is a food safety failure with serious consequences — product recall, consumer harm, regulatory action, and brand damage. The risk arises at production changeovers: when a production line switches from an allergen-containing product to an allergen-free product, the cleaning procedure must be thorough enough to remove allergen residues to a level that will not cause a reaction in a sensitised consumer.

The challenge is that allergen control is a systems problem, not just a cleaning problem. The production schedule must be planned to minimise allergen changeovers — scheduling allergen-containing products before allergen-free products within a production day, not after. The cleaning must be verified, not just performed. The verification result must gate the release of the first batch produced after the changeover. And the entire chain — scheduling, cleaning, verification, release — must be documented for audit and recall purposes.

Live workflow view

The step-by-step sequence

1. 1

   Allergen matrix loaded and schedule checked

   HublerX maintains an allergen matrix — which ingredients and products contain which declared allergens. When the production schedule is generated, HublerX checks for allergen changeovers and flags high-risk transitions — allergen-containing product scheduled before allergen-free product on the same line.

   On schedule generation
2. 2

   Schedule resequenced to minimise allergen changeovers

   Where the schedule contains a high-risk allergen changeover, HublerX suggests an alternative sequence — grouping allergen-containing products together and scheduling allergen-free products after the allergen run, rather than interleaved. The planner reviews and approves the resequencing.

   On schedule generation
3. 3

   Allergen changeover cleaning protocol triggered

   When an unavoidable allergen changeover is confirmed in the schedule, HublerX triggers the correct cleaning protocol — based on the specific allergens being removed and the line being cleaned. The cleaning team receives the protocol, the required chemical concentrations, the contact times, and the verification requirement.

   On changeover start
4. 4

   Cleaning record captured and verified

   The cleaning team records the cleaning completion in HublerX — chemical used, concentration, contact time, surfaces cleaned, and supervisor sign-off. Where the protocol requires an allergen swab test, HublerX triggers the swab request and tracks the result. The cleaning record is stored against the changeover event.

   On cleaning completion
5. 5

   First batch release blocked until allergen clearance

   The first batch produced after a high-risk allergen changeover is automatically placed on hold in the ERP until allergen clearance is confirmed — either the swab result or the QA sign-off on the cleaning record. The batch cannot be released, picked, or dispatched until the hold is lifted by the QA team.

   On first batch completion
6. 6

   Allergen clearance confirmed and batch released

   When the swab result is clear and the QA team confirms allergen clearance, the hold on the first batch is lifted and it is released for picking and dispatch. The allergen control record — schedule sequence, cleaning record, swab result, and QA sign-off — is stored against the batch for audit, traceability, and recall purposes.

   On QA clearance

Results are directional. Allergen control effectiveness depends on cleaning protocol validation, swab test sensitivity, and the completeness of the allergen matrix.