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
In the Android app, a push for a request that is still pending carries Approve and Reject when the recipient may decide it; Reject takes the reason in the reply field. The app re-reads the approvals queue before acting, so a request already decided is never decided twice. Others get a plain notification, and the lock screen hides the details and buttons.
Every vendor says yes to "does it work offline". The word bundles six unrelated capabilities and a product can hold any subset of them. Here is the operation-by-operation list for AWRA — including the till, which keeps selling on the phone — and the questions that make every other vendor be equally specific.
Our app holds a sale, a count line, a check-in, a check-out, a transfer, an asset movement and an approval through a dead connection. The count was the hard one to bring offline — a count is not a delta, and a stock freeze is a promise — and how that was solved is the useful part for a branch pharmacy with weak signal.
The dominant payment rail across much of the continent and the worst-reconciled item on most balance sheets. Five structural reasons the statement never matches, the pattern that fixes it without an integration, and which single provider we actually connect to.
A storekeeper spends Thursday in a warehouse with no signal, and everything they do sits on the handset in their pocket. Which operations work offline — sales and counts included — and why a device reporting zero queued is worth a second look before one reporting forty.
Approve and Reject on a push notification get payments out on time, and they can also approve a record that changed, be pressed by whoever holds an unlocked phone, or show an amount on a lock screen. How AWRA builds the button, and why the approver’s phone settings are part of the control.
An app that works offline also keeps working after an account is suspended, until it next connects. The offline trust window sets how long that can be per role, and a workspace offline policy decides which work may wait in the queue and what the server refuses when it arrives.
Our scanner bridge turns a phone into a paired scanner and stores every beep as an auditable event with a device, an actor, a resolution and an exception code. It is one of the better things in the product, and it decides exactly one thing where buyers assume four.
Grants awarded in dollars, spent in kwacha, reported in a template nobody else uses, and audited two years later by someone who was not there. The reconstruction test, the advance regime that survives it, and an honest line on mobile money.
A phone number stored one way from a browser and another way from a phone is two records for one organisation. One normaliser serves all three signup routes here — and it makes the shape uniform without inventing the country nobody typed.
Three different things get sold as offline and only one is worth anything to a driver in Kitui. Idempotent replay so a lost response cannot duplicate work, conflicts surfaced rather than resolved, and device trust that expires.
The airplane-mode test, sync queues and conflict rules, two-minute capture design, and the nightly heartbeat — what offline-first actually means, and which operations survive it here.
There is exactly one mobile-money integration in this product and the supplier record is shaped around it. Everywhere that provider is not the rail, a supplier payment is something we record rather than something we operate.
The API accepts six photos on an asset movement. The phone stops at four, compresses every one, and shows you the running total in kilobytes. All three of those are the same decision about a queue row.
For installers, distributors, and service crews the office is wherever the van stopped — job evidence, traveling stock, custody, and fleet discipline in one guide.
Ugandan SMEs digitized payments a decade before operations — EFRIS pressure, the reconciliation gap, and the stock-first sequence Kampala businesses are using in 2026.
A queued approval that lost a race gets refused, and somebody has to decide whether to throw away their own capture. That decision needs both numbers on one screen — and a live connection to be worth anything.
One question can eliminate a vendor outright regardless of how well they demonstrate, and most buyers ask it last. It is not about features, price or the deadline.
The AWRA OpsHub Android app is published on Google Play, free to install, and covers inventory movement, asset custody, scanning, GPS proof and offline field work.
Deliver approvals and operational alerts to phones and browsers.
Page 1 of 6 · 121 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.