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.
Stock balancing suggests moving stock from where there is too much to where there is too little. Each warehouse can carry its own minimum, which becomes its floor; a warehouse without one falls back to the item's single reorder point — and on the default of zero, nowhere is ever short.
A transfer between your own warehouses is an administrative detail — until the two warehouses are the coast and somewhere landlocked, and the stock spends weeks in a state that appears in no warehouse's figure. The workflow handles it well. The reporting has a hole in exactly the wrong place.
Clinics, hospitals and health programs share a hard inventory problem: medicines that expire, cold chains that cannot break, equipment that must work, consumables that vanish. The disciplines that keep a health facility supplied, safe and accountable.
A transfer that arrives short is usually saved as a smaller receipt, and the missing stock is on no shelf at all. Picking before dispatch, a discrepancy for every shortfall that closes only when each unit is found, returned or written off, and a ledger that checks the road.
Forty cartons on the shelf, twenty-five of them promised for Monday, and a till that sees forty. Why in stock and free to sell are different numbers, why the rule between them has to live in one place every outgoing movement passes through, and what a hold placed by hand is for.
European food law asks who supplied a batch and who received it. Our schema answers both — with two caveats that decide whether the answer arrives in an hour or not at all: the tracking is off by default per item, and deleting a batch leaves its movements pointing at nothing.
Addis is Ethiopia's trading engine — importers, distributors and retailers moving goods to the regions. What inventory and distribution software must do when your stock is imported, your currency moves, and your customers are a day's drive away.
In Lagos the distance between your warehouse and your customer is measured in hours, and stock spends most of its life in the gap. What inventory software must do where traffic, van sales and multiple warehouses hide your real position.
A caesarean consumes roughly the same forty items every time. Held as a procedure pack, one click raises a single check-out for all forty, so component stock stays true instead of drifting until the stockout is found in theatre.
The return trip costs more than the margin on the original job. Why two of the five causes are intake failures, treating each van as a counted stock location, and the parts you fit but never bill.
Dead stock has no event to hook, so it is scanned for nightly, deduplicated, and cleared the moment the item moves. Good engineering, measured against one idle period for the whole catalogue — the same number for a filter and a gearbox.
A city of twenty-odd million where a delivery van covers a fraction of the ground it would anywhere else, and the working week ends on a different day. Density, custody and the routing of stock through a megacity.
Stock leaves this system by two paths, and the till keeps its own record. Bringing both onto one vocabulary, so a counter-only shop's consumption reports read correctly, is a unification we can apply to your workspace.
Nine provinces, one promotion, and a customer who checked online before driving to the store. Price consistency, long-leg transfers and the reserved-stock problem that omnichannel creates.
Our turnover report counts consumption from the till as well as from issues, rolls balances back through the period's own movements, and works over any dates. Then it hands you one figure for the entire company and stops.
Accra traders run retail and wholesale out of the same stock at two different prices, then wonder why margin is impossible to read. How to separate the two channels without splitting the business in half.
Gauteng, the Cape and KZN on one stock position, long inland legs from the port, and capture that survives a scheduled power cut. What national distribution actually demands of a system.
A shocking share of Kenyan produce is lost between farm and buyer, invisible because nobody measures where. Turning loss into a number at each step protects the margin.
The fastest read on whether stock is an engine or an anchor — the formula, days-on-hand, sane benchmarks by sector, and the averaging trap that hides dead stock.
Goods and the service that goes with them, on one invoice. Each line is labelled for what it is, the stock check reads only the stock lines, and a confirmed order never backorders a service.
Switching off an email should not mean switching off the alert behind it. Why email and the in-app notice are separate switches on the same row, and which combination saves a stock-out.
Step-by-step guides and operational playbooks for inventory, procurement, sales, and accounting teams.
Page 2 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.