Cannabis Claude
The #1 AI meets the #1 Cannabis CRM
Design-partner preview · Built on Salesforce
Claude, on the cannabis operating system
Cannabis Claude pairs Claude‘s reasoning with your Metrc-consolidated Salesforce records. It reads what your permissions allow, drafts the compliance work you dread, and takes no action without your confirmation.
- Location
- Flagship Dispensary — Bay 3
- Metrc packages scanned
- 214
- Salesforce inventory records
- 211
- Variance
- 3 packages unmatched
- Recommended action
- Flag 3 for manual recount
Nothing here has been written to Salesforce yet.
Operating model
Read, draft, review, confirm, audit
This five-step loop is the product contract for every preview skill. No step is skipped, and no write happens without you.
-
Read
The preview is designed so Claude reads only what your Salesforce permission set already allows — packages, transfers, sales, cash counts.
-
Draft
It drafts the reconciliation, memo, manifest, or summary in plain language, citing the records it used.
-
Review
You review the draft against the source records and edit anything before it goes further.
-
Confirm
Nothing writes to Salesforce until a person with the right permission explicitly confirms it.
-
Audit
The package direction attributes confirmed actions to your Salesforce user and records them in your existing audit trail.
Metrc MCP connector
Broad Metrc visibility, behind one governed door
A read-first MCP layer gives Claude typed access to documented Metrc v2 endpoints while the integrator and licensee user keys stay server-side — never in the prompt.
- 01You ask
Packages, plants, transfers, sales, lab tests, tags, or facilities.
- 02MCP validates
HTTPS host, approved v2 resource, query shape, response size, and read-only method.
- 03Metrc authorizes
Integrator key plus the licensee user’s key; that user’s Metrc permissions still decide access.
- 04Cannabis Cloud grounds
Results can be reconciled with Salesforce records and prepared for a human-reviewed workflow.
{
"path": "/packages/v2/active",
"query": {
"lastModifiedStart": "2026-08-27T00:00:00Z",
"pageSize": 50
}
}Vendor and user keys are injected by a secret manager. They are never returned to Claude or written to logs.
Ten skills for the preview
The compliance work Claude drafts
Every skill below produces a draft against your own records. Nothing here posts, files, or adjusts inventory on its own.
-
Package reconciliation
01Matches Metrc-scanned packages against Salesforce inventory records and flags variances for recount.
Draft outputPackage tag Metrc Salesforce 1A4FF0100…02A1 On hand On hand 1A4FF0100…02B7 On hand Missing 1A4FF0100…02C4 On hand Missing -
Transfer manifest prep
02Drafts the outbound transfer manifest from the order, cross-checked against Metrc package status.
Draft outputLine Item Status 1 Flower — 1lb case Ready 2 Pre-roll 20ct Ready 3 Vape cart 0.5g Needs lab result -
Sales-sync triage
03Finds orders where the POS sale and the Metrc-reported sale disagree, and drafts the likely cause.
Draft outputOrder POS Metrc #48211 Closed Closed #48219 Closed Not reported -
Cash-variance investigation
04Drafts a plain-language memo explaining a drawer variance, citing the shift, tenders, and prior counts it used.
Draft memoDrawer 2, close 8/26 shift: $42.00 short. Cash sales totaled $1,180.00 against a $1,138.00 count. No refunds logged this shift. Closest match: 3 cash sales between 6:40–6:55pm rung by the same operator. Recommend reviewing that window’s register tape before adjusting.
-
Cycle counts
05Builds the count sheet for a location and reconciles it against expected on-hand quantities.
Draft output- Flower — Bay 1: counted, matches
- Concentrates — Bay 2: counted, matches
- Edibles — Bay 3: not yet counted
-
Closing summaries
06Drafts the nightly closing report — sales, tenders, variances, and open exceptions — from the shift’s records.
Draft summaryTuesday close: $9,412 gross across 214 orders. Card $6,180, cash $2,940, split $292. One open exception: Drawer 2 short $42 (memo drafted). No sales-sync mismatches outstanding.
-
Purchase-limit checks
07Checks a customer’s same-day purchases against the state limit before checkout is finalized.
Draft outputCustomer Today Limit J.M. 21.5g 28.0g R.T. 27.8g 28.0g — near limit -
Recall tracing
08Traces a flagged lot forward through transfers and sales to draft the list of affected packages and locations.
Draft output- Lot 48-B — traced to Flagship Dispensary
- Lot 48-B — traced to Eastside location
- 2 units sold — customer notice drafted, not sent
-
Audit-prep bundles
09Assembles the records an auditor asks for — packages, transfers, sales, variances — into one reviewable bundle.
Draft bundle- Package ledger, Q2 — attached
- Transfer manifests, Q2 — attached
- Variance memos — 2 awaiting your review
-
Grounded menu copy
10Drafts menu descriptions straight from a product’s own record — strain, potency, terpenes — nothing invented.
Draft copyBlue Dream, 22.4% THC. Sativa-leaning hybrid with a sweet berry aroma from myrcene and pinene. Sourced from the record’s lab result batch #48-B; no claims beyond what’s on file.
Governance
Every draft is bounded by mechanics, not promises
This is the package contract we are validating with design partners.
- Permission-scoped reads. The design limits Claude to what your Salesforce user can already see.
- Draft-first. The design treats every output as a draft record or document, not a live transaction.
- Human confirmation gate. A person with the right permission must approve before anything writes.
- Attributed writes. The package direction attributes confirmed actions to your Salesforce user, not a shared service account.
- Existing audit trail. The package direction records confirmations and writes in your org’s audit log — no shadow system.
- No autonomous filing. Claude does not submit state or Metrc compliance reports on its own; a person still reviews and files.
Cannabis Claude is built by the Cannabis Cloud team on the Salesforce platform, using Claude‘s reasoning. There is no official Anthropic partnership, and this preview is not endorsed by Metrc.
Two different jobs
Bud vs Claude
Bud runs the register. Claude is designed for the back office. They don’t compete — they cover different shifts.
Bud
- Lives on the POS home screen, in front of your budtenders
- Voice, chat, and SMS — built for the floor, mid-shift
- Looks up stock, rings a sale, walks through configuration
- Agentforce-hosted, inside your org
Claude
- Lives in back-office and compliance workflows, not the register
- Drafts written on request — memos, manifests, summaries
- Helps managers reconcile, investigate, and prep for audits
- Confirmation-gated writes; no direct POS actions
Both are designed to work from your Salesforce data, under your permissions, with an audit trail — not a separate system of record.
Dreamforce
Meet us at Dreamforce
Bring us the compliance workflow your team still handles by spreadsheet, swivel chair, or late-night reconciliation. We’ll map how Cannabis Claude could read, draft, and prepare it for a human-confirmed action.
A 30-minute working session
- 01Show us one high-friction Metrc or Salesforce workflow
- 02See the governed MCP and skill pattern against your use case
- 03Leave with a scoped design-partner next step
FAQ
Questions design partners ask first
Is this an official Anthropic product?
No. Cannabis Claude is built by the Cannabis Cloud team on the Salesforce platform, using Claude‘s reasoning. There is no official Anthropic partnership.
Can Claude take actions without me?
No. The preview is designed so Claude reads what your permissions allow and drafts the work. Nothing writes to Salesforce until you confirm it.
Does Claude file compliance or Metrc state reports automatically?
No. Claude drafts the underlying reconciliation, manifest, or summary work. A person still reviews and files anything that goes to a regulator.
Is this listed on the Salesforce AppExchange?
Not yet. It isn’t certified, listed, or security-reviewed there today. An AppExchange-ready package is the direction we’re building toward.
Is this endorsed by Metrc?
No. Cannabis Cloud consolidates your Metrc data into Salesforce; Metrc has not endorsed this preview.
How do I get access?
Join the design-partner preview and we’ll reach out to scope your org.
Ready to see it on your own data?
Join the design-partner preview and we’ll scope Cannabis Claude against your Salesforce org.