Finished Goods Dispatch Checklist: 8 Checks Before a Truck Leaves a Food Factory

By Isaac Muthui, CEO, Tamalaki Business Network Ltd

The lab sheet is green. The warehouse has pallets stacked and shrink-wrapped. The driver is at the gate with a delivery note, and someone is already waving the truck through because "the batch passed."

That sentence hides a different failure. A batch can clear QA and the wrong physical stock can still leave: a held pallet pulled by mistake, yesterday's short-dated lot instead of the FEFO pick, a torn case from the return bay, or a second customer's cartons mixed onto the same flatbed. Traceability dies at the gate when release, pick, documents and the load are not checked together.

This article is for store managers, dispatch clerks, QA leads and owners of small and mid-sized food and agro factories in Kenya: dairies, millers, juice and edible-oil processors, bakeries, snack makers, honey and spice packers, and similar plants. It gives you an eight-point finished goods dispatch checklist to run before a truck leaves. It is operations guidance, not legal advice.

Why dispatch needs its own checklist

Most factories already have some form of warehouse release. The weak point is usually not the lab result. It is the hand-off between "cleared in the system or notebook" and "loaded onto this vehicle for this customer."

Public process expectations point the same way without turning this into a courtroom brief. The Ministry of Health Checklist for Food Hygiene Licensing (April 2023) expects documented process controls and a hazard monitoring system that covers handling after production. EAS 39:2001, Hygiene in the food and drink manufacturing industry: Code of practice, emphasises documented procedures and records for food handling. KEBS Standardization Mark inspections and the published STA-10 initial inspection form look for process and quality records you can show—not only a green lab sheet.

None of that replaces your HACCP plan or your counsel. It supports a floor rule: a load is finished when someone has checked the physical stock against release status, the pick list and the documents—and signed—before the truck leaves.

This checklist sits after QA hold before a batch leaves the warehouse and after label control. Release says the batch may ship. Dispatch says these pallets, for this customer, on this vehicle, are the ones leaving.

The 8-point finished goods dispatch checklist

Run these checks for every outbound load. Light loads (one SKU, one customer, ambient) may feel fast; chilled multi-stop runs need the full list. Keep answers on paper or in a system so you can show them later.

1. Is the load only released / cleared finished goods?

Status on the system or hold board must match what is physically on the pallet:

• Every pallet or carton on the load is in released (or equivalent "cleared for sale") status—not quarantine, hold, rework, returns or scrap.
• Hold tags, red tape or quarantine bays are not mixed into the pick "because the customer is waiting."
• If a pallet was released this morning and later put back on hold, it is not still sitting in the dispatch lane as if nothing changed.

A green lab sheet for batch A does not authorise pallet B from the hold bay. See the QA hold checklist for the release decision itself; this check confirms the load only contains released stock.

2. Do the lots/batches and quantities match the pick list / sales order / delivery note?

Identity and quantity must agree across pick, order and what is on the truck:

• Lot or batch codes on the cartons match the pick list (or the lots the system allocated for this order).
• SKU, pack size and quantity match the sales order and the delivery note being handed to the driver.
• Short picks and substitutions are written down and approved—not silently "made up" from a nearby pallet.

If the delivery note says 40 cartons of batch 2410-A and the truck has 35 of 2410-A plus 5 of 2410-B, you have already broken the story a mock recall will need later.

3. Is FEFO / earliest-expiry respected for the SKUs being loaded?

Where shelf life matters, the oldest suitable released stock should leave first:

• Picks follow first-expiry-first-out (FEFO) for the SKUs on this order, unless a named exception is recorded (for example a customer contract that requires a minimum remaining life and a later lot is the only one that meets it).
• Short-dated stock is not left behind while longer-dated stock ships "because it was nearer the door."
• Expiry or best-before dates on sampled cartons match what the pick list claims.

Dispatch is where FEFO either happens or becomes wallpaper. Tie this to your warehouse practice on reducing expiry and spoilage losses with FEFO and batch expiry tracking.

4. Are pack condition, seals, labels and date/lot codes intact and readable on sampled units?

Do not assume shrink-wrap equals fitness to ship:

• Sample cartons or bags: seals intact, no crushing, leaks, pest signs or wet packaging that makes the product unfit for the customer.
• Labels and date/lot codes on sampled units are present, readable and consistent with the batch you think you are shipping.
• Damaged outer packs are removed, replaced or quarantined under your procedure—not "sent as is and credited later" unless that is an explicit, recorded commercial decision.

Wrong or unreadable codes at the gate turn a later recall into guesswork. Pack identity problems that should have been caught at label control still need a last look before the truck leaves.

5. For chilled/frozen product: is the vehicle / cold chain ready where applicable?

Where the product requires temperature control:

• The vehicle is suitable (refrigerated or insulated as your product and journey require) and, where you pre-cool, the box is pre-cooled before loading.
• A temperature check is recorded at dispatch (set-point or actual box reading per your SOP)—not assumed because "the reefer usually works."
• Loading practice protects the cold chain (doors not left open longer than necessary; frozen and ambient not mixed in a way that thaws product).

Ambient dry goods skip this check. Chilled yoghurt, frozen pastry or cold-chain juice do not. If you cannot confirm the vehicle is ready, do not load "and hope the driver notices on the road."

6. Are dispatch documents complete and consistent with what is on the truck?

Paper and product must tell the same story:

• Delivery note (and invoice references where used) lists the correct customer, SKUs, quantities and, where you print them, lot or batch references.
• Customer purchase order number is present when the customer requires it.
• Quantities and lots on the documents match the physical load—not an earlier draft of the pick.

Kenyan manufacturers also need stock movements and invoices to stay aligned as eTIMS expectations tighten. A delivery note that does not match the truck is an operations problem today and a books problem tomorrow.

7. Is the destination and customer identity correct?

One unchecked flatbed is a classic mix-up:

• Pallets or zones on the vehicle are tagged or staged for the correct customer and drop.
• Two customers' orders are not interleaved on one load without clear separation and matching paperwork for each drop.
• The driver's destination and the delivery note address match what sales and the customer agreed.

Illustration (not real customer data): a mill stages two Nairobi drops on one truck. The first customer's bags are loaded; the second customer's bags are stacked behind without bay tags. At the first stop the driver offloads by count alone and leaves five bags that belonged to the second order. The first customer calls about short weight; the second about missing stock. A ten-minute bay check—customer identity on each stack, documents per drop—would have prevented both calls.

8. Has a named person signed the dispatch decision—before the truck leaves?

The load is not done when the tailgate closes. It is done when someone with authority has accepted it:

• A named person (dispatcher, store lead or QA, per your SOP) signs that checks 1–7 passed for this load.
• Record time, and vehicle registration where you capture it.
• Record sample counts or pallet IDs checked, not only a tick in a blank "OK" column.

If the only "approval" is the driver hooting and the gate opening, you do not have a dispatch control. You have a hope.

Habits that make dispatch control stick

• Separate release from loading. The person who picked should not be the only person who signs the truck out when the order is large or mixed.
• Stage by customer. Mark bays or pallet labels with customer and order before the vehicle arrives.
• Never "borrow" from hold. Urgency is not a release. Put held stock back or escalate to QA.
• Close the loop on short picks. Update the delivery note before the truck leaves; do not fix paperwork after the customer has counted.
• Tie intake and dispatch. Goods that entered through a weak supplier intake process are harder to trust at the gate; identity starts inbound.

Illustration (not real customer data): a dairy clears batch D-118 on paper. A quarantine pallet from D-117 still sits at the end of the same rack with a faded hold tag. The picker is late; both pallets look identical under shrink-wrap. Two pallets of D-117 leave on a supermarket order. The customer receives product that was never released. A status-vs-physical check at the staging bay would have stopped the truck.

Where an ERP helps

A clipboard dispatch sheet works when you have few SKUs and one gate. Pain grows with many lots, FEFO pressure, multi-drop trucks and holds that change during the day.

FactoraERP links sales orders and delivery notes to released finished-goods lots, pick lists and warehouse status so held or quarantine stock is harder to allocate onto a dispatch. FEFO allocation, lot identity on the delivery note and a recorded dispatch sign-off give you the same story in the warehouse and in a later recall. See factoraerp.com.

Free download: eTIMS readiness checklist for factories

Dispatch documents, stock movements and invoices increasingly have to tell the same story for Kenyan manufacturers. If you want a free eTIMS readiness checklist for factories, sign up for the FactoraERP Insights newsletter at https://isaacmuthui.substack.com. You will get practical operations notes for food and agro manufacturers—no spam, unsubscribe anytime.

FAQ

What is a finished goods dispatch checklist?
It is a short, repeatable set of checks run before a truck leaves to confirm the load contains only released stock, lots and quantities match the order and delivery note, FEFO is respected where applicable, pack condition and codes are acceptable, cold chain is ready when required, documents and destination are correct, and a named person has signed the dispatch decision.

How is this different from a QA hold / release?
QA hold and release decide whether a batch may be sold. Dispatch decides whether this load for this customer on this vehicle is correct. Use both: release first, then dispatch checks on the physical truck.

Who should sign the dispatch?
Usually a named store lead, dispatcher or QA person with authority to stop the gate. For mixed or high-risk loads, separate the picker from the final signer.

What if the customer is waiting and one check fails?
Stop the load, fix or re-pick, update documents, then re-check. Shipping a known mismatch to "save the relationship" usually costs more when the customer counts, rejects or traces a complaint.

Can a small factory do this without software?
Yes. Released vs hold bay markings, a printed pick list, a delivery note, a short signed checklist and vehicle/time fields cover the basics. Software helps when lot count, FEFO and multi-drop complexity outgrow paper.

---

Isaac Muthui, CEO, Tamalaki Business Network Ltd