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.
Each warehouse can carry its own minimum and maximum, and Reorder reads them. Low-stock alerts compare the national total against the item's reorder point, and safety stock and lead time live on the item — so a distribution centre can sit at zero while the alert stays quiet.
When stock runs low our system can raise a purchase requisition on its own. It raises it against a department. It does not name a supplier, look at who supplied the item last time, or consider who is cheapest — because nothing in the automation has any concept of who you buy from.
Three automatic stock alerts watch an input store, and every input they read is a number somebody typed. Which of them helps a business that buys once a season, which will train your team to ignore it, and where the notice period is actually spent.
A customer confirms on Tuesday, you deliver Friday, you invoice Monday. The sales order holds that interval: the accepted price, the reserved stock, the backorder, invoicing in parts. What it does on each day, and the two places it hands the decision to a person.
Every reorder calculation assumes an order placed today arrives a fixed number of days from today. On an island resupplied by scheduled sailings, the wait depends on when you asked relative to the cut-off — so the same order, placed two days apart, can land weeks apart.
AWRA Intelligence Insights is the analytics layer of AWRA OpsHub — signals across inventory risk, vendor reliability, revenue momentum and financial stability from data you already generate. What it does and how it fits the suite.
Low stock announces itself: there is an instant when the quantity crosses the line, and something can be hung on that instant. Stock that has stopped moving has no such instant, because it is defined by the absence of one, so it has to be gone looking for.
A boxed machine on a rack is stock; bolted to a floor it is an asset. Our system moves it across that line properly, on approval, with a linked record — and the moment it crosses it gains capabilities it never had, a calendar service schedule among them.
A restaurant, a bar and a pool bar are four businesses drawing on one set of stores. There is no outlet entity, so an outlet is a location plus a counter — and a counter belongs to one person, which quietly rewrites your bar rota.
An asset here is born one of two ways: entered by hand, or converted from stock. Neither remembers the purchase order. For a business buying equipment against a grant, a client project or a capitalisation threshold, that forgetting is the whole problem.
A batch is identified by your organisation, the item and the number on the carton — nothing else. Receive that combination twice and the second delivery joins the first, filling in what was blank and rewriting exactly three fields that were not.
AWRA Inventory is the stock-control module of AWRA OpsHub — real-time levels across warehouses, approval-controlled transfers, counts, quality holds and reorder alerts. What it does and how it fits the suite.
Goods in transit are on your balance sheet and in nobody's stock count. Most systems model a location you operate, so a consignment sitting in a foreign port for eleven days becomes a purchase order — which is a document, not an asset.
Stock valuation, receivables ageing, payables ageing and a payments register all exist and all work — every input a cash conversion cycle needs. Turning them into the three ratios, sized in days, is a report we can add to your workspace.
The invoice reader returns the page as text and three candidate values: a total, a date and a document number. It returns no line items, and everything it does return is a suggestion. Knowing exactly that is what makes it useful.
Every bin location can be given a pick sequence. The field is validated, stored and displayed, and nothing in the product sorts anything by it yet. A field of exactly this shape, and what it tells you about reading a form as a promise.
One needs twelve records, the other needs one record and a count. The choice quietly determines whether your register is maintainable — and it is much harder to reverse than to make.
A storage location here has a capacity, counted in stock units, shown as a percentage full, and raised as an Ops Center alert when a location goes over. It never refuses a delivery — and why that is the right design.
Where withholding applies to service fees and not goods, a mixed supplier bill has to be split first. Withholding is calculated on the service and typed lines, never on the stock goods beside them.
AWRA Sales is the revenue module of AWRA OpsHub — customers, quotations, invoices, payments and POS with real-time inventory deduction. What it does and how it fits the suite.
Ninety-four cartons left Industrial Area and eighty-nine arrived in Eldoret. The system knows what went on the lorry and what came off it — and has no opinion about the person in between.
Agro-dealers sell by the kilo, hardware by the metre, fuel by the litre. Every item has a unit of measure, stock moves in decimals where the unit allows it, and a box of screws still refuses 0.4.
Money you already spent, sitting on a shelf, earning nothing and costing more every month. How to define dead stock, find it before it fossilizes, and clear it.
One shipment, two companies, two systems. Two records that were both correct when they were made — and a difference that only appears when somebody adds them together.
Page 4 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.