A food business can know how many cartons are in its store and still be unable to identify which delivery they came from. Batch traceability answers a different question from stock valuation: where did this particular food come from, what happened to it here, and where did it go? Those links become important when a supplier flags a lot, a customer reports a problem, or a delivery contains inconsistent labels.

Start with the Inventory Calculator and Local Stock Tracker for product quantities and input-based stock values. Keep a separate batch register and movement log alongside it. The tracker provides local SKU and category records, backups and exports; it does not automatically connect supplier lots, production batches, expiry dates or customer deliveries. This guide explains the records to prepare before choosing a specialist traceability system.

Sources reviewed: October 2, 2026. This is an operational preparation checklist. Codex principles and the Ghana and Nigeria references below have different scopes and original publication dates. Confirm requirements for your product, activity and destination with the responsible authority. A complete spreadsheet is not a food-safety approval, a product registration or permission to sell recalled goods.

Define the job your records must do

The Codex traceability principles, CXG 60-2006, describe following food through specified production, processing and distribution stages. They identify the ability to establish where food came from and where it went as a traceability objective. They also explain that tracing contributes to food-safety action when combined with appropriate controls; tracing alone does not make food safe.

Write down your own operating boundary. A retailer receiving sealed packs needs a different record design from a bakery mixing ingredients or a wholesaler splitting deliveries between shops. List the activities actually performed: receive, store, open, combine, repack, manufacture, transfer, dispatch, return and dispose. Each activity that changes identity or ownership needs a reliable link.

Choose a responsible person and a deputy. Specify who records a delivery, who checks missing information and who can authorise a stock hold. Keep those responsibilities usable during absence or a power interruption. A register that only one person understands creates a weak handover even if its entries are technically complete.

Keep product, supplier lot and internal batch separate

A SKU identifies the product your business tracks. A supplier lot identifies a particular group supplied or produced upstream. An internal batch identifies your own processing or repacking group. An invoice identifies a commercial transaction. These references may appear on the same record, but they are not interchangeable.

Preserve the supplier's lot exactly as shown, including letters, leading zeros and separators. Do not overwrite it with an easier shop code. If an internal reference is needed, store both references and their relationship. Check spreadsheet settings so a code is not silently converted into a date or a number.

Record the pack size and unit as part of identity. Cases, individual packs, kilograms and litres cannot be combined as if they were one quantity. When staff break cases into individual units, retain the actual conversion from the product specification. Avoid guessed conversions or a default pack size that belongs to another product.

Photographs of labels can help resolve transcription queries, but make them supporting evidence. Give each photograph a record reference and protect any personal details visible on the paperwork. A folder of unlabelled images is difficult to search and does not replace a structured batch register.

Capture the receiving evidence before stock is mixed

At receipt, compare the actual goods with the delivery note and purchase record. Record the delivery date, supplier identity, product description, lot or batch, labelled dates where applicable, quantity and unit. Include the receiving location and the person who completed the check. Keep invoice and delivery-note references together so the goods can be traced without guessing which purchase they belong to.

Record groupPractical fieldsWhat the link answers
SupplierSupplier reference, contact route, delivery-note numberWho supplied the affected goods?
Product identitySKU, description, pack size, original lot codeWhich product and lot are involved?
ReceiptDate, quantity, unit, location, checkerWhat entered the business and where?
DecisionAccepted, held or rejected, reason, reviewerWas the product available for use?
DocumentsInvoice, label image, applicable quality evidenceWhere is the supporting material?

Make missing lot information visible. Ask the supplier for the correct identifying evidence and use the business's receiving and hold procedure while the query is resolved. Do not invent a manufacturer's lot or assume that all deliveries received on one day belong to the same batch. Mark a correction with its source and date.

Condition checks belong beside traceability records, with clear limits. Record damage, broken seals or the relevant measurements required by your product-specific procedure. This guide supplies no universal storage temperature, shelf life or acceptance threshold. Those decisions need the appropriate specification and qualified food-safety advice.

Link every batch to a location and status

Identify the physical storage location in terms staff can find: room, shelf, bin or clearly designated holding area. Update the movement record when stock changes location. Keep different supplier lots distinguishable until your process intentionally combines them, and retain the connection if stock is divided across several locations.

Separate available stock from held, rejected, returned and disposal-pending stock. A quantity in the building is not automatically a quantity that can be sold. Use physical identification and an authorised release procedure as well as the record. A spreadsheet status alone cannot stop someone picking from an unmarked shelf.

Use labelled date information and the applicable product procedure when planning rotation. Where an expiry-based picking rule is appropriate, organise the work around the actual dates and any holds. Do not treat first receipt as proof of earliest expiry, or relabel a manufacturer's date to fit a stock-control routine.

Preserve the links when you process or repack

For an internal production batch, link the output reference to the actual ingredient lots used, quantities issued, production date and relevant process records. If several ingredient lots enter one batch, keep all the links. If one ingredient lot enters several output batches, retain each destination. A product name without its lot loses this connection.

Include packaging references where relevant. A packaging or labelling problem can require a different investigation from an ingredient problem. Nigeria's NAFDAC food GMP guidance discusses lot identification and the correlation of finished-product packaging with packaging deliveries. Its recall section connects raw materials, packaging, processing data and laboratory results.

Keep rework, leftovers and part-used materials identifiable under the approved procedure. Record what was returned, its status and where it was used next. Do not hide a missing link by assigning everything to the latest batch. When the relationship cannot be established, record the uncertainty and escalate it through the quality process.

Keep recipes and process specifications versioned separately from the movement log. The log shows what happened; the approved specification shows what should happen. A change to an ingredient, label or production method should not erase evidence of the earlier version.

Record the next destination when goods leave

For business-to-business deliveries, connect the dispatched lot to the recipient, delivery date, quantity, unit and dispatch document. Record partial deliveries and transfers between your own branches. A sales total by product cannot establish which customer received a particular lot when several lots were available.

For retail sales, establish what records are appropriate for the activity and legal requirements. Do not collect unnecessary customer identity details merely to make a register appear complete. Anonymous retail distribution may require different recall communication from a delivery to a named distributor. Agree that boundary with the responsible authority and your food-safety adviser.

Returns need their own entry. Preserve the original dispatch reference where it can be established, the quantity returned, condition observations, return date and decision. Do not automatically put returned food back into available stock. Physical handling and disposition must follow the applicable procedure.

Reconcile quantities without manufacturing precision

Reconcile each batch using a consistent unit. The starting relationship is opening quantity plus receipts or production, less dispatches, consumption and documented losses, equals the expected balance. Compare that balance with the physical quantity and record the difference. This is record arithmetic, not evidence that the food is safe.

For processing, material conversion, moisture changes and yield can make a simple input-to-output comparison inappropriate. Use the documented process basis instead of forcing raw kilograms to equal finished packs. Record units and conversion assumptions explicitly, and ask the responsible production specialist to review unexplained differences.

Investigate missing stock, duplicate receipts, unrecorded branch transfers and wrong pack conversions before changing a balance. Preserve the original entry and the reason for any adjustment. An unexplained difference remains an open issue, rather than becoming an invented loss figure used to close the worksheet.

Use country and product guidance correctly

Ghana's FDA Market Control page lists recall initiation and monitoring among its enforcement activities and links the product-recall guideline. The linked guideline effective August 7, 2023 covers FDA-regulated products. It calls for records of recall notices, available stock and stock returned from outlets, and addresses checking whether affected outlets received notifications and took action.

Nigeria's NAFDAC bread-manufacturing facility guidance provides a specific food-sector example: its complaint and recall section links production batch history with distribution records. That is a bakery reference, not a claim that every food activity follows identical requirements.

Keep a short requirements register containing authority, product category, activity, document title, document version, source URL and date checked. Check separately for export destinations and buyer specifications. Do not apply Ghana's recall classifications or a Nigerian bakery procedure as an Africa-wide rule. Where documents differ or a later rule may apply, obtain clarification before relying on a deadline or disposal instruction.

Test retrieval before an incident

Run a clearly labelled internal tracing exercise with an existing batch record. Identify its supplier evidence, current locations, linked production outputs and recorded recipients. Check whether someone other than the usual record keeper can retrieve the documents. Do not send a simulated recall notice to customers or regulators without an approved exercise plan.

Measure your own retrieval time and list gaps rather than claiming a universal pass mark. Check whether quantities reconcile, contacts are current and label images remain readable. Distinguish a missing record from stock already sold through anonymous retail channels. Agree corrective actions, owners and completion evidence for each gap.

If a real supplier alert or suspected food-safety issue arrives, preserve the notice and affected identifiers, follow your hold and escalation procedure, and obtain appropriate regulatory and professional direction promptly. A rehearsal checklist does not replace required notifications, a recall decision, hazard assessment or authorised disposal.

Use local tools with an honest boundary

The inventory tracker can support an accompanying stock summary. Its optional SKU field can hold a user-chosen reference, but it has no dedicated traceability relationship engine. Do not describe a manual code in that field as automatic batch control. Keep the authoritative supplier, processing and dispatch links in a suitable register or verified specialist system.

Export a local backup after meaningful updates and store it securely with the related records. Test restoration using a copy before depending on it. Limit access to supplier and recipient contact details, avoid putting them into public links, and agree retention with applicable requirements. Device-local storage still needs protection and recovery planning.

Use the inventory reorder-point guide when you need purchasing assumptions; it solves a different job from lot tracing. The NAFDAC registration checklist helps organise a separate product-registration handoff. Neither guide turns a stock export into regulatory approval.

Frequently asked questions

Does a stocktake establish food traceability?

No. A stocktake counts what is present. Traceability also needs links to supplier lots, relevant internal processing and recorded destinations.

Can an invoice number replace a manufacturer's lot?

Keep both. An invoice identifies a transaction and may contain several lots; preserve the lot shown on the product or verified supplier record.

Does AfroTools automatically manage recalls?

No. The inventory tracker supports local stock records and exports. Batch relationships, hold decisions, notifications and recall actions require separate procedures and responsible review.

How long should these records be kept?

Confirm the period for your jurisdiction, product, activity and contracts. This guide does not impose a single retention period across African food businesses.

Idris Diallo

Editorial pen name. This byline covers AfroTools money, agriculture, energy and household guides. Each guide carries its own sources and review date where current rules or prices matter.