Most Florida discrepancies fall into four families, and the right correction depends on where the record first went wrong. Figure out which family you are looking at before you touch anything, since the fix for one can make another worse.
The four families
- Physical vs system: the count in the vault disagrees with the system. The break started with a physical control.
- POS vs BioTrack: the two systems disagree. Usually a sync or event-posting problem.
- MMUR / allotment: the patient allotment is wrong while package quantity is right. Usually route, sale-state, or order-type mapping.
- Production / transfer: conversion math or manifest state is off.
Symptoms and first responses
| Symptom | Likely cause | Florida-safe first response |
|---|---|---|
| BioTrack shows more than the physical count | Unposted destruction, shrinkage, theft, or a duplicate receipt | Freeze the package, recount, review package history and pending destruction before adjusting down |
| Product exists but is not active in BioTrack | Initial inventory not uploaded, failed sync, or manifest still pending | Confirm whether it exists only in POS, then push through the approved sync or intake workflow |
| POS quantity differs from BioTrack quantity | Package-level sync failure, duplicate adjustment, unit-vs-weight mismatch | Investigate transaction lineage before syncing levels; do not force-sync without a root cause |
| Sale in POS but not in BioTrack | Receipt failed to post | Re-post only after checking whether the original took effect downstream |
| Refund processed but inventory did not return | That may be correct | Confirm whether the event was a refund or a void; if inventory should return, it likely needed a void |
| Allotment wrong but quantity right | Wrong route, order type, or THC value; reservation not cleared | Correct via void, refund-for-destruction, reroute, or return path depending on event state |
| Store has product but BioTrack shows another location | Transfer received physically but not posted; room ID error | Complete the receive-side posting first; do not sell from a package assigned elsewhere |
| Conversion or manufacturing failed | Wrong inventory type, UOM issue, or conversion math | Correct category or UOM before repeating the conversion |
The decision order
Once you know the family, work through these questions before making the correction.
1. Which record is authoritative for this defect?
For package existence, quantity, room, and manifest state, the authoritative chain is physical count plus state traceability plus package history. For patient allotment, it is the MMUR order, the rolling-window amount available, and route-level dispensation history. For product classification, it is the approved product setup and unique product ID data.
2. Is the sale state still reversible?
A void returns product to inventory and fits when the sale should not have existed in that form. A refund does not return product to inventory and instead requires tracking the disposition of the returned product. When a system creates a new package for a returned item, that package should be quarantined and destroyed, not resold.
3. Has the error already hit the rolling-limit calculation?
If the dispensation has propagated into the patient's rolling window, treat it as both an inventory issue and an allotment issue: check route, THC milligrams, order type, current amount eligible, and any delivery reservation state.
4. Has the package moved, been partially sold, or transferred?
Once a package has downstream events, the safe correction is usually to preserve the traceability history and correct forward rather than erase earlier steps. Florida's API-driven environment makes vendor-side receipt, package, and journal audits the primary tool for that root-cause review.
Two things that trip people up
Do not force a sync without understanding the root cause. A reposted receipt appears in BioTrack under the repost date, which creates an audit-date mismatch. And a return-for-destruction flow creates a non-resellable replacement package by design, so segregate it and schedule it for destruction.
Why the sequence matters
Working the questions in order keeps you from correcting only the symptom. The failure I see repeat in Florida is a quantity variance that was really a route error, or a package mismatch "fixed" in the wrong direction.