Advisory and warning statements are among the most overlooked mandatory requirements in Australian food labelling—and among the most consequential to get wrong. Unlike allergen declarations, which receive sustained industry attention, the advisory and warning statement obligations under FSANZ Standard 1.2.3 operate quietly in the background until a compliance gap surfaces during an audit, a retailer review, or a consumer complaint.
For food manufacturers operating in Australia and New Zealand, the obligation is unambiguous: if your product contains a specified trigger ingredient or belongs to a defined product category, a prescribed statement must appear on the label. The text is not discretionary. Neither is the trigger. Failing to include a required statement exposes the business to regulatory action under the Food Standards Code, potential product recall, and—in the case of warning statements—serious reputational risk given that the underlying hazards involve severe allergic reactions and, in documented cases, fatalities.
This guide covers every trigger food, the exact statutory statement text, the practical distinction between advisory and warning statements, the most common compliance failures, and how digital production management platforms are eliminating manual labelling gaps across Australian food businesses.
What Standard 1.2.3 Actually Requires
FSANZ Standard 1.2.3 governs the labelling of certain foods with information statements, warning statements, and advisory statements. The obligations exist because certain ingredients or product categories create health risks for identifiable consumer groups who may have no way of recognising the risk from the ingredient list alone.
The Standard creates two distinct categories of mandatory statement, each with a different threshold for obligation:
| Statement Type | Trigger | Regulatory Basis |
|---|---|---|
| Advisory statement | Ingredient or product category that may cause health risks in specific consumer groups (e.g. people with phenylketonuria, young children, pregnant women) | Standard 1.2.3, Clause 4 |
| Warning statement | Ingredient or product where people may be unaware of a severe health risk, including anaphylaxis or fatality | Standard 1.2.3, Clause 3 |
The practical distinction matters during product development. Advisory statements are generally targeted at vulnerable sub-populations—infants, people with specific metabolic disorders, pregnant women. Warning statements are reserved for ingredients where the risk profile extends to severe allergic reactions or death in susceptible individuals.
In both cases, the exact wording is prescribed by the Code. Manufacturers do not have the freedom to paraphrase, summarise, or substitute equivalent language. The statutory text must appear verbatim on the label.
The Complete Table of Mandatory Advisory Statements
The following table lists every food or ingredient category that triggers a mandatory advisory statement under Standard 1.2.3 as at the date of publication. Each row shows the trigger condition and the required statement text that must appear on the label.
| Trigger Food or Category | Required Advisory Statement |
|---|---|
| Bee pollen (as food or as an ingredient) | "Contains bee pollen which can cause severe allergic reactions." |
| Cereal-based beverages (≤2.5% m/m fat and <3% m/m protein, or <3% m/m protein only) | "Not suitable as a complete milk replacement for children under the age of five years." |
| Evaporated and dried products made from cereals (≤2.5% m/m fat and <3% m/m protein, or <3% m/m protein only, as reconstituted for direct consumption) | "Not suitable as a complete milk replacement for children under the age of five years." |
| Evaporated milks, dried milks, and equivalent soy or cereal products (≤2.5% m/m fat as reconstituted for direct consumption) | "Not suitable as a complete milk food for children under the age of two years." |
| Foods containing aspartame or aspartame-acesulphame salt | "Contains phenylalanine." |
| Foods containing quinine | "Contains quinine." |
| Foods containing guarana or extracts of guarana | "Contains caffeine." |
| Foods containing added phytosterols, phytostanols, or their esters | Three separate statements required: (1) "When consuming this product, it should be consumed as part of a healthy diet." (2) "This product may not be suitable for children under the age of five years and pregnant or lactating women." (3) "Plant sterols do not provide additional benefits when consumed in excess of three grams per day." |
| Foods containing polyols and polydextrose | "Excess consumption of the food may have a laxative effect." |
| Formulated caffeinated beverages | Two statements required: (1) "Contains caffeine. Not recommended for children, pregnant or lactating women and individuals sensitive to caffeine." (2) A product-specific consumption level statement: "Consume no more than [one-day quantity] per day." |
| Kola beverages containing added caffeine (or food containing such a beverage as an ingredient) | "Contains caffeine." |
| Milk, and beverages made from soy or cereals (≤2.5% m/m fat) | "Not suitable as a complete milk food for children under the age of two years." |
| Propolis (as food or as an ingredient) | "Contains propolis which can cause severe allergic reactions." |
| Unpasteurised egg products | "This product is unpasteurised." |
| Unpasteurised milk and unpasteurised liquid milk products | "This product has not been pasteurised." |
The Mandatory Warning Statement: Royal Jelly
Beyond the advisory statement list, Standard 1.2.3 prescribes one mandatory warning statement that applies to any food containing royal jelly as an ingredient. The required text is:
"This product contains royal jelly which has been reported to cause severe allergic reactions and, in rare cases, fatalities, especially in asthma and allergy sufferers."
This statement exists because of documented incidents in which consumption of royal jelly triggered fatal anaphylaxis in individuals with asthma or pre-existing allergic conditions. The risk is not apparent from the ingredient name alone, and standard allergen labelling frameworks do not capture it. The Code therefore mandates the explicit warning to ensure consumers in the relevant risk group can make an informed decision before consumption.
Manufacturers of honey products, natural health supplements, nutraceuticals, and functional foods that incorporate royal jelly must include this statement in full, verbatim, on every product label in every format in which the product is sold.
5 Compliance Failures That Surface Repeatedly in Audits
Despite the clarity of the obligations, advisory and warning statement gaps appear consistently during internal audits, retailer compliance reviews, and FSANZ-initiated label checks. These five failure patterns account for the majority of non-conformances:
No statement at all. The most common failure is omission. Technical teams focused on allergen declarations, nutrition information panels, and ingredient statements frequently do not cross-check formulations against the advisory statement trigger list. A product containing aspartame that has never included a phenylalanine statement may have been on shelf for years without detection—until it is flagged.
Paraphrased or abbreviated text. Manufacturers sometimes include a statement that conveys the general intent without reproducing the statutory wording verbatim. A label that reads "May contain caffeine from guarana" does not satisfy the Standard 1.2.3 obligation, which requires the text "Contains caffeine." The Code is prescriptive: the statement must match exactly.
Plant sterol products with incomplete multi-part statements. The phytosterol/phytostanol trigger requires three separate statements. Products that include only the diet statement or the child suitability statement—but omit the three-grams-per-day advisory—are non-compliant. All three components are mandatory when the trigger applies.
Formulated caffeinated beverage consumption level statements missing or generic. The consumption level statement for formulated caffeinated beverages must state the actual one-day quantity for that specific product. Generic placeholders are not compliant. This statement must be individualised at the SKU level, not applied from a shared template.
Statement text not updated when formulation changes. A product reformulated to add guarana extract, change its fat-to-protein ratio, or incorporate a plant sterol source triggers new advisory obligations. Where labelling is managed through static artwork files without a linked formulation system, these changes frequently do not cascade to the label. A formula change logged by the product developer never reaches the label artwork brief.
The Relationship with Allergen Declarations Under PEAL
Advisory and warning statements under Standard 1.2.3 operate independently of allergen declarations under the Plain English Allergen Labelling (PEAL) framework introduced via Proposal P1044. The two regimes address different risks, involve different trigger criteria, and require different statement formats.
| Dimension | Allergen Declaration (PEAL / Schedule 9) | Advisory & Warning Statement (Standard 1.2.3) |
|---|---|---|
| Governed by | Standard 1.2.3, Schedule 9 | Standard 1.2.3, Clauses 3–4 |
| Trigger | Presence of a Schedule 9 allergen | Specific ingredient or product category listed in the Standard |
| Format | Bold in ingredient list + co-located "Contains" summary statement | Prescribed text statement, exact wording mandated |
| Editable by manufacturer | No—Schedule 9 terms are fixed | No—statement text is prescribed verbatim |
A product containing both a Schedule 9 allergen and a Standard 1.2.3 trigger ingredient requires both types of declaration. Satisfying one obligation does not satisfy the other.
For example, a formulated caffeinated beverage containing milk and guarana requires: the Milk allergen bold in the ingredient list plus a "Contains milk" summary statement under PEAL, and separate advisory statements under Standard 1.2.3 indicating the product contains caffeine and is not recommended for children, pregnant or lactating women, or individuals sensitive to caffeine. Both are mandatory. Neither substitutes for the other.
Practical Implementation: Connecting Formulations to Label Obligations
For food businesses managing multiple product lines, the core operational challenge is maintaining a reliable, SKU-level mapping between formulation ingredients and triggered advisory obligations. The failure mode is rarely deliberate non-compliance—it is a process gap where no one has systematically checked every formulation against the Standard 1.2.3 trigger list, or where the check was completed once at product launch but not maintained through subsequent reformulations.
A sound implementation approach has three components:
Trigger audit at formulation. Every new recipe and every reformulation should be cross-checked against the full Standard 1.2.3 trigger list as a standard step in the product development workflow. This check should be built into the technical review gate, not deferred to the artwork brief stage.
Per-SKU statement management. Because some statements—particularly the formulated caffeinated beverage consumption level statement—are product-specific, advisory statements must be managed at the individual SKU level rather than applied from a product-category template. A structured field in the product record is the appropriate mechanism; a shared note in a spreadsheet is not.
Change control integration. Any change to an ingredient that could affect Standard 1.2.3 trigger status—adding guarana, adjusting the fat or protein level of a cereal-based beverage, incorporating phytosterols—must automatically flag for a label statement review. This requires the formulation system and the labelling system to be connected.
How Batchbase Manages Advisory and Warning Statements
Batchbase has built Standard 1.2.3 advisory and warning statement management directly into the Labelling tab of every finished good record. Rather than requiring manufacturers to maintain a separate reference document or rely on artwork briefs to catch omissions, the platform provides a structured checklist of every Standard 1.2.3 trigger.
When a trigger applies to a product, the manufacturer selects it from the checklist. The platform immediately displays the exact prescribed statutory text for that trigger—pre-populated and ready to review. For cases where a product requires a variation from the default text (for example, specifying an exact consumption quantity for a formulated caffeinated beverage), the statement text is editable at the SKU level with a single-click reset to the FSANZ default at any time.
All selected statements are stored against the finished good record and flow automatically into the Label Preview, appearing in the advisory and warning section of the back-of-pack layout alongside allergen declarations, storage conditions, and manufacturer details. When a recipe is updated, the statement checklist remains linked to the product, prompting a review at the next save.
This approach eliminates the two most common failure modes: omission through oversight, and statement drift through reformulation without label review.
Conclusion
Advisory and warning statements under FSANZ Standard 1.2.3 are non-negotiable mandatory requirements for any food product that meets the specified trigger criteria. The obligations cover fifteen advisory statement triggers and one mandatory warning statement, each with exact prescribed wording that cannot be paraphrased or adapted.
For Australian food manufacturers, the practical priority is establishing a systematic process that connects formulation data to labelling obligations—and that keeps those obligations current through every recipe change. Manual spreadsheet approaches are structurally unable to maintain that connection reliably at scale.
Food businesses that want to eliminate advisory statement gaps and ensure every label is audit-ready can book a live demo of Batchbase to see how the platform manages Standard 1.2.3 compliance alongside allergen declarations, nutrition information panels, and country of origin statements in a single connected workflow.