One Platform • Governed Operations • Smarter Decisions
Your operations, connected from inventory to reporting.
Inventory, procurement, assets, sales & POS, financial controls, HR & payroll, projects and support & helpdesk — connected with approvals, vendors, reporting, offline mobile and AI insights on one operating layer.
AWRA Operations Hub is a cloud-based, multi-organization platform that unites your entire operation on one intelligent layer — so teams cut manual reconciliation, protect accountability, and make real-time decisions with confidence.
The Foundation — Inventory & AssetsWH-01 · WH-02 · BR-03 Live count
Stock that never loses count — and assets that never lose an owner
Every AWRA workflow starts here. One live, bin-level count across every warehouse and branch, and a custodian on every tracked asset — so procurement, sales, and finance all read from the same truth.
Count sheet
SKUs tracked4,812
Locations12
Bins mapped340
Rack elevation · WH-016 bins · every movement logged
A-01 Live
Multi-location, bin-level
Warehouses, branches, and bins tracked in one real-time count — no more spreadsheet reconciliation.
90%
A-02 Reconciled
Counts & variance control
Cycle counts, blind counts, variance review, and approved corrections with a full evidence trail.
80%
B-01 Quarantine
Stock status & quality holds
Keep available stock separate from quarantined, damaged, expired, returned, and inspection-pending units.
40%
B-02 In transit
Transfers & adjustments
Move stock between locations with approvals, reasons, and an immutable audit history on every change.
60%
C-01 Scanned
Scan-first operations
Barcode & QR scanning from the mobile app and linked scanner bridge — receive, pick, and count hands-free.
100%
C-02 Reorder
Predictive guardrails
Low-stock and reorder signals surface before you run out, so replenishment happens on time.
One governed loop that turns an internal need into the right supplier decision — with approvals, competitive quotes, and finance context baked in before a single PO is issued.
Routed through
Multi-tier approval with a budget check before anything is committed.
Evidence on file
Quotes, scorecards, and landed-cost workings — attached to the record.
RFQ-2041
Bid tabulation
6 criteria3 approaches Sealed
Step 1
Request
Step 2
Approve
Step 3
RFQ
Step 4
Compare
Step 5
Purchase Order
Step 6
Receive
How each procurement capability is handled manually, on a spreadsheet, and in AWRA OpsHub.
No re-keying · no month-end catch-upBooks balanced
Included · Financial Controls
Financial controls that stay connected to operations.
No re-keying, no month-end guesswork. Sales, POS, procurement, and payroll post straight to a live, double-entry ledger — so your numbers are always close-ready.
CapturePostReconcileReport
General ledger
Every invoice, PO, payment, and payroll run auto-posts to a double-entry ledger.
Budget controls
Track budget vs actual by department or project, with alerts before you overspend.
Close & reconcile
Reconcile exceptions, review AR/AP aging, and close the books to a checklist.
Reports & sync
Live statements and one-click sync to QuickBooks — always close-ready.
Employees, leave, attendance, and payroll in one place — with every pay run posting straight to the finance register. No side spreadsheets, no double entry.
Timesheet · July 2026Clock-in, shifts & timesheets
Explore HR & Payroll Employees don't need a login — HR works with or without user accounts.
05
Projects & TasksSchedule · WK 01–08 On track
Plan it, ship it — without the spreadsheet sprawl.
Scope · Q3
Run every initiative as a real project — break work into tasks, assign owners, set deadlines, and track progress from kickoff to go-live. All wired into the same operating layer as the rest of your business.
Support & Helpdesk4 open · 3 queues SLA clock running
Every request becomes a ticket someone owns.
Ticket · description
Scattered emails and “can you look at this?” taps become tracked tickets — routed to a department queue, owned by a real person, and kept on an SLA clock. All wired to the same identity, approvals and records as the rest of your business.
Step 01
Raised
From self-service, a PIN portal or email — stamped with a reference.
Step 02
Queued
Lands in a department queue the whole team can see.
Step 03
Assigned
Claimed by a real person — and the SLA clock starts ticking.
Step 04
Resolved
Answered, timestamped, with CSAT captured on close.
Partner Program — Free to join Revenue share · 2 years per client
Turn Your Network Into Recurring Income.
Refer, resell, or implement AWRA OpsHub — and earn up to 20% revenue share for 2 full years on every client you bring. Built for agencies, freelancers, NGO consultants, and sales partners.
Tier ladder · share of client revenueExample · Pro plan
8%
Registered
1 client
$4/mo
12%
Silver
2 clients
$11/mo
16%
Gold
6 clients
$43/mo
20%
Platinum
15 clients
$134/mo
Free to join · no targetsRecurring for 24 months
For agencies, IT consultants, NGOs & sales partners
Deal protection — your leads stay yours, always
Earn on Basic ($19.31), Pro ($44.80), or Premium ($96.56) clients
Scanning, GPS proof, and approvals that keep working when the signal drops. Field custodians and mobile operators capture work offline — it syncs securely the moment they reconnect.
Capture log · on device4 records
08:14ScanAST-2049 checked in — custodian J. OtienoSynced
08:22GPSHQ Floor 3 geo-stamped as field proofSynced
09:03ApprvTransfer TRF-118 approved from the fieldQueued
Practical guides on inventory, procurement, finance, HR and running a tighter operation — written by the AWRA team and the operators who use it every day.
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.
