Find answers, support paths, and rollout guidance fast
Search the same approved public knowledge source used by AwraIQ. Results stay grounded in published AWRA resources, so buyers, customers, and support teams work from one source of truth.
Product helpImplementationSecurity reviewsBilling & support
First-expiry-first-out is a sentence in a procedure manual and a suggestion at the point of issue. What decides whether it actually happens is which batch the system proposes when somebody is dispensing at four in the afternoon with a queue.
A shop sells and a store issues, and the difference decides which movements the replenishment maths can see. Why a hospital store's reorder points work when the same building's pharmacy counter stays silent — and the ward dimension you have to choose before go-live.
The generator that failed had been serviced twice in four years and nobody could say when. Maintenance as a recorded movement, the rising-frequency pattern that decides repair versus replace, and a preventive schedule that opens its own work orders.
A second shop doubles your revenue and quadruples your blind spots. What breaks when a Nigerian retailer goes from one location to several, and the controls that decide whether the third branch makes money or quietly consumes it.
EAC currencies differ in unit value by roughly thirty times, so adding two of them together produces a number that looks reasonable and is wrong by an order of magnitude. Three ways a system can answer "what did we spend", only one of them honest — and a report of ours that adds Ugandan shillings to Kenyan ones and calls a budget breached on the result.
Every supplier payment is authorised properly and recorded one at a time. There is no payment run — no way to select forty approved invoices, review them as a batch, approve the batch and pay it. The control at the end of your purchasing process is strong, and nobody ever sees the total before it leaves.
Receive more than you ordered and the system refuses, counting every earlier delivery so a split consignment cannot creep past one lorry at a time. Receive less and it never refuses at all. The asymmetry is deliberate, and the reasoning is worth more than the feature.
Vendors sell "Southern Africa" as one market. It is four buying problems wearing one label — a replacement decision in South Africa, a support-depth decision in Botswana, a currency-discipline decision in Zambia, and a record-what-happened decision in Zimbabwe.
Small money, large risk — the place where controls are weakest and leakage most common. The simple imprest system that keeps small cash honest without smothering it.
A requisition is an internal request to buy; a PO is an external commitment to a supplier. Confusing them is how organizations get bound to spend nobody approved.
This product tracks where every asset is, who holds it and what happened to it — a register built for custody. A depreciation ledger is the companion system, and we can add schedules, methods and period postings alongside it.
A till sale has no approval step to hang a lock on — the money moves and the receipt prints in the same breath. So the signature had to become its own lock: signed once, never replaced, and refused entirely once the sale has been reversed.
Stock is where most Kenyan businesses keep the largest share of their working capital and the smallest share of their attention. The six controls that account for nearly all recoverable loss, in the order they pay for themselves.
An auditor asks to see one that was refused. Our product answers that well in the two places it records decisions properly — item master changes and deletions, both with segregation of duties. In the generic workflow engine, which has by far the richer approval model, the approver receives a task whose four states do not include yes or no.
Turning stock into a tracked asset does not produce an asset. It produces an adjustment and a pending record holding what the asset would be — and the asset is created on approval, at the quantity the approver settled on rather than the one that was asked for.
Our budget module gets the hard part right: money leaves a budget when the order is approved, not when it is paid, and a cancelled order releases the commitment. What it does next is the part to know about — it works out that you are over, approves the request anyway, and sends a notification explaining why. A control refuses; this one explains.
A payment provider returns a reusable card token in the response to almost every call. Logging that response for debugging puts a live payment credential into log files, log shippers and backups — where nothing protects it, because nobody thinks of a log as holding card details.
A hold here is a rule rather than a note — held stock genuinely cannot be issued. What that gives a school laboratory, what an inspection can be shown from records, and the one gap that depends entirely on whether somebody reads their email.
A supplier sends 110 against an order for 100 and the storekeeper books in what arrived, because that is what arrived. Over-receipt is refused here by default with zero tolerance, counting every prior delivery — and short delivery is never refused, which is the more interesting half of the design.
A tenth off the price is two fifths off the profit, nothing goes missing from the shelf, and in most Kenyan shops nobody can tell you who authorised any of it. The arithmetic, the controls that exist, and the ones that do not.
A record saying "issued to J. Otieno" settles nothing. One with an approver, a location and a verification date settles most things. And the default for the most important setting gates nothing at all until you configure it.
Our asset register can tell you exactly what a departing officer holds — the list is one click away on their own record. Nothing in the process of them leaving asks the question, moving one person's custody to their successor is one action per asset, and while the incoming custodian can now sign for what they take, nothing requires them to. Three specific gaps, each of them closable with a line on a clearance form.
A credit limit is evaluated at exactly one moment. What it compares, what it snapshots onto the invoice, and what it silently clears are all worth knowing — starting with the fact that a limit of zero means no limit at all.
Page 2 of 8 · 176 articles
Still need a human answer?
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
We use necessary cookies for secure sessions. With your permission, we also use cookies and browser storage for preferences, analytics, and demo engagement. Privacy Policy
AWRA OpsHub
Cookie settings
Cookie Consent Manager
Necessary cookies stay on for login, CSRF protection, and security. You can choose the optional categories below.
Overview
General Information
AWRA uses cookies and browser storage to keep public pages secure, remember selected preferences, measure website performance, and manage demo engagement prompts.
You can choose whether functional and marketing engagement storage apply. Analytics measurement is always active in this AWRA setup.
These settings apply to AWRA public website experiences such as the homepage, feature pages, pricing calculator, blog, help center, and request-demo page. Authenticated dashboard and vendor portal sessions still rely on required security cookies.
Required
Always active
Functional
Optional
Analytics
Always active
Marketing
Optional
For more context on privacy handling, open the Privacy Policy.
Required Cookies
Required Cookies
Always Active
Required cookies and storage support basic website delivery, secure sessions, request protection, and remembering the consent choice itself.
These cannot be switched off from this manager because disabling them would break login/session behavior, form protection, or the ability to remember the privacy choice you save.
Cookie details
Session security: keeps secure server sessions working while browsing AWRA.
CSRF protection: helps verify form submissions and protect requests.
Consent record: stores the preference decision so the banner does not keep asking after a choice is saved.
Examples: Laravel session cookies, CSRF tokens, and the AWRA consent preference record.
Duration: session security can expire with the browser/session; saved consent can last longer so the same browser remembers the choice.
Functional Cookies
Functional Cookies
Functional storage improves the public website experience by remembering interface choices, helper states, dismissed notices, and short-lived interaction preferences.
Turning this off does not stop secure required cookies or analytics. It only limits optional convenience memory.
If disabled, AWRA may show some helper prompts again or forget non-essential display choices. Core public pages, contact forms, and request-demo forms still work.
Cookie details
UI preferences: remembered display choices and helper states where available.
Dismissed notices: session-level or preference-level memory for notices the visitor has closed.
Frequency helpers: optional browser storage that prevents repeated prompts when allowed.
Examples: localStorage or sessionStorage values for dismissed banners, guide/helper states, and lightweight public-page preferences.
Effect when off: AWRA avoids optional convenience memory unless it is also allowed through marketing and engagement preferences.
Analytics Cookies
Analytics Cookies
Always Active
Analytics helps AWRA understand public page performance, traffic patterns, and content usefulness so we can improve the marketing website.
This category does not by itself enable demo popups, exit-intent prompts, or advertising pixels. Those are controlled by Marketing & engagement.
In this AWRA setup, Google Analytics and Google Tag Manager measurement are treated as mandatory website measurement and remain active.
Cookie details
Google Analytics / GTM: measures aggregate traffic and page activity.
Performance insight: helps identify which public pages, docs, and demo paths visitors use.
Operational signal: supports website quality decisions without enabling demo popups by itself.
Examples: Google measurement identifiers such as GA/GTM tags and related browser identifiers set by Google scripts.
Use: page views, source/referrer trends, public content performance, and product education page effectiveness.
Marketing & engagement
Marketing & engagement
Marketing and engagement storage supports demo prompts, exit-intent prompts, campaign attribution, and future advertising pixels.
When disabled, AWRA will not auto-open demo or exit-intent popups. CTA buttons can still open a form because that is a direct visitor action.
When enabled, AWRA can remember that a visitor already saw, dismissed, or submitted a demo prompt so the same popup is not repeated aggressively.
Cookie details
Demo prompt memory: tracks whether an auto prompt or exit prompt was recently dismissed.
Demo submission memory: avoids asking again after a visitor submits a demo request.
Campaign context: keeps source page, referrer, and UTM context available for demo requests.
Examples: popup frequency caps, demo-submitted flags, engagement source fields, and UTM/referrer context.
Effect when off: auto demo prompts and exit-intent prompts stay blocked; normal navigation and manually clicked CTA buttons still work.