Intelligence · Integrations
Metrc, the POS you run, and the hardware you own.
Smoke Alarm reads from the systems you already run through authorised connections and never writes without a named person's approval. This page says what is connected today, what waits on an outside party, and what is not built, in those words.
- Available
- Available features still require store setup and authorized data. This is not a connected-account status.
- Preview
- Explore with illustrative data. Not generally released for customer use.
- Requires setup
- Provider credentials, a partner agreement or approval may be needed before use.
- Planned
- Not available yet.
Built on the Metrc third-party API. Reads first; one write, approved.
Metrc is architected as its own service: application → event engine → durable queue → connector → Metrc → confirmation, retry or exception. No screen calls Metrc directly, and every external write is traceable and read back.
Reads
Requires setup- Facilities
- Active packages and quantities
- Incoming transfers (manifests)
- Lab test results
- Sales receipts (read-back for verification)
Built on the Metrc third-party API (v2), with each licensee’s own user API key stored encrypted. Reconcile organisations get a read-only adapter and can never write.
One write
Requires setupA package quantity adjustment, and only that. It goes through the write-operation ledger: proposed from an investigation, approved by a named person, preflighted (product allowed to write, live connections on, credential present), sent once, and read back before it is treated as done. Every attempt and the provider’s answer stay on the ledger.
Sales reporting queue
PreviewEvery sale at the Smoke Alarm register is queued to Metrc with verify-before-retry, so nothing is sent twice and a receipt is confirmed before it counts as reported.
Packages, incoming transfers and lab results read through Metrc's third-party API with the licensee's own key; nothing is written without a named person's approval.
Waiting on: Metrc integrator access for New York (Metrc case 02448265) and each licensee's user API key.
Production gating, plainly: the platform’s live-connections switch is off until Metrc grants New York integrator access, so every Metrc read and write today runs against the simulated adapter or a sandbox. Sales reporting to production also waits on Metrc’s written confirmation of five New York payload fields. Neither status is something Smoke Alarm can grant itself; both are shown here as they stand.
Your current POS, read and never written to.
Audit Shield Reconcile works beside the point of sale you already run. Inventory reaches Smoke Alarm through the vendor's export or, where a connector exists, a read-only connection with a store-scoped key.
CSV import, any POS
AvailableInventory and catalogue from your point of sale’s own export, with package tags and SKUs preserved and every legacy identifier kept as an alias. This is how most stores start; it needs no vendor credential.
Read-only connector built
Requires setup- Dutchie: catalogue and inventory read with a store-scoped key the vendor issues. Nothing is written to it.
Switched on per store when the vendor issues the credential; until then the store runs on CSV import.
Listed; connector not yet built
Recorded so a store can say which POS it runs; each reads through CSV import until a connector exists. Audit Shield AI does not guess at an API it has not read.
- Flowhub
- Treez
- Cova
- BLAZE
- BioTrack
- Jane (iHeartJane)
- Meadow
- Alleaves
- POSaBIT
- IndicaOnline
- Sweed
- Greenbits (now Dutchie)
- Leaf Logix (now Dutchie)
- Another point of sale
Only connectors that exist are described as connectors. A POS not shown here is imported through CSV like any other; a connector for it is scoped under an Enterprise implementation agreement.
Scanners, cameras and printers you already have.
The components stay replaceable: commercial off-the-shelf devices, no proprietary hardware. Everything here runs in the browser on Chromium over HTTPS.
USB or Bluetooth scanner
Any keyboard-wedge 2D scanner: package tags, Metrc Retail ID QR codes and retail barcodes at the dock, the count and the register.
Phone or tablet camera
The same scans from the device’s camera, in the browser, when there is no scanner to hand.
ESC/POS receipt printers and drawers
Receipts with New York’s required fields, and the drawer kick, over Web Serial or WebUSB in Chromium.
Label printers
ZPL labels for repacks and shelf edges; Code 128 barcodes generated in the app.
Where findings go, and what is not built yet.
Findings reach the people who act on them where they already work. A public API for your own systems is on the roadmap and is described as such.
Alert channels
High-severity findings can be posted to a Slack or Microsoft Teams incoming webhook you create in your own workspace, or sent by text message, beside the e-mail alert and under the same shadow-mode hold. Your webhook URL is the whole credential; it is stored encrypted and decrypted only in the moment of sending.
Text messages need the deployment’s own SMS account to be configured; until it is, the channel is off rather than half-working.
Customer API
PlannedA public API for your own systems is designed and not built. Until it exists, the reproducible reconciliation report (HTML and CSV, each with its inputs fingerprint) and the audit binder are the exports; a system not listed here is scoped through custom solutions.
We will say so here until it ships.
Tell us what you run.
Bring your POS export and your Metrc facility list. We show you what connects today, what waits on a credential, and what the CSV path covers in the meantime.