Inventory software has been a solved problem since roughly 1985, as long as the thing you are counting is a box. A box has a quantity, a location and a cost. It does not change size, it does not become available next Thursday, and it does not die.
Almost every inventory product a grower will be shown was built on those three assumptions. Live goods break all of them, and the breakage does not show up in a demo — it shows up in April, when the number on the screen and the number in the house have quietly diverged and somebody has already sold the difference.
Three assumptions that do not survive a nursery
The unit is not the constraint. A greenhouse does not run out of plants, it runs out of bench. You can always start more; what you cannot do is put them anywhere. Any system where space is a note in a comment field rather than a number it can reason about will let you plan something physically impossible, and you will find out when the trucks arrive.
Availability is a date, not a yes or no. The honest answer to "do you have four hundred of those" is frequently "not today, but on the eleventh". Software that can only say yes or no forces your sales team to say no to orders you could have filled, which is the most expensive rounding error in the business.
The product changes identity while you own it. Stock grows into a different size, a different price and a different customer. A system that models this as a manual write-off and re-entry will be wrong for the entire period between the plant becoming a #7 and someone remembering to say so.
The count is always wrong. Plan for that instead of denying it.
This is the part vendors avoid and growers already know. The authoritative record of what you have is not a database — it is a block of ground somebody has to walk. Plants die, get moved, get miscounted, get taken for a display and never come back.
So the useful question is not "how do we make the count perfect", it is "how short is the loop between reality and the record". A system that makes counting easy and frequent beats one that makes counting authoritative and annual, every time.
Which means the counting has to happen where the plants are. In GrowerLive, scanning to count, scanning to move stock between zones and receiving against vendor orders all run in a browser on a phone or tablet — so a count happens in the yard rather than on a clipboard that gets keyed in on Friday. There is nothing to install on anyone’s device, which matters more than it sounds when your crew turns over seasonally.
Be specific with vendors on this point. "Mobile" can mean a genuine working screen or a read-only summary that is useless with a scanner in your hand.
Space as a first-class number
If you take one thing into a vendor conversation, take this one, because it is the clearest dividing line between software built for growers and software adapted for them.
Ask whether a zone can carry a real square-footage capacity, whether an item carries its own footprint, and what the system does when someone tries to put more into a full zone. In GrowerLive both of those numbers exist and the overflow behaviour is yours to set — block the placement outright, or allow it and flag it for a manager. Operations genuinely differ on which they want, which is exactly why it should be a setting rather than a decision somebody else made for you.
A system that cannot express capacity will happily let you plan a season that does not fit.
If you run consignment, you have two inventories
The moment you are on a vendor-managed or pay-by-scan program, "what do we have" splits into two questions: what is on your ground, and what is sitting at your customers’ locations. They behave differently, they are counted by different people, and conflating them makes both wrong.
GrowerLive keeps both with separate screens for each, so a sell-through or replenishment conversation starts from recorded numbers rather than from an estimate somebody assembled the night before.
What accurate inventory actually buys you
It is worth being concrete about the return, because "better inventory accuracy" is not a business case on its own. The value is entirely downstream.
The person taking an order sees real on-hand figures and stocking percentages while the customer is still on the phone. Ready dates coming out of production roll into availability, so the answer is a date rather than a no. Rack-fill projections are computed from real quantities, which is what makes "we are two shelves short of a full rack" a sales conversation instead of a freight bill. Every one of those depends on the inventory layer being right, which is why it is worth fixing first and why a system that treats it as an afterthought will disappoint you everywhere else.
What to ask a vendor
- Can a zone carry a square-footage capacity, and can an item carry its own footprint?
- What happens when someone puts stock into a full zone — and can I choose the behaviour?
- Is availability expressible as a date, or only as a quantity on hand?
- Can my crew count and move stock on a phone, in the field, with a scanner?
- Do I need to install anything on their devices, and who keeps it updated?
- How does the system handle stock growing into a different size and price?
- If I run consignment, can I see my inventory and my customers’ separately?
- Where do on-hand figures appear while an order is being taken?
- How do I correct a count, and does the correction leave a trail?
The honest summary
Inventory is the layer everything else stands on, and it is the one most often bought on price because it looks like a commodity. It is not a commodity for growers. The difference between a system that models space, dates and change and one that models quantities is the difference between software that helps you plan a season and software you maintain alongside the spreadsheet where the real plan lives.
If a demo never mentions bench space, you are being shown a warehouse product.