Smoke Alarm by Audit Shield AI
One System From Manifest to Front Door.
The sale doesn't end at the register. Neither does compliance.
One transaction · five records
SA-TX-000184 · Blue Ridge 3.5 g · Register R-02
Retail ID
1A4FF03…C2E1 · Blue Ridge 3.5 g
Register
Front counter R-02 · age check by scanned ID
Payment
Cash $87 · Compliance Technology Fee $1.50 disclosed
Metrc
Sales receipt queued · read back before any retry
Reconciled
Ledger, POS and Metrc agree on the package
One identifier follows the order, the sale, the payment, the inventory change, the package, the Metrc submission, the receipt, the employee and the terminal into the audit log.
An illustration of the record Smoke Alarm keeps for every sale.
Eight short scenes follow a single sale through Smoke Alarm: the manifest, the dock, the shelf, the register, the payment and the Metrc queue, delivery as designed, the reconciliation and the evidence it leaves behind.
An animated explainer in eight scenes. One transaction moves through Smoke Alarm: the supplier's Metrc manifest arrives and becomes one record per package; at the dock each package is scanned against its manifest line and a short line becomes a case with an owner; accepted packages carry a state and a Retail ID on one inventory that the register and the storefront share; the register checks age by ID, purchase limits and package state and discloses the Compliance Technology Fee; tender is recorded against the sale and the Metrc sales receipt is queued and read back before any retry; delivery, still on the roadmap, would write a custody event at dispatch, at the driver and at the customer handoff; ledger, POS, Metrc and the shelf are compared package by package; and the audit binder collects findings, decisions, evidence and the fingerprinted append-only ledger.
01 / 08
The supplier's Metrc manifest arrives before the truck: every package gets one record.
One identifier follows the order, the sale, the payment, the inventory change, the package, the Metrc submission, the receipt, the employee and the terminal into the audit log.
Manifest, receiving, inventory, storefront, register, payment, Metrc, dispatch, driver, customer, reconciliation, evidence: one transaction record runs through all of it, and Audit Shield writes a status at every stage. Stages that are not built yet say so.
The supplier's manifest arrives before the truck does.
Audit Shield: Manifest lines are imported and checked for duplicates, missing lab results and mismatched packages.
Every package is scanned at the dock against the manifest.
Audit Shield: Short, extra and wrong packages become discrepancy cases; nothing enters inventory until a person decides.
Accepted packages carry a state and a Retail ID.
Audit Shield: One operational inventory state, reconciled against Metrc; every movement attributed and timestamped.
The customer orders from the same inventory the register sells.
Audit Shield: The order reserves inventory instead of promising stock the shelf does not hold.
The register is the last gate before a sale exists.
Audit Shield: Age verification, package state, quantity and price are checked before the sale can complete.
Tender is recorded against the sale, never beside it.
Audit Shield: Payment amount is matched to the sale; the Compliance Technology Fee is disclosed before completion.
The sale is queued for the state system of record.
Audit Shield: A durable queue with retries and read-back; a receipt is confirmed before it is treated as reported.
A prepaid order is picked, packed and assigned to a run.
Audit Shield: Only products on prepaid orders leave the store; each is manifested before it moves.
The driver takes custody, one scan per package.
Audit Shield: Custody transitions are events; a failed delivery returns to the store and is reconciled, never lost.
The customer receives the order and a verified handoff is recorded.
Audit Shield: Identity verification is an event, not a stored image; the minimum is kept.
Metrc, POS, ledger and shelf are compared package by package.
Audit Shield: Every mismatch is a finding with an owner, an explanation and evidence; the report is reproducible.
The record an inspector asks for already exists.
Audit Shield: An append-only audit log and a dated binder with its SHA-256 fingerprint.
Most operators start beside the system they already run. Nothing on this page asks you to replace everything on day one.
Keep your POS
Metrc, your point of sale, Smoke Alarm’s ledger and the physical count compared package by package, with a reproducible report and a case for every difference. It works beside Dutchie, Flowhub, Treez or any system that can export a CSV; Dutchie also has a read-only connector.
Replace it
The register with the compliance gate at checkout, statutory New York receipts, shifts and cash tender, running on pilot locations today. The branded storefront that shares the register’s inventory is designed and on the roadmap. Smoke Alarm Switch moves you across with shadow mode first and a Green Light cutover.
The Compliance Technology Fee is Smoke Alarm's fee, separate from payment processing and from any cannabis tax. It applies per completed qualifying retail transaction, is disclosed before the transaction completes, and its checkout presentation and tax treatment follow the merchant agreement and the location's configuration. Hardware, payment processing and professional deployment are priced separately. Live sales on Smoke Alarm POS open only after a location’s go-live checklist.
Sell, protect, move, deploy: each product writes to the same inventory state and the same audit log, so nothing has to be reconciled between Smoke Alarm's own modules.
Four sources compared package by package; every difference becomes a case with an owner, an explanation and evidence.
Explore ReconcileThe register with the compliance gate at checkout, and a branded storefront on the same inventory when it ships.
Explore POS + StorefrontImport, aliases for every legacy identifier, shadow mode beside the old system and a Green Light cutover.
Explore SwitchPrepaid orders from the shelf to the front door, every custody change an event. Designed and priced; not built.
Explore DeliveryRegister, receiving and kiosk kits from certified third-party hardware, configured and installed on site.
Explore Integrated StoreReconcile earns the right to the next step. Each stage stands on its own, and the record it builds carries into the one after it.
Audit Shield Reconcile beside the point of sale you already run. Metrc, POS, ledger and physical count compared, with a report you can reproduce.
Findings with owners and evidence. Shadow mode measures Smoke Alarm's own precision against the incumbent before anything is trusted.
Import and normalise with every legacy identifier kept as an alias; a fourteen-item go-live checklist that only an owner with an authenticator can clear.
Smoke Alarm POS takes the register with the compliance gate at checkout; the storefront follows on the same inventory.
Delivery, hardware kits and professional deployment, added as modules on the same transaction record.
Audit Shield sits across every stage of the lifecycle and runs one loop on every difference it finds.
A rule fires on recorded facts: a count, a manifest line, a Metrc read, a sale.
The finding carries the records behind it and, when a model is configured, a plainly labelled advisory explanation.
A case with an owner and a due decision. Nothing waits in a dashboard nobody owns.
A person decides, or approves the correction Autopilot prepared; the decision, its reason and its evidence are written down.
The result is checked against what was expected: read back where the record can be read, confirmed by a person where it cannot.
The append-only audit log and the fingerprinted binder hold the record an inspection asks for.
| Exception | What Audit Shield does | Status it records |
|---|---|---|
| Metrc mismatch | Metrc's package quantity and the ledger disagree; the finding names both figures and the last movement. | Exception |
| Manifest mismatch | Fewer, extra or wrong packages at the dock become a discrepancy case before anything enters inventory. | Review |
| Physical-count variance | The shelf count differs from expected; a blind recount is ordered and the variance is explained or adjusted. | Review |
| Retail ID mismatch | A scanned Retail ID does not match the package it should belong to; the sale stops until it does. | Blocked |
| Stale synchronisation | A source has not been read within its expected window; the comparison says so instead of trusting old data. | Pending |
| Duplicate record | The same manifest line or receipt appears twice; the second is held rather than counted. | Blocked |
| Missing transaction | A sale exists in one system and not another; the gap is a finding with an owner, not a rounding error. | Review |
Smoke Alarm doesn't just find discrepancies. It investigates them, determines the safest correction, prepares the fix, explains exactly what it intends to change, and executes only after authorized human approval.
AI case AS-00219 · rule SA-001
Blue Ridge 3.5 g · package 1A4FF03…C2E1
Exception Metrc and the point of sale disagree by one unit on one package.
Transaction SA-82941 sold one unit at register R-02 at 14:32; the point of sale and the shelf both moved to 11. The Metrc sales receipt for SA-82941 timed out before Metrc acknowledged it, so Metrc still reports 12. No other movement has touched this package.
Authorization · Manager approval required: an authoritative inventory quantity or a regulatory record would change.
| System | Before | After |
|---|---|---|
| POS | 11 | 11 |
| Metrc | 12 | 11 |
| Physical count | 11 | 11 |
| Audit Shield | Exception | Reconciled |
Static illustration of the decision row. In the product, the person who presses a button is recorded with their role, device and time; nothing runs before that.
IllustrationAn illustration on made-up figures. No store, product or transaction shown here is real; the statuses, button states and records are the engine's own.
The button on a case says what the engine is sure of. It never asks a person to trust a colour alone: each state has one meaning.
Smoke Alarm has one high-confidence correction ready.
More than one reasonable correction exists, or confidence is moderate; a person chooses.
A physical count, a scan or an employee's confirmation is needed before a correction can be prepared.
Automatic correction is inappropriate or prohibited; the evidence goes to the responsible person.
What was wrong, what was concluded, what was proposed, who authorized it, what actually happened and why the case closed: written on the case and in the audit log, never rewritten.
The exact discrepancy and the records affected.
The root-cause analysis and the evidence considered, with confidence.
The exact actions, systems, fields and expected effects.
Employee identity, role, terminal or device, timestamp.
API calls, mutations, responses, retries, failures.
Confirmation that the expected state now matches the resulting state.
AI may investigate, reason, recommend, simulate and prepare. Humans authorize consequential changes. Smoke Alarm records both.
Fix Me and Fix Inventory are built and tested and run on test and pilot locations; no customer’s records have been changed by the engine yet. Prepared Metrc actions are carried out only through the Metrc reporting queue and its own approvals; the engine never manufactures an API call.
Audit Shield AI builds transaction and compliance infrastructure for licensed cannabis operators, starting in New York. Smoke Alarm is that infrastructure: one transaction architecture for the register, the inventory, the state system of record and the evidence, with Audit Shield as the control layer across all of it.
Founded by Charles Underwood, Co-Founder & CEO, and Ken Clark, Co-Founder | Technology & Operations. Built on the Metrc third-party API; nothing is written to the state system without a named person’s approval.
Built on the Metrc third-party API · New YorkTwenty minutes with Ken and Charles. Bring one manifest and one register close; we will follow them from the dock to the audit log and show you what Audit Shield finds.