Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For manufacturing & agribusiness
From raw store to finished shelf, with the margin intact
Imports costed at true landed value, quality holds that hold at 2am, and a traceability chain that recalls one batch instead of a warehouse. Material leaving the store is recorded as actual consumption charged to a job — there is no recipe to issue against yet, and you should know that before the demo rather than after it.
Sound familiar?
If any of these ring true, you are exactly who this was built for.
The maize question
"I bought 3 tonnes, milled it, sold flour — did I make money?" Answered once a year, at stocktake, with a shrug.
Margins computed on fiction
Freight, duty, and clearing never reach the unit cost — so the price list quietly subsidizes the heaviest items.
The open-door raw store
Production "takes what it needs", yields drift 3% and nobody can say where the material went.
The recall you cannot scope
A complaint arrives and the honest answer to "which batches, where?" is everything, everywhere.
What you get with AWRA OpsHub
Each capability links to a deeper feature tour.
Material issued to a job
Every issue from the raw store carries a reason and can be charged to a job at the item's cost — actual consumption, recorded as it happens. Not consumption measured against a recipe.
Waste and by-products on the books
Waste recorded against a reason at the moment it happens, by-products brought onto stock as a receipt, and high-value adjustments held for approval. Input against output is arithmetic you do — there is no yield variance report.
True landed costs
Freight, duty and clearing allocated at receiving, carried into the unit cost you price against. Margins use the real number. Recipes do not exist here, so a costed bill of materials is not something this produces.
Quality holds
Incoming, in-process, and returned stock frozen until released — enforced by the system, even at 2am.
Batch traceability
Supplier → material batch → issue → despatch → customer, in both directions, in minutes. Note the middle of that chain: there is no production run object, so the link is the issue out of the store rather than a run it was consumed by. The scope section below is explicit about it.
Procurement & suppliers
Receiving against the order with the variance on the record, plus supplier performance over time. No weighbridge, moisture or grade capture, and no yield-by-supplier reporting — both are in the scope section as builds rather than features.
Running in the product now
- True landed costs. Freight, duty and clearing allocated across a receipt by value or by quantity, written onto the batch and carried into the weighted average cost your margins use.
- 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 — it holds at 2am. Hold, release and dispose each record the quantity, the reason and the person.
- Batch and serial traceability. Every inbound and outbound movement for a batch with its source document, quantities in and out, where the remainder sits, and a recall status per batch.
- Procurement with teeth — approval thresholds, RFQ comparison, purchase orders, receiving, three-way matching and supplier on-time and quality scoring.
- Stock by warehouse and bin, blind cycle counting with valued variance, and adjustments that require a reason.
The production layer — on the roadmap, and commissionable now
- Bills of materials and recipes, with versions and effective dates, so a run is measured against a contract rather than a memory.
- Production orders and issue-against-recipe, which turns materials leaving the store into consumption with an expected quantity behind it.
- Yield and consumption variance per batch — the number a processor actually manages on. Bringing a by-product onto stock is possible today as an ordinary receipt; what does not exist is the automatic version, where a run declares its outputs and the variance against expected falls out of it. Without production orders there is nothing for that variance to be measured against.
- Committed versus available stock, so a confirmed order ring-fences the raw materials behind it.
- Weighbridge, moisture and grade capture at receiving, with supplier payment computed from the verified weight.
Every item above is work rather than a position — there is nothing in this list we would decline, which is why this page has no third column. Each is commissionable now on the same terms as everything else here: a written specification, a timeline and a price, before any money moves. Bills of materials are the right place to start, because everything else in the list measures against them. The evidence that this is a real offer rather than a sales line is Kenya, where the eTIMS transmission and the maintained statutory payroll engine were both built exactly this way, because clients asked for them. We will not name a date on this page, and we will name one in a quote.
The costing, holds and traceability layers underneath production are already built and are the harder half to get right — which is exactly why the production layer on top is a well-defined build rather than a research project. Until it ships, hold your BOMs in a spreadsheet and use us for landed cost, quality holds and the recall chain. If measured production is the reason you are buying, say so early: we will either scope it properly or tell you to buy elsewhere, and we would rather do that now than in month three.
How teams get started
1
Baseline the raw store
Items, batches and bin locations loaded, and every issue out of the store starts carrying a reason and a job.
2
Run a counted month
Blind cycle counts with valued variance, against a store that now records who took what and why. The first count usually finds the leak.
3
Cost and trace everything
Landed costs on imports, holds at receiving, and the recall drill run as an exercise.
Guides from our blog
Manufacturing & Agribusiness 9 min
Manufacturing ERP in Kenya: Raw Materials to Finished Goods (2026)
"I bought 3 tonnes of maize and sold flour — did I make money?" Recipe control, yields, landed costs, and quality holds for Kenyan processors.
Read
Manufacturing & Agribusiness 8 min
Landed Costs in Kenya: The True Cost of Imported Goods & Materials
Freight, duty, clearing, transport, and currency all belong in the unit cost — or your margins are fiction and your best-sellers may be priced below cost.
Read
Manufacturing & Agribusiness 8 min
Quality Holds & Traceability: Recall One Batch, Not a Warehouse
When the lab result fails or KEBS calls, holds freeze suspect stock in one action and the batch chain traces to customers in minutes — build it before the call.
Read
Manufacturing & Agribusiness 14 min
Production Without a Bill of Materials
No BOM, no production order, no yield variance. What a small Kenyan factory can and cannot do on that basis — and which of four kinds of factory this actually fits.
Read
Manufacturing & Agribusiness 12 min
The Dropdown That Posts Revenue
Two of the reasons on your stock-issue list post revenue and cash at the item's selling price, with no customer, no invoice and no tax. Nothing in the label the storekeeper reads says which two.
Read
Manufacturing & Agribusiness 13 min
The Cost That Was Never Work in Progress
Material issued to a job used to be expensed at once and the finished output arrived as a debt to nobody. Both are fixed. What is left is the residual between what a job consumed and what its output was priced at — and why that number is worth reading rather than clearing.
Read
Questions we are asked here
Frequently asked questions
What kinds of producers is this built for?
Kenyan SME processors and producers — millers, bakers, dairies, feed and oil processors, water bottlers, furniture and metal workshops. The common thread is raw materials transformed into products, where yields and costing decide the margin.
Do we need barcode scanners and weighbridge integration on day one?
No — start with batch numbers on paperwork keyed into the system and verified weights recorded at receiving. Hardware accelerates capture at volume; the discipline works without it and tells you when the volume justifies the upgrade.
Can it handle by-products and rework?
Not as measured production yet — both are on the roadmap. Today you can receive anything as stock and adjust with a reason, so bran, cake or offcuts can be brought onto the books by hand and rework can be adjusted back in. What is missing is the production order behind it: by-product receipt against a run, and rework re-entering as recorded input with an expected quantity to measure against. Without that the entries are bookkeeping rather than yield measurement. By-product receipt and rework sit with bills of materials and production orders as one scoped build.
How long until the yield reports mean something?
That depends on a build rather than a run-in period: recipe-based issuing is on the roadmap rather than live, and there is no yield or consumption variance report today. What is live underneath it is the harder half — true landed cost written onto the batch and carried into weighted average cost, enforced quality holds, and batch traceability in both directions. Once bills of materials and production orders ship, three to four weeks of issuing against a recipe is a fair estimate for a trustworthy baseline. Until then, hold your BOMs in a spreadsheet and use us for costing, holds and the recall chain.
Cost one product honestly
Bring one recipe, one import shipment, and one week's production — see the true margin, end to end.