ET Grow Quarterly: Q3 2026

Software gets better in two ways. Occasionally something arrives that changes how a job gets done. Far more often, a hundred small frictions get filed down until a process that used to take an afternoon takes twenty minutes, and nobody can quite point to when it happened.

The last six months of ET Grow development have been mostly the second kind, with a few of the first mixed in. Close to forty improvements have gone out across the platform. Some came from our own roadmap. A lot more came from a grower mentioning something in passing on a support call, or a warehouse manager showing us the spreadsheet they’d built to work around a gap.

Here’s the full picture, organized the way you use the system.


Across the Platform

Some of the most useful work this cycle wasn’t tied to any single module. It was about who can see what, how information leaves the system, and how much setup your team rebuilds from scratch each morning. These are the changes that touch every user regardless of which part of ET Grow they spend their day in.

Individually several of them are small. Taken together they remove a surprising amount of daily friction: fewer trips outside the system to send a document, fewer report filters reconstructed from memory, and fewer pieces of information you track that have nowhere sensible to live.


Grow

The Grow App received a round of general workflow improvements, with the most substantial work going into the inventory view screens. Moving product to and from split and merged inventory lots is now considerably more efficient. Splitting and merging lots is a normal part of the production life cycle, plants get divided, consolidated, moved and regraded.  However, tracking that cleanly has always been one of the harder things to ask of a system. The new views make the movement itself faster and make lot history easier to follow after the fact.


Buy

Purchasing is where two sets of numbers have to agree: what you ordered, and what actually arrived and got invoiced. When those live in separate places, the gap usually surfaces at month end, discovered by whoever is reconciling payables against receiving paperwork that may or may not match.

Three additions this cycle close that gap from opposite directions. One works on the paperwork side, tying bills back to the purchase orders that created them along with the ability track debits. The other works on the physical side, so product arrives already identified the way your warehouse expects. Each are aimed squarely at operations buying in significant volume.


Sell

The sales side saw more activity than any other area over the last six months, and the theme running through it is friction removal rather than headline capability. Most of these changes address places where your team had quietly learned to work around the system: a screen that had never been modernized, a customer structure the system couldn’t represent, a field that let bad data through.

These features add up to fewer moments where someone has to remember an exception, and fewer cases where a new hire does something reasonable and gets a result nobody expected.


Ship

Fulfillment is where mistakes become expensive. An error in a sales order is a phone call. An error in what physically leaves the yard is a credit, a redelivery, and a customer who now checks every order that arrives. The cost of getting it wrong is why this was the largest area of investment this cycle.

The work split along two lines. The first is visibility: making it possible to see what was required, what was allocated, and what actually shipped, all in one place. The second is the tools themselves, putting better scanning and fulfillment workflows in the hands of the people on the floor who are doing the picking and loading.


Merchandise

Merchandising programs generate a steady stream of reporting obligations. What’s on hand, what shrank, what was marked down, delivered on someone else’s schedule and formatted to someone else’s specification. It is work that recurs every week, produces no insight for the person doing it, and quietly consumes hours that nobody has budgeted.

Most of this cycle’s Merchandise work was aimed at improving how the data collected in the field can be shared with other systems to support data based decision making.  This along alongside improvements for merchandisers who service more than one operation.


Finance

Accounting work has a way of accumulating small exceptions. The payment that arrived before the invoice existed. The journal entry that needs backing out. The transaction that arrived in an order the system didn’t anticipate.

Individually each one is minor and takes a few minutes to sort out. Collectively they become the pile of manual cleanup that someone works through at month end, every month, forever. Both improvements this cycle target that pile directly.

Reconcile Receivables

Payments don’t always arrive in the order accounting systems expect. Sometimes a customer pays before the invoice exists. A new reconcile option runs matching logic to pair those early payments with invoices once they’re created, rather than leaving unapplied payments for someone to chase down at month end.

Voiding Journal Entries

Improvements to the void action on journal entries, for more predictable behavior. This includes improvements to voiding common transactions such as creating invoices and payments.


What We’re Building Next

Looking ahead at what we’re building next, and the work currently underway:


Behind the Scenes: How We’re Building

We’re actively using the latest AI-based development tools to accelerate work on the platform.

At the moment, the biggest target for that effort is query optimization: making the system faster on the screens and reports you use most.

It’s less visible than a new feature. It’s also the improvement you feel every single day, on every screen, and it compounds as your data grows. We think that’s the right place to spend the advantage.


Now It’s YOUR Turn… Tell Us What’s Next!

A substantial share of what’s on this list started as an offhand comment from someone using ET Grow. Not a formal feature request — just someone describing a workaround they’d built, or an afternoon they’d lost to something that should have taken ten minutes. Those conversations are the best input we get.


If something in your operation would be easier with a change on our end, we’d like to hear about it.

Feedback Request

"*" indicates required fields

Name*
This field is for validation purposes and should be left unchanged.