Many inventory problems begin at the receiving table. A rushed delivery can leave the system with the wrong quantity, the wrong unit cost or one expiry date attached to several different batches.
A pharmacy goods-receiving checklist creates a deliberate handover between delivery, inspection, stock entry and put-away. This is an operating worksheet; product-specific instructions and applicable requirements still govern handling.
Prepare before opening the cartons
Have the purchase order and a suitable receiving area ready. Assign a receiver and identify any items requiring priority handling. Avoid leaving deliveries unattended at the counter while the staff member serves a queue.
Capture supplier, order reference, invoice, arrival time and receiver. Record discrepancies while the delivery evidence is available. Separate what arrived from what has been accepted for available stock.
Check identity before quantity
Match the product name, strength, dosage form and pack description. Similar packaging does not make two products interchangeable. Confirm the actual barcode where used and investigate mismatches before creating duplicate records.
For each batch, capture quantity, expiry and the required storage conditions. Inspect packaging and any relevant transport evidence. Products with damage, quality concerns or unresolved handling questions should follow the appropriate assessment process, rather than be made available because the invoice was entered.
WHO's good storage and distribution guidance provides background on receiving and storage controls. Do not replace product-specific conditions with a single assumed temperature range.
Count in the correct unit
Suppose the order is for six boxes, each containing ten strips of ten tablets. The delivery represents 600 tablets, 60 strips or six boxes, depending on the recorded unit. Entering “six” without a unit can change the stock balance by a factor of 100.
Use a conversion worksheet:
product,batch,purchase_unit,purchase_quantity,base_units_per_purchase_unit,accepted_base_units,expiry,location
Check free quantities and short deliveries separately. If the invoice includes a bonus quantity, record the physical quantity and cost treatment consistently; do not create unexplained stock just to match the commercial offer.
Match the purchase and financial records
Compare ordered quantity, delivered quantity, accepted quantity and invoiced quantity. Record price differences and credit requests. A partly received order should remain partly received until the remaining items are resolved.
Avoid putting a disputed delivery into available stock solely to close a purchase order. Where goods are accepted, ensure the batch and location records support the put-away routine. Rotate appropriately by expiry while preserving product identity.
Finish with a second-person check
For higher-risk or high-value lines, review conversions and batch entry before releasing the record. Then confirm the physical stock reached the intended location and the system reflects only the accepted quantity.
Retain the order, invoice, receiving record and discrepancy evidence together. A concise exception note should state what differs, who contacted the supplier and when a response is expected.
A first-week quality check is to sample a few received lines the next morning: can another person find the invoice, locate the exact batch and reconcile the quantity? That is a more useful test than asking whether every form was filled out.
For software developers, receipt posting should be idempotent: submitting a request twice should not double the stock. Partial receipts, batch splits and approval states deserve explicit records rather than being hidden in one “completed” field.
RunMyPharmacy's purchase-order tools and inventory-management pages provide relevant workflows to review against this checklist. Confirm the exact supported behaviour in your trial.
Disclosure: written for the RunMyPharmacy team with AI drafting assistance and an editorial check of examples, links and product claims. We build the linked product. Examples are hypothetical; worksheets and illustrative software-design advice are not guarantees of product automation.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.