A 20-liter bag is a 20-liter bag. At least that is what the label suggests.
But put two coco substrates with the same stated volume next to each other, irrigate them the same way, and they can behave differently. One may stay wet well into the next irrigation cycle. The other may drain quickly and be noticeably lighter a few hours later.
The difference usually has less to do with the number printed on the bag and more to do with what is inside it.
Coco coir is often discussed as though it were one uniform material. It isn’t. The size and proportion of pith, chips and fiber determine much of the pore structure in the root zone, and that structure influences how water and air move through the substrate.
Fine Pith Holds Water Differently
Coco pith is the fine, sponge-like material left after fiber is separated from coconut husk. A pith-heavy substrate contains many relatively small pores.
Those smaller pores tend to retain water more strongly after irrigation. That can be useful where a grower wants a larger moisture reserve between irrigation events, but it also means irrigation must be managed with the physical structure of the substrate in mind.
Adding more irrigation simply because the surface looks dry can leave the lower part of the root zone wetter than expected.
Chips Change the Pore Structure
Husk chips behave differently. Their larger particles create larger spaces within the substrate. Those spaces generally drain more readily and preserve more room for air after irrigation.
This is why growers often use pith-and-chip blends rather than choosing one fraction exclusively.
There isn’t a universal ratio that is right for every crop. A blend that performs well in a shallow grow bag under frequent drip irrigation may be unnecessarily coarse in a taller container irrigated less often.
The useful question is not, “What is the best coco ratio?” It is, “What physical structure works with this container, crop and irrigation strategy?”
Container Shape Matters More Than It Gets Credit For
Even the same substrate can behave differently when the container changes.
Water does not distribute identically in a shallow slab and a tall pot. Container height, width, drainage-hole position and the amount of expanded substrate all influence the balance between wetter and better-aerated zones.
This is one reason copying an irrigation program from another operation can cause trouble. Two growers may both be using coco, but if one is using a shallow slab and the other a deeper container, the root zones are not necessarily behaving the same way.
The plant count per container matters too. More roots eventually change how quickly water is removed from the substrate, so irrigation that worked early in the crop may need adjustment as the root system develops.
Compression and Expansion Can Hide Differences
Compressed coco adds another variable.
Two dry blocks can look nearly identical before hydration. Once expanded, however, differences in particle grading, compression and final volume become much easier to see. This is why expansion volume should be treated as a measurable specification rather than an assumption.
When evaluating a compressed product, hydrate a representative sample completely and look at the material itself. Is the texture uniform? Are there excessive fines? Are the chips within the expected size range? Does the material expand consistently from one sample to another?
For a commercial grower, consistency between batches is usually more valuable than an unusually impressive result from one block.
EC Numbers Need Context
Physical structure isn’t the only specification that can be misleading when viewed in isolation.
Electrical conductivity is a good example. Growers commonly ask for the EC of coco, which is sensible because soluble salts matter. But an EC value without the test method is incomplete information.
A result obtained using a 1:5 extraction should not automatically be compared with a result produced using a different extraction or saturation method. The preparation of the sample and the ratio of substrate to water affect the number being reported.
So instead of asking only, “What is the EC?” ask, “What is the EC, and how was it measured?”
That small question makes supplier comparisons much more meaningful.
Washed and Buffered Are Not the Same Thing
These terms are often used interchangeably, but they describe different processes.
Washing is primarily intended to remove soluble salts from the coco. Buffering goes a step further and deals with the exchange sites naturally present in coir. Calcium and magnesium are commonly introduced during buffering to displace unwanted potassium and sodium held on those sites.
Whether a grower needs buffered material depends on the production system and nutrient program, but the important point is to know what treatment the substrate has received.
“Low EC,” “washed” and “buffered” describe related aspects of a substrate, but they are not three ways of saying the same thing.
What Should a Grower Actually Compare?
When comparing two coco substrates, start with more than price and bag volume. Ask for the particle-size distribution or at least a clear description of the pith, chip and fiber fractions. Confirm the expanded volume rather than relying only on compressed dimensions. Ask for EC together with the test method, and find out whether the material is washed, buffered or both.
Then test the substrate under the irrigation conditions it will experience. A simple side-by-side trial can reveal things a specification sheet cannot. Irrigate equal containers to the same starting point and compare drainage, weight loss and moisture behavior over time. Look at how evenly the material hydrates and how quickly it dries back.
The goal isn’t to find the coco that holds the most water or the coco that drains the fastest.
The goal is to find a root-zone structure that gives the crop enough water while maintaining enough air, and that behaves predictably from one irrigation event and one batch to the next.
Volume tells you how much substrate is in the container.
It doesn’t tell you how that substrate will behave.
Comment here