Skip to content
SmokeAlarm.ioBY AUDIT SHIELD
Open app Book a walkthrough
Menu

NEW YORK BUILT. COMPLIANCE AT THE CORE.

Your store.
In focus.

New York compliance, built into the shift.

Ivory helps your team spot gaps in store records, see what to check next, and know what to say at the counter.

Try Ivory Book a walkthrough

Start with Audit Shield Reconcile. Keep your current POS.

Ivory at workInteractive example

Ivory

Powered by SmokeSense

  1. Sources
  2. Ivory
  3. You decide

Inventory Ivory recommends

Three units need a closer look.

The exports differ by three units. Count the package independently, then review the result and both source timestamps with a manager before proposing a correction.

POS export · Metrc export
POS export

24 units at 10:42 a.m.

Metrc export

21 units at 10:45 a.m.

At the counter

“I’m checking availability so I can give you an accurate answer.”

Adapt the conversation to the customer.

Compliance check

Independent counts and named approval protect the audit trail.

Explore inventory
Sample store recordsEvery next step is yours to review.
VETERAN-OWNED · MINORITY-OWNED · NEW YORK-BUILTExplore the platform

A system built for New York. In New York. By New Yorkers.

Rochester roots. A commitment to New York dispensaries.

Meet the people behind it

THE KNOWLEDGE BEHIND THE WORK

Know the standard.
Own the day.

A calmer day starts with a team that knows what to do. Bring compliance guidance, practical training and product knowledge closer to every decision.

01

Keep the standard in sight.

Work from cited New York requirements and OCM guidance. See the source, understand the issue, and give the next step a clear owner.

02

Learn while doing.

Give each role a guided path through the work. Follow progress, revisit a step and keep a record of what your team has learned.

03

Put knowledge behind the conversation.

Explore sourced strain lineage, reported terpenes and published lab ranges. Keep that reference distinct from the product’s own label and certificate of analysis.

From a source to a more informed conversation.Illustrative learning path

  1. Check the source

    Product record
    This package’s label and lab results.
    Strain reference
    Lineage. Reported terpenes. Published ranges.

  2. Start the conversation

    “Let’s look at this product’s label and lab results together. Then we can explore its strain reference.”

    A staff prompt to adapt after checking the available records.

  3. Keep learning visible

    Make the next shift stronger.

    Per-person progress.
    Completion dates.
    A downloadable training sheet.

Guided workflow records document software training. Keep required workforce training and its supporting certificates in your store’s training evidence. Strain references depend on source availability and licensing.

Better-informed people. More considered decisions.

Sell with context

The counter, connected.

Receive with clarity

Every package in view.

Reconcile the records

A next step for every gap.

Understand the why

Evidence beside the answer.

THE OPERATING SYSTEM BEHIND THE SALE

Less chasing.
More knowing.

Your team should be running the store, not piecing its story together from five different places.

01
One view of what needs you.

See the case, the source records, and the person who owns the next step. Keep stale and missing information in view.

02
AI that prepares useful work.

Explore sourced explanations, evidence checklists, and draft plans your team can review.

03
A record of how it was resolved.

Keep counts, causes, approvals, and confirmation together. A clear trail from the first question to the final check.

THE WHOLE STORE, IN THE PICTURE

Every handoff.
A little more connected.

Bring the work into a shared system, from the delivery at the door to the sale at the counter and the records behind it.

Current saleSample cart
Product + packageItem check
Purchase-limit checkExisting rules
01 / THE COUNTER
Confirm availability

Keep the customer.
Lose the clutter.

Products, customer checks, orders, and the current sale in a workspace built around the next step.

Explore the experience
Delivery checklistAt the dock
Physical package tagMatched
Manifest line itemMatched
Lab recordReview
02 / THE DOCK
Available

Catch the question
before it hits the shelf.

Check packages against the manifest. Keep exceptions and missing evidence with the delivery they came from.

Follow the evidence
ONE PACKAGE / THREE RECORDS · SAMPLE
METRC12
POS10
COUNT—
Count needed · cause unknown
03 / THE RECORD
Available

Make every difference
explainable.

Bring the source, the count, the case, and the approval into one reviewable trail. Then verify the result.

See the control layer

BUILT HERE. BY PEOPLE WHO CARE.

We call
New York
home, too.

New York dispensaries deserve technology built around their reality. SmokeAlarm is built by Audit Shield AI, with Rochester roots and a focus on the work behind every sale.

Veteran-owned Minority-owned New York-built
Get to know your advantage
Meet Cannabis Control · Interactive example

Your next move.
Backed by the record.

Ask Ivory what needs attention. Explore how the AI control layer prepares explanations and proposed next steps for your team to review.

Ivory / Cannabis ControlIllustrative response
Why don't these inventory records agree?
Needs evidence

The records differ. The cause isn't confirmed.

The stored Metrc snapshot and POS export show different quantities. Their timestamps also differ. Review a current count and the package history before selecting a cause.

Metrc snapshot · source 01 POS export · source 02 Physical count needed
See the walkthrough

A possible cause is never a confirmed shortage.

No source read or inventory change is triggered by this example.

Design concept · Proposed AI workflows · Illustrative records. Design target for the AI control experience. Final availability depends on implemented capabilities and source access.

WORK WITH THE RECORDS YOU HAVE

Connect the record.
Keep your stack.

Start beside your existing POS, or bring the counter into SmokeAlarm. Connection methods and availability stay explicit.

MMetrc

Authorized API access.
Manual reads and visible source state.

Your point of sale

Supported connector or export import. Method varies by provider.

Your team

Package scans, physical counts, and uploaded evidence.

Connection methods & availability
  • Read-only by default: Metrc is read through each store's own key, and a read starts when a person presses Sync. Every store starts on manual sync; a daily read is switched on per store, never by default. One narrow write exists and is off: a package-quantity correction from an approved case, only for a store an administrator has authorised, read back afterwards.
  • By export file: Dutchie, Flowhub and BLAZE inventory comes in as an export file, mapped once. Read-only API connectors are built for Dutchie and Flowhub but have not been run against a live store account, so the export is the path to rely on today. Other systems come in as a CSV through the same mapper.
  • Not available: writing to your point of sale; marketplace menu listings (held for a legal answer); point-of-banking tender (refused by decision).
Every connection, with its status
THE HUMAN IS STILL IN CONTROL

AI prepares. Your team decides.

A recommendation doesn't change inventory. Keep the evidence, required approvals, execution, and confirmation separate, with the actual state visible at every step.

EvidenceDraft proposalNamed approvalVerified result

A second person verifies a count before a correction is approved. Nothing is complete until the source is read back, and every step goes in an append-only audit log. A store's confidential data is never sent to a free model endpoint. Trust and security

See how the workflow works
LET'S CLEAR THE SMOKE

A clearer head.
For your entire store.

Book a walkthrough Start with your store. See the actual fit.Connect your dispensary