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 item has a unit of measure. Pieces, boxes, packs, cartons, pairs, sets, dozens, rolls, bags and bottles take whole numbers; kilograms, grams, tonnes, litres, millilitres, metres, centimetres, square and cubic metres and hours take up to three decimals — on receipts, issues, transfers, counts, holds, reservations, POS sales and returns, purchase orders and reorder suggestions. Converting between units on one item (buy cartons, sell pieces) is something we can add for you.
Each item's reorder point is Automatic (recalculated nightly from 30 days of issues, adjustments and POS till sales, lead time and safety stock) or Manual (kept exactly as typed). Typing a figure switches the item to Manual, and an Automatic item with no lead time or safety stock keeps its point instead of dropping to zero.
Yes. Whoever a stock count is assigned to is reminded on its due date if counting is not finished, and once more if it becomes overdue, with the warehouse and lines counted so far. Whoever placed a manual stock hold is reminded about a day before it is released, so they can extend it or turn it into a sales order.
Careers at AWRA Build the operating system growing businesses actually run on. AWRA OpsHub exists to give growing and emerging-market businesses the kind of connected operations — inventory, procurement, sales, POS, and finance — that used to be reserved for enterprises with deep pockets and long implementations.
Spreadsheets & manual trackers Spreadsheets AWRA OpsHub vs spreadsheets When the workbook quietly becomes the operating system. Spreadsheets are excellent calculators and a great way to start. They become fragile the moment several teams depend on the same file for inventory, buying, sales, and reporting.
A finger on a screen, a printed name, a timestamp — taken at the loading bay, the store counter or the desk where a laptop is handed over. AWRA keeps the mark on the movement record and prints it on the delivery note, so “we never received that” stops being a matter of who remembers harder.
Confirm a sales order and its stock is promised at that warehouse; whatever is not there yet is backordered and filled, oldest order first, as stock arrives. Until then the till, a transfer or anyone else’s check-out is told plainly that those units are taken.
See how AWRA OpsHub compares to Spreadsheets, Entry-level accounting tools, Single-purpose inventory apps, Legacy ERP suites, Bundled app suites, Generic work tools, Open-source modular ERP, and why teams switch to one connected operating system.
Capture the supplier’s invoice against the order it bills, or for rent and services with no order at all. Line it up with what was ordered and received, approve it, set returns against it, and pay a whole week’s bills in one run that a second person signs off.
They are also not inventory — inventory is consumed, and chairs come back. This is the category almost every asset system leaves out: things you own in quantity, that go out and return, that get damaged and lost, and that somebody is nonetheless responsible for.
AWRA is built by operators, engineers, product strategists, and customer-focused teams who have worked inside real inventory and procurement environments. The team is structured around one mission: helping organizations run critical operations with confidence, speed, and control.
We built AWRA OpsHub around the way operational work actually moves: inventory creates demand, procurement answers it, receiving updates stock, sales and POS consume it, finance reconciles it, and reports explain what happened. This tour follows that chain step by step.
Pick the approved bills that are due, choose how each supplier is paid, and submit the run. A second person approves it, the supplier details are fixed at that moment, and on the pay date each line goes out by bank file, cheque, cash, M-Pesa or Paystack.
Somebody in your organisation rebuilds the same filtered view every Monday: this warehouse, these three categories, last week, unpaid only. Ten minutes of clicking to reach a screen they have reached forty times before.
Convert approved sourcing decisions into controlled purchase orders, capture supplier acknowledgement, receive goods accurately, handle mismatches, and close the buying cycle with inventory and finance aligned.
Define a default warehouse, create a default storage location, and let AWRA prefill transfer and inventory screens automatically. Keep slotting consistent across every warehouse.
Single-purpose inventory apps Single-purpose inventory apps AWRA OpsHub vs single-purpose inventory apps Inventory is solved — but procurement, sales, and finance are not.
Entry-level accounting software Entry-level accounting tools AWRA OpsHub vs entry-level accounting tools Great books, but the warehouse floor is somewhere else.
Classifying inventory into A, B and C tiers by value or importance.
Page 6 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.
