Before signing with pharmacy automation companies, an independent pharmacy should ask five things in writing: how the machine connects to your pharmacy management system, what error and event logs it keeps and who can read them, the exact support terms and response times, what the contract costs over its full term, and how you leave and take your data with you.
The caveat: these are commercial and contract questions, not clinical ones. Accuracy and safety claims need the vendor's own evidence, your professional body's rules and a pharmacist's judgement. The commercial side is where independents most often get caught, for example by a lease with a 50% early-exit charge or consumables that only one supplier can provide.
What you are actually buying
Pharmacy automation is a loose label. One vendor sells a counting and vial-filling machine, another sells pouch or blister packaging for adherence packs, another sells storage and retrieval. For example, Parata's own site lists vial filling, adherence packaging, central fill, controlled substance management, will-call, workflow software and inventory management, and Omnicell lists medication adherence products, such as packaging machines and guided packing software, under its outpatient range. These pages describe product ranges rather than prices, and neither tells you what suits a pharmacy of your size.
Start by naming the job you want done. Is it speed in the vial-filling queue, adherence packs for a growing group of patients, or less time spent finding stock? Each job points to a different product and a different contract. A buyer who cannot say which job comes first tends to buy the most impressive machine.
Then write down your numbers, because every vendor will ask. Prescriptions dispensed per day, the share that are repeat items, the number of adherence packs you prepare by hand each week, and the staff hours those take. Even rough figures make quotes comparable. See the two-week routine task audit for a simple way to collect them.
The checklist, group by group
Each item has a question, why it matters and how to check the answer. Print it, take it to each vendor meeting and write the answers on the sheet.
Group one: connection to your systems
- Which pharmacy management systems does it connect to, and is yours one of them? Why: a machine that cannot receive labels or orders from your system forces double entry. Check: ask for the interface name and a reference pharmacy running the same combination.
- Is the connection built and supported by the vendor, by your system supplier, or by a third party? Why: when something breaks, three parties blame each other. Check: ask who answers the phone first and get it in writing.
- What happens when the connection drops? Why: you need a manual fallback that your team can run. Check: ask the vendor to demonstrate working without the connection.
- Who pays when your system supplier changes its software? Why: updates can break an interface, and the cost of fixing it is rarely mentioned. Check: look for a clause on interface maintenance.
Group two: error logging and records
- What does the machine record for each action? Why: when a problem is questioned, you need to show what the machine did and when. Check: ask to see a sample log from a real or demo unit.
- How long are logs kept, and can you export them? Why: records should outlast the contract. Check: ask for the retention period and the export format.
- Who can see the logs, and does the vendor access your data remotely? Why: a remote connection is a security and privacy question. Check: ask what data leaves your premises, where it is stored and under which terms. Your data-protection rules will apply, and your adviser should read this part.
- How are faults and near misses reported to you? Why: you want alerts, not a surprise when you cash up. Check: ask to see an example alert.
Group three: support terms
- What are the support hours, and what is the target response time? Why: a breakdown on a Friday afternoon is a different problem from one on Tuesday morning. Check: get hours and targets in the contract, not the brochure.
- Is there a loan or replacement unit while yours is repaired? Why: a pharmacy cannot stop dispensing for a week. Check: ask how many units sit within your service area and what the contract promises.
- Who does preventive maintenance, how often and at what charge? Why: it is a recurring cost. Check: ask for the maintenance schedule and whether it is included.
- What training is included, and what does extra training cost? Why: staff turnover means you will need it again. Check: ask for the hours included and the day rate after.
Group four: money over the whole term
- Purchase, lease or subscription, and what is the total over five years? Why: a low monthly figure can hide a large end-of-term payment. Check: ask for a five-year schedule that includes consumables, support and maintenance.
- What are the consumables, and are they tied to the vendor? Why: packaging film, labels or cassettes may be the largest running cost. Check: ask for the price per unit and the price history.
- What price rises are allowed during the term? Why: an uncapped rise is a risk. Check: look for a cap or a fixed schedule.
- Is the price quoted for your volume? Why: some pricing assumes volumes you may not reach. Check: ask what happens if your volume is lower or higher.
Group five: leaving
- What is the notice period and the early termination cost? Why: this sets the real length of the commitment. Check: ask for the figure in writing and a worked example.
- Who owns the data, and in what format can you take it? Why: you may need records for years after you stop using the machine. Check: ask for an export in a standard file.
- What happens to the machine at the end? Why: removal, resale or trade-in can carry charges. Check: ask who pays for removal and whether there is a buy-out price.
- What happens if the vendor is bought or stops supporting the product? Why: the sector consolidates, and the company that signed may not be the one supporting you. Check: ask for a clause covering support continuity.
A filled-in example for a mid-sized independent pharmacy
Take an illustrative independent pharmacy that dispenses about 220 items a day and hand-prepares around 90 adherence packs a week. The owner is comparing two quotes. These figures are made up to show the method and do not describe real products.
| Item | Quote A | Quote B |
|---|---|---|
| Equipment price | $38,000 purchase | $890 a month lease for 60 months |
| Support | $3,200 a year, next-business-day | Included, 4-hour response target |
| Consumables | About $600 a month, vendor only | About $520 a month, vendor only |
| Interface to the pharmacy system | $2,500 one-off, third-party built | Included, vendor built |
| Early exit | None, you own it | 50% of remaining payments |
Over five years Quote A costs 38,000 plus 2,500 plus 5 times 3,200, which is 16,000, plus 60 times 600, which is 36,000, so $92,500. Quote B costs 60 times 890, which is 53,400, plus 60 times 520, which is 31,200, so $84,600. Quote B looks $7,900 cheaper, and its support is quicker. But the early-exit clause means that leaving after year two would cost half of the remaining 36 payments, so about $16,020. Quote A has no exit cost, though you carry the risk of owning a machine that may be hard to resell. The table does not decide the choice. It makes the trade-off visible, which is the job of the checklist.
Scoring the answers
For each of the 20 items, score the vendor 0 if the answer is missing or vague, 1 if it is given verbally, and 2 if it is in the written quote or contract. Add up the points per group. A vendor can be strong in one group and weak in another, and the score shows which group to push on in negotiation.
Treat any 0 in group one or group five as a reason to pause. Those are the groups that are hardest to fix after signing. A vendor who scores 2 on support but 0 on exit has told you how they will treat you at the end of the relationship.
Contract wording to look for, and wording to question
You do not need to be a lawyer to spot clauses worth a second look. The table sets out phrases that commonly appear in equipment agreements, in a before and after form. The wording is illustrative, and your adviser should review the real text.
| Topic | Wording to question | Wording that is easier to live with |
|---|---|---|
| Support response | "The supplier will use reasonable endeavours to respond promptly." | "An engineer will respond within 4 working hours and attend within 1 working day." |
| Price rises | "Prices may be varied from time to time." | "Annual rises are capped at 3% or the stated index, whichever is lower." |
| Renewal | "The agreement renews automatically for a further full term." | "The agreement continues month to month after the initial term, on 60 days' notice." |
| Data | "Data remains available while the agreement is in force." | "The customer may export all logs and records in a standard format at any time and for 90 days after termination." |
| Interface | "Integration is subject to third-party cooperation." | "Go-live of the interface by [date]; if missed, payments are suspended until it is live." |
When a clause sits on the left, you can still sign, but ask what it costs you in practice. Vendors often have a standard version and a negotiated version, and the second costs nothing to request.
A day when the machine stops: what the logs should tell you
The point of asking about error logs is the day something goes wrong. Imagine a mid-afternoon jam that stops a packaging run with half the batch complete. You need to answer four questions quickly, and a good log answers each one.
- What stopped, and when? A time-stamped fault entry with a code.
- Which orders were in progress? A list you can reconcile against your dispensing records, so nothing is lost or duplicated.
- Who was operating it? A user entry, so the cause can be reviewed without blame.
- What was done to clear it? A record of the action, so a repeat fault can be traced.
Ask the vendor to walk through exactly this scenario on a demo unit, and watch whether the screen or the report gives you those four answers. If the answer is that a technician will tell you later, you are depending on the vendor for your own records. Also ask how a near miss, where the machine stopped itself or flagged a problem, is shown. A system that records only failures hides the early signs.
Go-live checklist for the first week
Even a good purchase fails in the first week if nobody planned it. Agree this list with the vendor before the installation date, and put the dates in the contract.
- Interface tested end to end with your real pharmacy system and sample records, signed off by you.
- Every user trained and listed, with the names written down.
- A written manual fallback, tested once, so staff know what to do if the machine is down.
- The vendor's support number, account reference and escalation contact on the wall by the machine.
- A named person in your team who owns the machine's daily checks.
- A date for a review with the vendor at 30 days.
The 30-day review, with a filled-in sheet
A review at day 30 tells you whether the promises held. Fill in a one-page sheet and bring it to the vendor. These figures are illustrative.
| Measure | Promised | Actual in month one | Action |
|---|---|---|---|
| Interface go-live | Day 7 | Day 12 | Claim the agreed payment suspension |
| Support response to faults | Within 4 working hours | Within 4 hours on 5 of 7 calls | Ask for an explanation of the two late calls |
| Staff hours saved on packaging | About 10 a week | About 6 a week | Check training and layout |
| Consumables cost | $520 a month | $610 a month | Ask for the usage breakdown |
The sheet turns a feeling that "it is not quite what we expected" into a list of specific items. Vendors respond better to dated, numbered gaps than to general disappointment, and the sheet helps if you ever need to invoke the exit clause.
Using AI to prepare, and what to keep out of it
An assistant is a fair tool for preparing questions and comparing documents. It is a poor tool for judging the contract or handling patient information. Never paste patient data, dispensing records or anything identifying a person into a general chat tool. Contract text and quotes with your pharmacy's own figures are the kind of material you may share, subject to your own confidentiality terms.
A prompt that helps you prepare for a vendor meeting:
I run an independent pharmacy and I am comparing two automation quotes. I will paste each quote's text below.
List, for each quote, the clauses on: support hours and response time, price rises, consumables, early termination, data ownership and what happens at the end of the term.
Present them in a table with one column per quote, and mark any item that the quote does not mention as "not stated".
Do not give legal advice and do not guess any figure that is missing.An illustrative reply would be a table with rows for each clause, where gaps appear as "not stated". What I would fix: check that the table quotes the contract accurately rather than paraphrasing it, since summaries can smooth over a limiting word such as "reasonable endeavours". Then send the "not stated" rows back to the vendor as written questions. A lawyer should read the final contract, and the AI table is preparation for that conversation.
Running the vendor meeting
Go into each meeting with the sheet and two colleagues, ideally the person who will use the machine daily and the person who deals with your system supplier. Ask the vendor to send you a written answer to every item you could not score 2 on. A vendor who answers quickly and plainly is previewing how they handle support.
Ask to visit a working site of similar size. When you do, watch the staff, not the machine. Ask them how often it stops, what they do when it does, and how the vendor responded the last time they called. Do not ask the vendor to choose the site, since they will pick their best one. Ask for two and let the vendor name one, while you pick the other from a list of customers.
Mistakes that turn a good quote into a bad contract
Signing on the demo. The demonstration used ideal data in an ideal room. Ask for a trial with your own workflow, or a site visit, before signing.
Leaving the interface until after the contract. The machine arrives and the connection is not ready, so staff re-key labels for weeks. Make the interface a dated milestone, with a right to delay payment if it slips.
Ignoring consumables. A cheap machine with tied consumables can cost more than a dear one with open supply. Compare the five-year figure, not the price on the front page.
Accepting an automatic renewal. Many agreements renew unless you give notice in a window. Put the notice date in the diary on the day you sign.
Forgetting the people. Automation changes jobs. Plan training, change the written procedures and agree who checks the machine's output each day. Writing pharmacy SOPs with AI shows a way to draft the updated procedures, and a professional must approve them.
Where this fits with the rest of your pharmacy's technology
Automation is one purchase among several. If you are also considering AI for phone queues or stock ordering, decide the order of projects before you sign, since a three-year automation contract will absorb the budget and attention for a while. Compare the payback of AI stock ordering with the machine, and read which tasks should never be handed to AI so the plan has clear limits. If you would like help turning the checklist into questions for your own system, my AI implementation consultation covers it.
Questions pharmacy owners ask before buying automation
How many vendors should I get quotes from?
Three is usually enough: it gives you a price range and shows which terms are normal. Ask each for the same written scope, covering your daily volume, your pharmacy management system, installation, training and support, so the quotes can be compared line by line instead of by headline price.
Should I ask for a reference from a similar pharmacy?
Yes, and ask for one of similar size that has used the system for at least a year. Ask what went wrong in the first three months and how long support took to fix it. A vendor who cannot name a comparable site is telling you something.
Can I use AI to read the contract?
AI can summarise a contract and list clauses on notice periods, fees and liability, which helps you prepare questions. It does not replace a lawyer or a qualified adviser, and you should not paste confidential patient data into a general assistant. Use it to prepare, then have a professional review the final text.
What if the vendor says integration is standard?
Ask them to name your pharmacy management system, say which interface the connection uses, and show it working at another site. Standard integration with one system does not mean it works with yours, and the connection is the part that most often delays go-live.
Further reads
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Parata (BD Parata) pharmacy automation page and Omnicell outpatient pharmacy pages, fetched 27 October 2026. No vendor pricing or clinical performance figures are quoted.