The corrections nobody plans for.
Every elevator has a handful of these every fall, and they are almost never dramatic:
- A load closed under the wrong customer — two farms with the same last name, or the wrong name picked off a list at 9 p.m.
- A load closed twice, because the same scale ticket got entered by two people during a rush.
- A number in the office that is not the number in the scale house, and no memory of who changed which.
None of these are unusual. They are just harvest.
Why “just fix it” is harder than it sounds.
The trouble is that a closed load is not one number. It is bushels sitting on a customer’s balance, a drying charge folded into an invoice that covers other loads too, and storage months accruing from that delivery date forward. Pull the wrong thread and you take all of it with you.
- Deleting is too blunt. The drying charge for one load usually lives on an invoice shared with a dozen other loads. Delete the invoice to fix one load and you have erased eleven correct charges.
- A correction can move grain into a different month. Storage accrues from the delivery date. Fix a load carelessly and you have quietly rewritten what the customer owes you for storage.
- More than one person touches the books. Scale house terminal, office computer, a phone in the pickup. When two of them change the same record, one edit wins and nobody ever sees the other one.
The books have to be correctable, and they have to be trustworthy. A lot of software makes you pick one.
Reopening a closed delivery.
Reopening is off by default. You turn it on in Site Config, and the switch says what it is for: emergency corrections, not everyday work. Leave it off and closed deliveries cannot be reopened or deleted by anybody, which is how most sites should run.
With it on, a closed delivery gets a reopen button on the customer’s page. Before anything happens, Horizon Grain tells you what it will cost you, in your own numbers: “While reopened, 1,842.50 bushels of corn come off Johnson Farms’ balance and the drying charge for this delivery is removed. Closing it again puts both back.” It also reminds you to recalculate storage invoices for the months since that delivery, because that is the part people forget.
Some deliveries should not be reopened at all — the bushels are already sold, the load is tagged to a contract, it was a spot sale, it is split between owners, or its drying invoice has been paid. In those cases you get the reason up front and no button, rather than a click that fails after the fact.
When it does reopen, the load goes back to the scale page where the normal edit, close, and delete flows apply. The drying charge is subtracted from its invoice, not deleted along with everyone else’s. Close it again and the original delivery date is preserved — a correction should not silently move a load into a different storage month.
Who changed that, and when.
There is a new Activity page: a running list of everything that has happened at your site, newest first, grouped under Today, Yesterday, and then by day. Each line reads in plain English — 3:41 PM edited Load #2510 — Johnson Farms — and the record is a link, so you go straight to it. Every line is tagged with where it came from: This computer, Website, Terminal A3F1 for another machine at the site, or the email address of whoever logged in. On edits, the fields that moved are shown right underneath, old value to new.
If two machines change the same record before they sync — the office edits a moisture reading while the scale house edits the same load — a Needs review panel appears at the top of the page, with a count beside Activity in the menu. It shows the two versions side by side, field by field: this computer’s value and the other machine’s. Open the record and sort it out, or keep this computer’s values in one click.
That is the piece we think matters most. Every multi-machine system has to resolve these. Most resolve them silently, and you find out in December.
How to use it: a quick walkthrough.
- Leave reopening off until you need it. Site Config → “Allow reopening closed deliveries.” Turn it on for the correction, turn it back off after.
- Read the warning before you confirm. It tells you the bushels coming off the balance and the drying charge coming off the invoice, for that specific load.
- Fix the load and close it again. It goes back to the scale page, where the normal edit and close flows apply. The delivery date does not move.
- Recalculate storage for the affected months if the delivery stayed open or was deleted.
- Check Activity at the end of a busy day. If a count is showing next to Activity, two machines disagree about something and it needs a decision from you.
Why this matters at small elevators.
At a two- or three-person elevator, the person who finds the mistake in November is the same person running the scale. There is no separate desk to hand it to, and the fix has to happen between trucks — which is exactly when you are least able to check what else it touched.
Paper had one real advantage: you could always see the correction, and you could see who made it. So none of this happens quietly — reopening a delivery, editing it, closing it again all land on the Activity page with the time and the machine they came from.
Software should not be worse than a pen. Corrections should be possible, they should be visible, and they should not break anything you were not looking at.
Related reading: the haul that ships before the contract does.