Overview
Cannabis inventory rarely sits in the form it was harvested in. Bulk flower gets split into individual jars. Bulk material gets rolled into pre-rolls or processed into edibles. Trim becomes concentrate. Each step changes the inventory record and adds new entries that need to be tracked back to their source.
Cloudbox sublotting and conversions handle that workflow. When you split or convert inventory, the system records the parent-child relationship, updates the weights in real time, and pushes the new inventory into both your operational system and the state compliance system automatically. The lineage stays intact from harvest through final sale.
What Problem It Solves
Bulk-to-package conversions are one of the most error-prone and frustrating parts of cannabis operations.
The first problem is volume. Most other inventory apps don't let you sublot into multiple new batches in a single step. You have to click through each new sublot individually, one entry at a time. The few apps that do allow batch sublotting often gate it behind a steep premium tier, charging extra for what should be a basic capability. For an operator running daily packaging or production, those single-step sublots add up to hours of clicking that produce nothing the operation actually needs.
The second problem is the compliance link. Every sublot needs a new state tracking ID from METRC, BioTrack, or whichever system applies, and that ID has to be tied back to the right parent state ID so the lineage is reflected correctly in the state record. Operators handle that manually too: type the new entry, log the parent ID, request a new child ID from the state system, then type that back in. Get any piece of it wrong and the entire batch's compliance can be questioned.
Conversions to other product forms add another layer. Turning bulk flower into pre-rolls means tracking input weight, output count, conversion yield, waste, and lineage from a parent batch to multiple child packages. The state system expects all of that documented correctly. Operators routinely lose track of one of those threads, and the discrepancy shows up in an audit.
Cloudbox automates the sublotting and conversion record-keeping, generates the new state tracking IDs in one operation, and removes the per-sublot click tax that other systems charge for.
How It Works
Sublotting in Cloudbox is a software workflow, not a hardware one. There are no scales or containers involved in the sublot itself. The whole thing happens in the Cloudbox web app, in a few clicks.
The flow looks like this. Open the web app and pull up the SKU or batch you want to sublot. Click the Sublot button. Tell Cloudbox how many new sublots you want to create from the parent batch.
From there, Cloudbox does the math.
In unit mode, the system divides the parent evenly across the number of new sublots you specified. A 200-unit parent split into 10 sublots becomes 10 new sublots of 20 units each.
In weight mode, the system divides the parent into packages of the weight you set. A 100-gram parent sublotted into 5-gram packages becomes 10 new sublotted batches of 5 grams each.
Once the new sublots are defined, Cloudbox syncs the operation to your state compliance system. METRC, BioTrack, or whichever system applies, returns a new state tracking ID for each child sublot. Cloudbox writes those IDs back into your inventory record, so every new sublot has its compliance ID attached from the moment it is created. The parent batch updates with its new lower remaining quantity. The lineage is recorded on both sides.
The conversion workflow follows the same logic but accounts for transformation. Turning bulk flower into pre-rolls, for example, has an input weight, an output count, and a conversion ratio. Cloudbox tracks all three. The parent batch records how much input was consumed, the child product records how many units were produced, and the conversion yield (and any waste) gets logged for later analysis.
After the new sublots exist as records in the system with their state tracking IDs assigned, you can optionally pair any of them with a physical container at any point. Once a container is linked to a sublot, scale-based inventory tracking takes over from there, and the new batch behaves like any other Cloudbox-tracked SKU.
How Cloudbox Does It Better
Other systems treat sublotting as a per-record manual task. The team builds each sublot one click at a time, types in the new quantities, and reconciles the state compliance ID for each child by hand. Operators running daily packaging end up paying for the privilege of doing that work, either in labor hours or in premium subscription tiers.
Cloudbox handles the entire sublot, including the state compliance IDs, in a single operation. You tell the system how many sublots and whether to split by units or by weight. Cloudbox does the math, requests the new state tracking IDs from METRC or BioTrack, writes everything back into your inventory, and updates the parent batch. The lineage is correct by default, because the system was the one doing the work.
Create dozens of new sublots from a parent batch in a single operation. No clicking through one entry at a time, no premium tier gating the feature. Tell Cloudbox how many sublots you want and whether to split by units or by weight, and the system handles the split.
Bulk-to-finished conversions log input weight, output count, yield percentage, and any waste, automatically. Operators get a real picture of conversion efficiency for every batch.
Every new sublot gets its own state tracking ID returned from METRC or BioTrack, written back into Cloudbox automatically and tied to the right parent ID. No manual ID lookup, no copy-paste from the state system.
Pull up any package and Cloudbox traces it back to the parent batch, the harvest, and the cultivation source. Auditors get the full chain on demand.
Lineage Without the Paperwork
Cannabis operators are required to track the lineage of every product from cultivation through sale. The compliance burden is real, but most operations meet it with a combination of spreadsheets, paper, and institutional memory. The lineage is technically there, but it takes effort to reconstruct.
Cloudbox sublotting and conversions make the lineage automatic. Every time material moves, splits, or transforms, the system records the relationship as part of doing the work. The team isn't building documentation. The documentation is built by the act of operating.
That changes the compliance posture from reactive to default. Audits surface no surprises because the data was always going to be correct. Recalls and adverse-event responses are fast because the lineage is queryable. And the team gets back the time they used to spend reconstructing the chain after the fact.