Solutions / Processors
Packages in. Packages out. Both sides on one record.
A processor receives packages from cultivators and ships finished packages to retailers, and each handoff is where a count goes wrong. Smoke Alarm works at the package level today: the receiving firewall on what comes in, the inventory ledger and reconciliation on what you hold, and vendor protection on both ends. Recording the transformation itself is on the roadmap, and is shown as such.
The operational problems, not the scare stories.
- Inbound packages are accepted on the cultivator's word, and a short delivery becomes your shortage.
- Finished packages in the vault and finished packages in Metrc disagree, and the difference is found at a count.
- A retailer's refusal or return arrives by phone, weeks after the transfer, with nothing to compare it against.
- Input packages, finished packages and returned product are counted in different places on different days.
- The record of what happened to a package is spread across e-mail, a spreadsheet and the state system.
What it does for you today, and what is still ahead.
Each card carries the honest status of the capability it rests on. Nothing on the roadmap is sold as live.
The cultivator's manifest imported from Metrc or a CSV, every package scanned at your dock, and anything short, extra or wrong held for a person to decide.
Inventory ledger
AvailableInput and finished packages carry a state and every movement is attributed and timestamped, so the vault and the record agree.
Audit Shield Reconcile
AvailableMetrc's packages against your own records and your physical count, package by package, on a schedule and on demand. Reads only.
Vendor protection, both directions
AvailableRaise a short delivery with your cultivator with the dock evidence attached, and receive a retailer's refusal or return on a secure link with theirs.
Discrepancy cases
AvailableEach receiving difference is a case with an owner, evidence, a human decision and a final inventory state; AI explanations are advisory and marked as such.
Audit trail and binder
AvailableThe append-only log and the dated, fingerprinted binder for the packages you hold.
Transformations and batches
PlannedRecording the transformation from input packages to finished packages, and the batch that ties them together. Designed, not built.
Outbound manifests and transfers
PlannedCreating and verifying the outbound transfer to the retailer. Smoke Alarm reads incoming transfers today; the outbound side is on the roadmap.
- Available
- Available features still require store setup and authorized data. This is not a connected-account status.
- Planned
- Not available yet.
The platform pages behind this.
- ReceivingEvery manifest verified at the dock before it becomes inventory.
- InventoryOne operational inventory state, every movement attributed.
- Audit Shield ReconcileMetrc, POS, ledger and physical count compared package by package.
- Vendor protectionRefusals, short deliveries, buybacks and returns with evidence.
- Audit trailThe append-only record and the binder an inspector asks for.
- IntegrationsMetrc, incumbent POS connectors, scanners and printers.
Start at your own dock.
Bring one inbound manifest and your finished-package count. Twenty minutes with Ken and Charles, and you will see what the receiving firewall and the reconciliation find.