Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Procurement for Kenya
Purchasing discipline, without the paperwork theatre
Requisitions, approvals, quotations, and receiving in one auditable chain — so spend follows policy and the audit file assembles itself.
Sound familiar?
If any of these ring true, you are exactly who this was built for.
Approvals by hallway
Verbal go-aheads and retro-dated signatures — untraceable when questions come.
Maverick spend
Purchases that skipped the process entirely, discovered at invoice time.
Supplier loyalty without evidence
The same vendor wins everything and nobody can show why — or why not.
Paying for what never arrived
Invoices approved against memory instead of matched against deliveries.
What you get with AWRA OpsHub
Each capability links to a deeper feature tour.
Requisitions & approval chains
Threshold-based approvals enforced by the system — your policy, running itself.
RFQs & quotation comparison
Simultaneous RFQs, timestamped responses, side-by-side comparison, recorded awards.
POs & three-way matching
Order, delivery, and invoice must agree before payment leaves.
Supplier performance
Delivery time, quality, and price stability per vendor — data at award time.
Budget controls
Committed and actual spend against budget lines — overspends blocked before they happen.
Vendor portal
Suppliers receive RFQs, submit quotes, and track orders in their own portal.
Running in the product today
- Thresholds that refuse rather than warn. Above a limit the transaction does not proceed. A warning somebody dismisses is not a control, and the difference is the whole reason to buy this.
- RFQ comparison with the losing quotes retained, and the award reason recorded at the moment of choosing — which is the single hardest thing to reconstruct afterwards and the first thing a reviewer asks for.
- Three-way matching before money moves — order against receipt against invoice, with tolerances you set and exceptions held rather than passed through.
- Supplier prequalification end to end: suppliers apply through your own public form, submissions are reviewed and approved in the system, and an approved applicant becomes a vendor record without anybody retyping a certificate.
- Supplier documents with expiry dates the system watches, held against the vendor rather than in a shared drive.
- Landed cost that stays open after receipt, so duty, clearing and freight invoiced weeks later still reach the unit cost.
- M-Pesa payment out to a vendor phone, paybill or till on your own Daraja credentials, recorded against the invoices it cleared.
More we can add — on the roadmap, and commissionable now
- Bank statement reconciliation. M-Pesa matching is real; matching a bank statement does not exist in any form. If most of your supplier payments leave by bank transfer, that reconciliation stays manual.
- Contract lifecycle management. A contract can be held as a document against a vendor. Renewal dates, obligations, milestones and variations are not modelled, so a contract register is not what this is.
- An integration with an external e-procurement or tender portal. Where a buyer requires submission through their own system, that stays a separate exercise and the two do not talk.
What we would decline, and would rather say now
- We will not decide whether a procurement was proper. The system records who authorised what, against which budget, on what evidence, and makes it retrievable. Whether that met your policy or your funder's rules is a judgement for your audit committee — and a vendor whose software issues that verdict is selling you a liability with the licence.
- We will not hide a refusal. A blocked transaction, an overridden threshold and a matched exception are all records, permanently. Buyers occasionally ask whether overrides can be made invisible to reporting; the answer is no, and if that is a requirement we are the wrong purchase.
The three items are work rather than positions, and each is commissionable now on a written specification, a timeline and a price agreed before any money moves. The evidence this is a real offer is Kenya itself: the eTIMS transmission and the maintained statutory payroll engine were both built exactly this way, because clients needed them and paid for them. We will not print a date here; we will put one in a quote.
The short version for a shortlist: the approval chain and the evidence behind it are genuinely strong, and the money side stops at M-Pesa. If your procurement pain is governance, this is the right module. If it is reconciling a bank statement against a thousand supplier payments, that specific thing is on the build list rather than in the product.
How teams get started
1
Load your thresholds
Approval bands and committee rules configured to your procurement policy.
2
Onboard your suppliers
Your vendor list imported; RFQs flow to them from day one.
3
Run purchases end-to-end
Request → approval → quotes → PO → receipt — every step on the record.
Guides from our blog
NGOs & Nonprofits 9 min
Procurement Challenges in NGOs (And Solutions)
The seven procurement problems behind most NGO audit findings — emergency purchases, quotation theatre, undocumented approvals — and the fixes that hold up in the field.
Read
NGOs & Nonprofits 9 min
NGO Procurement Policy Template (Free Template)
A complete, adaptable procurement policy for Kenyan NGOs — thresholds, committees, conflict-of-interest rules, and emergency procedures you can copy into your manual.
Read
Kenya Business Guides 8 min
ERP Pricing in Kenya: What to Expect (KES Breakdown)
License models, the implementation costs nobody quotes upfront, honest three-year totals in KES, and the questions that expose hidden pricing.
Read
Procurement Insights 12 min
Who Decides Which Department Is Spending
For most of your staff the department on a purchase request is stamped from who they are, and the request is refused when it cannot be. For an administrator it is a free choice from the whole list, and nothing records that they made it on somebody else's behalf.
Read
Procurement Insights 10 min
The Supplier Behind Your Supplier
Australia asks large buyers seven questions about their supply chains every year. Only one and a half are questions a system can answer from its own records — and a supplier register, by construction, stops at the company you pay.
Read
Procurement Insights 11 min
Quote Us for an Unspecified Quantity
The request-for-quotation form makes quantity compulsory. The API does not, on either creating or updating a line — and where it is missing, null is written. A supplier is then asked to price something without being told how much of it.
Read
Questions we are asked here
Frequently asked questions
Does this fit private companies or just institutions?
Both — the same chain (request, approve, compare, receive, match) protects a distributor's margins and an institution's compliance. Thresholds and formality scale to your policy.
Can it enforce our specific approval matrix?
Yes — approval chains are configured by amount, category, and department, so the KES 500,000 purchase takes a different path than the KES 5,000 one, automatically.
How do suppliers interact with it?
Through the vendor portal: they receive RFQs, submit quotations, and see order status. Their responses are timestamped, which quietly ends quotation backdating.
Does procurement connect to stock and finance?
Fully — receipts update inventory, matched invoices post to the ledger, and committed spend counts against budgets. Procurement in isolation is just prettier paperwork.
Watch your policy run itself
Bring one real purchase and your approval matrix — see the chain enforce it.