Audit Shield · Land, then prove
Audit Shield Reconcile compares Metrc, your point of sale, Smoke Alarm’s own ledger and your physical counts, package by package, and turns every difference into a finding a person owns. Works beside the point of sale you already run.
Audit Shield Reconcile only reads Metrc and your point of sale. It never writes to Metrc, and it never writes to your POS.
Reconcile finds it. Autopilot fixes it. How Fix Me works
| Package | Metrc | POS | Ledger | Count | Status |
|---|---|---|---|---|---|
Hudson Valley Kush 3.5 g …00004183 | 48 | 48 | 48 | 48 | Match |
Catskill Cart 1 g …00004190 | 60 | 57 | 60 | 57 | Review SA-001 |
Finger Lakes Gummies 10 pk …00004202 | 24 | 24 | 24 | not read | Pending |
Adirondack Pre-roll 1 g …00004215 | 0 | 12 | 12 | 12 | Blocked SA-009 |
Illustrative reconciliationA fictional run on a fictional dispensary. The tags, products and quantities are made up; the statuses and rule ids are the ones the engine uses.
Each source is read as it reports itself. Nothing is converted, guessed or edited to make two sources agree, and a source that could not be read is shown as not read, never as zero.
Active packages and quantities, read from the state system.
On-hand quantities, read from your point of sale or its export.
Expected on hand from receipts, sales and recorded movements.
Optional: the latest count, blind or full.
Deterministic comparison. Package by package, the same arithmetic every run. No model does the maths. Every run is stored with the SHA-256 of its inputs, so the same facts give the same report on any later day.
Audit Shield is a control and exception layer, not another dashboard. One case architecture serves both automation levels: on Reconcile your team makes the consequential change; with Autopilot, Smoke Alarm may prepare or make it after the approval its risk requires. Each step has a screen in the application and leaves a record.
Metrc, the point of sale, Smoke Alarm's ledger and the latest physical count, on one screen. Every difference becomes a finding with the records behind it; a source that could not be read is shown as not read, never as zero.
In the app: /app/reconcile · Reconcile screen
An AI explanation lists the likely causes and next steps for a finding or a case. It is advisory and never authoritative: it changes no record, the arithmetic is never done by a model, and it is marked as advisory wherever it appears.
In the app: /app/findings · Findings
The finding is assigned, recounted and documented. Evidence files carry their SHA-256, and every step is attributed and timestamped.
In the app: /app/investigations · Investigations
Accept as counted, accept as manifested, return, reject, quarantine, hold for a state correction or clear on recount. The decision records what the licensee still owes Metrc; Reconcile itself writes nothing there.
In the app: /app/cases · Discrepancy cases
The final inventory state is recorded with the decision, and a Metrc step the licensee owed is confirmed by the person who did it. With Autopilot, Smoke Alarm reads each corrected record back and compares it with what was expected; where an outside record cannot be read, the case says it closed on the licensee's confirmation.
In the app: /app/remediation · Remediation cases
The reproducible reconciliation report with its inputs fingerprint, the append-only audit log and the dated audit binder with its SHA-256 manifest.
In the app: /app/binder · Audit binder
AI explanations are advisory. A model suggests likely causes and next steps beside the records; it never changes a record, and the reconciliation arithmetic is never done by a model. A person decides.
On Reconcile Pro with Autopilot the same explanation becomes a prepared correction, checked by a second model and approved by a person before it runs: Fix Me.
Audit Shield Reconcile only reads Metrc and your point of sale. It never writes to Metrc, and it never writes to your POS. When a case is resolved, the Metrc step the licensee still owes is written on the case for a person to do in Metrc; Reconcile records what was found, what was decided and the evidence behind it.
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.
Reconcile: Audit Shield Reconcile only reads Metrc and your point of sale. It never writes to Metrc, and it never writes to your POS.
Autopilot: Autopilot changes a record only after a named person approves the prepared correction (a safe barcode mapping may apply on its own where an owner or compliance manager has switched that on for the location), and every change is recorded with who authorized it, on which device, and what actually happened.
No registered tool writes to Metrc directly: the tools change Smoke Alarm’s own records, and a prepared Metrc action is carried out through the Metrc reporting queue and its own approvals; the engine never manufactures an API call.
The class of a proposal is the highest class of any action in it, and it comes from the registered tool and the location’s policy, never from the plan a model wrote. The sentence in the last column is the one the product shows under “Authorization”.
| Class | What it covers | Example | Authorization |
|---|---|---|---|
| L0 | Read, search, analyse | Looking a package up in the ledger or in Metrc. | No approval needed: nothing changes. |
| L1 | Safe local mapping | Connecting a scanned barcode to the confirmed catalog record it belongs to. | One tap by the employee: a safe local mapping; no inventory quantity or external record changes. |
| L2 | Local operational change | Reactivating a product that exists, or putting a repaired item back into the open sale. | One tap by the employee: a local operational change; no inventory quantity or external record changes. |
| L3 | Inventory or regulatory change | An adjustment to an authoritative quantity, or a Metrc submission. | Manager approval required: an authoritative inventory quantity or a regulatory record would change. |
| L4 | Financial, destructive or high impact | A refund, a reversal, a destruction or a void. | Elevated approval required (owner, compliance manager or store manager): a financial, destructive or high-impact change. |
| L5 | Unsupported or ambiguous | The evidence supports two causes, or the action is prohibited by policy. | Escalated: Smoke Alarm will not prepare an automatic correction for this. The evidence package goes to the person responsible. |
Each state has one meaning; the colour is never the only signal.
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.
On the case, in its timeline and in the audit log, before anyone asks.
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.
On a discrepancy case: a planner model proposes the correction, a second model verifies it, a person approves it, and the approved actions run through the write ledger and are read back.
Waiting on: Running on test and pilot locations; no customer location has used it yet.
Smoke Alarm investigates a discrepancy, determines the safest correction, prepares it, explains exactly what it intends to change, and executes only after a named person's approval, with six records kept for every fix.
Waiting on: Running on test and pilot locations; no customer location has used it yet.
Preview Fix Me is part of Reconcile Pro with Autopilot (Reconcile Pro and Enterprise plans). On Reconcile Micro, Reconcile finds and explains the same discrepancy and keeps the manual path; nothing on a Micro plan is a wall.
A barcode that was never connected, a product marked inactive, a package never linked to a sellable product: the cashier taps once, the engine investigates, and the one safe action is prepared with a plain sentence about what changes. A change above the cashier's authority waits for a manager.
The scan does not resolve. The cashier taps Fix Inventory instead of typing a SKU or calling a manager.
The engine reads everything the store knows about the code: remembered identifiers, packages, products active or not, receiving's mappings, the manifest, Metrc's Retail ID lookup.
One cause, one prepared action, one plain sentence about what changes and what does not. The cashier confirms; a change above their authority goes to a manager.
Register R-02 · scan did not resolve
Blue Ridge 3.5 g
Barcode not connected. This product exists, but the barcode on the label was never connected to its inventory record. Connect the barcode to the existing product and package.
IllustrationA made-up scan on a made-up register. The cause, its risk class and the sentence beside the button are the engine’s own.
Exact identifiers first; a fuzzy match on the product name is the last resort, never the first guess.
Each with its risk class and whether an outside record would change. When none fits, the case reads “Cause not established” and escalates.
Below 80% the cause is not treated as established. Two reasonable corrections, or one the engine is unsure of, turn FIX ME into REVIEW FIX and hand the choice to a person.
Connect the barcode to the existing product and package. No quantity and no external record changes.
Two potential causes; the engine will not choose between them. Manager review, with both candidates and the evidence for each.
After a reconciliation run
IllustrationBatch fix review is designed for Reconcile Enterprise with Autopilot and is not yet built; the counts are made up.
A scan the register cannot resolve is investigated, the cause classified, the local correction prepared and applied after the tap the policy requires, then verified and recorded on an AI case.
Waiting on: Running on test and pilot locations; no customer location has used it yet.
Fix Inventory is part of Reconcile Pro with Autopilot (Reconcile Pro and Enterprise plans). On Reconcile Micro the register still says why a scan failed and keeps the manual path; a safe local mapping applies itself only where the location’s policy allows it, and is recorded either way.
SA-001 to SA-027, grouped by what they compare. Every rule says which sources it compared, what it expected, what it saw and what a person should do next. A rule whose source did not answer is skipped with the reason, never fired and never silently passed.
The same package, counted by different systems, must agree.
For every package the state system lists as active, the quantity the state system holds is compared with the quantity the point of sale holds under the same tag.
MetrcPOS
For every package the latest count covered, the counted quantity is compared with what the point of sale reported at count time (or now, for a count that did not record it).
POSPhysical count
For every package the latest count covered, the counted quantity is compared with what the state system reported at count time (or now, for a count that did not record it).
MetrcPhysical count
For every package both the state system and Smoke Alarm's ledger hold, the quantity the state system shows is compared with the units on hand in the ledger. A package the state system shows as finished counts as nothing left. Quantities stated in different units are not compared.
MetrcSmoke Alarm ledger
A tag means one package, filed under one product, in one place.
A tag that the point of sale holds stock under, or that a count found on the shelf, does not appear in the state system's active packages for this facility.
POSPhysical countMetrc
The same package tag appears more than once where it must be unique: under two products in the point of sale, or twice on one manifest.
POSManifest
A manifest line carries a tag that is already in inventory at this location; receiving it again would duplicate stock.
ManifestSmoke Alarm ledger
The point of sale files a tag under a product that is not the product Smoke Alarm's ledger holds for that tag, or under more than one product.
POSSmoke Alarm ledger
The state system lists an active package with quantity under a tag that Smoke Alarm's ledger does not hold at this location. The state knows about stock the books do not.
MetrcSmoke Alarm ledger
What the transfer says shipped against what the dock received.
A manifest line says one quantity shipped and the dock count recorded another.
ManifestSmoke Alarm ledger
A package on the vendor's packing list is not on the state system's transfer, or its status on the transfer could not be read.
ManifestMetrc
A package on a manifest that has been received, in whole or in part, was not received: missing at the dock, held, or blocked.
ManifestSmoke Alarm ledger
Stock in hand needs a passed test and a certificate that agrees with it.
The state system reports a failed lab test for a package that is still in stock in the state system, the point of sale or the ledger.
Lab resultMetrcPOS
A package in stock has no passed lab result in the state system and no test row at all.
Lab resultMetrc
A package in stock has no vendor certificate of analysis on file at this location.
Certificate of analysisSmoke Alarm ledger
The total THC on the certificate of analysis differs from the state system's lab result by more than 2 percentage points, with both stated in the same unit. Figures in different units are not compared.
Certificate of analysisLab result
Nothing expired on the shelf, nothing sold that the ledger did not have.
A package still in stock has passed the expiration date the state system or the point of sale carries for it.
MetrcPOSSmoke Alarm ledger
The point of sale sold from a package that Smoke Alarm's ledger did not hold, or sold more than the ledger had on hand.
POSSmoke Alarm ledger
The point of sale shows less than zero on hand under a tag.
POS
Every sale completed at the Smoke Alarm register is reported to the state system through the Metrc sync queue. This rule lists the sales Metrc refused, the ones whose outcome is uncertain, and the ones still waiting after the grace period. New York expects each sale to reach the state's tracking system in real time (9 NYCRR § 123.10(f)(1)).
POSMetrcConnection health
A source that was not read is never treated as agreeing.
Smoke Alarm has not read the state system successfully within the staleness window, or the connection is failing now.
Connection health
Smoke Alarm has not read the point of sale successfully within the staleness window, or the connection is failing now.
Connection health
A quantity adjustment was made in the state system or the point of sale that no approved Smoke Alarm correction explains.
MetrcPOSSmoke Alarm ledger
What the state system holds must make sense on its own, before it is compared with anything.
The state system lists an active package whose quantity is below zero. Metrc should never hold less than nothing; the figure is wrong whatever unit it is stated in.
Metrc
The state system lists an active package whose quantity is exactly zero. A package with nothing left is finished in Metrc; one left open still shows as active inventory.
Metrc
A sales receipt recorded in the state system in the last 24 hours sold from a package that the facility's active packages in Metrc no longer list: finished, on hold or otherwise not active. Informational: a sale that emptied a package which was then finished is normal; one on a package that was already closed is not.
Metrc
The state system lists an active package whose item is not among the facility's active items in Metrc (matched by item id when the package names one, otherwise by exact item name). The item has been archived or otherwise retired while stock is still filed under it.
Metrc
Rule engine version 2026.10.08. Severities shown are the defaults; an organisation can adjust thresholds such as the staleness window and the certificate tolerance, and every override is recorded. The rules decide nothing legal: a mismatch is a fact for a person to investigate.
The Reconcile screen: quantities per source, the variance against the shelf, the rule that fired and the status the package carries until a person closes it.
| Package | Metrc | POS | Ledger | Count | Δ shelf | Status |
|---|---|---|---|---|---|---|
Hudson Valley Kush 3.5 g …00004183 | 48 | 48 | 48 | 48 | 0 | Match All four sources agree. |
Catskill Cart 1 g …00004190 | 60 | 57 | 60 | 57 | -3 | Review SA-001 POS and shelf say 57; Metrc and the ledger say 60. Three units unaccounted for. |
Finger Lakes Gummies 10 pk …00004202 | 24 | 24 | 24 | not read | — | Pending Not covered by the latest count; no physical figure yet. |
Adirondack Pre-roll 1 g …00004215 | 0 | 12 | 12 | 12 | 0 | Blocked SA-009 Metrc reports a failed lab test on stock still in hand. Held from sale until resolved. |
Buffalo Balm 50 ml …00004227 | 30 | 30 | 30 | 29 | -1 | Reconciled SA-002 Recount matched 29; a damaged unit was written off with a reason. |
Niagara Tincture 30 ml …00004236 | not read | 15 | 15 | 15 | 0 | Review SA-016 Metrc not read within the staleness window; nothing assumed. |
Illustrative reconciliationA fictional run on a fictional dispensary. The tags, products and quantities are made up; the statuses and rule ids are the ones the engine uses.
Land with Reconcile and prove the discrepancies exist. Nothing about your register changes. The same control layer runs inside Smoke Alarm POS, where the sale itself is the ledger entry.
| Control | Audit Shield Reconcile beside your POSAvailable Metrc, the point of sale, Smoke Alarm's ledger and the physical count compared package by package, with reproducible reports and discrepancy cases. | Audit Shield inside Smoke Alarm POSPreview Register, cart, compliance rules at the sale, statutory New York receipts, shifts with blind close, voids and returns; live sales open only after the go-live checklist. |
|---|---|---|
| Metrc read and compared | Yes: Read only, with your licensee key. | Yes: Same reads; approved corrections go through the write ledger. |
| Your current POS | Yes: Read through a connector (Dutchie) or its CSV export; never written to. | No: The Smoke Alarm register is the POS; the sale is the ledger entry. |
| Receiving firewall at the dock | Yes: Manifests, scans, New York variance rules, holds. | Yes: Identical: one receiving workflow for both. |
| 27 reconciliation rules | Yes: SA-001 … SA-027 on every run. | Yes: Plus SA-021, register sales confirmed in Metrc. |
| Discrepancy cases, human resolution | Yes: The Metrc step owed is recorded for you to do. | Yes: The same case, with the sale's own transaction id attached. |
| Compliance gate at checkout | No: Your POS decides what sells. | Yes: Package state, age check, limits and price checked before the sale exists. |
| Sales reported to Metrc | No: Your POS keeps reporting, as today. | Yes: Durable queue, verify before retry; production waits on Metrc integrator status. |
| Audit trail and binder | Yes: Append-only, SHA-256 fingerprints. | Yes: Identical. |
| Change needed on day one | No: None. Keep your POS and your Metrc account. | Yes: A migration through Smoke Alarm Switch, with shadow mode first. |
Start beside your POS; the same findings, cases and binder carry over if you later move the register to Smoke Alarm POS through Smoke Alarm Switch.
One audit, then software that grows with the store. Each step builds on the record the one before it created; nothing on the path has to be bought at once.
The NYS Systems & Compliance Audit: a person-led review of one location across 15 categories, delivered as a graded report. One-time, and separate from the monthly Audit Shield Reconcile software.
from $1,000, one-time
Smoke Alarm detects the problem, explains the evidence and the correction, tracks the case and verifies the result; your team makes the consequential changes. It runs beside the point of sale you already have.
Reconcile Micro $99 per location a month
Smoke Alarm prepares or carries out as much of the repetitive work as is safe; consequential actions wait behind capability checks, validation, permissions, approval, read-back and audit evidence.
Reconcile Pro $399 per location a month; Reconcile Enterprise from $799
The move from your current POS: inventory imported with its old identifiers kept, shadow mode beside the incumbent, then a Green Light cutover.
Professional Deployment from $1,500, one-time
The register on the same inventory and transaction record: compliance rules at the sale, statutory New York receipts and Metrc sales reporting.
$0 base subscription; $1.50 Compliance Technology Fee per completed qualifying retail transaction
Delivery, a branded storefront and electronic payments on the same inventory and transaction record.
Delivery Service $3 per completed delivery; no storefront or payments price is published
Reconcile finds it. Autopilot fixes it. Priced so a single microbusiness store can start on its own and a multi-location operator can bring every licence into one view. Implementation is a one-time fee that connects Metrc, maps your POS and runs the first reconciliation with you.
Audit Shield Reconcile has two functional automation levels, controlled through the existing plan and entitlement architecture.
Smoke Alarm detects the problem, explains the evidence and the correction, tracks the case and verifies the result; your team makes the consequential changes.
Smoke Alarm prepares or carries out as much of the repetitive work as is safe; consequential actions wait behind capability checks, validation, permissions, approval, read-back and audit evidence.
Know what's wrong
Daily reconciliation for a very low-volume or microbusiness store.
$99
per location a month
One-time implementation $250–$500: Metrc connection, POS and facility mapping, inventory baseline, barcodes, first reconciliation, users and training.
Start with MicroLet Smoke Alarm fix it
Continuous manifest and inventory reconciliation beside your POS.
$399
per location a month
One-time implementation $750–$1,500: Metrc connection, POS and facility mapping, inventory baseline, barcodes, first reconciliation, users and training.
Start with ProFix it across every location
Every location reconciled and resolved from one place.
From $799
per location a month
One-time implementation from $2,500: Metrc connection, POS and facility mapping, inventory baseline, barcodes, first reconciliation, users and training.
Talk to us about EnterpriseLimits are the ones the product enforces, from the plan catalogue; an import that would pass a Micro limit is refused with the numbers behind it. Prices are the catalogue’s starting prices; the Reconcile pricing page quotes the price list in force, and /pricing shows how Reconcile sits beside the rest of the platform.
| What each tier does with a discrepancy | Know what's wrong Reconcile Reconcile Micro · $99 per location a month | Let Smoke Alarm fix it Reconcile Pro with Autopilot Reconcile Pro · $399 per location a month | Fix it across every location Reconcile Enterprise with Autopilot Reconcile Enterprise · From $799 per location a month |
|---|---|---|---|
| Discrepancy detectionAvailable | Included in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Reconciliation dashboardAvailable | Included in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Recommended resolutionAvailable | Basic | Prepared by Fix Me | Prepared by Fix Me |
| AI root-cause analysisPreview | Basic | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| AI remediation (the Remediation Engine)Preview | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Fix MePreview | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Fix InventoryPreview | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Scan to repairPreview | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| AI-guided returnsPlanned | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| AI-guided receivingPlanned | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Prepared Metrc actionsPreview | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Automatic low-risk repairsPreview | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Proactive problem detectionPlanned | Not in Reconcile | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| AI case historyPreview | Limited | Included in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Batch fix reviewPlanned | Not in Reconcile | Not in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Multi-location remediationPlanned | Not in Reconcile | Not in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Custom approval rulesPlanned | Not in Reconcile | Not in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
| Dual approvalPlanned | Not in Reconcile | Not in Reconcile Pro with Autopilot | Included in Reconcile Enterprise with Autopilot |
AI-guided returns, AI-guided receiving, Proactive problem detection, Batch fix review, Multi-location remediation, Custom approval rules and Dual approval are designed and not yet built; they are shown so you can plan, never sold as live. Everything marked Pilot is built and tested and runs on test and pilot locations before general release.
Every reconciliation run is stored with the SHA-256 of the facts it read. The printable report and the CSV carry that fingerprint in an X-Inputs-SHA256 header and on the page, so a copy handed over later can be checked against the run that produced it.
Each difference is a finding with the records behind it; each finding can become an investigation or a discrepancy case with an owner, evidence and a decision.
Every decision is an append-only entry with the actor, the reason and the record before and after. Nothing is deleted; things are resolved and closed.
A dated, page-numbered document for one licence over one period, with a manifest of record fingerprints and SIMULATED stamped on any practice record.
More on the record itself on Audit trail; the standalone product has its own site at the Reconcile site.
Illustrative examplesEvery table on this page runs on a fictional dispensary. No customer, product or transaction shown is real.
Twenty minutes with Ken and Charles: we run the four-source comparison on your export and show you what Audit Shield finds, beside the POS you already run.