Who it is for
Several licences, one account, no shared rulebook
Written from primary sources and checked against them. As of 2026-09-06. How that is done.
Short answer
How does Bloom handle a multi location cannabis operator?
Bloom models an operator as an organization holding legal entities, which hold licences, which hold facilities. Every regulated record carries the licence it belongs to, and each licence loads the rule pack for its own jurisdiction. So two stores in two states enforce two different rulebooks under one login, and neither can reach the other's inventory.
Why the rules are per licence and not per account
A setting that applies to your whole account is a setting that is wrong in at least one of your states. Bloom attaches the rule pack to the licence, so a store in Michigan and a store in Illinois each price, cap and refuse according to their own law without anyone remembering to configure it.
The same applies to tax. A local option rate belongs to the locality the facility sits in, not to the company, so opening a second store in a city with its own rate does not require touching the first one.
Isolation is enforced below the application
Every regulated table carries a licence, and row level security in the database filters on the licences a caller actually holds. A query that forgets to scope itself returns nothing rather than returning another site's data. That is the difference between isolation as a policy and isolation as a property.
What is honestly missing
Consolidated reporting across sites is being built. Each site runs completely today, and the records are separated correctly, but if the thing you need first is a single screen ranking twelve stores by margin, that is not ready.
Questions people ask next
- Can one login reach all of my stores?
- Yes. A membership can be scoped at the organization, the legal entity, a licence or a single facility, and what someone can reach follows from that rather than from a per screen setting. An owner sees every site; a store manager sees theirs.
- Do stores in different states work in one account?
- Yes, and they are walled from each other by design. Each licence carries its own jurisdiction and loads its own rule pack, and there is no code path that moves inventory across a state line, because interstate transfer is prohibited everywhere.
- Can I move product between my own stores?
- Between facilities under licences in the same state, yes, as a transfer with a manifest, which is what the state expects. The transfer is refused if the two licences are in different jurisdictions.
- Do all my stores have to use the same settings?
- No. Rules come from the jurisdiction, so a store follows its own state and its own locality automatically. What you set centrally is the things that are actually yours: catalogue, pricing policy, roles, and the screen rotation.
- What is not built yet for multiple sites?
- The cross site rollup reporting is the honest gap. The data model separates facilities correctly and each site runs fully today, but the consolidated views across sites are still being built.