Platform / Move
Switch systems without a blackout day.
Smoke Alarm Switch is the migration path from the point of sale you run now. Your data comes across with every legacy identifier preserved, the two systems are reconciled, Smoke Alarm runs beside the incumbent in shadow mode until it has proven itself, and the cutover happens only on a Green Light.
The first step is not a migration at all. It is Audit Shield Reconcile, working beside your current POS and reading it, never writing to it.
Shadow mode
Available- Your current POSProduction writer
Keeps selling and keeps writing. Nothing about its day changes.
- MetrcRegulatory system of record
The state's record. Smoke Alarm reads it; in shadow mode it writes nothing to it.
- Smoke AlarmReads, reconciles, compares
Runs every rule, holds every outward action, and records where it would have decided differently.
Never require immediate replacement to prove the system works.
The same lifecycle, a different register at the end.
Switch changes who writes the POS and payment stages. Receiving, inventory, reconciliation and evidence are already Smoke Alarm's during the Reconcile stage, which is why the switch is smaller than it looks.
- Verified
- Checked and agreed at this stage.
- Review
- A person needs to decide.
- Blocked
- The workflow stops here until it is resolved.
- Pending
- Waiting on a step that has not happened yet.
Nine steps, each with its honest status.
Every step carries the status of the software behind it. Where Smoke Alarm's people do the work today, the step says so.
Step 1: Identify
Which POS you run, which exports it produces, which Metrc facility licences you hold, what the contract says about notice and equipment. A conversation and a checklist, not software.
ServiceStep 2: Connect
Smoke Alarm reads the incumbent POS through a read-only connector where one exists, or from its CSV exports where one does not. It never writes to the system you are leaving.
IntegrationsRequires setupStep 3: Import
Inventory arrives from the export with package tags and SKUs preserved exactly as the old system wrote them.
AvailableStep 4: Normalize
Each legacy product is mapped to one Smoke Alarm product. Every legacy identifier is kept as an alias, marked exact, confirmed or proposed, so old receipts, labels and reports still resolve.
AvailableStep 5: Reconcile
Metrc, the incumbent POS, Smoke Alarm's ledger and a physical count compared package by package. This is Audit Shield Reconcile, and it is where most engagements start.
Audit Shield ReconcileAvailableStep 6: Shadow
The old POS stays the production writer and Metrc the system of record. Smoke Alarm runs every rule beside them, holds every outward action, and measures where it would have decided differently.
AvailableStep 7: Green Light
The go-live checklist is computed from the records: licence, Metrc facility, taxes confirmed, receipts, rules reviewed, a register, staff, a practice sale and more. Nothing is ticked by hand.
AvailableStep 8: Cut over
The incumbent's final export is imported after its last sale. An owner with an authenticator types the confirmation and Smoke Alarm becomes the register. Two systems never write the same regulatory transaction.
AvailableStep 9: Exit
Notice, cancellation, RMA and equipment return with the incumbent vendor. Today Smoke Alarm's people manage this with you; tracking it inside the product is on the roadmap.
PlannedService today
- 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.
Your legacy IDs survive the move.
A migration that renames everything breaks every old receipt, label and report. Smoke Alarm keeps the incumbent's identifiers as aliases and adds its own, so both resolve.
- Available
CSV import
Inventory imported from the incumbent's export with package tags and SKUs preserved exactly as written. Nothing is received into inventory until a person approves the batch.
- Available
Product identity aliases
Each legacy name, SKU or item ID is stored as an alias pointing at one Smoke Alarm product, marked exact, confirmed or proposed. An alias is never a correction: the old wording is kept as it arrived.
- Available
Matching proposes, a person confirms
Deterministic matching runs over every line and proposes the mapping. A person confirms the lines the rules could not settle, and the second import resolves without them.
Read from the POS you have. Never write to it.
A read-only connector contract, one vendor built against it, and a CSV path for every other system. Smoke Alarm will not guess at an API it has not read.
Connectors built
Requires setup- DutchieRead-only
Waiting on: The POS vendor's partner credentials.
Recorded, not yet readable
A store can record that it runs one of these so the migration plan knows what it is leaving. No connector exists for them yet; their data arrives through the CSV import above.
- Flowhub
- Treez
- Cova
- BLAZE
- BioTrack
- Jane (iHeartJane)
- Meadow
- Alleaves
- POSaBIT
- IndicaOnline
- Sweed
- Greenbits (now Dutchie)
- Leaf Logix (now Dutchie)
- Another point of sale
Vendor names identify the systems operators run today. No partnership, endorsement or certification by any of them is implied.
Prove it before you trust it.
Before cutover the old POS is the production writer, Metrc is the regulatory system of record and Smoke Alarm reads, reconciles and compares. It observes discrepancies before it becomes authoritative.
One gate
A single function answers “may this leave the building?” for every outward action. While shadow mode is on, no write operation leaves its proposed state and no e-mail is handed to a provider. A caller added later cannot get past it by accident.
One ledger
Every rule still runs. Each outcome is written to a shadow-decision ledger with the rule and version that produced it. When the staff action lands, the observed outcome is attached and compared. Nothing is overwritten to make them agree.
Honest measurement
Precision and agreement are reported with their denominator and window, and the product refuses to print a number until there are enough events for it to mean something.
Smoke Alarm does not become the register until every prerequisite is satisfied.
Use the checklist to plan your own cutover. Underneath it are the gates the product actually computes today, none of which a person can tick by hand.
Green Light readiness
A planning aid for your own cutover. It saves nothing and is not the in-app gate: that one reads each item from your records.
Smoke Alarm does not become the production register until every item is satisfied.
The fourteen gates in the product
AvailableEach is computed from the location's records every time it is read, with the fact behind it and a link to where it is fixed. Only an owner with an authenticator can activate live sales, by typing the confirmation phrase; an owner or manager can pause and resume.
- 01Connected to production MetrcMetrc
- 02Licence number
- 03Metrc facility licence
- 04Hours of operation
- 05Receipt settings
- 06Tax rules confirmed
- 07Compliance rules reviewed
- 08Register device
- 09Staff who can sell here
- 10Practice sale completed
- 11Metrc connection
- 12Live Metrc switched onMetrc
- 13New York sales report confirmed with MetrcMetrc
- 14No open critical findings
The gates marked Metrc depend on Metrc
Production Metrc sales reporting is itself gated on Smoke Alarm's integrator status with Metrc for New York and on Metrc's confirmation of the New York sales-report fields. Until both are in place, a location can complete every other gate and run practice sales, but live sales that report to Metrc cannot be switched on.
Every sale queued to Metrc with verify-before-retry so nothing is sent twice; New York's sales payload fields are still being confirmed with Metrc.
Waiting on: Metrc's written confirmation of the New York sales report fields; production API access.
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.
Two systems never write the same regulatory transaction.
The rule the whole path exists to protect.
- Available
Final legacy export after the last sale
The incumbent completes its last sale, its final export is taken and imported, and only then does Smoke Alarm sell. Nothing is sold twice and nothing is reported twice.
- Available
Owner, authenticator, typed confirmation
Activation is refused unless every required gate is done, checked again inside the same transaction that flips the switch. The confirmation is audited with the state of every gate at that moment.
- Available
Pause is a state, not a workaround
Live sales can be paused and resumed, and resuming re-checks every gate. A location that is not exactly live cannot complete a production sale.
We manage the exit process with you.
Notice periods, cancellation, RMAs and equipment returns are part of leaving a vendor. Today Smoke Alarm's people manage that with you as a service; tracking it inside the product is on the roadmap.
What the service covers
Service- Contract and notice-period review, with you and your counsel
- Cancellation timing against the cutover date
- Return authorisation (RMA) requests to the incumbent
- Equipment inventory and return shipping
- Confirmation that legacy access ends after the final export
A service performed by Smoke Alarm's team, not software. Smoke Alarm does not give legal advice on your incumbent contract.
Tracking the incumbent vendor's notice period, cancellation, RMA and equipment returns as part of the migration record.
Land, prove, then switch.
You do not have to decide to replace anything to start. Reconcile pays for itself beside your current POS; the switch is there when the evidence says so.
Audit Shield Reconcile beside your current POS: Metrc, POS, ledger and count compared package by package.
Audit Shield ReconcileWeeks of findings, cases and a reproducible report. You see what the incumbent missed before you change anything.
How Reconcile proves itImport, shadow, Green Light, cut over, exit. The path on this page, with professional deployment behind it.
Professional DeploymentBring the export. We will show you the aliases.
Twenty minutes with Ken and Charles: one inventory export from your current POS, and you will see how it maps, what stays, and what Reconcile finds first.