Saydalia binds logger data to the shipment instead of the invoice, so every lot carries its own temperature history from the distributor's cold room to the dispensing counter — and an excursion is flagged at the door, while refusal is still possible.
Scroll the chart sideways to read the full journey.
A shipment record as Saydalia renders it. The trace is the logger's own data, read at the door; the amber section is the 3 h 48 m the pallet spent above 8 °C on a loading dock. Sample data, shown to illustrate the interface.
An insulin shipment that spent four hours on a loading dock in August is indistinguishable, at the counter, from one that never broke the chain. The box looks the same. The barcode scans the same. The stock system says the same thing it always says: received, 240 units.
Your ERP knows how many boxes arrived and what they cost. It does not know what temperature they were at between the distributor's cold room and your shelf, and it has nowhere to put that answer if you found it.
Logger data that arrives as a PDF a week later documents a decision you already made. By then the delivery is signed for, the stock is on the shelf, and the loss has quietly transferred from the distributor to you.
When a lot is withdrawn, most networks cannot say which branches received it or which patients it reached. What follows is a spreadsheet reconstruction — delivery notes, WhatsApp messages, a phone call to every branch manager.
Inspectors increasingly want the same three things: the storage history of a specific lot, the chain of custody that moved it, and the list of sites it reached. Networks that keep this in delivery-note folders answer slowly, incompletely, or not at all — and a slow answer reads as a control failure whether or not one occurred.
A discarded pallet of insulin is expensive. A pallet that should have been discarded and was not is a patient-safety event, a licensing conversation, and a headline. Both outcomes trace back to the same missing fact: nobody read the logger while there was still a decision to make.
Saydalia binds logger data to the shipment rather than the invoice. Every transfer is scanned, every scan carries a temperature and a handler, and the record follows the lot all the way to the dispensing counter — or stops it at the door.
Scroll the diagram sideways to follow the whole chain.
Lot 4471-B never reached a counter. The receipt scan read the logger while the driver was still at the door, the excursion was flagged, and the transfer to dispensing was blocked — so the chain ends at stage three with the loss still on the distributor's side of the ledger.
Saydalia does not ask branch staff to change how they work. It asks them to scan what they already handle, and it does the record-keeping that used to be a delivery note in a drawer.
The distributor registers the shipment: lot, quantity, expiry, storage window and the logger travelling inside the box. The logger ID is now part of the lot record, not a loose PDF.
bind lot=4471-B logger=TL-8817
window=2–8 °C
Every hand-off is a scan — depot to van, van to branch, branch to branch. Each scan writes a timestamp, a handler and the current reading into the chain.
scan 11:35 rv-07 → branch-12
temp=6.9 °C ok
At the door, the receiving scan pulls the logger's full history and evaluates it against the storage window before the delivery note is signed. In-spec goes to stock; an excursion raises a refusal decision on the spot.
receipt 14:06 branch-12
excursion 3h48m · peak 11.2 °C
Dispensing links units to the lot. So when a lot is questioned — by a recall, an inspector or your own quality team — the answer is a query against records that were written as the goods moved.
trace lot=3902-D
→ 3 branches · 53 records
This is the whole argument. A system that reports an excursion after the fact tells you what you already dispensed. Saydalia reads the logger at the moment of receipt — driver still at the door, delivery note still unsigned — so the decision to accept or refuse is made with the temperature history in hand.
Scroll sideways to compare both timelines.
Seven capabilities, each of which exists because a pharmacy network told us the manual version of it costs them a day.
Every movement of every lot, from the distributor's cold room to the counter, written as a scan event with a handler, a timestamp and a reading. The chain is the record; there is no parallel paper trail to reconcile.
The logger ID is registered against the lot at dispatch, and its readings are attached to the shipment record — not emailed as an attachment, not filed against an invoice number that nobody will search for again.
The receiving scan evaluates the logger against the storage window and raises the flag while the driver is still there. The screen shows the duration out of range, the peak, and an accept-or-refuse decision with both outcomes recorded.
One lot number resolves to the branches that received it, the units still on the shelf, and the dispensing records it reached. What used to be a week of phone calls becomes a query you can run in front of an inspector.
Saydalia knows which branch is holding stock it will not sell before expiry and which branch is running that same line down. It proposes the transfer while the units still have shelf life left to be worth moving.
Register counts, dispensed units and returns reconciled per branch per period, with every discrepancy attached to the shift and the person who scanned. The audit log is append-only and exports as evidence.
The custody chain, the logger history and the dispensing records for any lot, exported as a single signed document set in the structure an inspection actually asks for: what it was, where it went, who held it, what temperature it saw, and who received it.
To be exact about this: the export format is designed against published good-distribution-practice documentation requirements. Saydalia holds no regulatory certification or approval, and we will not claim one. What we can say is that the fields are there and the timestamps were not typed in afterwards.
{
"lot": "4471-B",
"product": "Insulin glargine 100 IU/mL",
"storage_window_c": [2.0, 8.0],
"logger": "TL-8817",
"readings": 21,
"excursion": {
"minutes_out": 228,
"peak_c": 11.2,
"detected_at": "14:06 receipt"
},
"custody_events": 4,
"outcome": "refused_at_receipt",
"dispensed_units": 0
}
A withdrawal notice names a lot. Saydalia resolves that lot to the branches that received it, the units still sitting on shelves, and the dispensing records that put the rest into patients' hands — in one pass, with the evidence attached.
Scroll the diagram sideways to see the dispensing records.
| Branch | Received | Units in | Dispensed | On shelf | Status |
|---|---|---|---|---|---|
| Branch 04 · Nablus | 13 Jul 09:40 | 84 | 84 · 31 records | 0 | Patient contact |
| Branch 12 · Al-Bireh | 13 Jul 14:22 | 60 | 60 · 22 records | 0 | Patient contact |
| Branch 27 · Hebron | 14 Jul 08:05 | 36 | 0 · 0 records | 36 | Quarantined |
Every status carries a word as well as a colour, on screen and in the export, because a recall pack gets read under fluorescent light by someone in a hurry.
Five branches or two hundred, one distributor or nine, a modern POS or a laptop with a spreadsheet open. The constraint we design against is the branch on a bad connection at 8 a.m.
Register a logger ID against a lot and upload or sync its readings. We are not selling you hardware and we are not asking you to standardise on one vendor.
Receipt scans queue locally and reconcile when the connection returns. A branch that cannot reach the internet can still refuse a delivery on the evidence.
Dispatch data arrives by API or scheduled file so the lot exists in Saydalia before the van does. Where a distributor cannot integrate, the depot app covers it.
Saydalia does not replace stock or finance systems. It holds the condition and custody layer they were never designed to carry, and hands back what they need.
No per-scan metering and no per-user seat maths. A branch either has custody tracking or it does not.
For pharmacy chains and hospital pharmacy departments running their own receiving.
A 12-branch chain is $540 a month. Annual billing available.
Dispatch data and logger streams arriving from your distributor's systems, so the lot exists before the van does.
Priced once per distributor, not per branch.
Public dispensing networks and hospital pharmacy departments with procurement, hosting and reporting requirements of their own.
Tell us the number of sites and we will come back with a figure, not a discovery process.
Prices are in US dollars and exclude local taxes. Founding-cohort terms are different from the list above — we say so plainly in the first conversation rather than after it.
Saydalia has not shipped yet. We are building with a founding cohort rather than announcing customers we do not have, so instead of a wall of logos, here are the measurements the product is built to produce — and which we will publish once there is a real denominator behind them.
Not accounts, not licences — branches where a receiving scan actually happens on the goods that arrive. This is the only adoption number that means anything.
Excursions flagged before the delivery note was signed, as a share of all excursions detected. A high share means the alert is arriving in time to be worth something.
Lot number in, complete branch-and-dispense answer out. If this is not measured in seconds, we have not replaced the spreadsheet reconstruction.
We are taking a small number of networks into build alongside us: pharmacy chains, hospital pharmacy departments and one or two distributors willing to send us dispatch data. In return you get founding pricing held for the first term, direct influence on what gets built in what order, and an implementation we run with you rather than hand you.
We will not show you customer logos we have not earned, testimonials nobody gave, or a certification badge for a scheme we have not been audited against. Saydalia is not GDP-certified, not approved by any ministry or regulator, and does not pretend that installing software makes a network compliant.
What the product does is make the evidence exist and make it retrievable. Compliance is still yours; we just stop it depending on someone's memory of a Tuesday in August.
No. Saydalia registers a logger ID against a lot and ingests its readings — by file, by API, or by a reading captured at the receiving scan. We are not a hardware vendor and have no interest in becoming one. If your distributor already puts a logger in the box, that is the logger we use.
The receiving scan works offline. The logger evaluation runs against the storage window on the device, the accept-or-refuse decision is recorded locally with its timestamp, and the record syncs when the connection returns. The point of the product is a decision made at the door, and a dead 4G signal is not a good reason to sign for something.
Yes, with one caveat. Receipt verification, custody from your door onward, recall trace and controlled-substance reconciliation all work without distributor cooperation. What you lose is the upstream half of the chain — the depot-to-van leg — and the shared record that makes a refusal conversation short. Most networks start here and pull the distributor in once refusals start being upheld.
No software makes anyone compliant, and we would be suspicious of one that said otherwise. Saydalia produces the records an inspection asks for and makes them retrievable in seconds instead of days. Whether your storage, transport and procedures meet your regulator's requirements is a question about your operation, not about our database.
For a chain of 5–20 branches without distributor integration, we plan in weeks, not quarters: product and lot catalogue, storage windows, branch and user setup, then a pilot on one receiving line before the rest follow. Distributor integration is scoped separately after a mapping call, because the honest answer depends entirely on what their system will give us.
You do. Custody records, logger histories and dispensing links are exportable in full at any time in open formats, including when you leave. The audit log is append-only by design — neither you nor we can quietly rewrite a receipt event — and deletion requests are handled against retention rules we will put in writing before you sign anything.
Tell us about a shipment you had doubts about and could not prove anything about. We will walk that exact journey through Saydalia with you — the custody chain, the trace, the export — in about thirty minutes.
Pre-launch. Founding cohort forming now.