Manufacturing ERP in Kenya: Raw Materials to Finished Goods (2026)
From raw materials at the gate to finished goods on the lorry — what Kenyan processors and producers need from an ERP: recipe control, yield tracking, landed costs, and quality holds.
A trader's inventory question is "how many do I have?" A manufacturer's is harder: "I bought 3 tonnes of maize, milled it, and sold flour — did I make money?" Between the purchase and the sale sit yields, waste, rework, packaging, power, and a dozen places where margin evaporates without a record. Kenyan processors — millers, bakers, dairies, feed makers, oil pressers, furniture workshops — mostly answer the question once a year, at stocktake, with a shrug. The ones that grow answer it weekly.
The five questions a manufacturing system must answer
- What does one unit really cost? Materials at true landed cost, plus yield losses, packaging, and direct overheads — not the supplier invoice divided by optimism.
- Where did the raw material go? Issued to production against a recipe, with the variance between expected and actual consumption visible per batch.
- What did this batch yield? Input weight vs output units, batch by batch — the number that separates a good week from a bad one.
- Can I trace it? From supplier delivery through production batch to the customer who bought it — mandatory the day a quality complaint arrives.
- What is committed vs available? Raw materials already earmarked for confirmed orders are not "in stock" — selling them twice is how delivery promises die.
Recipe (BOM) control: the production contract
The bill of materials — 100kg flour + 2kg yeast + 1.5kg salt → 260 loaves — is not documentation; it is the contract production is measured against. Every production run issues materials against the recipe, and the variance report asks the only question that matters: why did this batch consume 8% more than the recipe says? The answers (moisture, spillage, theft, a wrong recipe) are all fixable — once they are visible. Without recipe-based issuing, raw material stores leak with perfect deniability.
The margin killers, ranked
| Killer | How it hides | The control |
|---|---|---|
| Yield drift | Output per input slides 2–3% and nobody baselines it | Yield per batch, charted weekly against standard |
| Understated landed costs | Freight, duty, clearing costs never reach the unit cost | True landed cost per receipt — see the dedicated guide |
| Waste & rework unrecorded | Damaged output quietly re-enters or exits the line | Waste and rework as recorded transactions with reasons |
| Raw store shrinkage | Bulk materials shrink between weighbridge and store | Receiving by verified weight; issues against recipes only |
| Packaging as an afterthought | Bags, labels, bottles bought ad-hoc at spot prices | Packaging in the BOM, bought on contract like any material |
Agribusiness has a weighbridge problem
When raw material arrives by the lorry-load — maize, milk, cane, sunflower — the receiving record is only as honest as the weighing. Verified weights at receipt, moisture adjustments recorded, and supplier payment computed from the system's number, not the transporter's manifest: this single discipline often recovers more money than any other in the sector.
Quality holds: stop bad stock from moving
Incoming materials pending inspection, batches awaiting lab results, returned goods under review — none of these should be sellable or issuable while undecided. Quality hold status freezes stock in place until released, and batch traceability means a failed result recalls one batch, not a warehouse. For food and feed processors, this is the difference between a contained incident and a brand event — the full treatment is in our quality holds guide.
The evaluation checklist
Make vendors demonstrate
- A production run: materials issued against a recipe, output received, variance reported.
- A landed cost: freight and duty allocated to a receipt, unit cost updated.
- A quality hold placed at receiving and released after inspection.
- A trace: this finished batch → its material batches → their suppliers, in one query.
- Committed vs available stock with two confirmed orders against one material.
- The weekly pack: yields, variances, waste, and margin per product — generated.
Then the standard Kenyan diligence applies — the provider questions and the three-year cost math. For how AWRA handles all of it, see manufacturing ERP for Kenya.
What AWRA OpsHub does today
- Landed cost on receipts — freight, duty, clearing and transport captured per purchase order, allocated across the lines by value or by quantity, written onto the batch and carried into the item's weighted average cost.
- Batch, lot and serial tracking — expiry date, supplier and originating purchase order recorded on every batch, with serial numbers where you need them.
- Quality holds that are enforced, not advisory — quarantined, inspection-pending, damaged, expired and returned stock is excluded from issuing and selling by the allocation query itself. Hold, release and dispose each record the quantity, the reason, a note and the person who did it.
- Batch traceability screens — per item, per batch and per serial: every inbound and outbound movement with its source document, total in, total out, and exactly where the remainder is sitting.
- Procurement with teeth — requisition, permission-gated approval, RFQ comparison, purchase orders, receiving and three-way matching, with supplier on-time rate, quality score and pricing trend tracked per vendor. The teeth are at receipt and payment: an over-delivery is refused at the bay, and a mismatched invoice cannot be paid without a written override.
- Stock by warehouse and bin location, blind cycle counting with valued variance, and adjustments that require a reason.
- Double-entry accounting, a cross-module Payments Register, and Kenyan payroll on date-effective PAYE, NSSF, SHIF and housing-levy rules.
More we can add to your workspace
- A bill of materials. A BOM or recipe with a version and an effective date — the entity itself, which the rest of this article hangs on.
- A production order and an issue-against-recipe. Materials leave the store as a stock adjustment or a transfer, not as consumption measured against an expected quantity.
- A yield and a consumption variance. Expected-versus-actual is the entire point of a recipe, and there is nothing here to compute it from.
- A committed-versus-available. The `reserved` and `allocated` statuses exist as labels, but nothing sets them — a confirmed order does not ring-fence the raw materials behind it.
- A finished-goods cost built up from inputs. Landed cost tells you what a raw material cost; nothing rolls that into a made product.
- A weighbridge, moisture or grade capture at receiving.
The six-item checklist in this post is the right checklist — so score us with it honestly. We pass the landed cost, the quality hold and the trace. We fail the production run, the variance report and committed-versus-available. Of the five questions a manufacturing system must answer, we answer two and a half. If you are a processor whose margin lives in yield, that is not good enough yet, and you should say so to us rather than discover it in month three.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsAnswer the maize question weekly
Landed costs, batch and serial traceability, enforced quality holds, and procurement whose refusals bite at receipt and at payment — three of the six checklist items above, honestly scored. Recipes, runs and yields are not built.
See AWRA for manufacturingFrequently asked questions
We are a small workshop, not a factory. Does this apply?
The principles scale down cleanly: a furniture workshop issuing timber against a job, a bakery issuing flour against the day's production — recipe-based issuing and yield awareness pay at any size. What scales with you is how much of it is automated versus reviewed weekly by hand.
Our recipes are trade secrets. Who sees them in the system?
Nobody, because the system does not hold them — as the honest note above says, there is no recipe entity, so there is nothing here to protect or to leak. Role-based access does govern who sees item costs and margins, which is the adjacent question people usually mean. If you want the formulation itself under access control rather than in one person's head, that is a real requirement and this is not yet the product that meets it.
How do we handle by-products (bran from milling, whey from dairy)?
Record them as secondary outputs of the production run with their own stock and value. By-products sold off-book are one of agribusiness's classic leaks — bran revenue alone often surprises millers who start recording it.
Batch tracking feels heavy for daily production. Is it worth it?
Size the batch to your reality — a day's run can be one batch. The weight is administrative only until the day a customer complaint, a failed test, or a KEBS query arrives; then one-batch recall versus total recall pays for years of the discipline in one afternoon.
