Platform / Move
One System From Manifest to Front Door.
Smoke Alarm Delivery is in development — no dispatch, driver or delivery code runs today. What follows is the design: a delivery is the same transaction the register created, carried to the customer's door with every change of hands recorded as an event.
Dispatch, driver custody, identity verification at the door, failed-delivery returns and reconciliation as one transaction. Designed and priced; not built.
Chain of custody · one package
Simulated11 states, 10 permitted moves. A move not in the table cannot be recorded, so inventory has nowhere to disappear to between states.
- Store inventoryVerified
- Reserved to orderVerified
- PickedVerified
- PackedVerified
- ManifestedVerified
- Driver custodyPending
- Customer deliveryVerified
- From driver custody, when the handoff fails:
- Failed deliveryReview
- Driver returnPending
- Store receiptVerified
- Inventory reconciliationReconciled
The sale doesn't end at the register. Neither does compliance.
Dispatch, driver custody and the customer handoff are stages of the same transaction lifecycle, with Audit Shield recording a status at each one.
- 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.
Not a bolt-on. The register's own inventory, on the road.
Delivery reads and writes the same operational inventory the register does, so the shelf, the storefront and the vehicle can never hold three different truths.
- Storefront
- POS
- Inventory
- Metrc
- Dispatch
- Driver
- Customer
- Reconciliation
Prepaid orders only
The first release transports only products already on prepaid orders. No speculative driver inventory, no rolling mobile dispensary: if it is on the vehicle, a customer has already bought it.
One inventory state
A package moves from store inventory to reserved, picked, packed, manifested, driver custody and delivered. Each is a state on the same ledger the register sells from, never a copy.
One transaction ID
The order, the sale, the payment, the Metrc submission, the manifest, the run, the driver, the handoff and any return share one identifier, so the whole story reads from one record.
The dispatch board.
Five columns, one per stage of a run. Select an order to read the custody events behind it. Everything here is fictional and static.
Dispatch · Evergreen Dispensary (simulated)
Illustrative design previewA preview of the dispatch board Smoke Alarm Delivery is designed around. Fictional orders, fictional store; no dispatch code runs today.
Custody event log · SA-7F3K-1041
Zone 1 (simulated) · 3 packages · prepaid
One transaction ID follows the order through the sale, the manifest, custody and reconciliation. Every row below is an event; none can be edited after the fact.
- 11:52Store inventoryEvergreen Dispensary (simulated) ledgerVerified
- 12:14Reserved to orderStorefront order (prepaid)Verified
- 12:31PickedPicker scanVerified
- 12:38PackedPacker scanVerified
- 12:45ManifestedDispatchVerified
The driver's phone, and the customer's.
The driver records custody and verification; the customer sees a status. Neither sees more than they need.
Driver workflow
Illustrative design previewThe driver workflow as designed. Fictional run, fictional packages; no driver software exists today.
- Accept run
- Scan each package into custody
- Navigate
- Verify at the door
- Hand off
- Return failed items
Run A · 3 stops · 8 packages
Accept run
The run lists only prepaid orders already picked, packed and manifested. There is nothing on the vehicle that is not on a manifest.
Customer tracking
Illustrative design previewThe customer's order status as designed. Fictional order; no customer-facing tracking exists today.
Your order · Evergreen Dispensary (simulated)
SA-7F3K-1033Your order is on its way.
Delivery window 12:00–2:00 pm. The driver will check ID before handing anything over.
No map and no live driver location. The customer sees a status and a window; the store keeps the custody record. Nothing about the customer beyond the order is retained for tracking.
Verification at the door is an event, not a photograph. The design stores the method (scanned or inspected), the result and the time. It does not retain the ID image, the licence number or the customer's address beyond the delivery itself. That is the same rule the register's ID verification follows today (Preview).
When the handoff fails, the package comes home on the record.
A failed delivery is not an exception to the chain of custody; it is a branch of it, and it ends in reconciliation.
Failed delivery · order SA-7F3K-1029 (simulated)
SimulatedIllustrative design previewThe return branch as designed. One fictional package that could not be handed over; no delivery code runs today.
Failed delivery
No one at the address can present a valid ID, or the recipient declines. The driver records the reason; the package stays sealed in driver custody.
Audit Shield: The order cannot be marked delivered without a verification event.
The controls that watch this branch
- BlockedFailed delivery not returned. A package left driver custody as a failed delivery and has no store receipt by the end of the run.
- ExceptionVehicle inventory mismatch. What was manifested onto the vehicle does not equal what was delivered plus what was returned.
Both are designed as Audit Shield findings with an owner, evidence and a resolution, like every finding today. Neither exists in code yet.
Priced now, so you can plan.
$3 per completed delivery
Optional Smoke Alarm Delivery module, in development. The price is published so operators can plan; customer-facing presentation follows the merchant agreement and applicable requirements.
Delivery Service (or “Delivery & Order Processing”) is Smoke Alarm's fee for the module. It is never a state-imposed fee and is separate from cannabis taxes and payment processing.
Requires Smoke Alarm POS
Delivery is a module of the register, not a separate product: it needs the register's inventory, its compliance gate and its Metrc queue to exist. The register is in pilot today (Preview), and delivery follows it. See the platform pricing.
Dispatch, driver custody, identity verification at the door, failed-delivery returns and reconciliation as one transaction. Designed and priced; not built.
- Preview
- Explore with illustrative data. Not generally released for customer use.
- Planned
- Not available yet.
Designed around New York delivery requirements as we understand them.
These are the provisions the design is built around, paraphrased from the regulations as we read them. Each is confirmed with counsel before release; none of this is legal advice, and Smoke Alarm does not claim any regulator's approval.
| Provision | As we read it | In the design |
|---|---|---|
| 9 NYCRR § 123.10(d)(4) | Orders not placed in person carry a 21+ attestation; the employee delivering verifies identity and age at the point of delivery by viewing or scanning an accepted document, and both identities are recorded when the person accepting is not the person who ordered. | The attestation is captured with the order; the driver step records a verification event with method and result; a second verified identity is recorded on the same event when the recipient differs. |
| 9 NYCRR § 123.10(k) | A dispensary providing delivery keeps a written delivery service plan available for inspection. | The custody model and the run records are designed to be the evidence behind that plan, not a substitute for it. |
| 9 NYCRR § 125.10(g) | Deliveries to consumers travel with a shipping manifest and an invoice; nothing not on the manifest may be transported; the manifest is not changed after departure except to reflect fulfilment. | The run is manifested before departure, packages are scanned against it into custody, and the only post-departure change is the delivered or returned status of each line. |
| 9 NYCRR § 125.10(i) | A transport attempted and not completed returns to the licensed premises; returned inventory may be restocked only if new, unopened and handled without compromising integrity. | The FAILED DELIVERY → DRIVER RETURN → STORE RECEIPT branch, with a seal check at receipt and quarantine for anything that fails it. |
| 9 NYCRR § 125.10(c) | An employee delivering to a consumer is at least 21 and can identify themselves as the licensee's employee. | Driver accounts are employee accounts with a role; a run cannot be accepted by an account without it. |
Illustrative design previewEvery board and workflow on this page is a design preview on simulated data.
Start where the delivery starts: at the register.
Delivery follows Smoke Alarm POS. Bring one manifest and one register close and we will show you the inventory the vehicle would leave with.