This release delivers key enhancements across data governance, formulation accuracy, compliance efficiency, and training workflows. Each update is designed to strengthen platform usability, improve data integrity, and support consistent, secure operations across teams. Below is an overview of the enhancements included in this release.
Advanced Product Notice: Updates to TraceGains Standard Titles and Descriptions
As part of the October 2026 release, TraceGains is updating:
- Selected standard document titles
- Three form titles
- All document descriptions
These changes make TraceGains Standards clearer, more globally applicable, and more consistent across Gather and Enterprise. The purpose and type of each affected standard will remain unchanged.
For additional information, please refer to this article: Updates to TraceGains Standard Titles and Descriptions
Enterprise
Clear Ownership Guidance for Health Monitoring Emails
Overview/What’s New?
TraceGains has improved health monitoring email notifications for account send mail errors with clearer guidance, ownership details, and self-service support resources. These updates make each notification easier to understand and help teams identify the right next step when an email-related issue occurs.
Who will use it?
Administrators and teams responsible for monitoring account email delivery will use the enhanced notifications to review alert details, understand ownership, and determine whether self-service action or additional support is needed.
What has changed?
Health monitoring email notifications now provide clearer information about what the alert means, the potential impact, who owns the next step, and where to find helpful resources. The updated format supports faster triage by presenting the most important action-oriented details directly in the notification.
Benefit to users
The improved notifications help reduce confusion, support faster issue resolution, and make it easier to determine the appropriate action without needing to search for next steps elsewhere. Clear ownership and self-service guidance help teams respond more confidently when account email delivery issues are detected. Overall, this enhancement makes health monitoring emails more actionable by pairing issue context with clear ownership and practical guidance for resolution.
Document Intelligence
Granular QA Playbook Control for Certificate of Analysis (COA) Processing
Overview/What’s New?
Document Intelligence now supports QA playbook rules in AI settings when the selected use is COA. This enhancement allows COA document review guidance to be applied from a broader AI settings level, helping teams establish consistent quality expectations for incoming COA documents.
Who will use it?
Supplier compliance, quality, and document review teams will use this capability when configuring QA guidance for COA documents processed through automated document processing.
What has changed?
AI settings configured for COA use can now include QA playbook rules. This gives teams a centralized way to apply rule guidance across COA document intake when a shared review approach is needed.
Benefit to users
QA playbook rules in AI settings help promote consistent COA review standards across applicable documents. Centralized rule configuration supports clearer quality guidance and reduces the need to manage the same expectations separately for each review scenario. Overall, this enhancement gives Document Intelligence a broader way to apply QA playbook rules for COA reviews, helping teams manage consistent quality guidance from AI settings.
Template-Level QA Rule Configuration
Overview/What’s New?
TraceGains AI Document Intelligence (TGDI) now supports QA Playbook rule configuration at the AI template level, giving users more targeted data governance options and granular control at the Item Supplied level for applying quality review guidance to specific templates and supplier, item, or location contexts.
Who will use it?
Quality, supplier compliance, and document review teams will use this capability when configuring QA expectations for COA-related document templates in Document Intelligence.
What has changed?
QA playbook rules can now be configured for individual AI templates. This supports more granular rule assignment for document review scenarios that vary by supplier item, location, or template-specific requirements.
Benefit to users
Template-level rule configuration helps improve review consistency by aligning quality expectations with the right document context. This gives teams more control over how rules are applied and helps reduce manual interpretation when different document templates require different review guidance. Overall, this enhancement makes Document Intelligence more flexible and precise by allowing QA playbook rules to align with the specific review needs of each AI template.
Audit Management
Customizable Audit Report Table Columns
Overview/What’s New?
Audit Management now supports flexible table column visibility controls when publishing audit reports, allowing teams to show or hide table template columns so the final report includes the right details for suppliers, internal stakeholders, or other review audiences while keeping unnecessary or internal-facing information out of shared outputs.
Who will use it?
Audit administrators and teams responsible for creating, configuring, and publishing audit reports will use this enhancement to tailor report tables for different reporting needs.
What has changed?
Table template columns can now be shown or hidden before an audit report is published. Hidden columns are excluded from the published report, while visible columns remain included in the final output.
Benefit to users
Column visibility controls make published audit reports easier to tailor, helping teams present the most relevant information for each report audience. This reduces unnecessary detail in report outputs and supports clearer, more focused audit documentation. Overall, this enhancement gives Audit Management more control over published report content by allowing table columns to be included or hidden based on reporting needs.
Formula Management
Multi-Comment Import for Allergen Details
Overview/What’s New?
Formula Management now supports importing multiple allergen comments into the data sheet allergens section. This enhancement allows allergen detail from more than one source to be carried into the item data sheet when additional context is needed for a product.
Who will use it?
Regulatory, formulation, quality, and specification teams will use this enhancement when reviewing and importing allergen information that includes multiple comments or source details for the same allergen.
What has changed?
The allergen compare import flow now supports selecting and importing more than one comment or detail entry. This makes it possible to bring forward multiple relevant allergen details, such as species or source information, into the item data sheet.
Benefit to users
Multi-comment import helps preserve important allergen context during data sheet updates. This supports more complete allergen documentation, especially when a product may contain allergen information from multiple species, varieties, or source entries. Overall, this enhancement gives Formula Management a clearer way to capture and carry forward multiple allergen details, supporting more complete and accurate data sheet allergen information.
Localized Ingredient Declaration Translation
Overview/What’s New?
Formula Management now supports translated ingredient declarations based on selected region and language. This enhancement helps ingredient statements reflect the market where a product is sold, including localized allergen display and translated declaration text.
Who will use it?
Regulatory, formulation, product developers, and labeling teams will use this capability when creating ingredient declarations for products sold across different regions and languages.
What has changed?
The ingredient declaration section now includes region and language options. The selected region determines which allergens appear and how they are displayed, while the selected language translates the ingredient declaration into the requested language.
Benefit to users
Translated ingredient declarations help support labeling needs for products sold in multiple markets. Region-specific allergen display and language selection make ingredient statements easier to tailor for local requirements and reduce the need for separate manual translation steps. Overall, this enhancement gives Formula Management a more flexible way to create localized ingredient declarations that align ingredient, allergen, region, and language information in one place.
Supplement Label Serving Size Display Control
Overview/What’s New?
Formula Management now supports a cleaner Supplement Facts panel display by letting teams show or hide calculated serving size weight on USA supplement facts labels, while still keeping serving size details available for label-generation logic and layouts that rely on a serving size description, such as a capsule count.
Who will use it?
Formula Management teams, supplement manufacturers, and labeling teams will use this option when creating USA supplement facts labels that need clearer control over serving size display.
What has changed?
Supplement facts labels now include a label option to show or hide the calculated serving size weight. The serving size description remains available for the label, while the calculated weight can be removed from the generated supplement facts panel when it is not needed.
Benefit to users
This option gives supplement labeling teams more flexibility to produce labels that match expected supplement facts formatting. It helps keep serving size information focused on the dosage description when calculated weight is not required on the label. Overall, this enhancement gives Formula Management more control over supplement facts label output by allowing calculated serving size weight to be shown or hidden based on labeling needs.
Region-Based Allergen Display for Ingredient Declarations
Overview/What’s New?
Formula Management now supports region-based allergen display within ingredient declarations. This enhancement helps ingredient statements reflect the allergen display requirements for the market where a product is sold.
Who will use it?
Formula Management teams, product developers, and labeling teams will use this capability when creating ingredient declarations for products sold across different regions.
What has changed?
The ingredient declaration section now includes a region selection that determines which allergens appear and how they are displayed. Supported regional formats can show allergens inline with the ingredient statement or below the declaration, depending on the selected market.
Benefit to users
Region-based allergen display helps labeling teams create ingredient declarations that better align with local market expectations. This supports clearer labeling, reduces manual formatting effort, and helps keep allergen information focused on what is relevant for the selected region. Overall, this enhancement gives Formula Management a more flexible way to present allergen information by aligning ingredient declarations with the selected region.
NutriCalc
Default Regional Formatting for Ingredient Declarations
Overview/What’s New?
Ingredient declarations now apply default formatting based on the selected region. This enhancement helps ingredient statements reflect regional expectations for layout, spelling, capitalization, and allergen display while still supporting adjustments when needed.
Who will use it?
Product developers, labeling teams, and Formula Management users will use this enhancement when creating ingredient declarations for products sold in different regional markets.
What has changed?
Each supported region now has its own default ingredient declaration format. The selected region determines the default layout, regional spelling, capitalization, and allergen presentation used in the declaration.
Benefit to users
Default regional formatting helps reduce manual formatting effort and supports more consistent ingredient declarations across markets. Region-specific defaults make it easier to produce declarations that align with the expectations for the selected market while preserving flexibility for updates. Overall, this enhancement gives ingredient declarations a stronger regional foundation by automatically applying formatting defaults that match the selected market.