Australia New Zealand Food Standards Code – Schedule 10 – Generic names of ingredients and conditions for their use

The Schedule’s core conceptual move is to standardise permitted generic ingredient names for use in statements of ingredients, and to attach conditions to some of those names. The Schedule operates by cross-reference: it applies “for section 1.2.4,4” of the Code, so its normative effect depends on the operation of Standard 1.2.4. The main concepts are the list of generic names, the conditions for use, and the transitional/application provisions that manage change (S10,2; S10,1 and application table).

List of permitted generic names. The Schedule provides a short, enumerated list of generic names, including cereals; cheese; cocoa butter; crystallised fruit; fats or oils; fish; fruit; gum base; herbs; meat; milk protein; milk solids; poultry meat; spices; starch; sugar; vegetables; and others (S10,2 table). Each name is a permitted labelling shorthand for ingredient statements under the relevant subsection of Standard 1.2.4.

Conditions for use. Several generic names carry conditions that change what the generic term may stand for. Examples drawn directly from the Schedule include:

• Fats or oils: the statement of ingredients must declare whether the source is animal or vegetable; and where the food is a dairy product, including ice cream, the specific source of animal fats or oils must be declared. The generic name cannot be used for diacylglycerol oil (S10,2, fats or oils).
• Milk solids: may be used to describe milk powder, skim milk powder or dried milk products, or any two or more of a defined list including whey, whey powder, whey proteins, lactose, caseinates, milk proteins and milk fat (S10,2, milk solids).
• Starch: the name ‘starch’ may be used for any unmodified starch or any starch modified by physical means or by enzymes (S10,2, starch).
• Sugar: the name ‘sugar’ may be used to describe a specific set of sugar forms (white sugar; white refined sugar; caster sugar; loaf or cube sugar; icing sugar; coffee sugar; coffee crystals; raw sugar) and the Schedule expressly provides that the name ‘sugars’ must not be used in a statement of ingredients (S10,2, sugar).
• Fish: the Schedule states that “The definition of fish in subsection 1.1.2,3(2) does not apply for the purposes of this table,” which means the Code’s general fish definition is excluded within this Schedule for table interpretation (S10,2, fish).

Transitional and amendment architecture. The Schedule contains an “Application, saving and transitional provisions” section and the Amendment History records multiple variations with associated transitional arrangements (application table; Amendment History). Notable examples recorded in the document are the Food Standards (Proposal P1026 , Lupin as an Allergen) Variation and the Food Standards (Proposal P1044 , Plain English Allergen Labelling) Variation. These entries specify transition and post-transition periods (for example, the P1044 transition period is 25 February 2021 to 25 February 2024, with a post-transition period from 26 February 2024 to 26 February 2026 for certain packaged products) and set out that during transition a food may comply with either the pre-variation Code or the amended Code but not a combination (application table entries; see clauses summarised under P1044 in the table).

Relationship to other Code provisions. The Schedule explicitly interacts with other provisions in the Code: it furnishes generic names for subparagraph 1.2.4,4(b)(iii) and excludes application of the definition of ‘fish’ in subsection 1.1.2,3(2) for the table (S10,2). It also refers to general Code provisions like section 1.1.1,3 and section 1.1.1,9 in the context of commencement and application in the transitional material (application table and Amendment History).

In short, the Schedule is a narrow, technical instrument that standardises labelling vocabulary and embeds a framework to manage change via transition provisions. Its functional effect is to constrain the shorthand language that can be used on ingredient statements and to require particular disclosures where the Schedule’s conditions apply.

Primary actors who must take account of this Schedule are food businesses that produce, import, package, label or sell foods subject to the Australia New Zealand Food Standards Code and the State/Territory or New Zealand instruments that adopt or incorporate the Code. That includes manufacturers and brand owners responsible for labelling, contract packers and private-label merchants, importers who supply packaged foods for Australian or New Zealand markets, retailers and wholesalers who place products on shelf, and compliance officers within state, territory and New Zealand food regulation agencies. The Schedule identifies its legal status as a standard under the Food Standards Australia New Zealand Act 1991 (Cth) and notes the Code’s provisions apply in New Zealand through the Food Act 2014 (NZ), so businesses operating across the two jurisdictions must account for both adoption mechanisms (Note 1; Note 2; S10,1).

Label designers, packaging houses and legal/compliance advisers are directly affected because the Schedule prescribes allowed generic vocabulary and conditions , examples include the obligations around declaring the source of fats or oils, the permitted use of ‘starch’ where modified by physical means or enzymes only, and the prohibition on using the plural ‘sugars’ in a statement of ingredients (S10,2). These are labelling design constraints that impose specific text choices.

Supply chain actors who supply ingredient specifications to manufacturers must also be involved. The Schedule’s conditions require accurate upstream information; for example, declaring whether a fat or oil is animal or vegetable, and for dairy products the specific animal source. This places information-gathering duties upstream on suppliers and processors to enable accurate final labels (S10,2, fats or oils).

Regulators and enforcement agencies are affected in the sense that they will interpret compliance against the Code to which the Schedule belongs. The Schedule itself does not set enforcement mechanisms or penalties. The document notes that the Code is a standard under the FSANZ Act and that Code provisions apply in NZ under the Food Act 2014; the mechanics of enforcement lie outside the Schedule (Note 1; Note 2). State and territory jurisdictions in Australia generally give force to the Code through their food legislation and enforcement frameworks, which is the practical pathway by which local regulators will act.

Businesses with existing stock during amendment transitions are affected by the Schedule’s transitional provisions and the Amendment History. For example, the P1026 variation established a transition period (25 May 2017 to 26 May 2018) and allowed a food to comply with either the pre-variation Code or the amended Code during that period, but not a mixture (application table summarising P1026). The P1044 (Plain English Allergen Labelling) variation established a transition period from 25 February 2021 to 25 February 2024 and a post-transition period to 26 February 2026 for packaged products labelled before the end of the transition (application table summarising P1044). Those transitional arrangements affect manufacturers, distributors and retailers who hold or move stock across those dates.

Finally, consumers , particularly those with allergies or dietary preferences , are an indirectly affected group. The Schedule’s conditions on certain generic names (for example, declaring animal or vegetable source of fats or oils, and the P1026 insertion concerning lupin as an allergen via amendments) are aimed at improving the traceability of potential allergens in ingredient statements, though the Schedule itself frames these as labelling standard elements rather than consumer entitlements (S10,2; Amendment History entries referencing lupin and plain-English allergen labelling).

Duties set by the Schedule flow from its operation as the source of permitted generic names and attached conditions for use in ingredient statements under Standard 1.2.4. The text sets out discrete duties and implicitly creates limited rights to use permitted terms when the conditions are met.

Duties (direct, express):

• Use of permitted generic names: When compiling a statement of ingredients under section 1.2.4,4, manufacturers and packers may use only the generic names listed in the Schedule for the relevant purposes in that subsection (S10,2). The Schedule lists the specific generic names available.
• Compliance with conditions attached to a generic name: Where a generic name carries a condition in the table, the label duty is to comply with that condition. For example:
  • Fats or oils: declare whether the source is animal or vegetable; if the food is a dairy product including ice cream, declare the specific animal source; do not use the generic label ‘fats or oils’ for diacylglycerol oil (S10,2).
  • Milk solids: ‘milk solids’ may be used only to describe milk powder, skim milk powder or dried milk products, or any two or more of the enumerated components (whey, whey powder, whey proteins, lactose, caseinates, milk proteins, milk fat) (S10,2).
  • Starch: ‘starch’ applies to unmodified starch or starch modified by physical means or enzymes; other modifications would not be covered by this generic name (S10,2).
  • Sugar: ‘sugar’ may be used for a defined list of sugar forms; the plural ‘sugars’ must not be used in a statement of ingredients (S10,2).
• Respecting table-specific definitions and exceptions: For the purposes of interpreting the Schedule’s table, “the definition of fish in subsection 1.1.2,3(2) does not apply,” so labellers must follow the Schedule’s direction rather than the general Code definition when using the table entry for fish (S10,2).

Duties (procedural/transition):

• During transition periods established by amendments, a food product may comply with either the Code as in force before a variation or the Code as amended by the variation, but not a combination of both. This is explicit for variations captured in the application table and S10,1A (application table summarising P1026 and P1044; S10,1A as added/omitted via amendments). For P1044 there is also a specified post-transition sale window for products packaged and labelled before the end of the transition period (application table summarising P1044).

Rights (direct):

• Right to use a listed generic name where the conditions for that name are satisfied: the Schedule provides an authorised shorthand for ingredient statements , the business may use the generic name in place of listing specific ingredients where the Schedule permits that usage (S10,2).
• Transitional flexibility: during stated transitional periods, businesses have the right to rely on either the previous or the amended Code for compliance purposes for the relevant product, subject to the “not a combination” restriction (application table; S10,1A entries summarised).

Rights (implicit):

• Predictability and narrow vocabulary: the Schedule grants businesses a predictable set of terminology they can adopt across product lines, reducing the need to invent bespoke ingredient phrasings where the generic names and conditions match the product composition (S10,2).

Limitations and interactional duties:

• The Schedule is not free-standing; it operates for the purposes of section 1.2.4,4. That creates the duty to read the Code holistically. For instance, where the Schedule excludes the Code’s general definition of fish for the table, the labeller must follow the Schedule’s instruction in constructing ingredient statements (S10,2).
• The Schedule does not itself set penalties or enforcement mechanisms within its text. Duty-holders must therefore be aware that compliance enforcement and penalties are managed under the broader legislative and regulatory framework that adopts the Code in their jurisdiction (Note 1; Note 2).

In short, the Schedule imposes concrete labelling duties where specific generic names are used, defines when and how those names may be used, and creates transitional rights to adopt either the prior or updated labelling regime during specified transition windows. The duty to gather upstream supply information is an operational corollary of the textual duties where conditions require source declarations (for example fats or oils).

The Schedule itself does not set out penalty provisions or enforcement mechanisms. The document identifies the Schedule as “a standard under the Food Standards Australia New Zealand Act 1991 (Cth)” and notes that the Code’s provisions apply in New Zealand by incorporation or adoption under the Food Act 2014 (NZ) (Note 1; Note 2). That legal status indicates the Schedule’s provisions operate as part of the Australia New Zealand Food Standards Code, but the Schedule text contains no fines, offences or specific enforcement powers.

Because this Schedule is a standard within the Code, enforcement and penalties will be determined by the statutory and regulatory frameworks that give force to the Code in each jurisdiction. The Schedule’s Amendment History and application table show amendments were made under section 92 of the Food Standards Australia New Zealand Act 1991 unless otherwise indicated, and commencement information is recorded for each amendment. The Schedule therefore functions as a regulatory standard whose non-compliance would typically be actionable under the enforcement provisions of the state, territory or national legislation that adopts the Code. The Schedule itself, however, is silent on enforcement mechanics (Note 1; Amendment History introductory text).

For New Zealand, the Schedule expressly notes that provisions of the Code are incorporated in, or adopted under, the Food Act 2014 (NZ), which is the instrument that would provide the enforcement machinery and penalties in that jurisdiction for non-compliance with Code standards as adopted (Note 2). For Australian jurisdictions, the Code is a national standard that State and Territory authorities typically enforce through their food legislation and compliance regimes; the Schedule’s text does not identify which agencies or the precise sanctions that might follow a breach. The Amendment History references section 92 of the FSANZ Act as the power under which amendments are made, but it does not convert that administrative provenance into a catalogue of sanctions in the Schedule itself.

Practical enforcement implications for businesses therefore include:

• Non-compliance with this Schedule’s requirements (for example, failing to declare animal or vegetable source for ‘fats or oils’ where used) will be judged against the applicable food regulatory scheme in the jurisdiction where the food is sold. The Schedule provides the substantive standard but not the enforcement toolset (S10,2; Note 1; Note 2).
• Transitional compliance must be demonstrable. During an applicable transition period set out in the Schedule’s application table, regulators will expect businesses to be able to show which Code version they complied with and that they did not apply a hybrid approach, since the Schedule expressly prohibits combining old and new requirements in the transition (application table; S10,1A provisions).

The Schedule’s omission of penalty text means legal teams should map the substantive labelling requirements here to the enforcement provisions and penalties contained in the relevant state, territory or New Zealand statute and enforcement guidelines when assessing compliance risk and potential sanctions.

The Schedule is an integral part of the Australia New Zealand Food Standards Code and operates by cross-reference to other parts of the Code and to the Acts that give force to the Code in each jurisdiction. The Schedule expressly states that it applies “for section 1.2.4,4,” meaning its permitted generic names and conditions are to be used where Standard 1.2.4 governs the statement of ingredients (S10,2). The Schedule also notes its status as a standard under the Food Standards Australia New Zealand Act 1991 (Cth) and that the provisions of the Code apply in New Zealand when incorporated or adopted under the Food Act 2014 (NZ) (Note 1; Note 2). These linking references set the Schedule’s place within the broader regulatory architecture.

Interaction with specific Code provisions:

• Standard 1.2.4: The Schedule furnishes the generic names and conditions for subparagraph 1.2.4,4(b)(iii). Practical compliance is therefore a two-step exercise: meet the substantive obligations of Standard 1.2.4 and, where a generic name is used, ensure it is a permitted name from the Schedule and that any attached condition is satisfied (S10,2).
• Section 1.1.2,3(2): The Schedule specifically disapplies the general definition of ‘fish’ contained in subsection 1.1.2,3(2) “for the purposes of this table.” That is an express textual carve-out; label-makers must follow the Schedule’s direction for the ‘fish’ table entry rather than relying on the broader Code definition when construing this Schedule (S10,2).
• Sections 1.1.1,3 and 1.1.1,9: The Schedule’s commencement notes and application/transitional provisions reference these general Code sections in relation to the availability, commencement and saving of provisions (Notes and application table). For example, the application table for certain amendments states subclauses that “section 1.1.1,9 of the Code does not apply to the variations,” meaning some of the general saving or transitional rules in the Code are displaced for those amendments (application table entries, P1026 and P1044 summaries).

Interaction with enabling Acts and enforcement regimes:

• Food Standards Australia New Zealand Act 1991 (Cth): The Schedule is made as a standard under that Act. Amendments recorded in the Amendment History were made under section 92 of that Act unless otherwise indicated. This places the Schedule within the national standard-setting regime and means that administrative processes under the Act are the vehicle for amendment and commencement (Note 1; Amendment History header).
• Food Act 2014 (NZ): For New Zealand, the Schedule’s operative effect depends on incorporation or adoption under the Food Act 2014 (NZ), which supplies the legislative mechanism for applying the Code in that jurisdiction (Note 2). Enforcement and penalties in New Zealand will therefore flow from the Food Act’s implementation of the Code.
• State and Territory law: The Schedule does not itself provide enforcement. In Australia, day-to-day enforcement of the Code and its Schedules generally occurs through state and territory food laws and enforcement agencies. The Schedule’s text does not specify those instruments or agencies, but its status as a national standard under the FSANZ Act means that State/Territory adoption and enforcement arrangements are the practical mechanism.

Interaction with amendment instruments:

• The Amendment History and the application table demonstrate that variations to the Schedule have bespoke transitional and savings arrangements that may displace normal Code transitional mechanics (the application table records that subclauses state 1.1.1,9 does not apply to some variations). The P1044 variation, for example, sets a three-year transition and a two-year post-transition sale window for pre-labelled stock (application table summarising P1044). Businesses must therefore track amendments and the specific transitional provisions in the relevant variation instrument rather than assume general Code transition rules apply.

In short, the Schedule is not standalone. Its substantive labelling rules are implemented through and constrained by Standard 1.2.4, its interpretation is affected by specific carve-outs (for example fish), and its practical enforcement and consequences depend on the adoption and enforcement frameworks in each jurisdiction. The Amendment History shows that subsequent variations may alter the Schedule and create bespoke transitional mechanics that displace generic Code transition rules.

The Schedule includes a documented Amendment History and an “Application, saving and transitional provisions” table that record the substantive changes made since publication. The compilation snapshot states this is Compilation No. 4 as in force on 25 February 2021 (up to Amendment No. 197) and that it was prepared on 1 March 2021 (Amendment History header). The amendments listed in the table are shown with instrument numbers, FRL registration numbers and Gazette dates, and the table describes how entries and sections were affected.

Key amendments recorded in the provided material include:

• Amendment 154, publication in the Food Standards Gazette No. FSC96 on 10 April 2015, which initially published Schedule 10 as part of Amendment 154 (F2015L00480 , 2 April 2015) (Amendment History opening line).
• Amendment No. 168 (FRL F2017L004141), 11 April 2017, which amended Note 1 to the Standard (a cross-reference) with commencement 13 April 2017 (Amendment History table; Section affected: Note 1 to Std; A’ment No. 168).
• Amendment No. 170 (FRL F2017L00585), 23 May 2017; this amendment added S10,1A (application, saving and transitional provisions) effective 25 May 2017 and made related amendments to items [2.2] and [2.3] of the Schedule, including entry adjustments for ‘fats or oils’ as a consequence of amendments to Standard 1.2.3 and inclusion of lupin (Amendment History table entries for S10,1A and table to S10,2; application table entries for P1026).
• Amendment No. 163 (FRL F2016L00783), 12 May 2016; the table to S10,2 was repealed and substituted effective 19 May 2016 for the entry for ‘fats or oils’ as a consequence of amendments to Standard 1.2.3 (Amendment History: table to S10,2, A’ment No. 163).
• Amendment No. 197 (FRL F2021L00145), 24 Feb 2021; this amendment amended S10,1A (omitted it) and amended S10,2 by omitting the entry for ‘nuts’ and the condition for use for ‘cereals’ and ‘nuts’, and added paragraph (a) to the condition for ‘fats or oils’. It also inserted conditions for the use of ‘fish’ and ‘starch’. The amendment came into effect on 25 Feb 2021 and included transitional arrangements recorded in the application table (Amendment History table entries for A’ment No. 197 and the application table summarising P1044) (Amendment History table entries referencing A’ment No. 197).
• The Amendment History notes that these amendments are made under section 92 of the Food Standards Australia New Zealand Act 1991 unless otherwise indicated and that each amendment’s commencement is recorded (Amendment History header and table).

Transitional specifics summarised in the application table:

• Food Standards (Proposal P1026 , Lupin as an Allergen) Variation: Items [2.2] and [2.3] of the Schedule were affected; the transition period commenced 25 May 2017 and ended 26 May 2018. Subsection S10,1A(3) provided that during that transition period a food may comply with either the Code as in force without the variation or the Code as amended by the variation, but not a combination (application table for P1026).
• Food Standards (Proposal P1044 , Plain English Allergen Labelling) Variation: Item [7] of the Schedule affected; amendment No. 197 registered 24 Feb 2021, Gazette 25 Feb 2021. Clause 4 established a transition period commencing 25 February 2021 and ending 25 February 2024, and a post-transition period from 26 February 2024 to 26 February 2026 for products packaged and labelled before the end of transition. Subclause 4(2) permitted sale during transition if the product complied with either the pre-variation or amended Code; subclause 4(3) allowed sale during post-transition for pre-labelled stock complying with either version (application table for P1044).

Practical consequences of the amendment history:

• The Schedule has been actively amended to address specific labelling concerns such as allergen disclosure (lupin inclusion) and plain-English allergen labelling (P1044), and to refine conditions of use for categories like fats or oils, fish and starch (Amendment History and application table).
• Each amendment may include bespoke transitional mechanics that displace general Code transition rules; businesses must review the Amendment History and the relevant variation instrument to determine the applicable compliance window and whether post-transition sale allowances apply (application table; Amendment History).

The Amendment History section in the compilation provides the formal record of how the Schedule’s table entries and transitional mechanics have evolved. It is the authoritative internal chronology for businesses and regulators to determine which version of the Schedule applies to labels at particular dates.

The compilation provided contains no litigation history, no court decisions, and no named cases. The Schedule and its Amendment History do not record judicial interpretations or any litigation outcomes. The text is purely a compilation of the Schedule itself, its commencement, amendment entries and transitional provisions (Amendment History header and tables).

Because the document does not include case law or adjudications, there are no source-provided judicial interpretations of the Schedule’s provisions to rely on. The Schedule therefore stands, in the supplied material, as a set of administrative standards and amendment records without accompanying litigation precedent. Practitioners seeking judicial guidance on questions such as interpretation of the Schedule’s table entries, disputes over whether a particular ingredient qualifies under a generic name, or the correct application of transition provisions, will need to search domestic court databases or administrative tribunal records for any cases decided after the compilation date, since none are included in this text.

Absent source-provided litigation, the typical areas where disputes might arise in practice , and which commercial teams commonly monitor for case law , include:

• Whether a specific ingredient or processing treatment falls within a permitted generic name and its conditions (for example, whether a modified starch is “modified by physical means or enzymes” or by other processes not permitted under the generic term) (S10,2, starch).
• Whether the use of a generic name (such as ‘fats or oils’) complies with the declaration requirements, including the adequacy of upstream supplier information to demonstrate the declared source (S10,2, fats or oils).
• Interpretation of transitional provisions where the transition window or the “not a combination” rule is invoked by a regulator or a competitor complaint (application table; S10,1A entries).

These potential litigation topics are identified as likely flashpoints because the Schedule is a labelling standard that depends on compositional and definitional boundaries. However, to repeat, the supplied compilation contains no litigation history or case law. Any reliance on judicial outcomes would require external legal research beyond the Schedule itself to identify relevant authorities and their holdings.

The Schedule contains a number of specific drafting features and transitional mechanics that create practical compliance traps if missed. The following list draws directly on the Schedule’s text and the Amendment History and highlights precise points where labelling practice commonly diverges from the Schedule’s requirements.

1. Using ‘sugars’ in the plural. The Schedule expressly states “The name ‘sugars’ must not be used in a statement of ingredients.” Instead the singular ‘sugar’ may be used but only to describe specified sugar types (white sugar; white refined sugar; caster sugar; loaf or cube sugar; icing sugar; coffee sugar; coffee crystals; raw sugar) (S10,2, sugar). Using the plural or a non-listed sugar form on a statement of ingredients risks non-compliance.

2. Overbroad use of ‘fats or oils’. The Schedule permits the generic name but imposes two express conditions:

   • Declare whether the source is animal or vegetable; and
   • If the food is a dairy product, including ice cream, declare the specific source of animal fats or oils. In addition, the schedule prohibits using ‘fats or oils’ for diacylglycerol oil (S10,2, fats or oils). A common operational pitfall is failure to capture and verify supplier data to support the “animal or vegetable” declaration, or neglecting the dairy-product-specific disclosure.

3. The ‘fish’ carve-out. The Schedule states that the definition of ‘fish’ in subsection 1.1.2,3(2) does not apply for the purposes of this table (S10,2, fish). This is a textual exception to general Code definitions. A labeller who relies on the Code’s general fish definition without checking the Schedule’s table could mis-label an ingredient.

4. Limited scope for ‘starch’. The Schedule allows the generic name ‘starch’ for unmodified starch or starch modified by physical means or enzymes (S10,2, starch). Chemical modifications are therefore not within the generic permission. Labellers should verify the type of modification; mischaracterising chemically modified starch as simply ‘starch’ will not meet the Schedule’s condition.

5. ‘Milk solids’ grouping rules. ‘Milk solids’ may be used only to describe milk powder, skim milk powder or dried milk products; or any two or more of a defined list of milk-related ingredients (whey; whey powder; whey proteins; lactose; caseinates; milk proteins; milk fat) (S10,2, milk solids). The Schedule does not allow arbitrary aggregation of milk components under ‘milk solids’. Users must ensure the composition matches the permitted combinations.

6. Diacylglycerol oil exclusion. The explicit prohibition on using ‘fats or oils’ for diacylglycerol oil is a narrow but absolute rule in the table. Diacylglycerol oil must not be represented by that generic term (S10,2, fats or oils).

7. Transition windows are not indefinite and may include post-transition sale allowances. The application table for P1044 sets a transition from 25 February 2021 to 25 February 2024, and a post-transition period from 26 February 2024 to 26 February 2026 that allows sale of products packaged and labelled before the end of the transition period if they comply with either the pre-variation or amended Code (application table summarising P1044). Businesses that miss re-labelling deadlines may still be able to sell legacy stock during a defined post-transition window but must observe the specific terms and dates in the variation instrument.

8. No mixing of versions during a transition. Where a transition is in force, the Schedule’s transitional rules recorded in the application table and in S10,1A entries provide that a product must comply with either the prior Code or the amended Code, but not a combination of both (application table; S10,1A). A labeller who attempts to mix elements from both versions risks non-compliance.

9. Changes to the table across amendments. The Amendment History records deletions and insertions (for example, the omission of the entry for ‘nuts’ and changes to conditions for ‘cereals’ and ‘nuts’ in Amendment No. 197). Labellers must track the Amendment History to know which entries and conditions are current as at a given date (Amendment History).

10. The Schedule does not itself specify enforcement. The absence of penalty or enforcement detail in the Schedule means businesses must identify the enforcement apparatus in the jurisdiction of sale. Failing to do so can lead to a mismatch between compliance planning and enforcement expectations (Note 1; Note 2; Penalties and enforcement section).

In practice, the most common operational gotchas are reliance on outdated versions of the Schedule, failure to collect supplier information necessary to satisfy source-declaration conditions, misuse of prohibited terms such as ‘sugars’ or ‘sugars’ plural, and misunderstanding the limits of permitted generic names where a specific ingredient or processing step (such as chemical modification of starch) falls outside the generic permission. These are not abstract risks; the Schedule’s text provides the specific constraints that make each a compliance issue (S10,2; Amendment History; application table).

Compliance with this Schedule is a discrete label-management and supply-chain information exercise. The following steps are grounded in the Schedule’s text and the Amendment History and are intended for legal, compliance and operations teams constructing or reviewing ingredient statements.

1. Identify the applicable Code version and amendments.

   • Confirm the version of the Schedule that applies on the relevant manufacture, import or sale date. Use the Amendment History and the FRL/Gazette entries recorded in the compilation to identify amendments and their commencement dates (Amendment History table). For variations with transition periods (for example P1026 and P1044), determine whether the product’s labelling falls within a transition or post-transition window and apply the “either the pre-variation or amended Code” rule in that window (application table entries for P1026 and P1044).

2. Map product composition to Schedule entries.

   • For each ingredient appearing in the statement of ingredients, identify whether a permitted generic name in S10,2 applies. Where it does, confirm that any prescribed condition is met. For example:
     • If using ‘fats or oils’, obtain supplier declarations on whether the fat or oil is animal or vegetable and, where the food is a dairy product, the specific animal source. Do not use ‘fats or oils’ to cover diacylglycerol oil (S10,2).
     • If using ‘starch’, ensure it is either unmodified or modified only by physical means or enzymes; chemically modified starch should be named appropriately and not simply labelled ‘starch’ (S10,2).
     • If labelling ‘milk solids’, check that the composition is either milk powder/skim milk powder/dried milk product or comprises any two or more of the listed components (whey; whey powder; whey proteins; lactose; caseinates; milk proteins; milk fat) (S10,2).

3. Avoid prohibited terms and misapplications.

   • Do not use the plural ‘sugars’ in a statement of ingredients. If using ‘sugar’, restrict that label to the enumerated sugar types listed in the Schedule (S10,2, sugar).
   • Avoid relying on the general Code definition of ‘fish’ for the Schedule’s table purposes because the Schedule expressly disapplies that definition within the table (S10,2).

4. Maintain supplier declarations and traceability records.

   • The Schedule’s conditions create upstream information requirements. Obtain and retain supplier declarations that identify the nature and source of fats/oils, the type of starch modification, and the composition of milk-based products. Keep records that demonstrate the basis for using a generic name and compliance with the Schedule’s conditions in the event of an audit or enforcement action.

5. Implement a version-control and label-change process timed to transition periods.

   • Develop a label-change timeline that aligns with amendment commencement and transition windows recorded in the Amendment History and application table. Where a transitional allowance exists, document the choice to comply with either the pre-variation or amended Code for each stock batch, and ensure you do not mix elements of both versions for the same product (application table; S10,1A where applicable).

6. Conduct periodic label audits and supply-chain checks.

   • Include a compliance review step in product release to verify that generic names used match the Schedule and their conditions remain satisfied. Audit supplier documentation annually or on each supplier change.

7. Liaise with regulatory advisers for cross-jurisdictional sales.

   • If selling in both Australia and New Zealand, confirm the Code’s adoption status under the Food Act 2014 (NZ) in New Zealand and any consequential differences in enforcement or accepted practices (Note 2). Map the Code’s substantive requirements against local enforcement guidance.

8. Prepare for enforcement queries and complaints.

   • Although the Schedule does not include penalties, be ready to demonstrate compliance with the Schedule via documentation and product testing where necessary. Maintain a compliance pack for each SKU that includes the applicable Code version, supplier declarations, batch records and labelling proofs.

9. Update consumer-facing communications where needed.

   • If the Schedule’s conditions require disclosures that consumer-facing claims may omit (such as the precise animal source for dairy fats), ensure packaging copy and marketing collateral do not contradict the ingredient statement and that both are updated in line with the Schedule.

10. Monitor future amendments.

    • The Amendment History demonstrates this Schedule is subject to change. Set up an alert or subscription to the Federal Register of Legislation or FSANZ publications to capture future amendments and transitional arrangements so that packaging updates can be budgeted and scheduled in advance (Amendment History header).

Operational checklist items to implement immediately:

• Inventory current SKUs and their ingredient statements.
• Map each ingredient to a Schedule entry and note any conditions that apply.
• Gather supplier disclosures that substantiate permitted generic use.
• Schedule label artwork updates and confirm transitional options where applicable.
• Retain records showing which version of the Code was relied upon for each production run during transition/post-transition windows.

Applying these steps will address the Schedule’s textual demands (S10,2), respect the amendment-driven transitional mechanics (application table; S10,1A where in force), and align label practice with the Schedule’s permitted generic vocabulary and conditions.