Flourish MCP Prompts: Practical AI Prompts for Inventory, Orders, Retail Metrics, and Compliance Sync Health
Flourish MCP provides approved users with a practical way to connect Flourish with AI tools such as Claude, ChatGPT, Gemini, Grok, and other compatible LLM interfaces. Once connected, users can ask plain-language questions about Flourish data, review operational records, and perform supported Flourish actions through a chat interface, subject to their permissions and tool approval settings.
This prompt library gives cannabis operators a verified starting point for common Flourish MCP workflows, including facilities, items, packages, inventory, outbound orders, retail order metrics, delivery and shipment routes, reference data, package locks, and compliance sync health.
The prompts below are designed to be copied, pasted, and adapted. Available results depend on your Flourish user permissions, facility access, enabled modules, and MCP tool permissions.
TL;DR
Flourish MCP lets approved users connect Flourish to an AI tool and ask plain-language questions about operational data.
Instead of searching through multiple screens or exporting data for basic lookups, users can ask questions such as:
“Show me all packages at [facility name] that are currently locked, and why.”
Or:
“Open order [order ID] and tell me whether each line has enough available inventory to allocate.”
This article includes safe, verified prompts for currently supported MCP workflows. It does not include speculative prompts for capabilities that are not currently documented as available through Flourish MCP.
Key Takeaways
-
Flourish MCP connects Flourish data to AI tools so users can ask operational questions in plain language.
-
This prompt library focuses on verified MCP workflows: facilities, items, packages, outbound orders, retail order metrics, delivery and shipment routes, reference data, package locks, and sync health.
-
Write actions that require approval. Current write tools update records in Flourish only and do not sync changes directly to Metrc, BioTrack, or other state compliance systems.
-
Specific prompts work better than vague prompts. Include facility names, SKUs, item names, package IDs, order IDs, shipment IDs, delivery IDs, date ranges, and statuses whenever possible.
How to Use These Prompts
To use these prompts, connect Flourish MCP to your AI tool of choice and enable the Flourish connector in your chat. Once connected, ask questions naturally and let the AI call the appropriate Flourish MCP tool.
For example, instead of manually searching through inventory screens, you can ask:
“Show inventory for facility [facility name].”
Instead of opening an outbound order and manually checking each line, you can ask:
“Open order [order ID] and summarize the header details, order lines, charges, discounts, payments, and per-line inventory levels.”
The AI will return answers based on the Flourish data your user account is already allowed to access.
Before using write actions, review your AI client’s tool permission settings. Read-only tools can be useful for fast lookups, reviews, and analyses. Write tools, such as item updates or package lock/unlock actions, should require approval before execution.
5 Tips for Getting the Most Out of Flourish MCP
1. Include the facility whenever possible
Many Flourish workflows are facility-specific. Instead of asking:
“Show locked packages.”
Ask:
“Show locked packages at [facility name].”
This helps narrow the result set and reduces ambiguity.
2. Use exact identifiers when you have them
Prompts work best when they include exact values such as SKU, item name, package ID, order ID, shipment ID, delivery ID, destination, sales rep, order status, or payment status.
For example:
“Find all items with SKU [SKU].”
Is better than:
“Find that product we sell.”
3. Start read-only, then approve changes separately
For workflows involving locks, unlocks, or item updates, start by asking MCP to show the records first. Then ask for the change after you confirm the data.
Example:
“Find packages matching [criteria] at [facility name] and show me the package list before I approve any lock action.”
4. Ask for summaries and exceptions
Flourish MCP is especially useful for reviewing operational exceptions. Ask for failed sync records, locked packages, insufficient inventory, unsynced allocated packages, orders awaiting payment, or items matching a specific status.
Example:
“What’s the current sync status of my Metrc integration? Are there any failed records?”
5. Save recurring prompts
Teams can save repeatable prompts for daily inventory checks, order review, retail order monitoring, and sync health review.
A simple daily routine might include:
“Give me today’s and tomorrow’s retail order counts for each store.”
“Show submitted outbound orders from [facility] with payment status Awaiting Payment.”
“What’s the current sync status of my Metrc integration? Are there any failed records?”
Role-to-Section Guide
|
Role |
Most Useful Sections |
|---|---|
|
Operations Manager |
Inventory & Operations, Outbound / B2B Orders, Compliance & Sync Health |
|
Inventory Manager |
Inventory & Operations, Package Lock Workflow, Items & Catalog Data |
|
Wholesale / B2B Sales |
Outbound / B2B Orders, Delivery & Shipment Routes |
|
Retail Manager |
Retail Orders, Inventory & Operations |
|
Compliance / Admin |
Compliance & Sync Health, Package Lock Workflow, Reference & Exploration |
|
Flourish Admin |
Reference & Exploration, Compliance & Sync Health, Package Lock Workflow |
Inventory & Operations Prompts
Use these prompts when you need fast visibility into facilities, inventory, package status, and package availability.
-
“What facilities do I have access to in Flourish?”
-
“Show me all packages at [facility name] that are currently locked, and why.”
-
“List items where the SKU starts with [SKU prefix] and the product class is [product class].”
-
“How many packages of [strain name] do I have on hand, grouped by facility?”
-
“Show inventory for facility [facility name].”
-
“Find all items with SKU [SKU].”
Pro tip: Start broad, then narrow the result. For example, first ask for inventory by facility, then follow up with a specific SKU, lot number, package status, or locked/unlocked state.
Items & Catalog Data Prompts
Use these prompts to search item records, review product details, and check reference data.
-
“Search active items by item name, retail display name, part number, or SKU for [search term].”
-
“Show item details for [SKU], including category, class, sellable status, purchasable status, pricing, cost, cannabis attributes, THC/CBD fields, and supplier info.”
-
“List active brands and which ones have logo images.”
-
“What units of measure does Flourish support, and which ones are count vs weight?”
Pro tip: Use exact SKUs when available. If you do not know the SKU, start with item name, retail display name, part number, or brand.
Outbound / B2B Order Prompts
Use these prompts when reviewing outbound orders, allocation readiness, payment status, shipment details, and B2B order inventory availability.
-
“Show submitted outbound orders from [facility] with payment status Awaiting Payment.”
-
“Open order [order ID] and tell me whether each line has enough available inventory to allocate.”
-
“For order [order ID], are all allocated packages in sync with Metrc?”
-
“List the orders on shipment [shipment ID] in stop order.”
-
“Show outbound orders by facility, order ID, destination, sales rep, order status, and payment status for [facility or filter].”
-
“Open order [order ID] and summarize the header details, order lines, charges, discounts, payments, and per-line inventory levels.”
Pro tip: For order review, include the order ID whenever possible. For queue review, include facility, order status, payment status, destination, or sales rep.
Retail Order Prompts
Use these prompts when retail teams need quick visibility into store-level order counts, fulfillment types, and delivery route activity.
-
“Give me today’s and tomorrow’s retail order counts for each store.”
-
“List orders on delivery route [delivery ID] with stop sequence and payment status.”
-
“Show retail order dashboard counts by company and store, including pickup, delivery, in-store, open orders, back orders, pre-orders, needs-review orders, today’s orders, and tomorrow’s orders.”
Pro tip: Use retail prompts for dashboard-style visibility. These prompts are best for order counts and operational status, not full financial analysis.
Compliance & Sync Health Prompts
Use these prompts to review integration status, failed records, and compliance sync readiness before operational handoffs.
-
“What’s the current sync status of my Metrc integration? Are there any failed records?”
-
“Show me any integration sync errors from the last 24 hours and explain what they likely mean.”
-
“For order [order ID], check whether allocated packages are synced with the compliance system before shipment.”
-
“Show company integration sync status summaries.”
Pro tip: These prompts are for reviewing sync health and identifying issues. They should not be written as requests to submit, certify, or directly modify state compliance system records.
Package Lock Workflow Prompts
Use these prompts to review, approve, and unlock packages. These workflows are useful for QA holds, testing review, inventory control, and operational exceptions.
Important: Write actions that require approval before execution.
-
“Find all packages at [facility] tagged with the test batch ID [test batch ID] and lock them with the [lock code] lock code.”
-
“Unlock the three packages I just locked for QA; testing came back clean.”
-
“Show valid lock codes for [facility name] before I lock any packages.”
-
“Find packages matching [criteria] at [facility name] and show me the package list before I approve any lock action.”
Pro tip: For package lock workflows, ask Flourish MCP to show matching packages first. Confirm the package list, then approve the lock or unlock action.
Reference & Exploration Prompts
Use these prompts when you are learning what your MCP connection can access or when you need to inspect available statuses, tools, and reference values.
-
“What tools does the Flourish MCP server expose? Group them by read vs write.”
-
“What order payment statuses are available?”
-
“What order payment types are available?”
-
“Which tools are read-only, and which tools can make changes in Flourish?”
Pro tip: Use reference prompts early in your MCP rollout. They help admins and operators understand what is available before building repeatable workflows.
Frequently Asked Questions
What is Flourish MCP?
Flourish MCP is a way to connect Flourish to an AI tool, enabling users to ask questions and perform supported actions via a chat interface. MCP stands for Model Context Protocol, a standard that allows AI tools to communicate with external software systems.
Which AI tools can work with Flourish MCP?
Flourish MCP can be used with supported LLM interfaces such as Claude, ChatGPT, Gemini, Grok, and other compatible MCP clients.
What can I ask Flourish MCP?
You can ask about verified MCP workflows, including facilities, active items, package and inventory data, package lock status, outbound orders, B2B order inventory readiness, retail order metrics, delivery and shipment route orders, brands, reference data, and integration sync status.
Can Flourish MCP make changes in Flourish?
Yes, but only through supported write tools. Current write actions include limited item updates and package lock/unlock actions. These actions should require approval before execution.
Does Flourish MCP write actions sync to Metrc or BioTrack?
No. Current Flourish MCP write tools update records only in Flourish. They do not sync changes directly to Metrc, BioTrack, or other state compliance systems.
Does Flourish MCP bypass user permissions?
No. Results depend on the user’s Flourish permissions, facility access, enabled modules, and AI client tool permissions.
Should we let AI perform write actions automatically?
For most teams, no. A safer starting configuration is to allow read tools where appropriate and require approval for write tools. Teams should review package lock, unlock, and item update actions before approving them.
Do I need SQL or exports to use these prompts?
No. These prompts are designed for plain-language questions inside your AI chat interface. The AI calls the available Flourish MCP tools as needed.
Can I save the prompts I run every day?
Yes. Teams can save recurring prompts for daily inventory checks, outbound order review, retail order monitoring, and sync health review.
Will more prompts be added?
Yes. This library should grow as Flourish MCP exposes additional capabilities and as teams identify repeatable operational workflows.
Ready to use Flourish MCP with your team?
Start with read-only workflows such as facilities, inventory review, order lookup, retail order metrics, and compliance sync health. Then expand to approval-based workflows, such as package locks, package unlocks, and limited item updates, once your team is comfortable with the process.
To get started, review your MCP connection setup, confirm your Flourish permissions, and work with your Flourish admin to decide which tools should be available, which should require approval, and which workflows should be saved as repeatable prompts.
Want To Learn More? Schedule a Demo Today!
