Controlled-substance handling, age verification, signed proof of delivery, and regulator-ready audit trails.
Pharmacy delivery is one of the most regulated last-mile categories. Controlled substances require signed proof of delivery; certain medications require recipient age verification; medical-courier handovers between pharmacy and patient have regulator-defined time windows in most GCC and South-Asian markets. SortDrops Team supports signature capture, photo proof, per-stop service time for verification, and a dispatch session export suitable for regulator audit.
Regulator-driven proof of delivery is the dominant non-routing constraint. Every controlled-substance handover must be evidenced by a captured signature (or biometric equivalent), a timestamp, and a recipient identifier. SortDrops Team captures all three on the driver-link — drawn signature, server timestamp, and recipient name field — and the dispatch session CSV export combines them into a single regulator-ready document.
Age-restricted medications add a per-stop verification step. The driver must visually confirm the recipient is over the regulator-defined age (typically 18 or 21) before handover. SortDrops doesn't process the verification automatically, but our per-stop service-time field absorbs the 60–90 second visual ID step and our stop-notes feature lets the dispatcher flag a specific stop as 'age-restricted, verify' so the driver sees it on arrival.
Time windows from pharmacy to patient are tighter for cold-chain medications (insulin, biologics) than for ambient drugs. Cold-chain pharma uses sealed cool packs with a typical holdover of 2–4 hours, much longer than grocery cold-chain. SortDrops Team per-route maximum-duration constraint handles this — set the pharmacy-defined holdover and the optimizer respects it.
A typical mid-sized pharmacy chain delivery: customer orders via app or phone, pharmacy fills in 30–60 minutes, dispatcher exports the ready-for-delivery roster every hour and runs SortDrops to assign across 3–6 drivers. Most pharmacy chains in the GCC run a 'within 2 hours' delivery promise for ambient medications and a 'within 90 minutes' promise for cold-chain. SortDrops respects per-route duration caps and per-stop time windows.
Driver workflow on arrival: park, walk parcel and signature pad to door, ring bell, verify recipient identity (name + age if applicable), capture signature on driver-link, capture optional photo, mark stop complete. The whole sequence is 4–6 minutes per stop on average — significantly longer than the 2-minute ordinary parcel handover, so the optimizer service-time-per-stop should reflect that.
End of day reconciliation is regulator-driven. The dispatcher exports the dispatch session as CSV (or PDF on Team), filtering for controlled-substance stops, and stores the document per the regulator's retention schedule (typically 5 years in the UAE). SortDrops dispatch session export is purpose-built for this.
Chain of custody for controlled-substance pharma is a multi-step record: pharmacy hands off to driver (record 1), driver hands off to recipient (record 2). SortDrops captures record 2 — the driver-to-recipient handover. Record 1 (pharmacy-to-driver) is typically managed in the pharmacy POS or e-prescription system. We integrate via Excel/CSV import to keep both records linked by order number.
Age verification is a manual step at handover. SortDrops surfaces the per-stop note ('age-verify, 18+', 'age-verify, 21+') prominently on the driver-link and the driver confirms via a checkbox before completing the stop. The checkbox state is recorded in the stop record and exported to the dispatch session.
Refusals: if the recipient cannot pass age verification or refuses delivery, the driver marks the stop as failed with reason 'age-verify-failed' or 'refused', and the parcel returns to the pharmacy. SortDrops fail-and-retry workflow handles the return-to-pharmacy stop automatically.
Yes — Team feature. Driver captures a drawn signature plus optional timestamped photo on the driver-link, and both attach to the stop record. The dispatch session export collates all signature/photo evidence into a single regulator-ready document.
Age verification is a manual step at handover; the driver confirms via a checkbox on the driver-link before completing the stop. The dispatcher flags age-restricted stops in advance via the per-stop note field, so the driver knows to verify on arrival.
The CSV/PDF export contains stop-level signature, timestamp, recipient name, and reason codes for any failed delivery — the components most regulator audits require. Confirm the specific format requirement with your DHA / MoH / MoPH compliance officer; we can extend the export for specific format needs on Team plans.
Yes. Per-route maximum-duration constraint (Team) lets you cap a route at 90 minutes (typical cold-chain pharma holdover), and the optimizer refuses to produce a longer route. If the load doesn't fit, the optimizer prompts to split or add a driver.