Food Product Specifications NZ: Build a Controlled Product File

A finished-food product specification brings together the identity, characteristics and agreed requirements for one product or a clearly defined product group. For a New Zealand food manufacturer or brand, its value is practical: different teams should be able to identify what is being made, which information supports it and when a change needs review.

This article explains how to build and maintain that product file. It does not provide a universal regulatory template, set safety limits for your food or approve a product for sale. A customer’s questionnaire, the printed label and a laboratory report may contribute evidence, but they do not replace a properly scoped specification.

Define the product before designing the form

Start with the product code, name, manufacturing or supplying entity, applicable site and pack configuration. Identify whether the food is ready to eat, needs preparation or is an ingredient for another business. State the intended users and any relevant restrictions without assuming the name alone communicates how the food should be used.

The FAO’s guidance on product description and intended use identifies these as preliminary steps in developing a HACCP system. Its product description covers relevant safety information, including composition, processing, packaging, storage and shelf life. This is a technical framework; the requirements applying to a New Zealand business still need separate confirmation.

Decide what the specification is for. An internal manufacturing specification may contain confidential formulation and release information. A customer version may communicate agreed supply characteristics without reproducing every confidential detail. Identify the link between them so that withholding a recipe does not conceal information the next business needs for safe handling or accurate declarations.

Choose specification fields that can be supported

Use the following structure as a starting point, then remove genuinely irrelevant fields or add product-specific ones. These are recommended headings, not a claim that every business must complete this exact form. Avoid filling an unknown field with an unsupported “standard” value.

On a small screen, swipe sideways to view all columns.

A grouped specification is useful only if the grouping remains meaningful. Separate products or add clear variants where composition, allergens, process, packaging or intended use differ in a way that affects the information. A shared brand name does not establish that all products have the same characteristics.

Connect each important field with a source and an owner

Build an evidence index alongside the specification. For each material statement, record which document, calculation, assessment or authorised person supports it. Include its product relevance, version or date and any limitations. The purpose is to make a future reviewer able to reconstruct the decision without searching through unexplained attachments.

On a small screen, swipe sideways to view all columns.

Keep source documents connected to their original scope. For a laboratory report, check the stated sample identity, method, results and conditions before using it. Do not assume that a certificate of analysis supplies a complete product description or supports a field it does not address. Similarly, a supplier ingredient specification is evidence about that input; it is not automatically your finished-product specification.

For businesses using MPI’s Simply Safe & Suitable template plan, the “Knowing what is in your food” card calls for keeping ingredient details and checking ingredient or supplier changes for allergens. Its packaging and labelling cards also connect product information with suitable packaging and customer instructions. Apply those cards within that plan’s actual scope rather than treating them as a complete manufacturing specification standard.

Keep safety criteria, quality targets and test methods distinct

Write down why each numerical limit or acceptance statement is included. It might come from an applicable legal requirement, a product-specific hazard assessment, a validated control, an agreed customer requirement or a quality target. Those sources have different purposes. Labelling every value “critical” obscures which decisions actually protect food safety.

Codex’s General Principles of Food Hygiene recommends a scientific basis for microbiological, physical, chemical and allergen specifications used for safety or suitability, with methods, limits and monitoring arrangements as appropriate. A value copied from another product does not establish that basis for yours.

Where analysis is relevant, agree what is being measured, in which units, on what sample and using which appropriate method. Clarify the sampling approach and the decision to take if a result does not meet the criterion. Obtain suitable technical or laboratory input where needed; this article does not prescribe a universal testing panel, frequency, pH, water activity or shelf-life limit.

For shelf life, connect the period with the actual formulation, process, packaging, distribution and storage conditions. An unopened-pack period and instructions after opening are different questions. Our guide to setting a food shelf life explains the separate evidence-planning work.

Approve the issue and keep changes connected

Review facts before approving the document

Have appropriate people review the fields they understand and control. Production can confirm what is made; purchasing can obtain current supplier information; technical staff can review safety and suitability; the authorised owner can release the specification. Assign roles to suit the business rather than collecting signatures with no defined responsibility.

Record unresolved items openly, with an owner and next step. A missing technical basis should not become an approved specification value simply because a customer deadline is close. Distinguish a draft for discussion from a released issue that teams may rely on.

Define what triggers a change review

Review relevant fields when an ingredient or supplier, formulation, manufacturing site, process, pack, intended use or storage condition changes. Check which other documents are affected before implementation. Depending on the change, this may include the hazard assessment, process instructions, artwork, customer data or shelf-life evidence.

Record the change, supporting assessment, authorisation and effective point. Identify how the new issue relates to stock made under an earlier version. Do not silently replace a specification and leave others unable to tell which information applied to a particular product period.

Issue the right information to each user

Provide the released version to the teams and customers who need it, using agreed confidentiality arrangements. Record the issue and any required acknowledgement without describing a sent email as customer acceptance. Keep superseded issues traceable but separated from current working information.

If the product file feeds into a retailer response, see our guide to answering a retailer technical questionnaire. That is a separate customer-response task; the specification remains the controlled product reference from which supported answers can be drawn.

A hypothetical review of a finished-product file

Hypothetical example: a food brand prepares a specification for a chilled sauce made by a contract manufacturer. Its formulation reference is current, but the draft packaging field refers to an earlier pack. The shelf-life report also identifies that earlier pack. Instead of carrying the old period across automatically, the brand and manufacturer identify the evidence gap and obtain the appropriate assessment before approving the new issue. This example provides no shelf-life recommendation and describes no AFVA client.

• Confirm the actual product and pack covered by each supporting document.
• Identify which business owns each statement and assessment.
• Keep unconfirmed characteristics visible rather than completing them by assumption.
• Connect any revised decision with manufacturing information and customer communication.

How AFVA can help with the specification file

AFVA’s food safety and quality consulting service includes product specifications, supplier quality requirements and documentation review. We can discuss a defined review of your product file and the gaps that need further evidence. Where artwork is affected, our food labelling review service addresses that separate scope. Consulting does not itself certify the product or grant official or retailer approval.

Frequently asked questions

Choose your next practical step

Select one product and trace its specification fields back to the actual supporting evidence. Resolve the highest-impact gaps, agree ownership and release a controlled issue that production and the intended customer can use confidently.

General information only: Requirements depend on the complete food activities, products, processes, locations and sales model. Use current official guidance and confirm the requirements applying to the specific business before relying on a classification, timeframe or record list.