Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
NGO inventory
Relief items, medical supplies, training materials — received against purchase orders, issued against programs, counted on schedule, and explained when adjusted.
If any of these ring true, you are exactly who this was built for.
The store card says 400 tarpaulins; the store has 260 and no explanation auditors accept.
Supplies went to beneficiaries — but proving who, where, and how many takes weeks.
Medical stock and food items expire in storage because nobody sees dates until the count.
Head office cannot see field warehouse levels, so items are re-bought while others expire.
Each capability links to a deeper feature tour.
Deliveries checked against purchase orders — short deliveries and substitutions surface immediately.
Stock issued against programs and activities, with distribution records that stand up in audits.
Cycle counts and full counts with variance explanations recorded per adjustment.
Date-tracked stock with first-expiry-first-out issue and holds for goods pending inspection.
Every field store and warehouse visible from head office, with governed transfers between them.
Follow any item from supplier receipt to beneficiary distribution — the full chain, timestamped.
Warehouses, field stores, and current stock — imported and reconciled.
One month of receipts against POs and issues against programs.
Variances explained at adjustment time — your next audit starts from clean numbers.
What NGO teams should look for in an ERP — donor fund segregation, procurement governance, asset registers, and Kenya-specific compliance — with a practical evaluation checklist.
The seven procurement problems behind most NGO audit findings — emergency purchases, quotation theatre, undocumented approvals — and the fixes that hold up in the field.
A practical system for tracking restricted funds from grant agreement to donor report — fund segregation, budget lines, burn rates, and audit-ready advances.
Yes — receipts, issues, and counts can be captured offline on mobile and synced when connectivity returns, so remote stores stay in the system instead of on paper.
Yes — batches carry expiry dates, issue logic can enforce first-expiry-first-out, and expiring stock is flagged before it becomes a write-off.
Issues can be recorded against programs, activities, and distribution points with quantities and receiving signatures — the evidence chain donors ask for.
Adjustments require a reason from your configured list and an authorized user; large variances can require approval. Every adjustment is attributable and reportable.
See receipts, issues, counts, and traceability on your own item list.