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
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
A quotation commits you to nothing and carries six fields describing tax and currency. A credit note reverses a taxable supply and carries none of them — no tax split, no currency, no line items. What that costs a single-country business is almost nothing; what it costs a group trading across four EAC currencies is an ambiguity on every unapplied credit.
The purchase order goes out on Tuesday. The same item is sitting four kilometres away, above what that branch needs, and has been since March. What the balancing calculation compares, why an item with a reorder point of zero produces no suggestion in either direction, and when buying is still the right answer.
A batch with four months left is stock you can sell if you move it now. A batch with four days left is a write-off that has not been declared yet. Most pharmacy systems hold both as the same number, and the day the difference becomes visible is the day it stops mattering.
A reorder level is two guesses: demand before the next delivery, and how long the delivery takes. How predictive levels work both out per warehouse from what actually happened, at a service level you choose, and where a person corrects a supplier lead time the history learned from two favours.
Our demand forecast adds twenty-five per cent in March, June and December — three Gregorian months written into the code, identical for every customer in every country. In a market whose largest demand event moves eleven days earlier each year, that is not a small approximation.
A retail or distribution chain that crosses East African borders faces the same shrinkage and thin margins in every market — plus currencies, corridors and connectivity a single-country tool never planned for. What it takes to run one chain across the region.
A stock item can be ours, a customer’s or a supplier’s on consignment, and only ours is valued. The other direction — your finished goods sitting at a distributor until they sell — is still the difference between what is in the building and what belongs on the balance sheet.
The hardest inventory problem in Kenya, and not because of volume — the same alternator carries four names, so stock is counted three times and one person holds the mapping. What fixes it, in what order, and the vehicle record this does not have.
Groups configure their systems for the trading subsidiaries, because that is where the stock and the customers are. Then they discover annually that the entity nobody configured is the one with the evidence obligation.
Ask our stock reports what one warehouse holds and you get an answer. Ask the ledger and you get half of one: a journal entry carries a branch, so the income statement splits by site, while the balance sheet stays one figure for the organization.
Every quantity the inventory module stores is a decimal to three places, and every item carries its unit — pieces stay whole, kilograms and litres take fractions. The conversion between two units of the same thing is the piece still to scope.
On hand and available are two different numbers and most systems hold only one. Where goods sit out a mandatory hold before they can move — and where one season carries most of the year — that gap decides whether the vessel sails full.
Every automatic reorder point is recomputed at one in the morning from thirty days of demand, a lead time and a safety stock. A figure somebody types is marked Manual and left alone, and a warehouse minimum is never touched.
A sale is not finished when the customer says yes. It is finished when the money is banked, the stock has moved, and the invoice matches what was actually delivered — and the gaps between are where revenue evaporates.
The one place serial tracking pays back in the first month. Read the serial and you know when it came in, when it sold and who supplied it — and six failures from one purchase order becomes a claim against your supplier.
There is no delivery note. An invoice knows which warehouse the goods left from, and there is no separate document that travels with them and gets signed at the other end. For internal transfers there is exactly that.
A return is the money, the stock and the story — and only the first is a credit note. Credit notes here carry an amount and no lines, and move no stock at all, which is how inventory quietly drifts upward.
A count assigned for Friday gets finished on Friday when the counter is reminded on Friday. A stock hold is still there for the customer when the person who placed it knew it was ending. Two reminders for the warehouse floor.
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.
The two numbers that decide whether you run out or tie up cash — the reorder-point formula, statistical safety stock, and where each quietly drifts wrong.
How much did services earn last quarter, and on what margin? An income account on each service, services in sales by item, and a margin shown as n/a rather than a flattering hundred per cent.
A SKU is how your system knows what an item is; a bin location is how a human finds it. Get both naming systems right and stock control becomes almost easy.
Watch quick demos to see AWRA OpsHub in action across inventory, procurement, and finance.
Page 3 of 9 · 209 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.