Food Safety and Traceability in Fruit Packing

Quality and safety are related questions

A fruit quality specification can describe size, appearance and maturity. Food safety asks how hazards are managed through relevant activities. A visually attractive pack is not evidence of a food safety system. Discuss the procedures and records appropriate to the service, alongside the product requirements.

Ask about the working controls

Request confirmation of the relevant hygiene, cleaning, water management, pest control and handling procedures. Ask which records are available and who is responsible for checking them. The Codex Committee on Food Hygiene identifies its General Principles of Food Hygiene as a core text that includes HACCP guidance. Referring to that guidance does not certify a business.

Give traceability a practical test

Ask whether an individual dispatched pack can be linked to its source lot and packing record. Then ask how receiving, rejected fruit and any combined lots are reconciled. A lot reference is only useful if the associated records make the connection understandable. The required detail should be defined for the programme.

Read the scope of evidence

If certification is required, check the legal entity, activity, location, product scope and validity shown on the document. ISO 22000 and GLOBALG.A.P. address different forms of assurance. Neither should be claimed by a supplier without valid supporting evidence. Ken Fresh Growers has no verified certifications listed for publication.

Agree how exceptions are handled

Ask how fruit outside specification is identified and held, how the customer is notified and what happens before release. Include documentation needs in the original service brief. Clear records support an informed response to a concern; broad statements about quality cannot replace them.

Test a traceability record in both directions

Start with a dispatched carton reference and ask which intake lot it relates to. Then start with the intake lot and ask which finished packs and dispatches contain that fruit. If lots were combined, the record should explain the connection. Agree the level of detail your programme needs and who can retrieve it. This is an evaluation exercise for the proposed records, not a statement that every provider has a verified traceability system.

A record-review example: make the code answer a question

A buyer asks which source fruit went into a specific dispatch. The lot code printed on a carton is a starting point, but the supporting receiving, packing and dispatch records provide the answer. If several lots were combined, the connection should remain understandable. Agree which records the programme needs and how they can be retrieved. A traceability review should examine the connection, not merely whether a label has an identification field.

Define the question a traceability exercise must answer

Choose a specific starting point, such as a finished carton code, and state what the reviewer should be able to identify from it. The exercise might ask which incoming source portions contributed to the pack and which dispatch received it. Set the scope clearly so that an incomplete answer can be distinguished from a question that was never part of the test.

Use a redacted example if the review involves another organization’s records. The goal is to understand the connection between records without exposing private customer information. A code printed neatly on a label is only useful when someone can explain what it identifies and retrieve the relevant information.

Review split and combined lots explicitly

A source lot may be divided into several packs, or accepted portions may be combined under an agreed packing instruction. Record how those relationships are preserved. A reviewer should be able to distinguish a new packing reference from the original source reference rather than assuming that every code describes the same stage.

Try a simple example: one incoming lot is split between two customers, and one customer’s order also includes another approved source. Ask how the records show those relationships and which quantities remain attributable to each decision. This is an original review exercise, not a claim that Ken Fresh uses a particular software system or consolidation method.

Connect a quantity check with the identity check

Knowing a source name does not explain how much fruit was accepted, packed or dispatched. Use quantities to test whether the recorded movements can be followed. State the units and the measurement basis at each stage, and explain any container or packaging allowances. An apparent discrepancy may come from inconsistent units rather than a missing physical lot.

Keep samples, held fruit and separately approved dispositions visible in the review. If a figure cannot be reconciled, record the question and the person responsible for investigating it. Avoid adjusting the records merely to make the totals match; an unresolved discrepancy is more useful when it remains identifiable.

Distinguish routine records from evidence of effective control

A form can show that a check was recorded, but the reviewer should also ask what happens when the result is outside the agreed condition. Follow one example from observation to decision and release or another disposition. This tests whether the record supports action rather than simply collecting signatures.

Codex’s food-hygiene framework provides a reference for control systems and HACCP. Applying that framework requires an activity-specific assessment by the responsible people; this article does not identify universal critical control points for every fruit packhouse. A traceability exercise and a food-safety assessment are related but answer different questions.

Prepare a contact route for a later concern

A customer who identifies a problem needs to know which reference and observations to send, and who will acknowledge the report. Agree a practical contact route before dispatch. Record the consignment, affected cartons where known, assessment date and any immediate action taken by the receiver. Preserve the original description alongside later interpretations.

Do not assume the first report establishes the cause or the full extent of the issue. The responsible parties may need to review other records or obtain a technical assessment. An organized information request helps that process without promising a particular outcome or replacing any applicable reporting obligations.

Make the exercise improve the next working record

After the review, choose the specific information that was missing or difficult to retrieve. A source field may need a clearer label, a split-lot relationship may need a reference or a dispatch record may need a consistent unit. Assign the improvement and check it on a later example rather than treating the first exercise as a permanent assurance.

Keep sensitive records accessible only to the relevant parties. This guide does not prescribe retention periods, which need to be established for the actual business and market requirements. Continue to quality and standards or the export preparation guide to connect records with the wider order.

Additional questions for the order review

What makes a redacted traceability example useful?

The example should retain the relationships needed to follow the exercise while removing confidential names or commercial details that are unnecessary to the review. Use consistent replacement references so that the reviewer can still connect intake, packing and dispatch. Removing every identifier may protect privacy but also destroy the purpose of the demonstration. Agree the scope with the record owner, and keep the review focused on whether the connections can be explained. Do not ask for another customer’s full file merely to complete a general supplier questionnaire.

Should a traceability exercise be timed?

A timing target can be part of an organization’s own assessment, but the target and scope should be stated before interpreting the result. Record what information was requested, which records were available and where clarification was needed. A fast answer that identifies the wrong lot is not a useful success. Review accuracy, completeness and the usability of the decision route as well as retrieval time. This article does not prescribe a universal response time or replace any requirement applying to the actual business or destination.