Tracking hay by the stack: the unit your inventory should have used all along

Ask a hay grower what they have and you’ll get an answer in stacks: “two stacks of first cutting by the pivot, a stack of premium alfalfa at the yard, and whatever’s left of that rained-on lot.” Nobody answers in fields, and nobody answers in bales. The stack is how hay people already think — it’s just not how most hay records are kept.

Most tracking schemes pick the wrong unit on one side or the other:

By field is too coarse. A field produces multiple cuttings at different grades, stacked in different places, sold to different buyers. “Field 12: 400 bales” can’t tell you which 120 of them the dairy spoke for.
By bale is too fine. Nobody scans 400 individual bales in a stackyard wind, and no decision ever hinges on bale #217. Systems that demand per-bale data collapse under their own bookkeeping in about a week.

The stack is the Goldilocks unit — big enough to record in ten seconds, specific enough to answer every question that matters.

A stack is a place, a quantity, and a promise

Track hay by the stack and each one carries exactly what you’d want to know standing in front of it:

A GPS pin. The stack is somewhere — a dot on the satellite map, not a description like “past the old corrals.” Anyone you dispatch finds it without a phone call.
A count and a grade. How many bales went up, which cutting, and what your hands said about it. This is the number history gets measured against.
A status. Available, reserved, or sold — spelled out in words. When a buyer commits, the stack flips to reserved and nothing about it can be double-sold by accident.

The pin matters more than it looks. Two stacks off the same field aren’t interchangeable — one got rained on, one didn’t — and the map keeps them honest as different records, which is exactly what the by-field spreadsheet couldn’t do.

The stack is also the unit of selling

Buyers don’t buy fields, and they don’t buy bale #217. They speak for a stack — sometimes two — at a price per ton, and trucks pull loads off it until it’s gone. Stack-level tracking follows that shape all the way through:

Commit a stack to a buyer at an agreed price. Status flips, availability math updates.
Share it. A read-only link shows the buyer their stacks, current counts, with pricing hidden by default — no app, no account, no “what’s left?” calls.
Haul it down. Each departing load is logged at the stack — by a driver who sees where and what, never the price — and the running balance drops toward zero.
Settle it. Every load is already on the ledger, so the settlement statement is a product of the record, not an argument at the kitchen table.

Do this with anything coarser than a stack and the middle two steps dissolve into phone calls.

The ten-second habit

Stack-level tracking lives or dies on capture cost. If recording a stack takes ten minutes at a desk, it happens never; if it takes ten seconds where the stack is, it happens every time: stand at the stack, drop the pin, count, grade, done — and it has to work with zero bars, because stackyards are where cell coverage goes to die. Records queue on the phone and sync when you’re back in range.

That’s the whole system: pin it when you build it, flip it when you sell it, log it as it leaves, and let February’s settlement fall out of the ledger. We built Windrow to make that ten-second habit the entire job — the stack does the remembering.