Tribal cannabis programs are not variations of a state program. They are sovereign regulatory systems established under tribal law, administered by the Tribe's own regulatory agency, and, in some cases, connected to a state through a negotiated compact. Every program differs in who holds licenses, which tracking system the regulator uses, what reports it expects, and what happens when a product crosses onto non-tribal land.
That variation is the core operational challenge, and it should shape your software decision. The right question is not which software has the most features. It is which software can conform to the way your regulator designed your program.
Flourish's first deployment, in 2017, was with the Iipay Nation of Santa Ysabel in Southern California, and we now support tribal operators across the country. We are live integrated with Tribal Metrc, we serve as the traceability system of record that reports back to a Tribe, we produce reports for tribal regulators, and we support compacted and hybrid tribal-state operations. The sections below explain how tracking-system choices affect daily operations and where Flourish fits.
Tribal Nations Compliance
Which tracking system applies to your operation
The tracking system is chosen by your regulator, not by your operating software vendor. In our experience, tribal programs fall into three models.
Model 1: Your Tribe has its own Metrc instance ("Tribal Metrc")
Some Tribes contract directly with Metrc or, under a compact, operate a Metrc instance that is separate from the state's. Metrc announced its first track-and-trace contract with a tribal government, the Twenty-Nine Palms Band of Mission Indians, in June 2024. Under Minnesota's compacts, each compacting Tribe runs its own Metrc instance alongside the State's. Licensees report into the Tribe's instance, and the Tribe's regulator administers it.
Where Flourish fits: Flourish is live on Tribal Metrc for ANANG Native Cannabis Co., which operates under the Fond du Lac Band of Lake Superior Chippewa in Minnesota. The team works in Flourish while required data reports to the Tribe's Metrc instance. When a product moves in or out, Metrc requires an external transfer. Flourish pulls in receipts and stages outbound transfers with transfer templates.
Model 2: Your Tribe reports into, or transfers product through, a state system
Under some compacts, tribal enterprises participate directly in a state's tracking system, or move product into it through defined transfer procedures. Michigan's compact with the Bay Mills Indian Community, finalized in July 2025, allows the Tribe to integrate its dispensary into Michigan's statewide Metrc system.
Where Flourish fits: Flourish supports compacted and hybrid tribal-state deployments, so an operator can meet its Tribe's requirements and the state's from the same system. Configuration follows the compact.
Model 3: Your Tribe uses another system or has not mandated one
Tribes are free to choose any vendor or to set their own record-keeping and reporting rules without a government-procured traceability platform.
Where Flourish fits: Flourish serves as your seed-to-sale system of record and produces the traceability reports your Tribal Regulatory Agency requires. Mountain Medicine, one of the first tribally owned cannabis dispensaries in California, uses Flourish for traceability reporting back to the Tribe.
Not sure which model applies? Ask your Tribal Regulatory Agency which system it has selected and whether your compact, if any, requires data to be sent to a state regulator. Those two answers determine most of your integration requirements.
How Tribal Metrc differs from a state Metrc instance
The Metrc interface looks familiar, but the governance around a tribal instance is different. The comparison below reflects Minnesota's published compacts and procedures.
| State Metrc instance | Tribal Metrc instance (Minnesota compacts) | |
|---|---|---|
| Administered by | State cannabis regulator | The Tribe's regulatory agency |
| Who sees the data | State regulator sees all licensee data | State regulator sees only compacted activity, such as product leaving tribal land for the state market |
| Cross-jurisdiction transfers | Within one instance | Between instances; Minnesota's January 2026 procedure uses external transfers with retagging on receipt |
| Testing data | Standard state requirements | Compacts may require full-panel test results attached to batches before product leaves tribal land |
| Medical product | State program rules | May require a separate, medical-only instance for certain transfers |
| Rule changes | State rulemaking | Tribal code; compacted standards may update when the state amends its rules, with notice and consultation provisions |
What this means operationally: segregating compacted from non-compacted inventory, attaching test results before product crosses a boundary, and tracking which records a state regulator can see all become part of daily work. The transfer mechanics are the same either way.
What makes tribal operations harder to run
- No two programs are alike. Rules, license categories, reporting formats, and tracking systems vary from Tribe to Tribe, even among neighbors in the same state. Software built around one state's rules doesn't transfer cleanly.
- Two rulebooks at once. Compacted operators must meet tribal code for on-reservation activity and compacted standards for anything that touches the state market, often in the same facility.
- Jurisdictional boundaries are data boundaries. Every transfer across tribal and non-tribal land carries testing, tagging, tax, and visibility consequences.
- Regulatory change on several fronts. Tribal code amendments, state rule updates that flow into compacts, federal rescheduling, and the federal hemp redefinition can all land in the same year.
- Banking scrutiny. Financial institutions follow FinCEN's 2014 guidance and rely on licensing information, so clean, auditable records directly affect access to banking.
- Few vendors understand the model. Most cannabis software is designed around state regulators. Tribal operators often end up explaining sovereignty, compacts, and their regulators' structure to every vendor they evaluate.
How Flourish works with tribal operators
Flourish is an operating system for the whole supply chain: cultivation, manufacturing, wholesale distribution, and retail point of sale, with compliance reporting built into the workflows rather than bolted on.
Configured to your Tribe's requirements
Tribal programs set their own rules, so Flourish is configured to your code rather than a state template. As across state markets, that includes:
- Special taxes set by the Tribe
- Purchase limits defined by tribal regulation
- Feature on/off controls, so workflows your program doesn't use are switched off
- Regulator reporting produced for your Tribal Regulatory Agency
- Hybrid operation for compacted Tribes that also report to a state system
- Hemp workflows for operators with hemp programs
Working with tribal operators since 2017
Our first deployment, in 2017, was with the Iipay Nation of Santa Ysabel. Today we support tribal operators across the country, including:
ANANG Native Cannabis Co. (Fond du Lac Band of Lake Superior Chippewa, Minnesota): live on Tribal Metrc, with data reporting to the Tribe's instance.
Mountain Medicine (Mooretown Rancheria Maidu Indians, California): one of the first tribally owned cannabis dispensaries in California, running retail, online ordering, and loyalty in one Flourish system alongside the Tribe's cultivation and manufacturing operations, with traceability reporting back to the Tribe. Read the case study.
Key Regulations in Tribal Nations
Tribal regulatory authority
Federally recognized Tribes possess inherent powers of self-government, including the power to license and regulate activity within their jurisdiction. Tribes that permit commercial cannabis typically establish the program through tribal code and create a regulatory body to administer it: a Tribal Regulatory Agency, cannabis commission, or cannabis control board. Well-designed programs separate the regulator from the business; Minnesota's compacts, for instance, require the Tribal Regulatory Agency to be independent from the Tribe's cannabis enterprises.
Tribal-state compacts
A compact is a government-to-government agreement that governs how a Tribe's cannabis activity interacts with a state's market: sales between tribal and state licensees, transportation across jurisdictional lines, testing, taxation, and data sharing. Compacts vary widely by state.
- Washington authorized cannabis compacts in 2015, and the Liquor and Cannabis Board reports that most of the state's federally recognized Tribes have one.
- Nevada authorizes the Governor to enter agreements with Tribes to coordinate the cross-jurisdictional administration of state and tribal cannabis laws (NRS 223.250).
- Minnesota signed its first compact with White Earth Nation in May 2025 and has since signed compacts with additional Tribes.
- Michigan has finalized compacts with several Tribes, including Bay Mills, Lac Vieux Desert, and Pokagon.
- California has no compact pathway; a Tribe seeking a state commercial cannabis license must submit a written waiver of sovereign immunity. A 2026 California Attorney General opinion (No. 25-102) addresses when Tribes need a state license to do business with California licensees.
A compact typically governs only the activity it covers. Minnesota's compacts, for example, keep non-compacted activity on Tribally Regulated Land under the Tribe's sole regulatory authority.
Federal backdrop
- 2013 and 2014: the Justice Department's Cole Memorandum set federal enforcement priorities, and the October 2014 Wilkinson Memorandum stated those priorities would guide enforcement in Indian Country. Both were rescinded on January 4, 2018.
- 2018: the Farm Bill authorized Tribes to submit their own hemp production plans to USDA.
- 2014 to present: FinCEN's February 2014 guidance remains the framework banks use to serve marijuana-related businesses, including tribal ones.
- 2025 and 2026: Congress narrowed the federal definition of hemp to a total-THC standard, taking effect in late 2026, and in April 2026 DOJ moved FDA-approved and state-licensed medical marijuana to Schedule III, with broader rescheduling still under administrative review.
This is general context, not legal advice. Your Tribe's counsel and regulator are the authorities on how these developments apply to your program.
Licensing for Tribal Nations Operators
Tribal programs license the same core supply-chain functions as state programs, though names, combinations, and ownership rules are set by tribal code and any applicable compact:
- Cultivation: indoor, greenhouse, or outdoor.
- Manufacturing: extraction, infused products, packaging, and labeling.
- Wholesale and distribution: sales between tribal enterprises, other Tribes' licensees, and, where compacted, state licensees.
- Transport and delivery: including movement across tribal and non-tribal land.
- Retail: adult-use, medical, or both.
- Testing: tribally licensed labs or state-licensed labs recognized under a compact.
- Hemp: under a USDA-approved tribal hemp plan or a USDA license, subject to the narrower federal hemp definition taking effect in late 2026.
Many tribal enterprises are vertically integrated, and Minnesota's compacts, for example, state that Tribal Enterprises are not subject to vertical integration limits other than for testing.
Cultivation
Track your entire cultivation lifecycle from seed to harvest. Real-time growth analytics and automated compliance reporting for Tribal Nations.
Learn moreManufacturing
Manage processing jobs, track inputs and outputs, and maintain batch-level traceability.
Learn moreRetail Dispensary
Integrated point-of-sale with compliance reporting, purchase limits, and age verification.
Learn moreMicrobusiness
A single platform for vertically integrated operations across cultivation, manufacturing, and retail.
Learn moreDistribution
Manage wholesale distribution, track compliance shipments, and maintain audit trails.
Learn more"Flourish gave us one system that does it all. It's easy for our team to use, handles online and in-store orders seamlessly, and gives us the flexibility to build modern loyalty and customer engagement programs."
Ryan A. Gregory
Assistant General Manager, Mountain Medicine
Resources & Regulatory Links
- Metrc: track-and-trace provider for state and tribal governments
- Flourish's Metrc integration
- BioTrack: traceability provider with a tribal government solution
- Indigenous Cannabis Industry Association: policy, programming, and the Tribal Cannabis and Hemp Programs Map
- National Congress of American Indians: tribal governance and sovereignty
- USDA: state and tribal hemp plan review
- Washington State Liquor and Cannabis Board: cannabis compacts
- Minnesota Office of Cannabis Management: compacts and cooperative agreements
- Flourish in Minnesota
Frequently Asked Questions
Which track-and-trace system does a tribal cannabis operator have to use?
The Tribe's regulatory agency decides. Some Tribes contract for their own Metrc instance, some participate in or transfer product through a state system under a compact, and some use BioTrack, Flourish, or set their own record-keeping rules without a government-procured system. Operating software like Flourish does not replace the regulator's choice. It reports into that system or, where none is mandated, serves as the operator's system of record.
What is Tribal Metrc, and how is it different from a state's Metrc?
Tribal Metrc is a Metrc instance administered by a Tribe's regulator rather than a state.
Does a tribal-state compact mean our operation follows state rules?
Usually only for the activity the compact covers. Compacts commonly address sales to state licensees, off-reservation operations, transport, testing, taxation, and data sharing, while activity wholly on tribal land remains under tribal law. Your compact's text and your Tribal Regulatory Agency are the authorities. Flourish supports compacted and hybrid tribal-state deployments, configured to what reports to the Tribe and what reports to the state.
Can Flourish be our system of record if our Tribe hasn't mandated a tracking system?
Yes. Flourish can serve as your seed-to-sale system of record, maintaining plant-to-sale genealogy, transfers, testing, and sales history in one place, and it produces reports for tribal regulators. Mountain Medicine and other tribes use Flourish for traceability reporting back to its Tribe. That record also supports the due diligence banks perform under FinCEN's 2014 guidance.
What operations can Flourish support on tribal lands?
Flourish covers cultivation, manufacturing, distribution and wholesale, and retail point of sale, including vertically integrated tribal enterprises that operate several of these under one regulator. Flourish also supports hemp workflows, and it can be configured to a Tribe's requirements, including special taxes, purchase limits, and turning features on or off.
How do recent federal changes affect tribal cannabis and hemp operators?
Several changes are in motion. In April 2026, DOJ moved FDA-approved and state-licensed medical marijuana to Schedule III, with broader rescheduling still under review; how this applies to tribally licensed programs is a question for your counsel. Separately, the federal hemp definition narrows to a total-THC standard in late 2026, which affects many hemp-derived cannabinoid products. Your Tribe's counsel should interpret these changes for your program.
How long has Flourish worked with tribal operators?
Since 2017. Our first deployment was with the Iipay Nation of Santa Ysabel in Southern California, and we now support tribal operators across the country.
Ready to Scale Your Tribal Nations Operations?
Talk to a Flourish specialist about how we can streamline your compliance and operations.
