Mānuka Honey Batch Documentation: What Wholesale Buyers Should Verify

01 · Give the product an identity

Why batch or lot identity matters

Without a stable batch or lot identity, analytical results and traceability records are difficult to connect to the physical product. A buyer may receive a valid laboratory report, a polished specification and a shipment packing list, yet still have no reliable way to prove that the three describe the same honey.

Australian food law uses lot identification as part of food identification requirements. Under the current Australia New Zealand Food Standards Code, Standard 1.2.1 (opens in new tab) requires packaged food labels to state lot identification in accordance with Standard 1.2.2 (opens in new tab), subject to the Code’s applicable exceptions and other labelling provisions. Separately, FSANZ describes food traceability (opens in new tab) as the ability to track food through production, processing and distribution and notes its importance for recall systems.

Those legal requirements are not a universal template for a commercial batch dossier. For procurement, the practical objective is broader: preserve an identity that can be matched across the records used to approve, pack and ship the product.

02 · Separate the records

A specification, COA and batch record are not interchangeable

One of the most common procurement errors is asking for “the certificate” as if one document should prove everything. A cleaner review gives each record a defined job.

The exact record set varies by supplier, buyer, destination and contract. The table is a buyer framework, not a statement that every transaction legally requires six separate documents.

03 · Make the chain visible

Build a batch map before reviewing the detail

Before analysing test values, write the identities in sequence. A clean map is easier to audit than a folder full of files.

Not every supply chain uses all six identities. Some steps may share one lot number; others may require parent-child mapping. What matters is that the relationship is explicit and reconstructable.

Work in both directions. Starting from a carton in the shipment, can you reach the packed lot, input lot and relevant test? Starting from the laboratory sample, can you reach the finished product and the quantity released?

04 · Control the hand-off

What to verify when bulk honey becomes a packed retail lot

Private-label projects often create an additional documentation step: the analytical report may relate to a bulk honey lot while the buyer ultimately receives jars carrying a new packed-lot code. That is not inherently a problem. The risk is losing the documented relationship between the two.

A useful packing record can identify the input bulk lot, finished packed lot, date, pack size, quantity produced, packaging or artwork revision where relevant, facility or line, reconciliation of quantities and authorised release. If more than one packing run uses the same bulk lot, each finished lot should still be traceable back to that source.

Ask whether the laboratory sample was taken from the bulk lot before packing or from the finished packed lot. Then decide whether that sampling point is appropriate for the parameter and risk being controlled. The answer can differ by analyte, contract and destination requirement; do not assume one sampling point is universally correct.

05 · Treat transformations explicitly

Blends, splits, rework and repacking need parent-child logic

Traceability becomes more demanding when one lot is split into several finished lots, several source lots are combined, or finished stock is repacked. The buyer should be able to see the parent-child relationship instead of receiving a new lot number with no documented ancestry.

Where several lots are combined, do not assume the test result from one parent lot describes the final blend. Ask what sampling and release logic supports the finished lot.

06 · Connect analysis to the lot

Independent testing matters only when the sample identity is relevant

Independent laboratory testing can strengthen confidence, but the laboratory does not automatically control the whole traceability chain. The report describes the sample it received and identifies the method and result according to the report conditions. The supplier, packer and buyer must still establish how that sample relates to the commercial lot.

If laboratory accreditation is part of the buyer requirement, verify the organisation and relevant scope. NATA explains ISO/IEC 17025 testing and calibration accreditation (opens in new tab) and provides a directory for checking accredited organisations and activities (opens in new tab). Accreditation status should be read at the relevant facility and scope, not inferred from a logo alone.

For a field-by-field COA review, use the dedicated Mānuka Honey COA, Batch Testing & Traceability buyer guide. For MGO-specific interpretation, use MGO Grades in Australian Mānuka Honey.

07 · Close the loop

Connect the released batch to the shipment the buyer receives

A technically strong batch file is still incomplete for commercial use if the dispatched goods cannot be matched back to it. Shipment documents should make it possible to identify which SKU, lot and quantity left the supplier and which transaction it belongs to.

Depending on the transaction, useful identifiers can appear across the commercial invoice, packing list, carton or pallet labels, warehouse release record and transport documents. Export or import certificates are separate matters and vary by product, destination and authority; they should not be invented as a universal “export document pack”.

For each shipment, ask: Which released lot did we buy, how much of it was shipped, and can the physical cases or pallets be reconciled to the invoice and packing list?

08 · Know when the chain is weak

Batch-documentation red flags

• Different lot numbers with no mapping: the COA, packing record and shipment each use unrelated identities.
• Specification without revision control: the buyer cannot tell which version governed release.
• COA treated as a batch record: analytical findings are expected to prove source, packing and shipment history.
• Historical COA: a result from a previous harvest or lot is used for current stock.
• No bulk-to-pack link: a valid bulk result exists, but no record connects it to the finished jars.
• Blend ancestry missing: a new lot is created from several inputs without documented parent lots or release logic.
• Quantities cannot reconcile: received, packed, released and shipped quantities do not make sense and no explanation is recorded.
• Origin changes by wording: source, production and packing locations are blurred into one claim.
• Certificate bundle without ownership: nobody is identified as responsible for approving or updating the records.

A discrepancy is not automatically evidence of misconduct; it is a reason to stop, identify the missing link and resolve it before relying on the file.

09 · Make supplier review repeatable

Wholesale buyer checklist for batch documentation

Use this as a commercial review framework, then adapt it to your contract, destination, retailer requirements and risk profile.

10 · Questions buyers ask most

Practical batch-documentation questions for wholesale buyers

Are “batch” and “lot” always the same thing?

Terminology varies between businesses and systems. For procurement, the critical issue is not the preferred word but whether an identified quantity of product has a stable, reconstructable identity across the records used to test, pack, release and ship it.

Must a packed lot use the same identifier as the bulk honey lot?

No. A packer may create a new finished-lot identifier. What matters is that the parent-child relationship is documented so the finished jars can be traced back to the relevant input lot and evidence.

Can a bulk-lot COA be used for several packing runs?

It can be relevant where the packing records clearly map each finished lot back to that tested bulk lot and the sampling/release logic is appropriate for the parameter and contract. It should not be assumed merely because the honey came from the same supplier.

What should a buyer do when lot numbers differ across documents?

Do not assume the documents are unrelated and do not assume they match. Ask for the mapping record or explanation that connects source, bulk, sample, packed and shipment identities, then resolve the discrepancy before relying on the file.

11 · Current-stage disclosure

What SELVEH can state today

As at 17 August 2026, SELVEH’s first collection remains in development. This article does not represent a real SELVEH batch dossier and does not claim a final supplier, packer, batch numbering system, product specification, COA, release procedure, export shipment or available inventory.

When production is confirmed, real records should replace illustrative frameworks only after they exist and can be tied to the relevant product and lot. Until then, SELVEH will keep development-stage intent separate from completed operational evidence.

For the full documentation relationship, continue to Australian Mānuka Honey COA, Batch Testing & Traceability. For country and provenance verification, read Australian Mānuka Honey Origin & Traceability.

For a line-by-line laboratory-report review before you connect a result to a batch record, use How to Read a Mānuka Honey Certificate of Analysis (COA): A Buyer’s Guide.