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
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.
The quotation importer opens PDFs, Word files and spreadsheets, and it will still refuse your supplier own letterhead quote. That refusal is the feature: a parser that guesses at a price it cannot actually find is worse than one that declines.
Collecting from a customer and paying a supplier use the same provider account and are not the same capability. The outgoing side needs credentials the incoming side never asks for, and an organisation configured to collect is not yet configured to pay.
A complete, adaptable procurement policy for Kenyan NGOs — thresholds, committees, conflict-of-interest rules, and emergency procedures you can copy into your manual.
Everyone sells offline capture as the answer to a power cut, and it answers the half that was not the problem. Your till records a sale in the dark; it cannot get a card approved — and in a card-majority market that is where the evening's revenue goes.
Our vendor scorecard reports an on-time rate. On time means the order's planned delivery date falls within seven days of the order being raised — seven, for every supplier, everywhere. It never checks when anything actually arrived.
Schools and colleges run real operations behind the classroom: procurement, boarding supplies, laboratory and ICT assets, transport fleets and tight budgets answerable to boards and parents. The disciplines that keep an education institution accountable.
Term dates are known years ahead — yet week one is always a buying emergency. The term procurement cycle, the big four contracts, and kitchen arithmetic.
Everyone knows which supplier is difficult; almost nobody can prove it. The 50/30/20 weighting, why acknowledgement is worth measuring, and the one definition inside the score you must check before quoting it at anybody.
Our quote comparison scores price, delivery time and a vendor rating, with weights that must sum to one. Two of the three are real. The third is a field nothing fills in, and when it is empty the score uses 3.5.
The approval was given at one moment and the money moves at another. Everything that happens in between belongs to the order that caused it — if anybody wrote the rate down.
Several jobs in the purchasing chain exist only to correct things that should not need correcting. They run every five minutes, every hour and every night — and a run that fixed nothing looks exactly like a run that had nothing to fix.
A generator is serviced every 250 running hours, a vehicle at 10,000 kilometres, a compressor on its duty cycle. Every one of those is a number the machine keeps and the asset register does not, so the only schedule it can offer you is a calendar.
A purchase order has no currency field. It borrows the quotation's, and where there is none it falls back to your base currency. A supplier has no currency at all — the column existed once and was removed as unused.
A purchase order fully paid for a week closes itself at one in the morning. Closing writes two facts nobody observed — that it was delivered, and when — so the window is worth setting deliberately rather than accepting.
A supplier signed into your portal can mark your purchase order closed. There are four conditions on it, and the fourth — that you have already paid in full — is what makes the whole thing safe.
A requisition has line rows. A request for quotation has line rows. A purchase order has line rows. A supplier's quotation has a JSON blob — the one document whose detail is not queryable, and the one you most need to compare.
Page 1 of 3 · 65 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.