Who it is for
From the plant tag to the manifest out
Written from primary sources and checked against them. As of 2026-09-06. How that is done.
Short answer
Will Bloom work for a cannabis cultivator or processor?
Not yet. The cultivation and production build is in design and the retail build ships first. What is planned is the full chain a licence actually has to record: plant batches and individual tags, movement between rooms, feeding and treatment, harvest and wet weight, drying loss, waste with the state's own reason codes, lab sampling, packaging into saleable units, and the manifest out. It will run on the same regulatory corpus, evidence log and reporting outbox the retail build already uses.
Why this is the same product and not a second one
The events a grower reports and the events a shop reports are the same kind of event: a quantity moved, a quantity destroyed, a package created, a test recorded, a transfer sent. The retail build already has the machinery that makes those defensible, an append only evidence log that records which version of which rule applied, and a reporting outbox with idempotency keys so a retry cannot file something twice.
Adding cultivation is adding the earlier half of a chain that already has its later half, and the value is that the chain is queryable end to end. A retailer holding a recalled package can be traced back to the batch, and a cultivator can see where a batch went.
What is being designed, specifically
Mother stock and clones. Batch creation and individual plant tags where a state requires them. Movement between veg and flower rooms as recorded events rather than as a status field. Feeding, treatment and pest applications with the product used, because that is what a state asks about after a failed test. Harvest with wet weight, then drying and curing loss, which is where reconciliation usually breaks. Trim and waste with reason codes drawn from the state's own vocabulary. Lab sampling and results. Packaging into saleable units with the tags the state issues. The transfer manifest out.
What we will not claim
No dates, because a date given now would be a guess. No screenshots, because there is nothing running to photograph. When there is, it will be photographed against a live demo the same way every other screen on this site was, and you will be able to open it yourself.
Questions people ask next
- Is the cultivation build available now?
- No. It is in design and the retail build ships first. This page describes what is being built and what it will share with the rest of the platform, so an operator can judge whether it is worth waiting for. Nothing here is available to buy today.
- Why build cultivation on the same platform as retail?
- Because it is one chain. A plant batch becomes a harvest, becomes a package, becomes a line on a receipt, becomes a row in a state report. Splitting that across two systems is what creates the reconciliation work that both sides currently do by hand.
- Will it report to track and trace?
- It is being built to. The outbox, the idempotency keys and the evidence log that the retail build already uses are the same machinery a cultivation event needs, which is a large part of why the two belong together.
- What about waste and destruction records?
- Those are among the events regulators examine most closely, so they are first class rather than a note field: quantity, reason code from the state's own vocabulary, who witnessed it where a rule requires a witness, and the evidence row that proves when it was recorded.
- Can I use it if I only cultivate and sell wholesale?
- That is the intent. The manifest out to a retailer is the boundary of the cultivation build, and a licensee who never runs a register should not have to carry one.