Fertiliser Orders

Planning the season from a pile of PDFs Before the tool, Jack read every supplier order and sorted it into a "when required" date range. When a load needed to go out, he printed the paper, or took a screenshot of the PDF, and texted the photo through to the driver. That worked when it was one order per client a month, when they actually needed an application. Merchants have started ordering a full season at the start. August, September, October and November can all come through in July. The monthly outlook is what he uses now. He checks an order before it goes out, rather than sorting it into a "when required" pile. Sending it to the driver takes around two minutes instead of five. A little time back. The point is seeing the season month by month, when it all arrives at once.

Now the inbox checks itself. Every few minutes, the system looks for new supplier PDFs, reads out the customer, property, tonnes, product and delivery date, and adds the order to the list. No one retypes anything. Staff open it on their phone, see what's due this month, and assign each order to a truck, trailer section or tractor. When a load's ready, one tap sends the team a summary with the order details and a link to the original PDF, so everyone's working off the same information before the trucks go out.

The load builder mirrors how JK actually loads a truck: truck, three trailer sections, tractor. Rather than a generic "assign to driver" screen, it matches the way the team already works. It also means if a supplier re-sends a corrected order, the system updates the existing one instead of creating a duplicate.