LEAF TRADE // IMPLEMENTATION GUIDANCE
Product Naming & Structure Recommendations
How to name products and structure categories in Leaf Trade -- and why each choice affects your storefront, reporting, and inventory accuracy.
Recommendation: One Product Per Package Size
| Create a separate Leaf Trade product for every package size you sell. If you offer Brand X / Strain X in 3.5g, 7g, 14g, and 28g, each should be its own product SKU. |
This does not change how inventory is tested or tracked. Batches in Leaf Trade are inherent -- every piece of inventory ties to a batch, which acts as your testing lot. Multiple products can stack within one batch and share the same test results, so sizes tested together can still live under one batch. Separating them at the product level is what matters -- here is why:
1 | Pricing & case configuration are accurate. Default case size and unit price live at the product level. Different sizes almost always sell at different price points and case configs -- separate products capture that without workarounds. |
2 | Your storefront looks right. Images live at the product level. Separate products let buyers see eighth jars distinctly from quarter bags -- the packaging they are actually ordering. |
3 | Weight-based inventory converts correctly. On import, Leaf Trade reads package size from the product name to convert weight-based inventory into units. One size per product keeps that conversion reliable. |
4 | Batch queue automations run reliably. FIFO batch queue automations function cleanly when each product maps to a single package size -- less manual oversight for your team. |
5 | Integrations and mappings stay clean. Separate products mirror how Seed-to-Sale systems are structured, making S2S integrations and cross-system product mappings far simpler to maintain. |
6 | Sales reporting is precise. Product-level reporting only shows how each size performs if each size is its own product. Collapsed SKUs hide which package sizes actually drive revenue. |
Package Size, Defined
| DEFINITION Package size is the total weight or content of a single unit -- 3.5g for an eighth, 100mg THC for an edible. Leaf Trade reads the last size and unit listed in a product name. On import, our integration first checks your Seed-to-Sale system for the package size; if that field is not populated, we parse it from the name. This is why one size per product -- with the size in the name -- keeps parsing and conversion accurate. |
Recommended Naming Format
Most operators use a consistent, predictable format. The package size belongs at the end of the name -- that is the position Leaf Trade reads for parsing and conversion.
Operator Type | Recommended Format |
Standard | Strain – Product Type – Package Size |
Multi-Brand | Brand – Strain – Product Type – Package Size |
Edibles / CPGs | Standard format, often plus flavor, phenotype, or cannabinoid ratio for customer clarity |
Category Structure
Categories in Leaf Trade are fully customizable with unlimited sub-levels. One rule should guide how you build them, because it directly controls what buyers can find:
| Only the two category levels directly below Cannabis / Non-Cannabis are filterable on the storefront and marketplace. |
Levels one and two become buyer-facing filters and are searchable across the entire Leaf Trade marketplace in your market. Anything deeper still exists in Leaf Trade -- it just will not surface as a buyer-facing filter.
Category Hierarchy | Filterable on Storefront? |
Cannabis › Flower | ✓ Yes -- buyer-facing filter |
Cannabis › Flower › Eighths | ✓ Yes -- buyer-facing filter |
Cannabis › Flower › Eighths › Brand X Premium Eighths | ✗ No -- exists, but not buyer-facing |
Two more capabilities worth knowing as you plan your structure:
A product can hold more than one category. You are not limited to a single classification -- assign both buyer-facing and internal categories to the same product.
Every sub-category has a “hide on storefront” toggle. Build internal-only categorizations for reporting or segmentation without ever exposing them to buyers.
| Takeaway: Put the categories you want buyers to filter by in the first two levels. Use deeper levels -- with the hide toggle as needed -- for internal organization, reporting, and segmentation. |
A Question for Your Team
| DECISION NEEDED: MED VS. REC PRODUCT NAMING Will your Med and Rec products share the same names, or will you maintain separate product SKUs for each? Leaf Trade can distinguish Med from Rec sales at the product level or at the license / stock location level -- so either approach is fully supported. Because this choice shapes how you name and structure the entire catalog, it is worth aligning internally before the build begins. |
Why This Matters
Naming and structure decisions are made once, early -- and everything downstream inherits them. A catalog built on these conventions gives your team accurate product-level reporting, reliable inventory conversion, clean integrations, and a storefront that presents the way buyers expect -- making these few decisions the highest-leverage investment in a healthy catalog.