Australia New Zealand Food Standards Code – Schedule 8 – Food additive names and code numbers (for statement of ingredients)

The Schedule organises one core technical concept: the mapping between additive names and their standardised numeric "code numbers" for ingredient-statement purposes. That mapping is presented in two complementary formats: an alphabetical listing of additive names with their code numbers, and a numerical listing that maps numbers to names. The instrument is a data standard within the legal architecture of the Code. The relevant legal hooks named in the Schedule are the definition of "code number" in section 1.1.2,2 and subsection 1.2.4,7(1) of Standard 1.2.4. The Schedule therefore functions as the authorised controlled vocabulary and index for any ingredient statement that relies on code numbers.

Several structural points in the Schedule are material to interpretation and operational use.

• Dual listings for convenience and cross-check. The alphabetical listing aids users who know the additive name and need the code; the numerical listing aids those who have a code and need the authorised name. Both are part of the Standard and together are the authoritative source for the Code's use of code numbers.

• Multiple names per code and multiple codes per name. The tables show that some numeric codes are associated with more than one name or variant (for example a single code may be mapped to several forms or synonyms), and conversely the same name may appear with different codes where variants are distinguished (for example caramel is split into 150a-150d). The numerical listing also shows some single numbers repeated for different related chemical forms (for example 339 applies to sodium phosphate dibasic, monobasic and tribasic entries in the alphabetical listing). Users must therefore check both entries to determine which name form the Standard uses for a given numeric reference.

• Non-numeric entries. Some names appear in the alphabetical listing with a dash instead of a code number (for example monk fruit extract or luo han guo extract, mushroom chitosan, sodium hydrosulphite, sweet osmanthus ear glycolipids). Those entries are carried forward into a numerical listing showing the same hyphen. The hyphen in the Schedule indicates the absence of a numeric code assigned within the Schedule for that named substance. The Schedule thus recognises named additives that do not, at the time of compilation, have a numeric code in the Code.

• Amendment and commencement metadata. The Schedule includes an Amendment History table that identifies amendments, their registration numbers, Gazette references and commencement dates. Amendments are generally made under s 92 of the Food Standards Australia New Zealand Act 1991, and the Schedule records instances of additions, amendments and a recorded "never commenced" variation. The presence of amendment metadata is operationally important because users must check for the commencement dates of entries before relying on them in compliance processes.

• Cross-jurisdictional adoption. The Schedule explicitly identifies that the provisions of the Code that apply in New Zealand are incorporated or adopted under the Food Act 2014 (NZ). That linkage makes the Schedule relevant to entities operating in Australia and New Zealand and requires attention to each jurisdiction's adoption processes where relevant.

Conceptually the Schedule is a labelling and information-standards instrument, not a safety standard. It is design-focused: it standardises how additives are named and indexed for ingredient statements across the Code, thereby reducing semantic uncertainty about what a particular code number on a label refers to under the Code. The Schedule centralises that semantic authority in a single legal text that other Code provisions instruct users to consult.

The Schedule affects anyone who must prepare or assess ingredient statements that refer to food additives by name or by code number under the Australia New Zealand Food Standards Code. The Schedule itself identifies the link to Standard 1.2.4 and the relevant definitional provision in section 1.1.2,2. Therefore, the parties most directly affected are:

• Food businesses that manufacture, package or import foods for sale in Australia or in New Zealand where the Code applies. Those businesses are the ones who will need to apply the names and code numbers from Schedule 8 when preparing ingredient statements that reference additives by code number, because that is the source the Code points to for the definition and use of "code number" and for subsection 1.2.4,7(1).

• Label designers, regulatory affairs teams, compliance officers and consultants engaged by food businesses. These practitioners must translate formulation information into an ingredient statement that complies with the Code, and Schedule 8 provides the official mapping they must use when including code numbers in labels.

• Importers and distributors. Entities that bring foods into Australia or New Zealand must ensure the product labelling is compliant with the Code and, where the label uses code numbers, use the Schedule's mappings to ensure the code number corresponds to the additive name intended.

• Regulators and enforcement officers who assess compliance with the Code. Schedule 8 is the official list they will consult to verify whether a code number shown on a label corresponds to the named or intended additive in the Code.

• Consumers, indirectly. While the Schedule does not itself impose consumer-facing disclosure obligations, it underpins how additives are identified on labels. The mapping between names and code numbers affects the precision and uniformity of information available to consumers who read ingredient statements.

• New Zealand entities. Note 2 of the Schedule states that provisions of the Code that apply in New Zealand are incorporated in, or adopted under, the Food Act 2014 (NZ). Therefore, businesses operating in New Zealand and relying on Code-based labelling must pay attention to the Schedule as adopted under the NZ statute.

Who does not appear to be directly affected by the Schedule, on its face, are bodies setting food-safety thresholds or approving novel food additives, because the Schedule does not set safe limits or authorisations. Those matters are handled elsewhere in the Code and in other regulatory instruments. The Schedule is specifically a labelling/information reference. However, because many labelling obligations depend on which substances are listed and how they are named, the Schedule will indirectly influence any stakeholder for whom the exact labelling of additives is legally relevant.

Two further practical impacts arise from the Schedule's structure. First, the Schedule centralises naming authority with Food Standards Australia New Zealand and therefore concentrates the decision about what name maps to what code number with that central authority and its amendment process under s 92. Second, the Amendment History and compilation dates show that entries change over time; therefore businesses that trade across dates must track commencement dates for amendments. The Amendment History includes entries marked "never commenced" and entries with later insertion dates; those markers matter for applying the Schedule to labels with specific compliance dates.

The Schedule itself is primarily a reference and does not set out substantive duties or civil penalties within its text. Its legal operation is to supply the names and code numbers to be used in the Code where the Code requires or permits the use of a code number in an ingredient statement. Two defined-code hooks within the Code are explicitly referenced in the Schedule: the definition of "code number" in section 1.1.2,2 and subsection 1.2.4,7(1) of Standard 1.2.4. Those cross-references are the channels through which duties arise in practice. From the Schedule as supplied, the following duties and rights can be stated with textual grounding.

• Duty to consult the authoritative list where the Code requires or permits a code number. If an ingredient statement in a food label invokes a code number, the Code’s definition and Standard 1.2.4 will require, by cross-reference, that the code number used corresponds to the official mapping in Schedule 8. The Schedule therefore supplies the names that fulfill the definition of "code number" in s 1.1.2,2 and the content for s 1.2.4,7(1).

• Duty to use current, commenced entries. The Schedule includes commencement metadata in the Amendment History. Where an amendment adds, amends, or removes an entry, the date of commencement in the Gazette (as recorded in the Amendment History) will determine when that entry becomes the operative schedule to be consulted for compliance. Users therefore have a duty to ensure they are relying on the version of Schedule 8 that was in force at the relevant date of manufacture, importation or sale.

• Right to definitive naming. Businesses and regulators have the right to treat the Schedule as the definitive and authorised source for the relationship between an additive name and its code. This reduces argument over which colloquial or proprietary name constitutes the additive for labelling purposes because the Code mandates the use of the Schedule for the definition of "code number".

• Duty to account for entries without numeric codes. The Schedule includes named additives without assigned numeric codes (represented by a dash). Where a business wishes to reference such an additive on an ingredient statement, there is an implicit need to check how Standard 1.2.4 requires those additives to be presented (for example by name rather than by code number) because the Schedule shows no numeric code to be used for them.

• Duty to track amendments made under s 92 of the FSANZ Act. The Amendment History explicitly states that amendments are made under section 92 of the Food Standards Australia New Zealand Act 1991 unless otherwise indicated. Users therefore must monitor FSANZ announcement channels, Gazette notices and the Federal Register of Legislation for commencement notices. The Schedule itself signals that some changes have "never commenced" (for example Amendment No. 184 relating to an entry for potassium polyaspartate), which creates an additional duty to check commencement status.

• Right to cross-jurisdictional applicability notice. Note 2 gives businesses operating in New Zealand notice that the Code provisions that apply in New Zealand are incorporated or adopted under the Food Act 2014 (NZ). That affects the rights and duties of New Zealand-registered food businesses which rely on the Schedule through the NZ statutory adoption process.

Operationally those duties mean that the Schedule functions as the required lookup table for anyone selecting whether to display an additive by name or code number on an ingredient list where the Code contemplates the use of code numbers. The Schedule creates a compliance-oriented task: match the additive used in the product to the Schedule entry, use the code number if the Code allows or requires it, and ensure the Schedule version relied upon is the one that was in force at the relevant time.

What the Schedule does not itself do, on its face, is impose penalties, set safety limits, or make substantive authorisations for an additive's use in particular food categories. Those substantive regulatory constraints remain in other parts of the Code and in other instruments. The Schedule supplies the informational infrastructure that makes other duties in the Code operationally specific.

The Schedule, as presented, does not itself set out offences, penalties, or an enforcement regime. It is an informational Standard within the Australia New Zealand Food Standards Code and provides the authorised names and code numbers that feed into labelling requirements elsewhere in the Code. The Schedule text identifies the legal framework within which it sits: it is a Standard made under the Food Standards Australia New Zealand Act 1991 (Cth) (Note 1), and amendments are made under section 92 of that Act unless otherwise indicated (Amendment History preface). Note 2 links the Code's application in New Zealand to the Food Act 2014 (NZ). Enforcement and penalty mechanisms for breaches of the Code typically reside in other parts of the Code or in the enforcing jurisdiction’s food legislation, but those enforcement provisions are not reproduced in Schedule 8.

From the Schedule’s content the following enforcement-relevant points can be recorded:

• The Schedule is the authoritative reference for the meaning of "code number" in s 1.1.2,2 and for the content of subsection 1.2.4,7(1). Non-use or misuse of the Schedule mapping in an ingredient statement that relies on a code number would be an issue of non-compliance with the Code. Enforcement action for such non-compliance would therefore be taken under the statutory enforcement powers and penalty regimes that give effect to the Code in the relevant jurisdiction, whether under Australian law or, for New Zealand, under the Food Act 2014 (NZ) where the Code is adopted. The Schedule does not itself state which penalties attach; it provides the list that an enforcement officer will use to check whether a code number was used correctly.

• Amendment commencement matters carry practical enforcement consequences. The Schedule’s Amendment History records entries that never commenced, entries added on specific dates, and corrections. For a regulator assessing a label, the relevant question is which Schedule entries were lawfully in force at the date of manufacture, importation or sale. The Schedule provides the metadata required to make that determination (Gazette references and commencement dates). Errors in applying an entry that had not commenced or that had been superseded can result in findings of non-compliance. The Schedule’s own amendment metadata therefore creates an evidentiary pathway for regulators to determine compliance status.

• No internal enforcement or appeal procedure is described in the Schedule. Any right of review or appeal against a decision to treat a label as non-compliant must be sought under the procedural and judicial mechanisms provided in the broader statutory scheme,those mechanisms are not described in Schedule 8.

• Cross-jurisdiction enforcement nuance. The Schedule signals its availability in both Australia and New Zealand. Enforcement approaches and penalties may differ between jurisdictions because the Code is incorporated domestically in New Zealand under the Food Act 2014 (NZ). The Schedule does not, however, detail those jurisdictional enforcement differences.

Users should therefore treat Schedule 8 as an evidentiary and definitional instrument: it supplies the names and numbers that regulatory officers and courts will consult when assessing whether a code number on a label matches the authorised list. The precise penalties and the process by which enforcement action is pursued against a party who fails to use the Schedule correctly are to be found in the enforcement provisions of the relevant food laws and not within the Schedule itself.

Schedule 8 is designed to be read as a component of the Australia New Zealand Food Standards Code. The Schedule itself references the statutory instruments and Code provisions that give it legal effect and cross-jurisdictional reach. The principal statutory cross-links and interactions identifiable from the Schedule text are the following.

• Food Standards Australia New Zealand Act 1991 (Cth), sections 92 and 93. The Schedule declares that it is a Standard under the FSANZ Act and that it commences on a specified date, with commencement notified in the Gazette and the New Zealand Gazette under section 92 of the Act (S8,1 Commencement note). The Amendment History explicitly records that amendments are made under section 92 unless otherwise indicated. Section 93 is referenced in connection with the commencement notices. Those references establish the Schedule’s procedural and formal relationship with the FSANZ Act.

• Australia New Zealand Food Standards Code, section 1.1.2,2 and Standard 1.2.4, subsection 1.2.4,7(1). The Schedule identifies these specific Code hooks. Section 1.1.2,2 contains the definition of "code number" and Standard 1.2.4 contains provisions relating to statements of ingredients, including substances used as food additives. Schedule 8 supplies the names and code numbers to be used under those Code provisions. In practical terms the Schedule is a definitional annex for the operation of those parts of the Code.

• Food Act 2014 (NZ). Note 2 states that the provisions of the Code that apply in New Zealand are incorporated in, or adopted under, the Food Act 2014 (NZ). The Schedule therefore interacts with New Zealand domestic law through the mechanism of incorporation or adoption. That interaction means that New Zealand regulators and businesses need to consider the Schedule as an adopted part of the domestic regulatory framework in New Zealand, subject to local commencement and adoption details.

• Gazette and Federal Register of Legislation. The Schedule’s Amendment History shows registration numbers, Gazette references and commencement dates. The Schedule itself instructs users to see the Gazette notices and the Federal Register of Legislation for commenced amendments and for reflection of any uncommenced amendments as shaded boxed text. This indicates that the Schedule must be read in light of the official publication and registration instruments that give effect to amendments under the FSANZ Act.

• Internal Code interdependencies. Because the Schedule is the defined source of additive names and code numbers, any other Standard or provision in the Code that permits, requires, or restricts the use of an additive by reference to a code number will interact with Schedule 8. For example, provisions that authorise the use of a named additive in certain foods or set maximum permitted levels will require cross-reference to Schedule 8 to determine the exact label presentation clause when a label uses a code number. The Schedule itself does not contain those authorisations or limits; it is the canonical naming register for such references.

• Administrative and trade implications. The Schedule’s listing of names with and without numeric codes, and the presence of both alphabetical and numerical listings, is tailored to the administrative need for precision in labelling and for cross-border consistency between Australia and New Zealand. The Schedule’s interaction with the Food Act 2014 (NZ) means that New Zealand adoption choices affect how Schedule entries operate in that jurisdiction.

Limitations in the Schedule’s cross-law scope should be noted. The Schedule does not purport to alter other statutory instruments beyond naming and code-number mapping. It also does not include enforcement mechanisms or detailed procedural rules for disputes about entries; those are handled under the FSANZ Act, domestic food law and administrative processes. When multiple regulatory instruments refer to an additive, the Schedule is intended to be the common list to be consulted to resolve naming and numbering questions. Users must therefore consult Schedule 8 together with the substantive Code provisions, the FSANZ Act, and any relevant domestic implementing laws (such as Food Act 2014 in New Zealand) to determine the complete legal obligations.

Schedule 8 contains an explicit Amendment History and metadata about compilations. The Schedule states that the Amendment History provides information about each amendment to the Schedule, and that that information includes commencement or cessation information for relevant amendments. It also states that these amendments are made under section 92 of the Food Standards Australia New Zealand Act 1991 unless otherwise indicated. The Schedule’s compilation metadata states that the document is Compilation No. 8 of Schedule 8 as in force on 16 September 2025 (up to Amendment No. 231), prepared by Food Standards Australia New Zealand on 16 September 2025. The Amendment History section then lists particular amendments by the section affected, amendment number, Federal Register of Legislation registration and Gazette references, commencement or cessation dates, how the Schedule was affected, and a short description of the change.

The Amendment History contains discrete entries illustrating the type of changes made, with examples including:

• Amendment No. 168, FRL registration F2017L0041411 April 2017 FSC11013 April 2017, commenced 13 April 2017, described as an amendment to numerical entries for tocopherol to correct a typographical error.

• Amendment No. 182, FRL registration F2018L0159523 Nov 2018 FSC12329 Nov 2018, commenced 29 Nov 2018, which amended the table to include Polyoxyethylene (40) stearate and added Polysorbate 20.

• Amendment No. 183, commenced 23 January 2019, which added monk fruit extract or luo han guo extract and also added Rosemary extract (392).

• Amendment No. 184, described as a variation that never commenced, relating to Potassium polyaspartate.

• Amendment No. 188, commenced 5 Dec 2019, adding an entry for Potassium polyaspartate, indicating that the earlier variation in No. 184 did not commence but the substance was later added by a subsequent amendment.

• Amendment No. 198, commenced 26 March 2021, inserting Sweet osmanthus ear glycolipids.

• Amendment No. 231, FRL registration F2024L0115113 Sept 2024, commenced 13 Sep 2024, inserting di-alpha tocopherol, sodium hydroxide and potassium hydroxide.

• Amendment No. 244, FRL registration F2025L0108111 Sep 2025, commenced 16 Sep 2025, amending the alphabetical table to insert Mushroom chitosan and amending the numerical listing entry for Mushroom chitosan.

The Amendment History entries demonstrate several operational features:

• Amendments can add or correct entries, and can also be recorded as never commenced. Users therefore need to check the commencement status of an amendment before relying on it.

• The Schedule keeps a running record of the substantive content changes and the formal registration and commencement actions that create legal effect. The Gazette and FRL registration identifiers supplied in the table are the primary documents that confirm commencement.

• The compilation metadata and the Amendment History together aim to help stakeholders identify which version of Schedule 8 is in force at a given date, and which specific changes were made by an amendment. The Schedule notes that commenced amendments are included in a compilation on the Federal Register of Legislation with the relevant dates.

Two matters of technical attention arise from the Schedule’s Amendment History as provided. First, the Schedule identifies both commenced amendments and a variation that "never commenced" (No. 184). That shows that proposals to change the Schedule may be registered but fail to commence, which can complicate a user’s assessment of the effective list. Second, the compilation statement at the top states the compilation is "as in force on 16 September 2025 (up to Amendment No. 231)" but the Amendment History includes Amendment No. 244 with commencement dated 16 Sep 2025, which appears in the table. Users should therefore treat the compilation metadata and the amendment entries as part of the same document to be read together and confirm the actual commencement of an amendment via the FRL and Gazette references supplied.

Finally, the Amendment History reveals the instrument’s evolutionary character; entries are added over time to reflect new additive names, corrections, and administrative changes. For compliance and record-keeping, businesses must track the amendment numbers, commencement dates, and register notifications shown in the Schedule’s own Amendment History to determine which entries they are required to use at any point in time.

The Schedule itself does not include, cite or summarise any litigation records. No case names, judicial decisions or dispute records are set out in the text provided. The Schedule is an administrative Standard and the compilation text records only the standard content and its amendment history. The document contains no litigation history section and does not identify any judicial interpretations or court decisions concerning the Schedule or specific code-number mappings.

In practical terms, this means two things based on the Schedule alone:

• The Schedule does not purport to record court interpretations of any of its entries, nor does it register any legal controversies about the meaning of specific additive names or code numbers. If litigation involving the interpretation of a Schedule entry has occurred, it is not reflected in the Schedule text supplied.

• For users needing to understand how courts or tribunals have treated the Schedule, the Schedule provides no guidance. Any party requiring such interpretative history will need to consult external law reports, case law databases and tribunal records for decisions that discuss the use or meaning of code numbers or Schedule 8 entries. That material is beyond the Schedule's text and is not provided in this instrument.

Because the Schedule is primarily a technical list of names and numbers intended for labelling and information purposes, disputes that reach litigation would typically concern whether a label complied with the Code as a whole, whether an amendment had commenced at a relevant date, or whether the use of a particular name or code was misleading. The Schedule itself does not describe any dispute resolution pathways or list past adjudications. The absence of litigation material within the Schedule is therefore an absence of recorded judicial engagement in the text, not an indication that litigation has not occurred; it merely indicates that such material is not incorporated in the Schedule.

Several practical and interpretative pitfalls arise from the Schedule’s form and the metadata it contains. These are points where users frequently err or where the Schedule’s structure can create ambiguity if not handled carefully.

1. Multiple names share a single numeric code and vice versa. The tables show many instances where a single code is associated with multiple names or synonyms. For example, the numerical listing shows code 101 mapped to both Riboflavin and Riboflavin-5′-phosphate sodium. Likewise, 339 is used in the numerical listing for sodium phosphate dibasic, monobasic and tribasic. Users must not assume a one-to-one relationship between name and number without checking both alphabetical and numerical listings and any parenthetical qualifications in the entry. Using the wrong variant can create a labelling mismatch under the Code.

2. Entries without numeric codes. Several additives appear in the alphabetical listing with a dash instead of a numeric code. Examples include monk fruit extract or luo han guo extract, mushroom chitosan, sodium hydrosulphite, and sweet osmanthus ear glycolipids. The presence of a named additive without an assigned code signals that the Schedule recognises the name but does not provide a numeric code for use in ingredient statements. If a label attempts to use a numeric code for such a substance, there will be no authorised mapping in Schedule 8. Users must check how Standard 1.2.4 requires such additives to be presented (for example by name) rather than by code number.

3. Duplicate or overlapping wording and entries. The alphabetical table sometimes splits names across table rows and the numeric listing repeats similar strings, which can make cross-referencing error-prone. Example: Calcium phosphate entries are spread over multiple rows in the alphabetical listing with descriptive disambiguation (dibasic, monobasic, tribasic) but in places the table formatting makes it easy to miss which numeric code applies to which specific chemical form. Careful cross-checking between the two lists is required.

4. Amendments that "never commenced." The Amendment History includes an amendment (No. 184) described as a variation that "never commenced" in relation to Potassium polyaspartate. A later amendment (No. 188) added Potassium polyaspartate with a commencement date. The "never commenced" flag is a practical trap: an FRL registration may exist but the legal effect depends on formal commencement. Users must verify each amendment's commencement status via the Gazette/FRL registration cited.

5. Compilation metadata mismatch. The Schedule contains a compilation statement that says the compilation is "as in force on 16 September 2025 (up to Amendment No. 231)" and prepared on 16 September 2025. The Amendment History table includes Amendment No. 244 with a commencement date of 16 Sep 2025 and an FRL registration noted. Users should not rely solely on the compilation summary line but should read the Amendment History and the FRL entries to confirm which amendments are actually in force. This internal inconsistency in the compilation metadata is a document-management gotcha.

6. Jurisdictional adoption differences. Note 2 states that provisions of the Code that apply in New Zealand are incorporated in, or adopted under, the Food Act 2014 (NZ). Users operating across Australia and New Zealand must verify local adoption and commencement details in the New Zealand context, because adoption mechanisms or commencement arrangements may differ and the Schedule alone does not specify those domestic adoption details.

7. Synonyms and trade names. The Schedule includes several common names and synonyms within entries (for example "Monosodium L‑glutamate or MSG 621"). Labels that use an unlisted proprietary or trade name that is not obviously synonymous with a Schedule entry risk being challenged by regulators. Users should avoid reliance on proprietary names without mapping them clearly to a Schedule entry.

8. Formatting and typographical corrections matter. Amendment No. 168 corrected typographical errors in tocopherol numbering. Small typographical differences can change legal meaning. Users preparing labels must ensure they consult the most current, formally commenced Schedule rather than an earlier or draft copy that may contain typographical errors.

9. Enzyme and gas entries in unusual numeric ranges. Additives like enzymes are in the 1100 series, and gases occupy codes in the 940-949 range. Those ranges may be overlooked by practitioners used to traditional lower-range additive numbers. Check the full numerical listing when searching by code.

10. Reliance on Federal Register of Legislation and Gazette. The Schedule repeatedly directs users to FRL and Gazette notices for commencement details. Practically, failure to verify the FRL/Gazette entries for commencement creates a material risk of using a code that was not yet in force or failing to use an entry that has just commenced.

In short, the gotchas cluster around version control, the presence of hyphen/no-code entries, multiple mappings between names and numbers, and the need to confirm commencement via the FRL/Gazette. The Schedule’s structure makes it an authoritative source, but only if the user attends to the detail in both the content tables and the Amendment History metadata.

Compliance with the labelling aspects of the Code that refer to Schedule 8 requires a predictable, document-controlled approach. The Schedule is the authoritative list for the definition of "code number" (s 1.1.2,2) and for subsection 1.2.4,7(1), so the basic compliance rule is: where the Code requires or permits an additive to be identified by code number in an ingredient statement, the code number and the name used must correspond to the entries in Schedule 8 that were in force on the relevant date. The following practical steps, grounded in the Schedule’s own structure and metadata, form a compliance checklist.

1. Identify relevant Code provisions. Start by identifying where in your product’s labelling Standard 1.2.4 and the definition in section 1.1.2,2 apply. The Schedule is the reference for the "code number" component of those provisions. Do not rely on Schedule 8 in isolation; confirm the substantive label requirements in Standard 1.2.4.

2. Match your additive to the Schedule entry. For every additive used in the formulation, locate the additive in the alphabetical listing to find the code number or note that no numeric code is assigned (a hyphen). Then cross-check in the numerical listing to confirm the code maps to the intended name or variant. Where there are multiple variants associated with a code, determine which variant the Code requires or which is technically accurate for your ingredient.

3. Verify the commencement date of the Schedule version. Use the Amendment History entries and the FRL/Gazette references cited in the Schedule to confirm which amendments had commenced at the time the product was manufactured, packed, imported or sold. Where an amendment is marked "never commenced" or has a later commencement date, do not rely on its entries until the FRL/Gazette shows formal commencement.

4. Handle entries without numeric codes by name. If the additive appears with a dash (no code number), the Schedule does not provide a numeric code for that substance. In that case, present the additive by name in the ingredient statement in the manner required by Standard 1.2.4. The Schedule indicates the absence of a code; do not invent a code or use an incorrect code.

5. Avoid shorthand or proprietary names without mapping. Where labels use proprietary or colloquial names, ensure there is a clear, documented mapping to the Schedule entry. If the Schedule lists the substance under a scientific or alternative common name, include that recognised name or the authorised code number as required by the Code.

6. Maintain version control and document history. Keep a version-controlled record of which Schedule compilation and Amendment History entries were relied upon for each product batch and labelling run. Record the date of manufacture/packaging and the Schedule version in use on that date, including the FRL/Gazette references for the relevant commencement notices.

7. Monitor FSANZ publications and the FRL. Because the Schedule is amended via s 92 processes, set up monitoring for FSANZ amendments, FRL registrations, and Gazette notices. The Schedule itself lists these reference points in the Amendment History; operational compliance requires tracking them to detect additions or corrections.

8. Cross-check in New Zealand. If you supply products in New Zealand, confirm the local incorporation or adoption status via the Food Act 2014 (NZ) instruments and any domestic regulations implementing the Code in New Zealand. Note 2 in the Schedule makes clear that adoption or incorporation occurs under the NZ statute.

9. Check for ambiguous mappings and seek clarification where necessary. If a code maps to multiple names or a name maps to multiple codes and the correct choice is unclear for the product in question, seek authoritative clarification from FSANZ or the relevant domestic regulator before finalising labels. Document that clarification in the label-change record.

10. Factor label-change lead time into product planning. Because amendments have formal commencement dates and may post-date manufacturing or importation schedules, plan label changes well in advance. Use the Amendment History to determine whether an entry is newly added and when it will become binding.

11. Keep evidence for compliance. Retain copies of the Schedule compilation used, the FRL/Gazette notices confirming commencement, and the product labels and ingredient declarations. This evidence will be necessary to demonstrate compliance to enforcement agencies who will use Schedule 8 as the reference to verify any code numbers on a label.

12. Internal training and audit. Train regulatory and quality staff on the existence of dual listings, hyphen/no-code entries, and the importance of confirming amendment commencements. Conduct periodic audits that check label content against the Schedule entry in force on the date of packaging.

In practice, compliance with Schedule 8 is a documentation and version-control exercise as much as a technical one. The Schedule is the authoritative reference for additive naming and numeric code use in ingredient statements under the Code. The operational risk is mostly procedural: misreading the dual listings, failing to confirm commencement dates, or using an unavailable code. The Schedule’s Amendment History and FRL/Gazette citations are the control points to resolve those risks; good compliance is achieved by systematising those checks into the labelling workflow.