How the software runs through a pharmacy shift
In the morning a distributor’s delivery arrives: the pharmacist scans the packs, the goods land in stock at once and the printer produces price tags. During the day a customer names a medicine, the pharmacist finds it by name or scans the box, sees price and stock, and rings up the sale. Frequent actions sit on keyboard shortcuts, so the queue does not wait while someone hunts for a button. In the evening the shift closes, sales go to the server and the director sees revenue and stock for every branch. Expiry dates, batches, selling by the blister and markup rules are specified with you in the brief and priced before the contract is signed.
What drives the price
A full pharmacy till is the Workstation level, from $15,000: Windows and macOS, offline mode, receipt and label printing, scanners and auto-update. Enterprise is for chains: server sync, staff roles, Linux for terminals and cash-register hardware. If all you need is a standalone single-task Windows tool, such as barcode receiving, the entry Utility level covers it and costs less than a till. 1C sync, fiscal receipts through an online cash register and an AI assistant that finds products from a plain-language description are separate lines; the AI runs on OpenAI models only. Cost is driven by rules rather than screens: markups, transfers between branches, reports cut the way you need them. The configurator adds it up and the contract fixes it.
Off-the-shelf or custom
For a single pharmacy with standard processes, an off-the-shelf product is a sound choice: it costs less up front and starts quickly. A custom system makes sense once a chain has rules it keeps working around by hand. Markups depend on supplier and product group, stock moves between branches, the owner wants reports in a specific shape, and accounting already lives in 1C. There is also the per-till subscription, which grows with the chain, while a custom system is built once and then shaped around your processes. Exchange with government systems, such as Uzbekistan’s electronic prescription module, is not part of the standard scope: if you need it, we study the requirements and price it separately.
How the work runs and what the contract says
We start by walking through the processes with your pharmacists: receiving, sales, returns, transfers, closing a shift and the exceptions to every rule. Then come screen mockups and the build. You get a working version every two weeks and test it on your own scanner and printer, not on a demo bench. Before launch we test offline mode: the connection drops, sales continue, and once it returns the data reconciles without duplicates. The timeline from 8 weeks is in the contract; every day of delay cuts the invoice by 2%, up to 10% of the contract. Bugs are fixed free with no time limit, and your own engineer may audit the code against the contract: any unfulfilled item means a 10% refund.