Australia New Zealand Food Standards Code - Standard 2.3.1 - Fruit and Vegetables

The Standard is short; the main concepts are definitional breadth and a single compositional limit.

• Definitional breadth: Clause 1 expands the label fruit and vegetables to encompass "fruit, vegetables, nuts, spices, herbs, fungi, legumes and seeds." That is an inclusive definition. A separate defined label, surface treated fruit and vegetables, covers produce "harvested, washed and treated with permitted processing aids and food additives." These definitions are presented as the grounding terms for downstream rules (notably additive permissions), and the Purpose links the definitions to processing categories in Standard 1.3.1. The Standard therefore decouples the regulatory category from narrower culinary or agricultural senses of "fruit" and "vegetable" and ties it to a regulatory object for additives and processing.

• Permitted processing aids and additives: The text repeatedly refers to "permitted processing aids and food additives" (Purpose, cl 1), but it does not itself enumerate them. The Standard therefore functions as a definitional node in a larger network of compositional and additive permissions. The reader must consult the referenced processing categories (Standard 1.3.1) and any additive-permission schedules elsewhere in the Code to determine which processing aids and additives are allowed for items that fall under these definitions.

• Composition requirement (pH ceiling): Clause 2 states a precise compositional requirement: "Fruit and vegetables in brine, oil, vinegar or water, other than commercially canned fruit and vegetables, must not have a pH greater than 4.6." The rule applies to the product presentation (in brine, oil, vinegar or water) and creates an express exclusion , commercially canned products are outside the rule's reach. The clause therefore delineates a set of packaged presentations (for example, jarred, bottled, or otherwise containerised products not commercially canned) that must meet the numerical pH limit.

• Scope by process and presentation: The Standard links the definitions to processing categories and restricts the pH rule by presentation type (non-commercially canned in specified media). The Standard does not describe testing methodology, sampling frequency, or acceptable analytical methods for determining pH; nor does it define "commercially canned." Those terms therefore remain points that require cross-reference or regulatory interpretation.

• Relationship to other instruments: The Purpose explicitly states that the definitions are "based on processing categories in Standard 1.3.1" and that the goal is to provide "specific additive permissions." The Standard is therefore a component intended to be read in conjunction with other Standards in the Code that control processing, additives and compositional requirements.

These concepts together mean the Standard provides regulatory category formation (who/what is 'fruit and vegetables' for additive-permission purposes) and a single compositional constraint for a circumscribed set of packaged presentations.

The Standard affects market participants and regulators that interact with fruit-and-vegetable products presented in the specified media or that use the Standard's definitions as the basis for additive permissions.

• Product owners and manufacturers: Businesses producing, processing, packaging or marketing fruit, vegetables, nuts, spices, herbs, fungi, legumes and seeds in brine, oil, vinegar or water will be directly affected when the product is not commercially canned. These businesses must ensure the compositional requirement (pH ≤ 4.6) is met for relevant presentations (cl 2). That includes small-scale processors producing jarred, bottled or otherwise non-canned products in the specified liquid media.

• Raw-material handlers and surface-treatment service providers: The definition of surface treated fruit and vegetables covers items "harvested, washed and treated with permitted processing aids and food additives" (cl 1). Entities that supply washing, surface treatment, sanitisation or other processing-aid services will need to align their inputs and records with the permitted processing aids regime referenced in the Purpose and clause 1, insofar as those treatments feed into products that are subject to additive permissions.

• Importers and exporters: Where the Standard applies within the applicable domestic Code, importers and exporters of jarred or otherwise non-commercially canned products in brine, oil, vinegar or water must ensure the pH criterion is met and that the product categorisation (for example, whether a product is commercially canned) is correct. The Standard does not explicitly address jurisdictional issues, but the definitional and compositional rules will be relevant at points of import control or regulatory approval.

• Retailers and wholesalers: Businesses that store and sell packaged fruit-and-vegetable products must be aware of the product build and labelling implied by the Standard because suppliers must supply products compliant with the pH limit. Retailers may be the point where non-compliance is detected; they will be exposed to supply-chain disruptions or product recalls where upstream actors fail to meet the Standard.

• Laboratories and testing services: The imposition of a pH ceiling creates demand for analytical testing services to measure pH of finished products in brine, oil, vinegar or water (cl 2). The Standard does not prescribe methods, sample sizes, or accreditation requirements; affected parties will need to decide on appropriate testing frequency and methods consistent with their obligations and with any guidance from enforcement agencies.

• Regulators and enforcement agencies: Although the text supplied does not include enforcement clauses, the Standard will be implemented and enforced by the relevant food standards enforcement authorities (not named in the text). Those authorities will determine compliance expectations, acceptable test methods and whether to treat a product as "commercially canned" for the clause 2 exemption.

• Consumers indirectly: While consumers are not addressees of the Standard, the compositional limit may change product characteristics (taste, shelf life, acidulant use) and therefore marginally affect consumer choice or product availability. The Standard itself does not create labelling obligations or consumer-facing information in the supplied text.

Who pays and who decides: The primary financial burden of compliance falls on producers and processors (manufacturers, packers, importers) who need to test and, if necessary, reformulate or acidify products to meet the pH limit. Decisions about product formulation, classification as "commercially canned" and whether to use permitted processing aids are taken by businesses under the oversight or interpretation of the applicable enforcement authority; the Standard itself does not specify which agency will administer or adjudicate these matters.

The Standard principally creates duties expressed in Clause 1 (definitions) and Clause 2 (composition), and it implicitly creates rights by way of definitional clarity that may enable certain additive permissions elsewhere in the Code.

Key duties:

• Duty to meet definitionally framed additive permissions: The Purpose states that the Standard "provides specific definitions for fruit and vegetables ... for the purpose of providing specific additive permissions." That situates an obligation for any party relying on additive permissions for products under these definitions to ensure the product genuinely falls within the defined category ("fruit and vegetables" or "surface treated fruit and vegetables") before using additives permitted for those categories. In practice, that means manufacturers must apply the definitions in Clause 1 when claiming additive authorisations available to those categories.

• Duty to ensure compositional compliance: Clause 2 sets a numeric duty: where a product is a fruit or vegetable as defined and is "in brine, oil, vinegar or water" and is not "commercially canned," the product "must not have a pH greater than 4.6." That is an affirmative requirement on any person responsible for the composition of such product to ensure pH ≤ 4.6 at the relevant compliance point(s).

• Duty to ensure processing aids and additives are permitted: The surface treated definition limits its scope to items treated with "permitted processing aids and food additives" (cl 1). The duty is to use only permitted aids and additives; the Standard references but does not list permitted items, so affected parties must consult the broader Code and related standards (notably Standard 1.3.1 as referenced in the Purpose) to determine permitted substances.

Key operational rights or entitlements:

• Right to rely on the "commercially canned" exemption: Clause 2 explicitly exempts "commercially canned fruit and vegetables" from the pH requirement. Where a product legitimately meets the accepted criteria for being commercially canned, the producer benefits by not being required to maintain pH ≤ 4.6 under this Standard. The Standard does not define "commercially canned" in the extracted text, so the right to rely on this exemption requires either an accepted regulatory definition or interpretative guidance from enforcement bodies.

• Definitional clarity that supports additive permissions: Because the Standard is designed "for the purpose of providing specific additive permissions," stakeholders have a procedural right to seek and apply additive permissions that attach to the Standard's definitions, subject to the provisions of the rest of the Code. The Standard supplies the definitional basis for those permissions.

Operational implications of the duties:

• Businesses must classify their products against the Standard's definitions and the composition clause to determine compliance obligations. Classification errors , for example, mislabelling a jarred product as commercially canned , would expose the business to potential non-compliance.

• The Standard creates a compliance duty that is discrete (one compositional metric) but comprehensive across a wide definitional field. The breadth of the "fruit and vegetables" definition means that products not traditionally thought of under that label (for example, nuts, spices, seeds) could be caught by the pH requirement when presented in the listed media, unless otherwise excluded (e.g. commercially canned).

The Standard does not set out procedural rights such as notice periods, correction opportunities, or appeal mechanisms. It is limited to definitions and one compositional requirement; enforcement, compliance processes and appeal rights (if any) are located outside the supplied text.

The supplied Standard contains no penalty provisions and no direct enforcement mechanics. The text provided comprises a Purpose statement, Clause 1 (Interpretation), Clause 2 (Composition) and some formatting placeholders; it does not specify sanctions, inspection powers, administrative fines, criminal offences, or the identity of an enforcement body.

Implications of the absence of penalties in the text:

• Enforcement must be effected through the broader statutory and regulatory framework that governs food standards. Because this Standard is an instrument within a code, compliance monitoring and enforcement will typically be the responsibility of food safety authorities and state or federal agencies empowered under the parent food standards legislation. The Standard itself does not name those agencies nor provide enforcement powers.

• Non-compliance consequences are therefore indirect in this instrument: parties that fail to meet the pH requirement or that use unpermitted processing aids will be subject to the enforcement consequences that derive from the parent regime. The Standard gives a substantive rule; incidental consequences (recall, fines, injunctions, prosecution) depend on the enforcement provisions of the statute(s) under which the Code is made enforceable.

• There is no statutory guidance within the text on evidentiary standards, pH testing methods, sample sizes, tolerances, or how to treat borderline results. Because the Standard contains only the numerical limit and the definitional coverage, enforcement will require either administrative guidance or interpretive practice from the relevant regulator to operationalise compliance expectations.

Practical enforcement risks and compliance points:

• Measurement and proof: Enforcement action will rely on measurements of pH. The Standard does not prescribe accredited methods or sampling schemes; in disputes, the absence of prescribed methods may produce contested evidence over the method chosen, the sampling point (finished product, brine, etc.), and whether the sample represents the batch.

• Classification disputes: The exemption for commercially canned products introduces the possibility of contested classification. Enforcement bodies will need criteria to decide when a product is "commercially canned" and therefore exempt. Until guidance is issued, producers and inspectors may disagree, generating compliance uncertainty.

• Additive permissions: The Standard's reference to "permitted processing aids and food additives" implies enforcement of additive permissions through the broader Code. Inspection regimes that detect unlisted or unpermitted additives will enforce those rules under the applicable statutory powers, not under this Standard's text directly.

In short, the Standard sets substantive requirements without prescribing enforcement modalities. Parties seeking clarity on penalties and enforcement must consult the enabling legislation and administrative instruments that implement the Code in the relevant jurisdiction.

The Standard is explicitly connected to other parts of the food standards architecture by text and by omission.

Explicit linkages:

• Standard 1.3.1: The Purpose states that the Standard's definitions are "based on processing categories in Standard 1.3.1." That is a direct instruction to read this Standard in conjunction with Standard 1.3.1 when interpreting what categories of processing are relevant and which additive permissions should apply. Any additive permissions or processing aid listings that are allocated by processing category in Standard 1.3.1 will therefore be applied to the items falling under this Standard's definitions.

• Additive permissions elsewhere in the Code: The Purpose indicates the primary functional reason for the definitions is "for the purpose of providing specific additive permissions." This implies that other Standards or schedules that list permitted food additives and processing aids will apply to items classed as fruit and vegetables or surface treated fruit and vegetables under this Standard. The Standard does not itself list additives; it creates the definitional basis that will determine entitlement to permissions in other parts of the Code.

Implicit interactions and cross-cutting points:

• Compositional and labelling regimes: The composition rule (cl 2) establishes a substantive requirement , pH ≤ 4.6 for non-commercially canned products in brine, oil, vinegar or water. That requirement will interact operationally with any statutory regimes governing composition, labelling, shelf-life statements, preservative use and hygienic processing established elsewhere in the Code or in enabling Acts. For example, additive permissions that permit acidulants or preservatives may be used to meet the pH requirement, but such use must be reconciled with labelling obligations and other compositional rules elsewhere in the Code.

• Food safety and public-health laws: Although the Standard does not reference public-health statutes, compositional limits are typically enforced as part of broader food safety regulation. The Standard's pH rule will be enforced alongside food safety inspection powers, recall mechanisms and other statutory instruments that regulate food safety in practice. Because the Standard itself does not enumerate enforcement powers, those mechanics must be drawn from the enabling legislation.

• Trade and import regulation: The pH requirement and the expanded definitional scope will interact with import standards and customs controls that check composition against domestic standards. The exemption for "commercially canned" products could create an interface where customs or quarantine authorities seek evidence of classification.

• Product categorisation and commercial standards: The distinction between "commercially canned" and other presentations has implications for standards that treat canning processes differently. If other instruments in the Code treat commercially canned products under different compositional or additive rules, the exemption will generate a legal seam where interpretation and administrative guidance will be required.

Cross-reference risks arising from the instrument's brevity:

• Missing definitions: The Standard does not define "commercially canned" or specify methods to determine when a product is in brine, oil, vinegar or water. Interpreting those terms requires reference to other Standards or regulatory guidance. Absent those cross-references in the supplied text, parties must rely on the rest of the Code or regulator-issued guidance.

• Application to non-traditional items: Because the definition of fruit and vegetables expressly includes nuts, spices, herbs, fungi, legumes and seeds (cl 1), the pH requirement could interact unexpectedly with standards governing those categories elsewhere; the jurisdictional reach must be verified against other Code provisions.

In sum, the Standard operates as a narrow definitional and compositional instrument that presupposes a broader Code for implementation and enforcement. For practical compliance and legal effect, stakeholders must read this Standard alongside Standard 1.3.1 and the additive-permission schedules and then with the enabling food standards legislation that confers enforcement powers.

The supplied text does not include any amendment history, dates of commencement, version numbering beyond "Standard 2.3.1" and a top-line label "Standard 2.3.1" with a meta header. The document contains a Purpose, Table of Provisions, and the two operative clauses, followed by what appears to be a blank page indicator. There are no notes of previous versions, no schedule of changes, no commencement provisions and no marginal notes indicating amendments.

Practical consequences of the absent amendment history:

• Uncertainty over currency: Because the supplied text lacks an amendment log or effective date, a user must verify whether the version supplied is the current operative version. The Standard as provided cannot be assumed to be the latest consolidated instrument without confirmation from the authoritative Code repository or the government gazette where amendments would be published.

• Need to consult authoritative sources: Where compliance, regulatory advice or litigation strategy depends on the exact text and its commencement date, affected parties should consult the official consolidated Code, the relevant regulator's website, the government gazette or statute database to confirm the Standard's currency and any subsequent amendments. The supplied text alone does not allow reconstruction of amendment history.

• Risk of untracked changes elsewhere: Because the Standard cross-references Standard 1.3.1 and other potential additive permissions, changes in those related standards could alter the practical effect of this Standard. The absence of an amendment history in the supplied text makes it impossible to infer whether interdependent standards have been updated in ways that shift permissions or obligations without consulting the consolidated instrument.

Where amendment records are required for due diligence, procurement, or compliance, the absence of an internal amendment history in this text means users must undertake external verification. The Standard as provided functions as a snapshot; it is not accompanied by the meta-information required to establish its procedural lineage.

The supplied instrument contains no litigation history or references to court or tribunal decisions. It is a standalone extract consisting of a Purpose, two short clauses and administrative formatting; there are no references to past disputes, interpretive guidance from courts, or consolidation notes that mention judicial treatment.

Implications of an absence of litigation history:

• No textual judicial interpretation in the source: The Standard itself has not, within the supplied text, been annotated by case citations or comments arising from litigation. As a result, potential ambiguities in terms such as "commercially canned," "in brine, oil, vinegar or water," or the measurement of pH remain untested in the supplied source, and no precedent is captioned in the instrument itself.

• Need for external legal research: Where stakeholders anticipate disputes over classification, measurement methods or the applicability of the pH limit to particular products, they must search case law databases, tribunal decisions and administrative determinations external to the supplied text. The absence of litigation references in the instrument means any interpretive authority will have to be sourced externally.

• Predictability and enforcement: Because there is no litigation history attached to the Standard in the provided material, regulators and businesses operate without textual markers of how contentious issues have been resolved. This increases legal uncertainty on borderline issues until either administrative guidance is issued or a court/tribunal provides a determination that addresses contested points.

In sum, the supplied extract gives no adjudicative history. Parties that require settled interpretations should undertake a separate search of judicial and tribunal databases, and consult administrative guidance issued by the enforcement authority.

This Standard is compact and therefore concentrated with a small number of practical pitfalls. The following concrete issues arise directly from the text.

1. Broad definitional sweep: The definition of fruit and vegetables explicitly includes "nuts, spices, herbs, fungi, legumes and seeds" (cl 1). A business that handles nuts or seeds may not intuitively treat those goods as "fruit and vegetables" for regulatory purposes. Under this Standard, they are included. That means a jarred spice or seed in oil or vinegar might be caught by the pH requirement. Practitioners should not assume common culinary categories align with regulatory categories in this Standard.

2. Surface-treated category scope: The defined term surface treated fruit and vegetables covers items "harvested, washed and treated with permitted processing aids and food additives" (cl 1). The phrase "permitted processing aids and food additives" is relative , the Standard does not list permitted substances. A supplier using a processing aid that is permitted for one processing category might not have permission for another, so relying on a supplier's label of "surface treated" without documentary evidence of the permissibility of the aids used is risky.

3. Presentation-based pH rule: The pH ceiling (cl 2) applies only to fruit and vegetables "in brine, oil, vinegar or water" and explicitly excludes "commercially canned" products. This creates multiple potential classification traps:

   • Is a product "in" brine, oil, vinegar or water if the liquid is incidental or only a small component of the pack? The Standard does not define the threshold for when a product is "in" a medium.
   • What constitutes "commercially canned"? The term is not defined in the supplied text. Products claiming to be commercially canned to avoid the pH rule must be able to demonstrate that they genuinely meet whatever administrative or legal definition the regulator recognises.
   • Products such as marinated olives, jarred peppers in oil, pickled cucumbers, and similar presentations will clearly fall within the clause, but borderline formats (e.g. dried herbs with a small oil coating) may be uncertain.

4. Measurement method absent: The Standard sets a pH threshold but does not prescribe a testing method, sample point (e.g. brine vs. solid), sampling regime, tolerances, or acceptable analytical standards. That creates an evidentiary gap: disputes about whether a batch complies may depend heavily on the chosen analytical method. Operators should pre-empt this by adopting robust accredited methods and retaining test records.

5. Cross-standard dependencies: The Purpose ties the definitions to "processing categories in Standard 1.3.1." Since permitted additive permissions are not in this text, compliance requires cross-referencing other Standards. Failure to consult the related Standards may lead to inadvertent use of non-permitted additives.

6. Narrow but binding rule with broad product coverage: The Standard provides one specific number (pH 4.6) which is easy to state but may require formulation changes, preservative choices, or processing changes for a wide variety of products within the inclusive definition. Small processors may underestimate the cost of meeting a single numeric limit that applies across many categories.

7. No transitional or saving provisions here: The supplied text does not include transitional arrangements for pre-existing stock or grandfathering for existing products. If this Standard was introduced or amended, absent transitional rules could impose immediate compliance costs; users must seek the full instrument or administrative guidance to determine whether transitional arrangements apply.

8. Potential for supply-chain friction: Retailers or importers accepting products from suppliers who believe themselves compliant may discover a mismatch if suppliers have interpreted "commercially canned" differently or have used unlisted processing aids. The Standard's brevity increases the probability of such misalignment unless parties document compliance explicitly.

These are concrete operational and legal points that arise from reading the Standard as supplied. None require reading outside the text to identify; they follow from the definitions, the pH rule and the notable absence of measurement, enforcement, or definitional detail for some terms.

Compliance requires a short checklist of classification, formulation, testing, documentation and cross-referencing to other Standards.

1. Classify product under the Standard:

   • Determine whether the product falls within the Standard's definition of fruit and vegetables, which expressly includes "fruit, vegetables, nuts, spices, herbs, fungi, legumes and seeds" (cl 1).
   • If surface treatments are used, document the processing steps to demonstrate the product is a "surface treated fruit and vegetables" only if the treatments are indeed "permitted processing aids and food additives" (cl 1).

2. Determine whether the pH requirement applies:

   • If the product is presented "in brine, oil, vinegar or water" and is not "commercially canned", clause 2 requires the product to have a pH not greater than 4.6. Check whether the product presentation meets the "in" threshold; where borderline, seek regulator guidance or treat the product conservatively as subject to the pH requirement.
   • If the product is commercially canned, the clause expressly exempts it from the pH limit. Obtain and retain evidence that the product qualifies as commercially canned under regulatory definitions or commercially recognised standards.

3. Establish analytical methods and testing regime:

   • The Standard provides no testing method. Implement accredited pH measurement methods for finished products that are defensible in an enforcement setting (e.g. ISO-accredited methods, validated in-house methods where permitted).
   • Define sampling protocols (batch acceptance testing, periodic testing, challenge testing) and retain records demonstrating compliance. Ensure test points are clear (e.g. whether pH is measured in the liquid medium or homogenised sample) and consistent.

4. Reformulate or acidify where required:

   • If product testing shows pH > 4.6, consider formulation changes or permitted additives that safely acidify the product. Confirm that any additive or processing aid is permitted for the product category under the Code (Purpose and cl 1 reference permitted processing aids and additives and link to Standard 1.3.1).
   • Document the additive permissions relied upon, with explicit citations to the Code provision that allows the additive for the specific processing category.

5. Documentation and traceability:

   • Keep records that show product classification, pH testing results, methods used, dates, batch identifiers and certificates of analysis. For surface-treated products, retain supplier declarations and technical data sheets for processing aids to demonstrate permissibility.
   • If relying on the commercially canned exemption, retain manufacturing process records and any evidence relied upon to show the product is commercially canned.

6. Labelling and supplier contracts:

   • Ensure product labels and supplier contracts reflect the compliance position. If an importer or retailer is dependent on supplier statements, obtain written warranties and the right to audit compliance documentation.

7. Cross-reference relevant Code elements:

   • Consult Standard 1.3.1 and the additive-permission schedules to establish which processing aids and additives are permitted for products within the Standard's definitions. The Purpose points users directly to Standard 1.3.1 for processing categories.

8. Engage with regulators where uncertainty exists:

   • Where terms are ambiguous (for example, "commercially canned") or where a product presentation is borderline, seek written guidance or a pre-market ruling from the competent authority. The Standard itself does not supply interpretative definitions for those terms.

9. Incorporate compliance costs into pricing and supply decisions:

   • Testing, reformulation and documentation create costs. Small producers should model those costs and determine whether continued production in the affected presentation is commercially viable, or whether alternative presentations or distribution channels (including commercial canning, if available and appropriate) reduce compliance burden.

10. Monitor for updates:

• Because the supplied text lacks an amendment history or enforcement notes, maintain a practice of checking the consolidated Code and regulator publications for updates to Standard 2.3.1, Standard 1.3.1 and additive-permission lists to ensure ongoing compliance.

These steps follow directly from the Standard's text: definitions (cl 1) and the pH requirement (cl 2) are the operative points. The Standard does not prescribe test methods, tolerances, or an enforcement regime, so businesses must adopt defensible laboratory methods and retain documentation to demonstrate compliance to the relevant enforcement agency.