A container is booked, the invoice is ready and the buyer asks for the batch record behind a pallet of processed food. The operations team then discovers that the production log sits in one workbook, laboratory results sit in email and the packing list uses a different batch reference.
A food processing ERP Africa programme should prevent that moment. We help processors use ERP implementation in Africa (Odoo) to connect traceability, batch costing and export evidence before goods reach the port.
The objective is not to create another compliance folder. It is to make each saleable batch carry the records that a regulator, customs officer, buyer or auditor may request: supplier lot, ingredients, production date, quality test, expiry date, label version, certificate, invoice and shipment reference.
As of 3 October 2026, no single African food-export rulebook exists. Your controls must reflect the exporting country, the product HS code, the destination market and the certificate type.
Start with the export route, not the software
Before configuring Odoo or any other enterprise system, map each product from intake to export clearance. A frozen fruit line leaving South Africa does not carry the same document path as a semi-processed food consignment leaving Nigeria.
Create one export route record for every combination of product, country of export and destination. Include the product description, HS code, buyer specification, regulator, customs declaration, certificate type and label requirement. This gives the implementation team a defined control point rather than a broad instruction to “improve compliance”.
Step 1: Classify the product and destination
Ask a practical question first: what exactly will customs and the food regulator see on this shipment? A processor may sell tomato paste, dried fruit and a spice blend, but each can call for different evidence because the product, treatment and importing-country rule differ.
For Nigeria, NAFDAC requires an Export or Health Certificate for processed and semi-processed food. The application asks for exporter and product details, quantity, batch number, manufacture date, expiry date, pack size and consignee. Configure these fields as mandatory shipment data, because a team cannot reliably recreate them from memory after dispatch.
NAFDAC says exporters should apply at least three weeks before the intended export date. Build that lead time into the sales and shipping workflow, because NAFDAC will not approve products that have already left Nigeria.
For Ghana, the Food and Drugs Authority export process calls for a letter of intent, packing list, commercial invoice, FDA product-registration certificate, certificate of analysis and, where applicable, a phytosanitary report. The consignment also needs an approved export permit and a Manufacture and Free Sale Certificate. Product registration alone does not authorise the export.
Ghana Customs adds a second track. Exporters register with the Ghana Export Promotion Authority, complete the Bank of Ghana FXD Form A, lodge the declaration through UNIPASS/ICUMS, obtain a bank Letter of Commitment, attach transport, invoice and packing documents, then present goods for export examination. Ghana requires declarations even for non-dutiable exports, so do not treat a zero-duty shipment as declaration-free.
In South Africa, exporters register with SARS and lodge a Goods Declaration unless a specific exemption applies. Processed-food exporters should retain HACCP and traceability records, product export-standard data, packing and marking records, plus inspection certificates issued through DALRRD and its assignees.
Build batch traceability that an export officer can follow
Traceability fails when the business treats it as a warehouse task. Warehouse movement matters, but export evidence must join raw-material lots, production batches, laboratory results, approved labels, certificates, invoices and customs declarations.
Step 2: Set the batch record before production starts
Assign a unique internal batch reference when production begins. Link it to every ingredient lot consumed, the production line, production date, planned quantity and quality-release status.
At goods receipt, record supplier identity, supplier lot, ingredient description and expiry information where relevant. During production, record the quantity issued and the output produced. This lets the business answer two separate questions: where did this batch go, and which inputs went into it?
The step teams often skip is label control. Store the approved artwork or label version against the batch and destination market, because the label seen on the carton must match the evidence in the export file.
Nigeria gives this issue added weight. Since 27 January 2025, NAFDAC’s semi-processed-food export-labelling guideline has required mandatory product information. Where a label appears solely in an importing-country language, it must state “EXPORT ONLY”, and the exporter must support it with a sworn undertaking that the product will not enter the Nigerian market.
Do not use one generic label field for all markets. Create a controlled label approval step that records the destination country, language, version number and the person who approved release.
Illustrative example: a Nigerian dried-food processor
Take a processor producing dried vegetable ingredients for two overseas buyers. One buyer requests English packaging, while the other supplies packaging only in its domestic language. The company should create separate label versions and block picking until the production batch carries the correct destination label record.
If the second shipment originates in Nigeria, the file also needs the “EXPORT ONLY” statement and the sworn undertaking described by NAFDAC. The operational cost may be a few hours of document review before loading. The alternative can be a shipment held while the team searches for a label approval that never entered the system.
The better judgement call is to configure this control only for export-only foreign-language labels, not for every domestic carton. That keeps the workflow proportionate while protecting the specific NAFDAC requirement.
Make batch costing useful to finance and operations
Export compliance and batch costing use much of the same data. Ingredient lots, yield, packaging, rework and freight documents can tell finance what a batch cost and tell compliance what the batch contained.
Step 3: Record actual inputs and yield variance
Set a standard recipe or bill of materials, then record actual material issues against each production batch. Capture packaging separately where the destination buyer requires specific cartons, labels or marking.
Track expected output against actual output. A yield difference affects margin, but it can also flag a traceability problem when the production record cannot account for material consumed.
Take a retailer with twelve staff and a US$40,000 monthly payroll that also repacks imported ingredients into export cartons. If a batch uses US$8,000 of ingredients and packaging but the team posts only the finished-goods total, management cannot see whether a label change or production loss caused the margin decline.
The processor should record ingredients, packaging and production loss against the batch before invoicing the export sale. This does not replace a finance review, but it gives finance a defensible starting point for batch profitability. If the enterprise has only occasional export consignments, do not build a complex cost-allocation model first. Start with materials, packaging and measurable production variance, then add labour and overhead rules when managers use the reports consistently.
Step 4: Release stock only after quality and document checks
Create a release status that distinguishes produced stock from export-ready stock. The stock becomes export-ready only when quality results, label approval and required certificate requests are complete.
For Ghana, attach the certificate of analysis and FDA product-registration evidence to the relevant export file. For a product requiring phytosanitary evidence, add that report as a separate checklist item rather than assuming it applies to every processed food item. The applicable requirement depends on the product and shipment.
South African processors should retain the packing and marking records alongside product export-standard data and inspection evidence. South Africa’s Department of Agriculture published July 2025 export-certificate formats for frozen and canned fruit and vegetables, which makes certificate version control a practical necessity for processors in those categories.
Connect origin evidence to AfCFTA decisions
A preference claim can improve a buyer’s landed cost, but only if the exporter can support origin. Do not make an AfCFTA origin claim because the goods shipped from an African country. Preserve the bills of materials, supplier-origin information and processing evidence that support the claim.
Step 5: Put origin evidence inside the batch file
For each ingredient, capture the supplier, country of origin and supporting supplier documentation where the preference analysis needs it. For each production batch, retain the transformation or processing record that connects those inputs to the finished product.
In South Africa, SARS made AfCFTA exporter and approved-exporter applications available through SARS RLA from 1 November 2025. Traders must register as exporters or producers to trade under AfCFTA. Store the relevant registration and origin-supporting records against the export route, because an origin preference without supporting evidence creates a customs risk.
Illustrative example: a South African canned-food exporter
Consider a canned-food producer supplying a regional buyer under an AfCFTA preference claim. The commercial team sees a tariff advantage and wants to confirm origin on the invoice, but procurement cannot identify the origin of a key ingredient lot.
The right response is to pause the preference claim for that shipment until the business can support it. The company may still export under the normal customs process, subject to the applicable requirements. On the next purchase cycle, procurement should make supplier-origin documentation part of the approved supplier file.
That decision may protect a single shipment’s timing, but it also prevents the business from creating a pattern of unsupported claims. Finance should quantify the preference value before investing in detailed origin controls for every low-volume product line.
Set implementation ownership and evidence rules
ERP implementation succeeds when each record has an owner. Compliance cannot repair missing production data at the port, and finance cannot calculate a reliable batch margin from incomplete issue records.
Assign procurement responsibility for supplier and ingredient data. Give production ownership of batch creation, actual consumption and yield. Quality should own test results and release status, while export or logistics personnel should own certificates, customs files and shipment milestones.
Run a monthly exception report before peak shipping periods. Look for batches without expiry dates, shipments without linked batch numbers, export orders without required certificates, and origin claims without supplier documentation.
Keep evidence for the period required by the applicable regulator, customs authority, customer contract and tax rules. The sources above do not set one universal retention period, so M&J recommends that each business confirm this point by jurisdiction before publication or configuration.
The official sources supporting these controls include NAFDAC in Nigeria, the Ghana Food and Drugs Authority, Ghana Revenue Authority Customs, SARS and South Africa’s Department of Agriculture, Land Reform and Rural Development. Their requirements change, so the compliance lead should review country rules before each major system release.
Frequently Asked Questions
Can one ERP setup cover food exports from Nigeria, Ghana and South Africa?
Yes, one enterprise platform can hold shared batch and costing controls, but each country needs its own export route, document checklist and approval rules. Nigeria’s NAFDAC certificate process, Ghana’s UNIPASS/ICUMS declaration process and South Africa’s SARS Goods Declaration process do not follow one identical sequence.
What records should a food-processing batch contain?
At minimum, retain supplier and ingredient lots, production details, quality-test results, batch number, expiry information, label version, packing records, certificates, invoice and shipment reference. These records connect the physical product to the export declaration and buyer documents.
Does a Ghana FDA product-registration certificate allow export automatically?
No. Ghana’s FDA export process also requires an approved export permit and a Manufacture and Free Sale Certificate, alongside documents such as the commercial invoice, packing list and certificate of analysis.
When should a Nigerian exporter apply for a NAFDAC Export or Health Certificate?
Apply at least three weeks before the intended export date. Do not wait until after dispatch, because NAFDAC states that it will not approve products already exported.
A food processing ERP should make the export file complete before the truck reaches the gate, not after the buyer asks for proof. Speak With Our Team or visit the ERP implementation in Africa (Odoo) hub page to plan your compliance and traceability controls.
