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
Material issued to a job used to be expensed at once and the finished output arrived as a debt to nobody. Both are fixed. What is left is the residual between what a job consumed and what its output was priced at — and why that number is worth reading rather than clearing.
One cost basis, weighted average, and no way to restate the past — a correction is a new transaction, never a revaluation. In a stable currency that is a footnote. Where prices move quickly it decides what your margin appears to be.
A Dubai entity buys and consolidates; an African operating company clears, distributes and collects. Almost every group runs these on separate systems and reconciles by email — which works right up until somebody asks what the group actually earned on a container.
The value on a purchase request is the quantity times the item's last recorded buying price. It is not a figure the requester supplied, it changes when somebody edits the catalogue, and nothing compares it to what you actually paid.
The consolidated accounts are accurate, the auditor signs, and nobody in the building can say what the group is holding today. Those are not contradictory statements.
A plan controls two separate things: which permissions exist in your workspace, and how many of certain things you may have. They do not move together — the free plan grants every permission in the product and caps you at two users.
Your clearing agent bills you three weeks after the container cleared. By then some of the goods have sold. That freight and duty will attach to whatever is still on the shelf and to nothing that has already gone — so the margin you reported on the fastest-moving lines is the one that was most wrong.
Corporate accounts and long-stay guests need the same invoice on the same day of every month. Credit limits, statements, matched payments and automatic chasing are all built. The generating is not — and an invoice nobody raised is completely silent.
Freight was quoted, so freight is in the cost. Demurrage, escort charges and border formalities were not, arrive later, and get posted to expense — which quietly prices every sale made from the consignment.
An import payable in Malawi passes through six states. Every accounting system models the first and the last. The four in between are where the money and the risk actually sit.
A catalogue check compares two numbers somebody typed. It finds the item priced below cost — and misses the discount applied every afternoon, the supplier who crept eleven percent over a year, and the freight that landed three weeks after the goods. Three margin questions, three different places.
An item has one selling price and it is a field. Change it and the old value is gone — no revision, no effective date, no history. The documents remember what they were sold at; the catalogue remembers only the last decision.
An asset's purchase cost is stamped with your workspace's own currency by the system, not chosen by the person registering it, and stamped again on every edit. That is what lets the register total itself — and it is why an imported machine needs translating before anybody types.
A return runs stock, revenue, cost and cash backwards at once, and most of that is built and enforced here. One tender on the refund dropdown was implemented nowhere, and the ledger was quietly missing a leg on every refund ever given.
Duty is assumed to be a property of the country. In Somalia it is a property of the port, so two containers of one product can cost different amounts to bring ashore — and a system holding one cost per item has already averaged the difference away.
No customs duty, overnight road delivery, a currency at par and an invoice with no VAT on it. Everything about a South African supplier says domestic, and two things that cost money say otherwise.
Most Kenyan distributors do not own a fleet, they hire one. So transport is not a fuel problem but a rate problem: the arithmetic on the invoice is right, and nobody is checking the rate it was multiplied by.
There is an anomaly detector here and everything it watches is a price — below cost, under five per cent margin, priced at nothing. It refreshes every fifteen minutes. And the cost it compares against is not the cost your ledger uses.
The subscription is under a third of it. The five components, a five-year model for a forty-staff distributor, and the recurring item nobody puts in the spreadsheet — two hours a month of somebody tending the thing.
Rwanda's hotels, lodges and tour operators run on tight margins and high standards. The operational back-office — F&B stock, procurement, cost control, assets — that protects the margin, and an honest line on where AWRA stops and a hotel PMS begins.
Costs in one currency, receipts in the other, both of them cash, and no treasury function anywhere. The exposure is real, it is structural, and it is nobody's job.
Stock is counted in whole units, which keeps every count unambiguous. One rule resolves the 12.5-kilo case — define the item as the smallest unit you ever transact — and where you need true fractional quantities and unit conversion, we can add them.
A recharge recovering 88% of a bulk bill loses money every month, invisibly. The recovery ratio per building, why you record readings rather than consumption, and the handover reading that ends a whole category of dispute.
Four tiers, four revenue shares and four client counts — recomputed nightly, applied automatically in both directions, with a sixty-day grace before a fall takes effect. Here is exactly what moves when a tier does.
Page 4 of 8 · 189 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.