Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
For healthcare & clinics
Batch-and-expiry pharmacy stock, FEFO at dispensing, consumables topped up by consumption, and every machine on a register with a named holder — clinical operations, governed.
If any of these ring true, you are exactly who this was built for.
Expired stock quietly eats 3–8% of drug spend — bought with real money, dispensed into a write-off.
A prescribed item unavailable is a patient turned away — and nobody logs how often it happens.
Dispensing records, stock cards, and the physical shelf tell three different stories.
The autoclave fails on procedure day; the BP machine drifts out of calibration for a year, unnoticed.
Each capability links to a deeper feature tour.
Every receipt records batch and expiry; 30/60/90-day horizon reports keep write-offs preventable.
First-expiry-first-out recommended at issue — rotation enforced by the system, not the shelf arrangement.
Stock is held per location, so the lab, the dressing room and the main store are separate positions you can count and top up independently. What does not exist is a par level per point with an automatic top-up suggestion — the reorder judgement is a person reading the position, which the scope section states plainly.
Batch and expiry captured at receiving, with shelf-life short-dated stock visible on the expiry horizon reports before it becomes a write-off. Reorder points are not derived from consumption velocity or supplier lead time — you set a level and the system reports against it.
Every machine with a named custodian, location, condition, warranty expiry and a verification trail. Service and calibration calendars are not built — the honesty note below lists every missing field.
Weekly cycle counts and dispensing-to-stock reconciliation — variances surface in days, not at year-end.
Running in the product now
The clinical layer — on the roadmap, and commissionable now
What we would decline, and would rather say now
Every item in the middle column is an absence rather than a position, and each is commissionable now on the same terms as everything else here — a written specification, a timeline and a price, before any money moves. The evidence that this is a real offer rather than a sales line is Kenya, where the eTIMS transmission and the maintained statutory payroll engine were both built exactly this way, because clients asked for them. We will not name a date on this page, and we will name one in a quote.
We are a stock and asset system for a clinic today, and a good one — batches, FEFO, expiry alerting, enforced quarantine, cycle counts and consumption-driven buying all work now. The equipment calendar is the nearest and cheapest item on the right, since the register it needs already exists. The clinical layer at the bottom of that list is the honest exception: we would rather integrate with your HIS than pretend to replace it. Tell us which of these you need and we will scope it in writing before you commit.
Items, batches, and expiry dates in — the first horizon report usually pays for the project.
FEFO at the pharmacy window; dispensing moves stock in real time from day one.
The register gets service dates; orders start coming from consumption data instead of habit.
A stockout is a clinical event and expired stock is money in the disposal drum — batch tracking, FEFO, consumables par levels, and the weekly hour that runs it all.
Expiry routinely eats 3–8% of drug spend invisibly. Where it comes from, the 30/60/90 routine, and the purchasing habits that stop it at the source.
Broken equipment announces itself; miscalibrated equipment misdiagnoses quietly. Three maintenance tiers, calibration discipline, and the replacement horizon.
A shop sells and a store issues, and the difference decides which movements the replenishment maths can see. Why a hospital store's reorder points work when the same building's pharmacy counter stays silent — and the ward dimension you have to choose before go-live.
The request is always the same shape: show us what happened, and show us you have not edited it since. What an evidence pack contains including the section people do not expect, exactly what a SHA-256 checksum proves, and the row caps worth knowing before you hand one over.
Four people are certain about four different pumps, and all four are remembering something real, because there are eleven and they are identical. What a custody register records that a list cannot, why "verified" is the action nobody uses, and the one thing about equipment it does not do.
Questions we are asked here
Yes — each facility is its own stock location with its own counts, while short-dated stock transfers between branches move medicine to where demand exists. Head office sees consumption, expiry risk, and equipment status across all sites.
Not by a source flag today — that is on the roadmap. There is no program or donor attribute on stock, so KEMSA and program commodities sitting on the same shelf are not separately accountable in reporting as things stand. The usual workaround is a separate location or a distinct item code per source, which keeps the quantities apart but does not give you the single consumption picture you actually want. Program and donor source flags are a scoped build: tell us which programs you report on and we will price it.
Not as a register today; it is on the roadmap. What exists now is generic and still useful — every movement is attributed to a person with a reason, quantities are enforced, and quarantined stock cannot be issued or sold. What is not built is the controlled-substances register itself: per-transaction sign-off, the running balance a regulator asks to see, and the register view that makes an inspection a report rather than a reconstruction. Treat your statutory register as a separate obligation we do not discharge today, and talk to us if you want it built.
Stock moves out accurately; the dispensing-to-billing link is roadmap work. Issuing reduces stock by batch under FEFO, and invoicing and payments exist on the finance side — but there is no dispensing record tied to a patient, and no reconciliation proving that everything dispensed was billed and everything billed was dispensed. That reconciliation, and the patient, prescription and dispensing records underneath it, belong to the clinical layer. Worth saying plainly: that is a health information system, and for most facilities the right answer is to run a dedicated HIS alongside us rather than ask us to become one.
Batch tracking, FEFO, the expiry horizon, and the equipment calendar — demonstrated on your own item list.