The Core Loop — Stored, Then Applied

 Harvests

As you grow, all the labor and overhead on a cultivation batch builds up on that batch. When you take a harvest, the batch's cost is applied to it — the harvest becomes the stored cost of everything you grew.

Good to Know

A harvest links to one cultivation batch. If several harvests pull from the same batch, that batch's cost splits across them by total plant weight.

 Production Outputs

When a manufacturing batch produces something — a distillate run, a batch of edibles, packaged units — the batch's accumulated cost is stored on that production output. It captures everything that went into making it.

Good to Know

You may still see these called yields in some places. It's the same idea: the costed result a batch hands off to whatever comes next.

 Vault Yields

Right from the vault, you can turn tags into a costed output without building a full workflow. Multi-select your tags, quick-create a batch, and choose yield — Hashio gathers the parent tags and stores cost on the new output.

Good to Know

Great for combining or repackaging tags after the fact. Choose material instead when the result is an input, not a finished output.

 Inheriting From a Parent

When you break a tag off another tag, the new child tag inherits its cost from that single parent — carried over on the same basis the parent was measured in (by weight, by volume, or by each).

The Clean Case

One parent, one child: cost flows over automatically with no extra steps. This is the everyday path for splitting and breaking down inventory.

 The Multi-Source Rule

When a tag is built from two or more parents, Hashio now pulls the cost straight from those parent tags. Convert the items in Hashio and — as long as each source carries a cost per unit — the Convert Items screen shows what every source will contribute to the new package.

How It Shows Up

Each source line reads “will contribute $X to target package,” and Hashio rolls those amounts into the new tag's cost. You can also quick-create a batch with the sources as production inputs and the result as the output. It still starts at $0 if tags are combined outside Hashio, or a parent has no cost yet.

 The Cost Cascade

When a stored cost changes, you don't re-do anything. Hashio cascades the update down to every child tag and downstream batch automatically — the new number flows through the whole chain.

Works Back in Time, Too

Add a harvest or batch after the fact and its cost still flows down to everything that came from it — no manual recalculation needed.

 Splits Share Cost by Weight

When one thing splits into several, cost divides proportionally by weight. Split an 800 lb / $800 batch and the pieces carry their share:

300 lb → $300  ·  500 lb → $500

The same logic shares one batch's cost across multiple harvests, and one parent's cost across multiple outputs — always by weight.

A Quick Note on Wording

Costing Is Where Most Questions Start

If a number isn't flowing the way you expect, reach out to your Hashio Customer Success contact. We'll trace it back to where the cost is stored and walk the path with you — this is exactly the stuff we love to untangle.