Food Batch Coding NZ: Design a Traceable Lot System

Food batch coding in NZ needs to connect the identity on a pack with the records behind it. A clear printout is useful, but it cannot tell you which ingredient lots were used or where finished stock went unless those connections have been recorded.

This guide helps food manufacturers and brands design or revise a lot-coding system before a launch, line change or co-packing arrangement. It focuses on choosing unambiguous identifiers and preserving their meaning through production and dispatch. A full recall rehearsal is a separate exercise.

Separate the pack code from the record system

The pack code is an entry point. The traceability system is the set of procedures and records that explains what that entry means. You need to be able to start with a finished identifier and find its production history, or start with a supplier lot and find the finished products that used it.

It is not necessary for every business document to use one identical number. A supplier delivery, an internal production batch, a co-packer job and a warehouse dispatch may each have a different reference. The useful question is whether the next person can follow the recorded connections without guessing.

FSANZ’s practical food traceability guidance recommends connections between suppliers, inputs, customers, delivery dates, batch identifiers and quantities. Its page also discusses Australian food-safety provisions; the New Zealand legal duties relevant to this guide are identified separately below.

Keep product identity and stock status clear as well. A batch reference identifies the relevant food history; it should not be relied on as the only indication that stock is awaiting a decision, held, released or rejected. Define those controls in the business’s actual system.

Check the NZ lot-identification requirements

Standard 1.2.1 of the Australia New Zealand Food Standards Code distinguishes retail sales, sales to caterers and other sales. Lot identification appears in the applicable information lists, but the rules about labels, accompanying information and exemptions differ. Start with the actual food, packaging and sales arrangement rather than assuming every transaction has the same label.

For ordinary packaged retail food required to bear a label, section 1.2.1—8 includes lot identification. Catering sales are addressed in Division 3. For packaged food covered by the “other sales” provisions, section 1.2.1—20 includes lot identification; that Division excludes intra-company transfers. These provisions need to be read with the relevant scope and exceptions.

Standard 1.2.2—3 on lot identification specifies exceptions, including an individual portion of ice cream or ice confection, and a small package stored or displayed for sale in a bulk package or container whose labelling includes the lot identification. An exception to a particular label requirement does not settle every record or traceability duty.

MPI’s guidance on food supplied to a manufacturer or processor provides a practical New Zealand starting point for that business-to-business situation. If the pack-information question is unresolved, discuss the actual product and market through AFVA’s food labelling review service.

Food Act tracing duties are wider than the label field

For food control plan operators, regulation 26 of the Food Regulations 2015 requires procedures for identifying and locating units of food, and tracing it from suppliers, while under the business’s control, and to the next supply-chain recipient other than the final consumer. Regulation 71 for National Programme operators includes corresponding duties and the records needed for identification and tracing.

Under these provisions, the tracing information must be accurate and sufficient for an effective recall. When requested by the chief executive or a food safety officer, it must be provided in a readily accessible format within 24 hours, or within a reasonable shorter period they specify. The regulations also provide for exemptions; use the requirements applying to your business.

This article concentrates on Food Act manufacturing and packing systems. Animal-product, wine, importer, exporter and customer arrangements may have additional or different requirements. It does not supply one record-retention period for every pathway.

Design clear food batch coding rules

Write the rule before choosing the printer or database field. We recommend agreeing the following points with production, quality, purchasing and dispatch staff:

• What the code identifies: define the relevant production or packing boundary, product and site. Explain what begins a new identifier, including changes in the operation that affect the history you need to distinguish.
• How uniqueness is controlled: prevent the same complete product-and-lot reference from pointing to two indistinguishable histories. Consider multiple sites, repeat runs and a date counter starting again.
• What each character means: use a code key and examples. If a date is included, state whether it refers to manufacture or packing and define the format.
• Who assigns and checks it: identify the responsible role, deputy, register and controls for manual overrides or reprints.
• Where it is used: connect consumer packs, cartons, internal records and warehouse references, including mixed-lot handling where relevant.

For illustration, a business might use P12-S1-261029-R02: product P12, site S1, a defined production date and run 02. Another system might use a sequential lot number with the details stored in a register. These are design examples, not mandatory formats or a conclusion that either fits your operation.

Do not make a code so complicated that staff cannot enter or check it accurately. Conversely, a short date alone may leave several runs indistinguishable. Test the chosen approach against the real combinations of products, sites and runs the business needs to control.

Worked example: connect the identifiers

This hypothetical example shows record connections rather than a recall calculation. The identifiers are invented solely to explain system design. They are not an AFVA client record, a required numbering system or evidence of product safety.

On a small screen, swipe sideways to view all columns. Keyboard users can focus the table region to scroll horizontally.

The map works in both directions. Starting with R02 leads to PK-88, B-204 and the input receipts. Starting with I-41 identifies B-204 and its relevant finished outputs. The record system should reveal these links; the meaning should not depend on one person recognising the code from memory.

Control split runs, repacking and co-packers

Split runs and repacking

Document the relationship when one production batch is packed in several runs, or several identified inputs feed a later batch. Do not force a one-to-one relationship into the records when the actual process is more complex. If a new identifier is assigned, retain its source links and explain the boundary it represents.

For repacking, retain the incoming food identity, repack job and resulting identifiers, with the actual quantities and disposition records. Changing the printed code does not, by itself, establish a new shelf life or erase earlier history. A coding procedure is not permission to rework, relabel or release suspect food.

Where authorised rework is part of the process, follow the separate food manufacturing rework control guide for eligibility, source-to-receiving-batch links and other controls. This coding guide does not decide whether material is suitable for reuse.

Co-packer and warehouse handovers

Agree the identifiers and returned information before the job starts. The brand’s purchase order, the manufacturer’s batch reference, a co-packer’s job number and a warehouse receipt can differ, but their cross-reference needs to be explicit. Identify who checks a mismatch and who provides the corrected record.

The handover should explain code assignment, print location, product and pack version, output identifiers, quantities and units, returns or remaining stock, and the records the business needs to retrieve. Obtain a completed example during setup. A commercial invoice may not contain all of that information.

Check the printed code and record access

Check an actual printed pack under its intended handling conditions. The Code’s general legibility provision, section 1.2.1—24, requires required label content to be legible and prominent against its background, and words to be in English. An approved artwork file does not establish that the production print is readable.

We recommend recording first-pack checks and further checks appropriate to the operation, including after relevant setup changes, restarts or code corrections. Check the assigned value as well as its appearance: the printer can produce a perfectly clear wrong code. This article does not prescribe a universal checking frequency.

Choose one real finished reference and ask an authorised person who did not assemble the records to retrieve its history and destinations. Check the reverse link from one contributing input. Include off-site records and a deputy’s access. Record gaps rather than creating unsupported historical entries.

This small retrieval check helps establish whether the design works. It does not replace a required simulated recall, its decision-making or communications. Use the mock food recall and batch reconciliation guide for the wider exercise after the system is established.

If printing or record links fail, follow the business’s actual control and correction procedure. Identify the potentially affected stock and preserve what is known while the responsible person assesses the issue. Avoid inventing a batch reference simply to make a form complete.

Before-use checklist

1. Confirm the applicable pack-information and tracing requirements.
2. Define the code’s meaning, assignment boundary, format, owner and override controls.
3. Test for ambiguity across products, sites, repeat runs and identifier changes.
4. Connect actual inputs, production, packing outputs, stock and dispatch records.
5. Agree co-packer and warehouse handovers and the returned cross-references.
6. Check actual printed codes and the records needed to interpret them.
7. Ensure authorised people can retrieve retained information when needed.
8. Document gaps and corrections, then test the affected connection again.

Common mistakes

• Printing a date and assuming the job is finished: check what history that reference retrieves.
• Reusing an identifier without a clear distinction: assess whether another person can separate the relevant product histories.
• Keeping only the final code: retain the connections when production, packing or repacking identifiers change.
• Recording dispatch totals without lot references: preserve which identified food was supplied, to whom and in what quantity.
• Leaving records with one employee or contractor: agree controlled access and deputies before the information is needed.

Prepare your traceability-system review brief

AFVA’s new food product development service expressly includes traceability and batch-coding review. Food safety and quality consulting includes traceability procedures, records and practical system improvements. Agree whether the immediate task is code-rule design, a record-link review, a co-packer handover or another defined issue.

Send the current and proposed code rules, a pack example, process flow, the relevant ingredient–production–packing–dispatch record links, sites or contractors involved and the precise retrieval problem. A redacted completed example is more useful than blank forms alone.

Consulting support is separate from registration, recognised verification, evaluation and certification. Formal engagements remain subject to the applicable recognition, scope and independence requirements.

General information only: Requirements depend on the complete food activities, products, processes, packaging, locations, sales arrangements and regulatory pathway. Use current official guidance and confirm the provisions applying to the specific business before relying on a label exception, timeframe or record list. This guide does not authorise relabelling, changing a date mark or releasing affected food.