Goods-In Inspection: A Procedure You Can Run
Almost every food or retail operation we work with has a goods-in pest procedure in its manual, and almost none of them perform it. The reason is consistent: the procedure was written to look thorough for an audit, it takes eight minutes per delivery, and the receiving bay has four trucks waiting.
A procedure that is not performed is worse than no procedure, because it creates a false record and it removes the pressure to design something workable. What follows is deliberately short enough to survive a real shift.
The ninety-second check
- Look at the vehicle interior before unloading. Droppings, live insects, strong odour, standing water, previous load debris. Ten seconds from the tailgate.
- Look at the pallet base and the bottom layer. This is where damage, damp and evidence concentrate. Twenty seconds.
- Check for damaged, wet or previously opened packaging anywhere in the load. Twenty seconds.
- Check the pallet itself: broken boards, visible boring holes, staining, mould. Twenty seconds.
- Record: accepted, accepted with note, or rejected. Twenty seconds including the signature.
That is the whole procedure. It fits on a card by the door, it does not require anyone to identify a species, and it produces a dated record for every delivery.
What to reject, and what to accept with a note
Reject outright when there is live activity in the vehicle or in the load, when there are droppings on packaging, or when food product packaging is wet or has been opened. These are not judgement calls and staff should not be asked to make them under pressure from a driver.
Accept with a note when the pallet is damaged but the product is sound, when there is minor external soiling, or when the load is warmer or damper than expected. The note matters because three notes about the same supplier in a month is a supplier conversation, and without the notes that conversation never has any evidence behind it.
The driver problem
The practical obstacle is not the inspection, it is the twenty-year-old on the receiving door being asked to reject a load from a driver who is angry and behind schedule. Unless a supervisor has explicitly authorised rejection in advance and will back it up afterwards, the answer will always be to sign and move on.
So the procedure needs one sentence that most manuals omit: who to call, by name, when something is rejected. That sentence is what makes the rest of the card real.
High-risk deliveries worth more than ninety seconds
- Rice, flour, grain and pet food in permeable sacks — the classic route for pantry moths and weevils.
- Returned or transferred stock from another site, which carries that site\x27s problems and no supplier accountability.
- Fresh produce in reusable crates, especially crates that go back and forth without washing.
- Anything that has been standing in a yard during or after rain.
One more category deserves a mention because it is invisible on a delivery note: consolidated loads. When a single truck carries stock for four customers, your pallets have spent the morning beside somebody else\x27s, and whatever was in that yard travelled with them. Consolidated deliveries justify the full check every time rather than a spot check.
Where the record lives
A goods-in log is only useful if it is in the same file as everything else. Keeping it in the warehouse office while the pest file lives with the quality manager means that when an auditor asks how a problem entered the site, nobody can connect the trend in the pest report to the deliveries that preceded it. One file, one location, and a monthly glance at both together.
What an auditor is actually testing
Auditors rarely test whether your procedure is comprehensive. They test whether it is followed, which they do by picking a date and asking for that day\x27s record, then asking the person on the door what they do. A short procedure that everybody performs passes easily; a long one with gaps in the log fails, and it fails harder because the gaps show intent.
Related reading
Storage practice after the delivery is covered in pallet management in a warehouse, and the doorway itself in retail stockrooms and delivery doors. For the audit file see HACCP pest control records and the food safety audit file. The programme itself is our factory and warehouse programme. Our parent company provides the Vietnamese-language version through its factory and business programme.
Global Pest Control is the English-language arm of Khử Trùng Toàn Cầu. We supply the goods-in card in English and Vietnamese on the same sheet, so the supervisor and the receiver are reading the same rule.
Common questions
Should we photograph every delivery?
No — that becomes a chore and then stops. Photograph only rejections and accepted-with-note deliveries. Those are the ones that ever get discussed later, and a photograph attached to a note turns a disagreement with a supplier into a short conversation.
What if the supplier disputes a rejection?
A dated record with a photograph settles it in almost every case. Where it does not, the value of having rejected is still there: the load did not enter your building. Suppliers adjust quickly once they learn that a site actually checks, which is usually visible within two months.
Can this replace a pest control contract?
No, it complements one. Goods-in controls introduction; the contract controls what is already inside and what enters through the fabric of the building. Sites that do goods-in well typically need less reactive work, which usually shows up as a smaller programme rather than no programme.
