AWRA Help Center
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.
What is new, release notes, changelog history, status updates, and product change tracking.
Human Resources — employee records, leave, attendance and time, payroll and payslips, and employee self-service.
Delivery management — projects and tasks, Kanban board and my tasks, planning and Gantt, agile sprints, time and budget tracking, and flexibility (labels, checklists, templates).
Support desk — tickets, department queues, categories and assignment, SLA timers and escalation, the public intake portal, and staff self-service (My Tickets).
Android, iOS, mobile workflows, barcode scanning, scanner bridge, and field operations.
APIs, webhooks, sync patterns, QuickBooks, connectors, and external system implementation.
Trust, security, privacy, compliance, uptime, access controls, and procurement review resources.
Pricing, plans, subscriptions, ROI estimates, billing conversations, and commercial review.
AWRA Academy courses, lessons, assessments, and verifiable certificates — learn the platform module by module.
Implementation, onboarding, migration, demos, training, rollout, and customer success guidance.
Common questions, support paths, issue diagnosis, exceptions, controls, and operational fixes.
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
Buying — requisitions and approvals, RFQs and quotation comparison, purchase orders and receiving, three-way matching, supplier prequalification, and landed cost.
Selling — quotations and orders, invoicing and credit notes, customer records and statements, receipts and collections, and point of sale with shift reconciliation.
Money — chart of accounts and journals, expenses, budgets and controls, vendor payments, the payments register, aging reports, and period close.
Asset register — tagging and custody, assignment and location history, condition and verification, maintenance, depreciation schedules, and disposal.
The supply base — supplier records and documents, performance scoring, the vendor portal and collaboration, and vendor-side self-service.
Seeing the business — the report catalog, BI Studio and custom report builder, saved filters and scheduled reports, dashboards, and predictive insights.
Making the system act — approval workflows, rules and triggers, the unified action queue, exception handling, alerts and notifications, and scheduled jobs.
Core product documentation, module explainers, operating concepts, and platform overviews.
Browse Help Sections
Each article is backed by approved public knowledge and links back to the authoritative AWRA resource for deeper context. Tap a section to expand it.
Stock control — item master and locations, counts and adjustments, transfers and approvals, traceability and quality holds, replenishment, and warehouse operations.
AWRA Blog
A batch with four months left is stock you can sell if you move it now. A batch with four days left is a write-off that has not been declared yet. Most pharmacy systems hold both as the same number, and the day the difference becomes visible is the day it stops mattering.
AWRA Blog
A SKU is how your system knows what an item is; a bin location is how a human finds it. Get both naming systems right and stock control becomes almost easy.
AWRA Blog
The hardest inventory problem in Kenya, and not because of volume — the same alternator carries four names, so stock is counted three times and one person holds the mapping. What fixes it, in what order, and the vehicle record this does not have.
AWRA Blog
Every quantity the inventory module stores is a whole number — on hand, per location, expected, counted, in transit, received. And no record anywhere carries a unit of measure, so an item is a countable thing and the system has no opinion about what kind of thing it is.
AWRA Blog
Our asset register knows a forklift on your floor might be owned, leased or borrowed, and enforces it in five places. Our stock system has no equivalent idea at all — every unit is yours by assumption. For anyone holding supplier-owned components, that assumption is the difference between what is in the building and what belongs on the balance sheet.
AWRA Blog
On hand and available are two different numbers and most systems hold only one. Where goods sit out a mandatory hold before they can move — and where one season carries most of the year — that gap decides whether the vessel sails full.
AWRA Blog
Ask our stock reports what one warehouse holds and you get an answer. Ask the ledger and there is nowhere to look, because a journal entry carries no branch. Two views of the same goods, one dimensioned and one not.
AWRA Blog
The purchase order goes out on Tuesday. The same item is sitting four kilometres away, above what that branch needs, and has been since March. What the balancing calculation compares, why an item with a reorder point of zero produces no suggestion in either direction, and when buying is still the right answer.
AWRA Blog
There is no delivery note. An invoice knows which warehouse the goods left from, and there is no separate document that travels with them and gets signed at the other end. For internal transfers there is exactly that.
AWRA Blog
A quotation commits you to nothing and carries six fields describing tax and currency. A credit note reverses a taxable supply and carries none of them — no tax split, no currency, no line items. What that costs a single-country business is almost nothing; what it costs a group trading across four EAC currencies is an ambiguity on every unapplied credit.
AWRA Blog
Our asset register knows who holds the cold-chain unit, where it is, what condition it was in at the last hand-off and when a person last laid eyes on it. It does not know when it is next due for calibration — and the reason is more useful than a flat absence: the machinery that watches a date arrive is built and running, for batch expiry, quotations, purchase orders and invoices. It is simply not wired to assets.
AWRA Blog
Groups configure their systems for the trading subsidiaries, because that is where the stock and the customers are. Then they discover annually that the entity nobody configured is the one with the evidence obligation.
AWRA Blog
Every item's reorder point is recomputed at one in the morning from thirty days of demand, a lead time and a safety stock. Nothing is excluded from the sweep, so a figure somebody typed by hand survives until the job next runs.
AWRA Blog
Our demand forecast adds twenty-five per cent in March, June and December — three Gregorian months written into the code, identical for every customer in every country. In a market whose largest demand event moves eleven days earlier each year, that is not a small approximation.
AWRA Blog
Reorder point, safety stock and lead time all live on the item and nowhere else, and every low-stock check compares the national total against them. A distribution centre can sit at zero for a fortnight while the dashboard stays green.
AWRA Blog
When stock runs low our system can raise a purchase requisition on its own. It raises it against a department. It does not name a supplier, look at who supplied the item last time, or consider who is cheapest — because nothing in the automation has any concept of who you buy from.
AWRA Blog
Every allocation goes oldest-expiry-first, with no setting, no per-item policy and no override — and there is a column on the item that looks exactly like one. The behaviour is stricter than the interface suggests, which is an unusual direction to be wrong in.
AWRA Blog
Every bin location can be given a pick sequence. The field is validated, stored and displayed, and nothing in the product has ever sorted anything by it. The sixth inert field of exactly this shape, and what it tells you about reading a form as a promise.
AWRA Blog
A batch is identified by your organisation, the item and the number on the carton — nothing else. Receive that combination twice and the second delivery joins the first, filling in what was blank and rewriting exactly three fields that were not.
AWRA Blog
One shipment, two companies, two systems. Two records that were both correct when they were made — and a difference that only appears when somebody adds them together.
AWRA Blog
You can tell our system how much a storage location holds. There is a field for it, it is offered when you create one, and it saves correctly. Nothing has ever read it — you can put four times that quantity in the location and the system records it without comment.
AWRA Blog
Goods in transit are on your balance sheet and in nobody's stock count. Most systems model a location you operate, so a consignment sitting in a foreign port for eleven days becomes a purchase order — which is a document, not an asset.
AWRA Blog
Three automatic stock alerts now watch an input store, and every input they read is a number somebody typed. Which of them helps a business that buys once a season, which will train your team to ignore it, and where the notice period is actually spent.
AWRA Blog
Ninety-four cartons left Industrial Area and eighty-nine arrived in Eldoret. The system knows what went on the lorry and what came off it — and has no opinion about the person in between.
Page 3 of 8 · 187 articles
For rollout planning, enterprise procurement, billing, security review, or customer support, share the context and we will route it to the right owner.
