May 26, 2026 · By the RxRescue Team
Cycle counting without closing the pharmacy
The traditional pharmacy inventory count is a project. Pick a Sunday. Close the pharmacy. Print a count sheet. Walk every shelf with a clipboard. Mark every bottle. Reconcile to the system. Re-count the disagreements. Apologize to the staff who lost their weekend.
The result — the spreadsheet that says you have n bottles of x drug — is correct on Sunday evening. By Tuesday it is already drifting. By the time the next annual count rolls around, the variance is large enough that the next annual count is the only way to get a clean number again. The cycle, ironically, is the all-or-nothing count itself.
Cycle counting is the alternative pattern: count a small subset of inventory continuously, on a rotating schedule, while the pharmacy stays open. The variance is fresh every day instead of stale for eleven months. The disruption to operations is zero. And the audit, when it comes, is never a project — it is just always partway done.
What cycle counting actually is
The mechanics are simpler than the name suggests. The pharmacy is broken into named sections — a fridge, a controlled-substance cabinet, a back wall of stable generics, a short-dated bin, a high-velocity dispensing shelf, a quarantine zone. Each section has an assigned cadence: the fridge gets counted every week, the cabinet every two weeks, the back wall every quarter. The cadences are calibrated to the actual movement and risk profile of each section, not to a single calendar number that has to work for everything.
On any given day, one or two sections are due. A tech walks those sections, scans the bottles, the system compares to its own record, and any discrepancies surface immediately. The tech resolves them while the bottle is still in hand — before the chain of memory breaks. The next day, a different section is due. The day after that, another. Over the course of a month, every section has been touched at least once. Over a quarter, every section has been touched at the cadence its risk profile warrants.
The pharmacy never closes. The data is never more than a few days stale. The variance between system and shelf, if everything is working, hovers near zero indefinitely.
Why monthly walks aren't cycle counting either
Many pharmacies think they already cycle count because someone walks the shelves once a month with a printed report and marks expirations or short stocks. That is a monthly inventory check, not cycle counting, and it has three structural problems:
It runs at the same cadence for everything. The high-velocity dispensing shelf and the slow-moving back wall get the same monthly attention. The fridge that needs weekly review and the back wall that could go quarterly are both squeezed into the same cadence. The cadence is wrong for both ends of the distribution.
It is a parallel process to the system of record. The clipboard or printed report is a snapshot from when the report was generated. By the time the walk is done, the system has moved. The disagreements get reconciled in a batch later, by someone reading handwritten marks, and the reconciliation introduces its own errors.
It depends on one person. The monthly walk is usually a single technician's job. When that tech is out, the walk slips. When that tech leaves, the workflow leaves too. Real cycle counting is everyone's job, in small daily increments, against a live system.
Designing a cycle-counting schedule that works for a busy pharmacy
The hardest part of cycle counting is not the counting. It is the section design and cadence calibration. Get those right and the workflow is mostly self-sustaining; get them wrong and staff push back inside a month.
Start with named, bounded sections. "The fridge" is a section. "Everything else" is not a section. Each section should be physically bounded (a shelf range, a cabinet, a bin) so a tech can be told "count Zone 3" and know exactly what's included without judgment calls. Sections should be small enough that any single count can finish in 10–20 minutes — a tech can fit that into a shift without disrupting dispensing.
Calibrate cadence to risk, not to balance. The temptation is to set every section to "monthly" or "quarterly" so the calendar balances. Resist it. Each section should be counted at the cadence its risk profile warrants: refrigerated stock weekly, controlled substances every two weeks, short-dated bins weekly, high-velocity dispensing biweekly, stable back-wall generics quarterly. Some sections deserve a tighter cadence than the calendar wants to give them. That is fine — the workload still distributes evenly across days because not every section comes due on the same day.
Let groups share a cadence where it makes sense. If three short-dated bins all need weekly review, group them so they come due together and one tech can knock them out in a single 30-minute pass. If two storage cabinets in different rooms have the same monthly cadence, group them too. Grouping reduces context-switching and lets a tech batch work efficiently. It also makes the audit trail cleaner — one timestamped count for the group, instead of three separate counts at three separate times.
Let the system remind you. The whole point is to remove cycle counting from anyone's mental load. The system should know which section is due, surface it on the dashboard, and not let it slip past its cadence quietly. A red flag on the home screen is more reliable than a calendar reminder on someone's phone or a sticky note on the monitor.
What software needs to do to support real cycle counting
Most pharmacy management systems support cycle counting only as a feature label, not as a workflow. The CSV export gets called a "cycle count report" but it is still an annual-count print-out with a different name. Real software support has a small but specific set of requirements:
- Configurable sections, named by the pharmacy. Not predefined zones the vendor decided. The fridge is the fridge because that is what the staff calls it; the system should let them call it that.
- Per-section cadence configuration. Not a single global setting that applies to all inventory. Each section gets the audit frequency it actually needs.
- Live status: due, in-progress, audited-today, settled. A color-coded list at the start of every shift that tells staff what is due today is the difference between cycle counting that survives staff turnover and cycle counting that quietly stops working when one person leaves.
- Scan-driven counts against live data. The tech scans bottles in the section; the system compares to its own record in real time; missing bottles are surfaced before the count ends. No paper, no batch reconciliation later.
- Per-section grouping for related zones. If three sections share a cadence, the audit run should be able to address all three in one pass.
- Audit-pack inclusion. Every cycle-count run should be a row in the audit log with a timestamp, operator, and result. When the inspector asks for proof of an ongoing inventory program, the cycle-count history is the proof.
The shift
The shift is from inventory as an annual project to inventory as a continuous workflow. A pharmacy that runs it the second way operates with fresh data continuously, catches discrepancies before they compound, and walks into an audit calm instead of anxious — because the cycle-count history is the answer to most of the questions an inspector asks.
The annual count, in this model, becomes a confirmation step rather than the source of truth. It runs once a year because compliance still requires it on paper, but the actual inventory accuracy comes from the daily rhythm.
RxRescue is built around this pattern. The pharmacy defines named sections, each section gets its own cadence, the dashboard surfaces which sections are due today, and each run is a scan-driven audit against live data — not a parallel paper process. See how it works on the correctional pharmacy inventory and expiration tracking pages, or start a 30-day free trial.