Skip to main content

AVF Partners

Guide6 November 20267 min read

Food lot traceability for a small business without an ERP

You do not need an ERP to trace batches. Here is how a small food brand can link ingredients, batches and customers, then test it with a mock recall.

AVF PartnersUpdated 6 Nov 2026
A white framed picture
  • Australian rules ask food manufacturers, wholesalers and importers to keep a written recall plan and trace one step back and one step forward.
  • A spreadsheet with linked inputs, production and dispatch tabs can do the job when every batch has one clear code.
  • FSANZ recommends a mock recall, including traceability, once a year.

A small food brand in Australia can trace lots from ingredients to finished goods without an ERP. Under Standard 3.2.2, manufacturers, wholesalers and importers need a written recall system and must trace one step back and one step forward. A simple batch spreadsheet, your co-packer’s production records and a yearly mock recall can cover the basics.

Many small food brands want to know how to trace batches from ingredients to finished product without paying for an expensive system. For most, food lot traceability can run on a well-kept spreadsheet, clear batch codes and a co-packer that keeps good production records. What matters is being able to say quickly which batch is affected, how much was made and who received it, and that is true in Australia and in other markets.

What the law asks for in food lot traceability

In Australia, you need a written recall plan, and you must be able to trace one step back and one step forward. FSANZ’s Food Industry Food Recall Protocol (May 2023 edition) explains that Clause 12 of Standard 3.2.2 covers businesses in the wholesale supply, manufacture or importation of food. Under that clause, you need a recall system that is written down, shown to an authorised officer if they ask, and followed in a recall.

The Protocol also says every food business must be able to trace one step back. Businesses that need a recall plan must also keep records of where product went, which is one step forward. You can keep the plan electronically, but you must be able to give an officer a printed copy if they ask.

The business that runs a recall is called the sponsor. FSANZ says this is often the manufacturer, the importer or the business that owns the brand. So if your brand is on the pack, plan as if the job is yours, even when a co-packer makes the product.

In a recall, FSANZ asks the sponsor for details such as the date marking, package size, lot code, the quantity made, the date and amount released, and a distribution list in English. Your records need to produce these answers quickly.

How to set up lot tracing with a spreadsheet

A spreadsheet works when one batch code links your inputs, your production and your customers. FSANZ lists six steps for setting up a traceability system: decide the scope, choose the tracing unit, identify the information needed, set up record keeping, set up review and testing, then write it all down.

A close up of a metal shelf with boxes on it
One batch code should link the ingredient lots, the production run and every customer delivery. Photo by Arum Visuals on Unsplash.

Here is how we suggest a small brand puts those steps into practice:

  1. Choose your tracing unit. This is usually one batch or one production day. FSANZ notes that larger units make tracing simpler, but more food has to be recalled if something goes wrong.
  2. Set one batch code rule and print the code on every unit and every carton. Our guide on keeping batch codes and date marks readable covers the printing side.
  3. Inputs tab: log each ingredient and packaging lot you receive, with the supplier, date and quantity.
  4. Production tab: log the batch code, date, ingredient lots used, quantity made and quantity rejected.
  5. Dispatch tab: log each batch, the customer, the quantity, the date and the invoice number. FSANZ calls this a recall distribution register.
  6. Customer list: keep the business name, address, contact person and phone number for each customer.

FSANZ notes that most standard reports from accounting and stock systems need reworking before they are useful in a recall. It also says you must be able to sort distribution by state or territory and suburb, so add those columns now.

For cartons and pallets, GS1 Australia says GS1-128 barcodes (a carton and pallet barcode) can hold extra data such as batch number and best before date. These barcodes do not scan at the checkout. FSANZ also suggests checking that your distributors can quickly produce a list of their customers and contact them.

Which records your co-packer keeps and which you keep

In many co-packing deals, the factory holds the production records and the brand holds the sales records. Together, they make up the full chain FSANZ describes: batch histories from starting materials to finished products, plus customer details. The table below shows one common split, but your contract should spell it out.

RecordUsually held byWhat to agree
Ingredient and packaging lot receiptsCo-packerLot list for each batch, on request
Batch production recordsCo-packerQuantity made and lots used, per batch
Batch code formatBothWritten into your product spec
Import and shipping documentsImporterFiled by batch code
Stock on hand and dispatchesBrand ownerYour distribution register
Customer contact listBrand ownerKept up to date

Whether your partner only packs or also makes the product changes which records it holds. Our guide on co-packer vs co-manufacturer explains the difference. Ask how quickly the factory will send records when you request them, and write that answer into the contract.

FSANZ also advises agreeing in advance with suppliers and customers who organises a recall and who pays for it. Our guide on what recall insurance covers can help with the cost side, and our quality and compliance approach explains what we check before a factory makes a product.

How to run a mock recall and how often

FSANZ recommends a mock recall, including traceability, once a year, and a review of the recall plan at least once a year.

  1. Pick a real batch from a few months ago.
  2. Name your recall coordinator and start a timer. FSANZ notes that in a small business, just one or two people may be involved.
  3. Trace back: list the ingredient and packaging lots used. Ask your co-packer for its records and note how long they take to arrive.
  4. Trace forward: work out how much was made, how much is still in stock and how much went to each customer.
  5. Reconcile the numbers. Take the amount made, subtract what is on hand and what was shipped, and the rest is unaccounted for.
  6. Write down the time taken, the gaps you found and the fixes. File this with your plan.

If you supply a retailer, ask its supplier team which traceability records and mock recall evidence it expects, because requirements can differ. FSANZ has a food recall plan template on its website that you can use as a starting point.

This is general information. Check the official FSANZ guidance, or a licensed customs broker for import matters, for your own product.

What to do next

This week, set your batch code rule, build the inputs, production and dispatch tabs, download the FSANZ template and put a mock recall date in the calendar. Then ask your co-packer how quickly it can send batch records.

If you want a product made in Vietnam, with batch codes on every carton linked to the factory’s production records, you can start a project with us.

Written 6 November 2026.

Questions about this topic

Does a small food brand legally need a recall plan in Australia?

Yes, if it manufactures, supplies food wholesale or imports food. Clause 12 of Standard 3.2.2 requires these businesses to have a written recall system, show it to an authorised officer if asked, and follow it during a recall.

Can I use a spreadsheet instead of traceability software?

Yes. The FSANZ guidance does not name any particular software. Your records must link batches from starting materials to finished products and customers, be easy to follow, and be ready quickly when government officers ask for them.

How often should I run a mock recall?

FSANZ recommends a mock recall, including traceability, once a year, plus a review of the recall plan at least once a year.

Who runs the recall when a co-packer makes my product?

FSANZ calls the business that runs a recall the sponsor. This is often the manufacturer, the importer or the brand owner. Agree in writing with your co-packer who leads a recall, who pays, and how quickly batch records will be shared.

Sources

  1. Food Industry Food Recall Protocol (Food Standards Australia New Zealand, May 2023)
  2. Standard One-Dimensional, Linear Barcodes (GS1 Australia)

Cover photo by mockupbee on Unsplash.

Ready to make your product in Vietnam?

Tell us what you want to make. We reply within 1 business day.