Allergen Tracking for Candy Manufacturers: How Softengine Keeps Lines Safe and Labels Accurate

Candy looks simple on the shelf. Inside your plant, it’s anything but: coated centers, multi-step fillings, rework loops, and seasonal surges push people, equipment, and labeling to the limit. The result being that allergen risk is everywhere. And because undeclared allergens drive a large share of U.S. food recalls, confectioners need controls that work on the floor and stand up to audits. 

Today’s Softengine blog lays out a practical allergen-control playbook for confectionery operations and shows exactly how Softengine, powered by SAP Business One plus Softengine WMS+ and Softengine Web, helps you run it day after day.

The regulatory bar you have to clear

• The “Big 9” allergens in the U.S. now include sesame (as of Jan 1, 2023). Ingredient and allergen declarations must be accurate. 
• 21 CFR Part 117 requires allergen cross-contact controls as part of CGMPs and preventive controls, meaning your programs must be designed, documented, implemented, and verified.
• “May contain”/advisory statements are voluntary and not a substitute for robust controls and correct labeling. 
• Why this matters in candy: undeclared allergens remain a leading cause of U.S. recalls, and the sesame rule change pushed even more recalls tied to label accuracy. 

Why candy lines are uniquely tricky

• Coated, filled, and mixed products share depositors, enrobers, pans, and cooling tunnels raising cross-contact risk at changeover.
• Rework (e.g., off-spec shells or centers) can silently move allergens across SKUs if not tightly controlled by lot and recipe.
• Seasonal spikes compress schedules and increase the odds of label mix-ups and incomplete sanitation sign-offs.
• Contract/third-party packaging adds supplier material risk and more label versions to manage.

How Softengine helps (system capabilities mapped to real shop-floor needs)

Softengine’s approach ties item/recipe master data, warehouse execution, labeling, and quality together so allergen rules are baked into daily work, not parked in a binder.

1) Master data that “knows” your allergens

• Allergen attributes on raw materials, WIP, and finished goods; each recipe automatically inherits the right allergen set.
• Recipe version control with effective-date management, so when a nut-containing inclusion is introduced, downstream labels and work instructions update with it.
• Allergen matrix (SKU × allergen) generated from the master, exposed to planners, QA, and packaging.

2) Production controls that prevent surprises

• Allergen-aware staging: WMS+ blocks the wrong tote or ingredient from staging to a non-allergen run; barcode scans verify item, lot, and location.
• Line clearance & changeover workflows: digital checklists require teardown, cleaning task completion, ATP swab capture (where used), and supervisor sign-off before the next batch can start.
• Rework discipline: rework lots carry their allergen status; WMS+ only allows them into recipes with compatible allergen profiles.

3) Warehouse & inventory execution that enforces the rules

• Guided picking honors allergen segregation zones and location rules (ex. nut-only racks).
• Lot/serial genealogy from receiving → batching → packaging captures every touchpoint for backward/forward trace.
• Exception handling with audit trails: any override prompts role-based approval and a reason code.

4) Labeling that stays in lock-step with reality

• Single source of truth for label content (ingredients, “Contains” statement, and any advisory statement your policy permits).
• Template control by SKU and revision: when a recipe changes, the correct label template is required at print time; WMS+ blocks print of stale templates.
• Scan-to-print at packout: operators scan the batch and SKU; the system prints only the valid label for that combination.

FDA notes that advisory statements like “may contain” are voluntary and not a replacement for solid controls; Softengine keeps the primary label accurate by design and treats advisories as a separate, governed policy never as a crutch. 

5) Quality & sanitation with proof on every batch

• Digital batch records: capture allergen checks, ATP or protein swab results, and photo evidence of line clearance.
• Hold & release: finished lots stay in QA hold until label verification and required tests are marked complete.
• Supplier lots link COAs and allergen declarations right at receiving; non-conforming materials can’t move forward.

6) Recall readiness (that you hope you never need)

• One-click trace from any finished lot back to raw lots, rework lots, equipment, and label revision used.
• Targeted withdrawal lists by ship-to, PO, lot, and date range reducing both risk and disruption if you need to pull product.
• Live dashboards show exposure by channel and region, helping teams act fast during an incident or mock recall.

7) Customer-facing transparency

• Softengine Web surfaces order status, lot/COA availability, and allergen declarations in a portal experience, with data flowing bi-directionally from SAP Business One so sales and customers see the same truth your plant runs on.

A day in the life: milk-to-peanut changeover on a shared enrober

1. Planner schedules a peanut-containing SKU after a milk-only run; the system tags the changeover as high risk and loads the cleaning checklist and swab plan.
2. Warehouse stages only peanut-approved inclusions; scans reject any milk-only ingredient left in the area.
3. Operators complete digital line clearance, upload photos, and record swab results. The next batch can’t start until all steps pass.
4. Packaging scans batch and SKU; WMS+ prints the correct “Contains: Peanuts, Milk, Soy” label (as defined by the recipe and master data).
5. QA releases finished lots after label verification; rework is tagged peanut and made available only to compatible recipes.
6. If a supplier sends a corrected spec that adds soy lecithin, the recipe revision triggers an updated label template and audit trail, no tribal knowledge needed.

What this changes for your KPIs

• Fewer label-related holds and rework: system-governed templates and scan-to-print reduce misprints and mixed-label pallets.
• Faster, cleaner changeovers: guided steps and proof of completion cut guesswork and missed tasks.
• Higher mock-recall precision: lot genealogy trims the scope of withdrawals and shortens response time.
• Audit confidence: documented controls mapped to 21 CFR Part 117 and your food allergen program. 

Labeling policy you can live with

Many confectioners overuse advisory statements to compensate for weak controls. FDA’s guidance makes clear advisories are voluntary and shouldn’t replace CGMPs and preventive controls. A better path is policy by design: use your allergen matrix and risk assessments to decide when an advisory applies, and then let the system enforce it through label-template governance and production rules. That keeps your brand credible and reduces the noise on pack.

The takeaway

Allergen control in candy isn’t about one hero step it’s about dozens of small, reliable moves that add up: the right material at the right station, a clean line at changeover, a label that matches the actual recipe, and a record you can trust. Softengine ties those moves together. You get practical controls operators can follow, data QA can trust, and proof your brand needs when the regulator, or a retailer, asks for it.

FAQs

We run both nut-free and nut-containing SKUs on the same line. Can Softengine reduce cross-contact risk?

Yes. Allergen-aware staging and guided picking keep the wrong materials off the floor; changeover workflows require documented cleaning and verification (including swab capture where used) before release to the next batch.

How does this handle rework?

Rework lots carry the same allergen attributes as the batch they came from. The system only allows rework into compatible recipes, with approvals and audit trails for exceptions.

Can Softengine help with sesame labeling after the FASTER Act?

Yes. Sesame is modeled like any other major allergen. When a formula or supplier changes, the “Contains” statement updates with the recipe revision and drives the correct label at print time.

What evidence do we have during audits?

Digital batch records, sanitation sign-offs, label-template histories, exception logs, and lot genealogy, mapped to 21 CFR Part 117 requirements for CGMPs and preventive controls. 

Are “may contain” statements managed in the system?

They can be, but they’re governed by policy. The system keeps primary labels accurate and only applies advisories when your risk assessment calls for them, never as a workaround. 

How does this reduce recall exposure?

If a supplier update or internal error triggers a risk, you can identify all affected lots, customers, and geographies within minutes, pull targeted lists, and document actions, cutting both risk and disruption.

Softengine is Here to Help!

Partnering with Softengine, a Premier SAP Business One Partner and a Gold Acumatica Partner, for your ERP implementation not only streamlines the data migration process but also ensures a seamless transition to your new ERP platform. Our team’s expertise, dedication, and commitment to customer success make us the ideal partner for organizations seeking to unlock the full potential of their ERP investment and scaling in the digital economy. Contact us to learn more about how our clients utilize ERP to enhance and scale their organizations, and see our solutions in action for yourself!