Here's the test. A manufacturer notice lands in your inbox naming a specific lot number. Not a hypothetical — a real one, pulled off a real vial that went into a real client's face six weeks ago. Can you produce a list of everyone who received that lot in the next few minutes, or does someone have to start pulling paper charts and squinting at handwritten stickers?
What a Lot Number Actually Does
A lot number ties a specific client to a specific manufacturer batch. Not the product name, not the expiration date — the lot number is what connects a syringe to the run it came off of. If something goes wrong with that batch, the lot number is how you know whether your client was anywhere near it.
Your job as the practice is narrower than the manufacturer's. You don't have to trace the batch. You have to be able to identify who received it, and respond quickly when asked.
What Belongs on the Chart, and When
At minimum, an injectable visit record needs the product, the lot number, the provider's notes, and — where relevant — the dosage, captured while the vial is open on the tray, not reconstructed from memory after the client has left and the room's been reset.
That timing matters more than people think. A provider trying to reconstruct which lot went into which client at the end of a twelve-appointment day is relying on memory, and memory is exactly the failure mode a lot number exists to route around. If the record depends on someone remembering which box the vial came out of, you don't have a record. You have a guess with a lot number attached to it later.
Run the Recall Scenario for Real
The notice names a lot. Now what.
If your system holds lot numbers as a structured field on the client record, this is a search: filter every chart where that lot appears, and you have your list — names, contact info, appointment dates. You notify people, document that you notified them, and move on with your day.
If it isn't structured, someone starts flipping through paper charts, or cross-referencing a spreadsheet that was last updated by whoever was covering front desk three weeks ago and might not match what's actually on the chart. Maybe you find everyone. Maybe you don't, and you find out you missed someone when they call in with a reaction and ask why nobody told them.
Why Salon-Built Platforms Don't Have This Field
If you're running Mindbody, Vagaro, Boulevard, or a similar salon-first platform and you've gone looking for a lot number field, you've probably noticed there isn't one. These tools track services and time slots. An injectable-heavy practice running its clinical record on that kind of system is tracking the wrong unit of the visit — when what actually needs tracking is product, lot, and site.
A separate spreadsheet is a workaround. Workarounds get skipped on a busy day, and a recall isn't a good day to find out which one you skipped.
Where It Lives on One Record
The way we built client charts at Lumè, the lot number isn't a separate log you have to remember to update. It's a field on the same client record that carries treatment history, provider notes, dosages, and before/after photos.
The lot number sits right next to the provider note and the photo from that same visit. Not in an inventory app you check separately, not in a binder at the front desk — on the chart, at the point where the injection happened. When a recall notice comes in, you're running a query against a record that was already complete the day it was written.
The EHR Line
This is clinical documentation, not a certified EHR. A lot number field on a treatment record isn't the certified electronic health record infrastructure a full medical clinic writing prescriptions is required to run. Practices in that position still need a certified EHR alongside whatever CRM they use for scheduling and client management.
Capture It in the Visit, Not at the End of the Day
Build lot capture into the visit itself — the same moment the provider is opening the vial and noting the injection site. Not as something reconciled at the end of the day from memory or a stack of used vial stickers.
It's the same logic behind e-signed, versioned consent being auto-sent on booking and stored on the chart, rather than handled as a separate stack of paperwork someone has to remember to collect later. Anything treated as end-of-day cleanup gets skipped on a busy day. Anything built into the workflow at the point of service gets done.
The Honest Standard
None of this is a guarantee against liability, and we wouldn't claim otherwise. It's defensible recordkeeping — the kind that means you can answer the recall question in minutes instead of hours, and document that you did.
Weigh that against sticker price when you're comparing systems. Total cost, not the sticker: it's whether the system can answer this specific question fast, on the day you actually need it to.