Clinic Supplies Procurement: Buying on Data, Not Habit
Gloves, reagents, test kits, and the distributor relationship — buying clinic supplies on consumption data instead of habit, with supplier discipline that protects both price and shelf life.
Clinic purchasing has a habit problem. The order to the distributor looks like last month's order, which looked like the month before — quantities set by tradition, prices unchallenged since the relationship began, and delivery accepted on the driver's word. Meanwhile the actual clinic changed: patient load shifted, the lab added a test, two products expired in the store. Buying on habit when you could buy on data is the most expensive convenience in facility management.
Consumption is the order sheet
A facility whose dispensing and issues move stock in real time already owns the only number that matters: consumption per item per month. From there, ordering is arithmetic:
- Reorder point = consumption velocity × supplier lead time + safety buffer sized to how critical the item is clinically.
- Order quantity = expected consumption to next order − stock on hand − stock on order. Not "a box", not "same as last time".
- Review quarterly: items where orders persistently exceed consumption are your next expiry write-offs; items with repeat stockouts need bigger buffers or faster suppliers.
Suppliers: relationship plus verification
| Practice | Why it pays |
|---|---|
| Annual price comparison across 2–3 distributors | Loyalty premiums grow quietly; a yearly RFQ resets them — keep the supplier, verify the price |
| Minimum shelf-life terms in writing | Short-dated deliveries become refusable instead of arguable |
| Return terms negotiated upfront | A distributor who takes back 60-day stock is cheaper per dispensed unit than the discounter who refuses returns |
| Delivery verified against the order | Quantities, batches, and expiry checked before signing — the driver's manifest is not your receiving record |
| Performance tracked per supplier | Fill rate, lead time, and short-delivery history — data for the annual negotiation |
This is the standard three-way discipline — order, delivery, invoice must agree — with the clinical addition that receiving also checks batch and expiry against your shelf-life policy.
The KEMSA/program layer
Facilities drawing from KEMSA or program pipelines (government commodities, donor programs) run two supply chains in parallel. Keep program stock flagged by source in the same system: separate accountability, same shelves, one consumption picture — so your commercial orders account for what the program pipeline already covers.
Approvals sized for a clinic
- Routine consumables within budget: clinic manager approves, weekly batch.
- New items and formulary additions: clinical lead signs off — purchasing should not introduce products clinicians didn't choose.
- Above a threshold or off-contract: administrator/owner approval, in the system, before commitment.
- Emergency purchases: allowed, documented within 48 hours, reviewed monthly — the same emergency lane discipline any institution needs.
Purchasing discipline is the upstream half of stock control: it decides what enters the store at what price and shelf life. The downstream half — batch tracking, FEFO, and the weekly rhythm — decides what happens after. AWRA for clinics runs both halves from the same consumption data.
What AWRA OpsHub does today
- Procurement with teeth — requisition, approval thresholds, RFQ comparison, purchase orders, receiving and three-way matching, with supplier on-time rate, quality score and pricing trend tracked per vendor.
- Approval thresholds are configurable, so the tiered sign-off in this post — routine, new item, above threshold — maps onto real gates rather than habits.
- Reorder points that alert the moment they are crossed — edge-triggered on the stock movement itself rather than on a scan, with a daily digest at 08:30 as well — and an automation that raises a procurement request when an item crosses its point.
- Batch, lot and serial tracking — expiry date, supplier and originating purchase order recorded on every batch, with serial numbers where you need them.
- Batch and expiry are captured at receiving, so shelf life at goods-in is visible on the record.
- Supplier performance — on-time delivery rate, quality score and pricing trend per vendor, which is the verification half of the relationship-plus-verification rule.
More we can add to your workspace
- Computed consumption velocity. The reorder point is a number you type and maintain today; deriving it from consumption per item per month, with a turnover report to read it off, is the build.
- A suggested order quantity. The auto-raised request currently closes the distance to the reorder point; suggesting expected consumption less stock on hand less stock on order is the build.
- A shelf-life policy at receiving. You can see remaining life; you cannot set a minimum and have goods-in warn or block.
- A program or donor source flag on stock, so KEMSA and program commodities cannot be separately accounted on the same shelves.
- An emergency-purchase lane as a distinct, retrospectively documented route — you would model it as an ordinary requisition with a note.
- Three-way matching is exposed on the API, not as a screen in the purchasing workflow.
This is the closest fit of the four clinic posts. Approvals, purchase orders, receiving, supplier performance and reorder triggers are all real, and the tiered sign-off maps cleanly. What the middle column adds is the arithmetic at the front: this post tells you to order from consumption data, and the consumption calculation is the piece to commission. Until it ships, the reorder points you set by hand are doing that work.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsOrder from data, not from habit
Requisitions with approval thresholds, RFQ comparison, purchase orders with receiving and matching, supplier performance, and reorder triggers that raise a request automatically. The consumption arithmetic is not built — see the note above.
See clinic procurement in AWRAFrequently asked questions
How many suppliers should a small clinic maintain?
Two to three for the main consumables lines — enough for annual price comparison and stockout backup, few enough that volumes stay meaningful per supplier. Single-supplier convenience is fine only as long as you verify its price annually.
Is it worth negotiating with distributors at small volumes?
Yes — on terms more than price. Shelf-life minimums, return windows, and delivery reliability are negotiable at any volume, and they are worth more than a 2% discount. Price leverage grows when you consolidate orders monthly instead of buying in dribs.
How do we set safety stock for critical items?
Classify items by clinical criticality: for the short list where a stockout is a clinical event (emergency drugs, oxygen, essential antibiotics), carry generous buffers and accept the carrying cost. For everything else, let consumption velocity and lead time set the number. One blanket policy fails both groups.
Who should own purchasing in a clinic — the pharmacist or the administrator?
Split it: the pharmacist/clinical lead owns what and how much (formulary, quantities from consumption), the administrator owns from whom and at what terms (suppliers, prices, approvals). One person owning both ends unchecked is how habit purchasing and supplier capture happen.
