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
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Exposure is the opening balance plus every open invoice plus the one you are raising. What the check measures, why paying frees headroom immediately, and the setting that silently switches it all off.
The cheapest sale a business can make is the second one to a customer it already has — and the reason most do not make it is that the record of the first sale lives in a salesperson's phone.
In Egypt "is it localized?" has five different answers depending on which layer you mean — language, currency, tax rate, e-invoicing, working week. A layer-by-layer buyer's guide, including the one where we tell you to look elsewhere.
The delivery note that comes back illegible is why an invoice gets disputed six weeks later. Why a printed name beats a signature, how to express a partial delivery, and treating delivery paperwork as a receivables control.
Four decisions hide inside every return, and collapsing them into one hurried moment is what breaks the records. Why restocking must be deliberate, how exchanges are really two transactions, and how unrecorded refunds manufacture till shortages.
One invoice per student, a unique payment reference, all channels into one ledger — how bursars end the evening matching game and make arrears report themselves.
Nobody decides to become a lender; it happens one favour at a time. Why exposure matters more than the invoice at the counter, how to set limits from behaviour, and the collection rhythm most retailers waive for their biggest customer.
A till that stops working when the connection drops teaches your cashiers to keep a paper book — and then you are running two systems. What offline selling requires, and what to decide before it happens.
The smallest document in your business and the one customers most often need. What belongs on the slip, why a stored copy settles disputes paper cannot, and the practical realities of digital receipts in Kenya.
The counter cannot sell on credit, by design, and there is no fee account to charge. Two shapes a school shop can take, why the credit limit is the control that matters in week one, and the small thing that decides your whole term's collections.
The earliest sales record is a quotation. Leads, deals, stages and forecasts have no home — what that costs you in four specific ways, and why raising speculative quotations is the worst available fix.
Sales · Accounts Receivable One page that answers “so what do we owe you?” A customer statement takes everything you've invoiced and everything they've paid, lays it out in date order with a running balance, and lands in their inbox as a cl
Revenue Signal Room Know which sales need follow-up before cash gets stuck. AWRA Sales Insights connects invoices, POS transactions, customer balances, payment behavior, and overdue exposure into a short list of revenue actions. Activate In
Payments & Collections Recover cash faster without losing payment evidence or invoice context. AWRA Payments & Collections helps teams record partial payments, track overdue balances, preserve receipts, follow up on collections, and keep fi
Blog Category All blog articles Archives Search articles in . Earlier articles No articles match your search yet — try another keyword. Articles coming soon We're writing guides right now. Meanwhile, explore the rest of the blog. Browse all
Refund a card via Paystack or reverse an M-Pesa payment via Daraja — the customer is paid back and the invoice/POS balance re-opens. Refunds are off by default (a guardrail for a destructive action) and a business enables them per account, with a confirmation showing amount and receipt. Receipts can be auto-emailed or SMSed to the customer the moment a payment succeeds, and the payment method shows on POS receipts and invoice PDFs.
Pay a vendor over M-Pesa two ways: B2C sends from your paybill or till to a supplier's personal phone number (common for small vendors); B2B pays a company vendor's registered paybill or till, with the PO number embedded as the account reference. Both run on Daraja using your stored initiator credentials, and the async result posts the payment onto the PO automatically.
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.