Wine Batch Traceability NZ: Linking Blending, Bottling and Dispatch Records

Wine batch traceability in New Zealand depends on the links between records. A supplier delivery, tank movement, blend sheet, bottling report and dispatch note may each look complete, yet still leave a gap if their identifiers do not connect.

This guide is for wine businesses organising an everyday record trail, particularly when wine is blended or sent to a contract bottler. It focuses on finding the source and destination of a particular wine, rather than explaining the whole Wine Standards Management Plan (WSMP) registration or export process.

What wine traceability requirements cover

Regulation 77 of the Wine Regulations 2021 requires a wine business that makes wine to identify and locate individual wines, trace the commodities and winemaking inputs used in each wine from suppliers, and trace wine to the next supply-chain recipient other than the final consumer. The information must be accurate and sufficient for an effective recall. Exporters also have traceability duties under regulation 78.

For businesses making or exporting New Zealand grape wine, regulation 79 adds the link from source vineyards through to the next recipient, and from packaged wine back to those vineyards. A finished-lot list alone therefore does not complete that trail.

Under regulation 40, winemaking operators must keep legible, accurate records demonstrating compliance with applicable requirements for at least seven years after creation. Regulation 80 requires traceability information requested by the Director-General or a wine officer within 24 hours, or a reasonable shorter period they specify, in a readily accessible format.

Your registered WSMP and applicable requirements determine the full records needed. MPI’s introduction to WSMPs explains the activities covered and notes that some wine businesses are exempt from registration. Do not assume that every storage arrangement or business has the same scope.

Build the wine batch traceability record trail

The following is a practical way to organise evidence, not a prescribed MPI form. Keep the original records and use a register or index to connect them. A tank number identifies a location; pair it with the wine identity and date so that later reuse of the tank does not confuse the history.

1. Receive commodities, inputs and bulk wine

Connect the supplier’s reference to your receipt and internal wine or input reference. For New Zealand grape wine, preserve the source-vineyard information needed for the backward trace. Keep supporting information with the receipt rather than relying on a trading name or invoice total alone.

• Record the material description, supplier, receipt date and relevant source or lot reference.
• Record quantity with its unit and the location or wine receiving it.
• Retain the documents supporting relevant origin, variety, vintage or other label statements.

2. Record blends, transfers, additions and top-ups

For each operation, make the source wine references and resulting wine reference clear. Include the date, quantities and units, relevant tank or barrel locations, and additions. Keep a readable connection when an identifier changes. A transfer entry saying only “to tank 6” may not tell a later reader which wine was transferred or what else was already there.

MPI’s Integrated WSMP internal verification guide asks about records for wine used in blends, transfers and top-ups, and adjustments made offsite. Use those questions to challenge whether the process history is complete.

3. Link bulk wine to packaged wine

Connect the wine sent for packaging to the bottling run and each finished lot created. Useful cross-references include the bottler’s job number, run date, pack format, finished-lot code, output quantity and packaging or artwork version used. Record supported samples, remaining bulk wine and other outcomes so that differences can be investigated.

One bulk wine may feed several bottling runs; one run may create several packaged identifiers. Keep these relationships visible rather than forcing every record to use one unchanged number.

A worked example of linked identifiers

Illustrative example only: these fictional references show a cross-reference method. They are not an AFVA client record, a required numbering system, or evidence that a wine is eligible for a label claim or export market.

If an input used in W-A is questioned, the same links should show the wine and packaged lots that may be affected. If the question starts with L-02, the links should work backwards without relying on someone remembering the run.

Agree the contract-bottling handover

MPI’s Integrated WSMP Model, “Taking responsibility” section explains that contracted processing needs clear responsibility and traceability. Its offsite-bottling example says the bottler operates under a registered WSMP, keeps adjustment or addition records, and provides them back to maintain traceability.

Before dispatch, agree which records will travel with the wine, which will come back, and who will resolve a mismatch. This practical handover can include:

• Your wine identity, transfer reference, quantity and intended packaging job.
• The receiving site, relevant WSMP identification and the contact responsible for the job records.
• Instructions and relevant wine information needed for the agreed work.
• The returned job report linking incoming wine to output lots, adjustments, additions and quantities.
• How any remainder, rejected stock, samples or return movement will be identified and recorded.

Keep the returned information with the source wine history. A bottling invoice confirms a commercial transaction; check whether it actually supplies the traceability detail needed. A contract does not by itself demonstrate that every step was recorded.

Connect packaged lots to stock and dispatch

Use the finished-lot reference in the stock and dispatch trail. For a practical dispatch register, link the lot, product and pack format to the quantity, dispatch date, business recipient, destination and delivery reference. Include offsite stock locations and transfers, not only stock in your own building.

Define units consistently. If the production report counts bottles and a warehouse counts cases, record the relevant pack conversion. Identify mixed-lot pallets by their contents so that a pallet reference does not hide the individual lots. Record returns and later movements against the original lot.

Keep label-claim evidence connected too: regulation 41 requires grape-wine records that allow the accuracy of vintage, variety and origin statements to be determined. Traceability records support that assessment; a lot code alone does not prove a claim. For a separate wording review, discuss the product and market scope through AFVA’s food labelling review service.

Check one complete wine record trail

Choose a real finished lot and ask someone who did not assemble the file to follow it. This is an everyday records check; it does not replace any required simulated recall or external WSMP verification.

1. Find the lot’s current location and any business recipients.
2. Retrieve the bottling report and connect it to the bulk wine supplied.
3. Follow each contributing blend, transfer and top-up back to its source records.
4. Check the relevant commodity, input and vineyard links.
5. Compare quantities using consistent units and investigate unsupported differences.
6. Check that offsite records are available and that another authorised person can retrieve the trail.

Record the gaps, the correction made and the person responsible for closing each gap. For the wider exercise of testing recall decisions, communications and product accounting, see the separate AFVA mock food recall guide.

Common record gaps and practical corrections

• Only the latest tank entry is retained. Keep dated movement history and the previous wine identity.
• The bottler uses a different code. Add an explicit cross-reference between both systems and confirm it against the returned report.
• A top-up is missing from the history. Link the source wine and quantity, then review the affected trail and any relevant claims.
• Dispatch says only “mixed pallet”. Keep the lot-level contents linked to that pallet and delivery.
• Records sit in one person’s inbox. Save them in the controlled business record system with an agreed retrieval route.

Frequently asked questions

Discuss your wine records with AFVA

AFVA’s WSMP verification support includes discussion of scope and record preparation where applicable and within recognised scope. Explain your wine activities, sites, bottling arrangements and export status when enquiring. Services depend on scope, recognition, conflicts of interest and independence requirements; consulting support and recognised verification are separate functions.

General information only: Requirements depend on the complete wine activities, products, processes, locations and markets. Use current official guidance and your registered WSMP, and confirm the requirements applying to your business before relying on a timeframe, classification or record list. Checked against sources accessed on 15 October 2026.