Stock-taking software that protects the count
A stock count should tell you what is physically present without destroying what nobody checked. PharmHive separates counting, discrepancy review and inventory correction, preserves saved work, and records who counted each line so the final adjustment has evidence behind it.
Common questions
What happens to products that nobody counted?
They remain uncounted. PharmHive does not silently interpret a missing entry as zero stock. Completion shows what is still open, and an authorized manager override keeps excluded lines unchanged. That protects inventory when a section, device or counter has not finished its work.
Can several people work on the same stock take?
Yes. Shelf- or category-based sections can be assigned to counters, saved counts retain the counter's identity, and the screen shows progress across the stock take. Assignments organize the work; they do not disguise which person submitted a quantity or which sections remain open.
What is a blind stock count?
Blind mode hides expected quantities from ordinary counters so they report what they find instead of copying the system number. Authorized reviewers can inspect expected stock and discrepancies. The setting protects the independence of the count while preserving a separate review step.
Can the pharmacy keep selling during the count?
Yes. PharmHive treats the count as a checkpoint and tracks recorded activity after it. The correction preview distinguishes the quantity at count, later activity, live stock and the projected result, so a sale after counting is not automatically mistaken for missing stock.
Does completing a stock take immediately change inventory?
No. Completion closes the counting stage. The pharmacy still reviews discrepancies and the correction preview, records required reasons, and deliberately applies corrections. Applied changes become inventory movements with an audit trail rather than an unexplained overwrite of the live balance.
What if another device has not synchronized its counts?
The completion barrier shows that counts have not reached the server and keeps completion locked instead of skipping an offline device. Saved work remains part of the in-progress stock take. The team can let the device synchronize or use the controlled manager-override path when the business deliberately accepts the exception.