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
A filtered list view can be saved under a name and restored with one click, on twenty-one list and report screens. Eighteen datasets can then be scheduled for delivery in PDF, CSV and XLSX on a daily, weekly or monthly cadence at an hour you set in your own timezone, to a whole role resolved at send time, named users, or external email addresses for people with no login. The next three run times are shown while you configure, and every delivery attempt is recorded with its error.
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.
One permission lets somebody schedule a report to a list of email addresses. The addresses are not checked against your user list, and nothing compares what the report contains against what each recipient is allowed to see.
Report Field Settings reporting Intermediate 40 min fa-gear Governed fields, visibility, validation, and cleanup. Learn AWRA report field settings: Governed fields, visibility, validation, and cleanup.
Release notes summarize new AWRA product capabilities, public page improvements, operational workflows, and support resources as they become available.
Use this public status center to review AWRA OpsHub’s security, privacy, audit, retention, and governance posture before procurement, legal, or internal risk review.
This module will refuse to move a project from planning straight to completed. It will not refuse to spend twice its budget. One of those is enforced by a state machine and the other is a percentage on a screen.
Apply a credit note and the invoice's amount-paid figure goes up by the credited amount. The invoice status says credited rather than paid, so the document is honest. The column is not — and anything measuring collections from it reads a credit as money received.
Our system records the result of an incoming quality check properly — a status on the consignment, a screen to set it, a summary and an analytics view built on it. What it does not do is stop you selling the goods that failed. Recording and enforcing live on two different records, and nothing connects them.
A milestone here is a name, a due date, a status and a sort order — the one level between a task and a project that reports cleanly. Turning that date into something that gates, triggers and alerts is an addition we can wire into your workspace.
The HR module manages the people side of your operations — employee records, leave, attendance and time, and payroll — from the same workspace you already use for inventory, procurement, and sales.
The Projects module manages delivery — projects, tasks, planning, sprints and time — from the same workspace you already use for inventory, procurement, sales and HR. It is a delivery tool that is wired into the rest of the business, not a silo.
A custodian is its own record rather than a user account, so drivers, site labourers, contractors, departments, vendors and visitors can hold assets with no login, no seat and no permissions. Six custodian types and four statuses including exited, so somebody who leaves stops receiving custody while every movement they were part of stays readable. Nine movement actions each carry their own permission, and every handover records the custodian, department, warehouse, location and condition at both ends, with an expected return date, optional photographs, optional GPS and a signature.
AWRA captures attendance three ways — a manual daily register, employee self-service clock-in/out, or CSV/biometric import — in one record. It adds shifts and weekly rosters, automatic late detection, overtime, correction requests, and timesheet approval and lock per pay period. Clock-in can be secured with device passkeys, GPS geofencing, and an office QR code.
Our public holidays repeat on the same date every year. Six of Japan's sixteen are not on a date at all — four are the nth Monday of a month and two are announced annually. The first year is correct, which is the problem.
End-of-service accrues from month one and nothing asks about it until somebody resigns. With a finance team of three, nothing that fails to raise an alert gets looked at.
Delivery management — projects and tasks, Kanban board and my tasks, planning and Gantt, agile sprints, time and budget tracking, and flexibility (labels, checklists, templates).
Projects & Tasks runs agile delivery on the same tasks you track: a backlog and sprint-planning board, a per-sprint Kanban, story points, velocity across completed sprints, and a burndown computed from real completion times. Completing a sprint carries unfinished work back to the backlog automatically.
No mandate means the decision has to stand on operational evidence alone. Three honest positions including buying nothing, seven things worth scoring, and what a joint venture's attribution really costs.
A cost that lands nowhere lands in overhead — and overhead is where project profitability goes to hide. The four routes cost reaches a job, and the one-field rule that closes all of them.
Projects end twice — when the work stops, and months later when the last invoice and the last claim land. Why the reported margin is never the real one, the retention trap, and the one review table that changes future bids.
Customers return because you know their car, and that knowledge lives in a folder that gets lost and a mechanic who leaves. How far a registration-prefix convention gets you, and the declined-work note that is worth more than any discount.
Most project plans are tasks with dates typed beside them, which is a wish rather than a schedule. What dependencies buy you, why slack decides which delays matter, and the procurement lead time nobody records.
Support desk — tickets, department queues, categories and assignment, SLA timers and escalation, the public intake portal, and staff self-service (My Tickets).
Turn scattered emails and "can you look at this?" requests into tracked tickets — routed to a department queue, owned by a real person, and kept on an SLA clock. This guide covers intake, queues, working tickets, SLAs, and the self-service portals.
Our helpdesk emails your customer when their request is updated. If they reply to that email, nothing happens — and the cost of that lands on your reporting rather than on your support desk.
A field called "notified at" was being filled in on tickets where nobody had been notified. A missing alert is a gap you can find; a false record of one closes the investigation and moves the blame to a colleague.
Four of the Act's seven operational duties are wholly yours, three are shared, and none can be discharged by a purchase. The controller and processor boundary, what belongs in a processing agreement, and the breach-notification gap stated plainly.
The breach alarm notifies the agent, then their manager, then the department — the right ladder in an organisation that has one. For a six-person business we can configure a flatter path, so the alert reaches somebody positioned to act on it.
The word "requester" hides four different kinds of person, stored differently, able to do different things — and one kind you assumed existed and does not. Which one raised a ticket decides what your reports can ever tell you.
The AWRA OpsHub Android app is published on Google Play, free to install, and covers inventory movement, asset custody, scanning, GPS proof and offline field work.
One question can eliminate a vendor outright regardless of how well they demonstrate, and most buyers ask it last. It is not about features, price or the deadline.
A storekeeper spends Thursday in a warehouse with no signal, and everything they do sits on the handset in their pocket. Which four operations work offline, and why a device reporting zero queued is worth a second look before one reporting forty.
The API reference documents every Developer API endpoint for inventory, sales, and procurement, with authentication, key scopes, pagination, error codes, and rate limits.
Blacklisting a supplier does five things at once, refuses to be undone by accident, and blocks them from reapplying through the public form. Marking one preferred does nothing at all. Two flags on one record, and only one is a control.
A budget is a category and an amount, and a purchase reaches it by matching a free-text string on the item. Case is forgiven; a plural is not. So the spend you are not watching is the spend that was spelled slightly differently.
A requisition carries its department as free text; a purchase order carries it as a reference. The bridge is a lookup by exact name — and when it fails the order is raised, received and paid with no department, and no budget ever hears about it.
Our table holds Canada at the federal rate, which is correct. It then writes that rate into an organization's own settings and never revisits the question — so a business in a harmonised province is configured at the federal figure and nothing says otherwise.
Sales tax on goods is federal in Pakistan and sales tax on services is provincial, levied by five separate authorities. So which government a figure belongs to depends on what you sold — and most systems store the amount without storing the answer.
Pick the billing interval that works best for your team. Compare the 30-day Free Plan, Basic at $16/month, Pro at $42/month, and Premium at $86/month, or request a custom Enterprise quote. Save 20% on annual billing.
Where the consumption tax cannot be reclaimed, it has to be charged to a budget line — and a line has a ceiling that a good intention does not raise. The arithmetic is simple and it is discovered late.
A tariff preference is worth nothing to a business that cannot quote in the buyer's currency, cost goods honestly through the border, or produce the records proving where they came from. Operational readiness, and a hard line at customs.
The transactions that cost you money are ordinary, small and buried among thousands of correct ones. What the pricing and financial radars actually watch, why explicit rules beat a black box, and how to stop alerts becoming furniture.
In most growing businesses the only real check on a supplier invoice is that somebody has to type it in and notices things. Structured e-invoicing removes the typing. What replaces the noticing?
ABC Inventory Analysis foundations Intermediate 35 min fa-layer-group Sort your items into A, B, and C tiers so you spend control effort where the money is.
Accounting AI Insights governance Intermediate 40 min fa-scale-balanced Large entries, reconciliation clues, and finance exceptions. Learn AWRA accounting ai insights: Large entries, reconciliation clues, and finance exceptions.
You type a minimum you are never willing to go below. At one in the morning a scheduled job recalculates it from thirty days of recorded usage and writes its answer over yours. Whether that helps or quietly disarms your low-stock alerts depends on one thing nobody mentions in a demo: which transactions count as usage.
"Best" cannot be answered as a product ranking across fifty-four regulatory environments. What can be answered: the five things that genuinely change country to country, the much larger set that does not, and how to test a regional claim in a demo.
Nobody adopts an asset register with no assets. The interesting part of a migration is never the file format — it is the four columns you have that the destination has nowhere to put, and deciding in advance which of them you are prepared to lose.
Six questions with structural answers — a number, a yes, a name — including the one almost nobody asks: who maintains the municipal rate dataset, and on what schedule?
A stocktake here does not change your stock. It raises adjustments somebody has to approve — so a counter can report what they counted and cannot set the record. The best decision in the module, and the three things it stops short of.
A discount at this till is four columns: the sale, the line, a free-text description and an amount. No approver, no reason code, no limit and no user. It is a record of what happened, not a control over whether it should have.
A discount at the till is an amount and a sentence — no approver, no reason code, no percentage, no person on the record. A stock write-off of the same value needs a dedicated permission and a second pair of eyes no permission can override.
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
A free-text field with validation is not a smaller version of a coded one. Where a jurisdiction wants a value from a published list, the field either holds it or your document is not the document.
Our ABC report bands the catalogue on cumulative consumption value, which is the correct definition and not the common one. Our counting module can hold a class against a plan. Nothing carries the first into the second, so at catalogue scale the classification is never refreshed.
Most stock counts produce a new number and throw away the evidence of how the old one went wrong. Blind, valued, placed and dated — miss any one and you get a correction instead of a reason.
Every quantity column in our stock schema is an integer, and there is no unit of measure anywhere in the product. For a business that counts cartons that is invisible and correct. For one that buys maize by the tonne and sells it by the bag, it is the difference between a stock figure and a guess.
Serial-number tracking for stock has a table, a model, three screens, two routes and a count on the dashboard. It has no code path that can create a row. The screens work perfectly and will always be empty — and the test that would have found it takes ninety seconds.
Buying — requisitions and approvals, RFQs and quotation comparison, purchase orders and receiving, three-way matching, supplier prequalification, and landed cost.
Our interface is English. Yours is not. That is a staffing question inside the building and a document question outside it — and only one of the two is actually solvable by a vendor.
We record how much tax was paid on a purchase and not what it means. That gap has a general shape — a stored value whose interpretation lives outside the data — and once you see it you find it in landed costs, quantities and dates.
Almost every prequalified supplier list has the same defect: nothing removes anyone. Ours has a shelf life — a validity period you set, a date stamped at approval, and a job that runs at six every morning, expires the qualification and deactivates the supplier so they drop out of the selectable list. Here is the whole pipeline, and the five things it does not do.
Most ERP regret comes from buying the wrong size, not the wrong brand. A buyer's guide that starts from your operation, right-sizes the system, and gets you there without overbuying.
The customer pays part by phone and the rest in notes. What your till records decides whether tonight's drawer reconciles — and recording it wrong manufactures shortages that nobody can trace.
Three supply chains in one apron — contracted dry goods, daily fresh buying with price-survey bands, and protein weighed twice. Each leaks differently.
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Everywhere else, voiding a document is something you do. Here it is something you ask for — and your customer can say no, or say nothing, which is worse.
In several Gulf markets a customer settles an invoice by handing over a cheque dated six weeks out. The invoice is closed as far as they are concerned, the money is not yours yet, and our receivables model has only two states.
A return against last year's sale is credited at last year's rate. Our credit note holds one amount and no tax split, so it cannot express that — and nothing will tell you.
You can invoice in another currency, record the rate that applied and take payment in it. You cannot keep a second set of books. The documents are right, the ledger is single-currency, and the difference lands on whoever reconciles.
The Marshall Islands passed a consumption tax in 2025 that applies to supplies made on or after 1 October 2026. Between those two dates sits every quotation, contract and recurring invoice a business raises — and almost no finance system can hold a rate and a date at the same time, including ours.
The card-data question worth asking a point-of-sale vendor is not how the number is encrypted — it is whether there is anywhere to put one. Our payments table has six columns and no card among them, which is the strongest position available and has a price we would rather state than let you find.
Nobody schedules the day they outgrow their books — you just do more work for worse answers. The seven signs your accounting tool has become the bottleneck, and what they mean.
For an exporter the tax balance is a receivable rather than a liability — often a large one, managed with less rigour than a debtor a tenth of its size.
Cash accounting records money when it moves; accrual records it when earned or owed. The choice changes what your profit means and whether your books can be trusted.
Profitable businesses run out of money regularly, and almost always with two weeks of warning nobody was looking at. A thirteen-week rolling forecast you can maintain, built from records you already have.
What each fund type is, where NGOs mix them by accident — salary borrowing, shared costs, exhausted lines — and the structure that keeps the wall intact.
A vendor-honest guide to choosing operations software in Rwanda — what an ERP must actually do for a Kigali-and-upcountry business, how to test each claim, what to budget, and the straight answer on EBM, RRA and RWF.
Registers fail because they record what an organization owns rather than who is holding it. Custody, verification and disposal as the three things that matter — and a precise line between an asset register and a maintenance system.
Maintenance is recorded here as a movement: what happened, to which asset, on what date, by whom — a real history you can read. Preventive schedules that generate the next visit from that history are the layer above, and one we can add for you.
A contractor's plant is capital designed to move — which is why it goes idle, goes missing, and breaks down unplanned. Custody, movement history, and service discipline.
The auditor's schedule says what was bought; nothing says where it is. Fleets, branch fit-outs, ICT custody, repossessed collateral, and the register that survives elections.
Schools are three businesses in one uniform — fees, logistics, and assets. What operations software must handle, and where school money actually leaks.
Every vendor says they are localized. Almost none are asked which layer they mean. A field guide to the seven layers of localization — and an unusually blunt account of where our own product stops.
Buyers use "multi-currency" to mean three unrelated things and vendors answer whichever one they can. Separating transaction, reporting and entity currency across a continent of pegs, managed floats and redenominations.
A report here is built on one dataset — a sound design that keeps a whole class of double-counting out of your numbers. The joins worth adding on top, where you need a supplier and a customer, or a purchase and a complaint, in the same row.
Every business system has a chat box now, and almost none do what users assume on first sight. Guidance assistant versus data agent, what ours answers today, and the one question that tells you which any vendor is selling.
Guyana's Local Content Act makes supplier eligibility a dated certificate that renews on its own anniversary. Every supplier has a different date and there is no renewal season. That is a diary problem, and it is one of the few on this site we can say is already solved.
Seeing the business — the report catalog, BI Studio and custom report builder, saved filters and scheduled reports, dashboards, and predictive insights.
The most expensive report is the one somebody assembles by hand every month because asking IT takes three weeks. What a report builder removes, and how to avoid the mess when everyone can build one.
The owner wants one honest answer: how did the whole group do? Getting there without a quarterly spreadsheet ritual — the monthly group pack, a currency policy that holds, and the clear line between management consolidation the system produces and statutory consolidation your auditor signs.
Three formats, a row cap worth knowing about, and a CSV convention for empty cells that changes how Excel totals a column. What to expect from an export today, and the wider formats and larger row limits we can enable for you.
A lease that expires unnoticed costs more than a month of rent — it costs the negotiation you never had. Four dates per lease, what a turnover truly costs, and why the renewal conversation belongs at ninety days.
The paragraph at the top of an AI dashboard is the part everyone reads and nobody interrogates. Every figure computed in plain code, the model forbidden to invent any, and a fingerprint that discards the sentence when the numbers move.
Making the system act — approval workflows, rules and triggers, the unified action queue, exception handling, alerts and notifications, and scheduled jobs.
This investor hub gives prospective investors, advisors, and strategic partners the funding story, company deck, usage guidance, and next diligence path around workflow depth, commercial readiness, and expansion potential.
Any system can push a message to a phone. What separates a control from a nuisance is whether every single event has a named switch, a delivery channel it may and may not use, a cadence that stops a reminder becoming a stream — and a separate control for the person whose bell it lands in.
AfCFTA and the EAC customs union are lowering the barriers to trading across African borders — but a tariff advantage is only real if your operations can follow. What cross-border trade demands of your system, and an honest line on where software stops and customs, tariffs and rules-of-origin begin. Hedged.
Burundi, South Sudan, Somalia and the DRC joined the EAC into one market — but they are frontier economies, not Nairobi. What actually matters when currency is unstable, infrastructure is thin, and the honest answer to "is it localized?" is no.
When members give toward a building, the money carries a promise. Pledges against receipts, restricted from general funds, spent transparently — how the promise is kept to completion.
Coffee and tea move through Uganda in a chain of weigh-ins, grades, advances and member payments — most of it still on paper. The operational disciplines that turn a cooperative's intake season into clean, trusted records.
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.
