Most software buying advice assumes you are purchasing something interchangeable. Grower software is not. The constraint that actually binds your operation — square feet of bench, a crop that finishes when it finishes, a truck that leaves at four — is invisible to software designed for boxes on a shelf.
What follows is the set of questions that reliably separate a system that will work in your yard from one that will demo beautifully and then need a spreadsheet beside it. Use them on every vendor you talk to, including us.
How it is delivered
1. Is it genuinely browser-based, or is there a server? This sounds like an IT detail and it is not. A system that needs a server on your site quietly hands you a list of jobs: buying and replacing hardware, applying updates, taking backups and testing that they restore, and giving anyone off-site a VPN or remote desktop. Ask where the software runs. Ask it plainly, because "cloud-enabled" and "web-accessible" are phrases that can survive a local server sitting in a cupboard.
2. What happens when it goes down in April? Not whether it goes down — everything does. Who you call, how fast they answer, and whether that is in the contract or in a brochure.
3. How do people in the field get to it? Your merchandiser is standing in a store two hours away. If the answer involves installing an app, ask who keeps it updated across every phone your team owns, what happens to the person hired on Monday, and whether the app can do everything the office can or only some of it.
4. How do upgrades happen? Continuously, or as a project you schedule and pay for? If the second, ask what the last one cost somebody.
The demo itself
5. "Can you show me that today, on data like mine?" This is the highest-value question in this guide and almost nobody asks it. Vendor websites are written in the present tense about things that are partly built. There is nothing sinister in that — release cycles are short and roadmaps move — but it means a feature page is a claim, not evidence.
So for every capability that matters to your decision, ask to see it working. Not a slide, not a video, not a sandbox with someone else’s tidy products in it. If the answer is "that is coming", that is a perfectly reasonable answer — write it down as a roadmap item and price the deal without it.
6. What does this do badly? A vendor who cannot name a weakness has either not thought about it or is not going to tell you. The useful follow-up is what kind of operation they are a poor fit for. Anyone who claims to fit everyone fits nobody in particular.
Whether it understands growing
7. Does it treat space as a real constraint? Ask whether a zone can carry a square-footage capacity, whether products carry their own footprint, and what the system does when a zone is over capacity. If space is a note in a comment field, the software was built for a warehouse and adapted afterwards.
8. What does availability mean here? Live goods become available on a date, not on receipt. Ask whether a ready date from production flows into what your sales team can sell, and what a customer sees when something is out of stock — "unavailable", or the week the next lot is expected.
9. Can it handle combination goods? A mixed container is one sellable item made of several crops. Ask whether the system understands that relationship or whether you will be faking it with a note.
Whether it understands the cost side
10. Does it pack racks and carts, and does it tell you before the truck is loaded? Freight is one of the few costs in this business you can attack with arithmetic — a three-quarters-full rack costs the same to ship as a full one. Ask whether packing is calculated automatically, and specifically whether fill is visible while the order is still being taken. After the fact it is a report. During the order it is a sales conversation.
11. Where are your racks? Returnable equipment is a capital cost that tends to get written off as a cost of doing business, largely because nobody has the numbers to argue otherwise. Ask whether containers are tracked by customer and location.
If you sell into retail programs
12. Does it invoice from scans or from shipments? For pay-by-scan and vendor-managed programs this is the whole question. If you own the inventory until it rings up at the register, billing from what shipped is the wrong number. Ask to see sell-through compared against what was delivered, per location — that gap is what tells you whether a program is working or whether you are financing somebody else’s shrink.
13. Is EDI native or bolted on? Ask which documents are handled — purchase orders, remittance advice, credit and debit adjustments — and whether there is an audit trail you can search when a partner insists they sent something. "We can integrate with an EDI provider" is a different product, with a second vendor and a second invoice.
On AI, ask a narrower question than you expect
14. If I ask it the same question next Tuesday, do I get the same number? Every vendor in this market now has an AI story, and the interesting question is not whether one exists. It is whether the output is repeatable and whether anyone can audit it.
A model that re-interprets your question on each run is useful for exploring and dangerous as a number you plan against. Ask whether a saved report still involves the model, or whether the question was turned into a query once and now runs deterministically. Ask what data the assistant can change — read-only should mean the permission does not exist, not that it has been asked nicely.
And be careful about forecasting claims specifically. Ask what the forecast is trained on, how it performed against last season, and what a person is expected to do when it is wrong. A confident number with no accountability behind it is worse than no number.
The commercial questions people forget
Ask what is actually in the contract as opposed to on the website: uptime, response time, and — the one nobody asks until renewal — how price increases are governed. A subscription with no stated escalation is a subscription that can be repriced when you are most dependent on it.
Ask what onboarding includes, who does the data migration, and how long support stays intensive. And ask about references — but ask for a grower like you rather than a logo list. Plenty of vendors in this industry cannot publish client names, for the good reason that their clients compete with each other; a private, arranged conversation is worth more than a wall of logos anyway.
One last thing
Notice how few of these are feature questions. Almost every one is about whether a claim is real, whether a cost is visible, and whether the fit survives contact with your actual season. That is not an accident — feature lists converge, and the differences that matter show up in how a vendor answers being asked a hard question.
We wrote this guide because these are the questions we would want asked of us. If you would like to put them to us directly, that is what a first conversation is for.