Every tea desk has a workbook that “almost works.” It has a sale tab, a result tab, a bill tab, and a garden tab. It works until two people type lot 1810 on the same afternoon, or until Kamlang’s invoice lot is a lookalike of Aruna’s catalogue lot, or until Maharastra’s rate is copied one row down.
Tea trading software is not a prettier grid. It is a refusal to let those four tabs become four truths. Here are nine breaks every broker has already seen, even if the house still calls the file “the system.”
1. The lot number is treated as unique
Two gardens can both send a “20.” Excel’s VLOOKUP does not know sale + garden + lot. The first mismatch is quiet. The garden call is not.
2. Catalogue and invoice share a column
The offer list changes. A lot is withdrawn. Someone still bills from last night’s printout. In a desk file, the catalogue lot and the invoice lot must be the same identity — and billing must be a later step, not a formula that fires when a cell says Sold.
3. Sold is wired to a tax total
A yellow cell that multiplies qty × rate the moment the status flips looks efficient. It is how a house invents a bill before the buyer order exists. The auction result is a result. The invoice is paper. Excel loves collapsing them.
4. Garden and billing company are one name
Aruna grew the tea. Another legal name may be on the GST invoice. Brokerage comes off the billing company. The garden is still who you settle. One master dropdown in Excel cannot hold that split, so someone types the payable by hand and the sale sheet never matches.
5. Buyer money and garden money share a running total
Maharastra pays the house. The house pays Aruna after brokerage. If those land in one “tea ledger” column, you will explain a negative to the estate while the buyer is still within credit. Two paths. Always.
6. There is no seat, only a shared password
The catalogue clerk, the auction desk, accounts, the garden, and the buyer should not see the same rows. Excel shared on a drive — or mailed at 11 p.m. — cannot hide Kamlang’s payable from Aruna, or another buyer’s bill from Maharastra.
7. Importing a sale sheet creates “invoice lots”
A result file is useful. A result file that auto-spawns bills is a fake invoice book. The house must be able to bring in Sold / Unsold / Withdrawn for lot 1810 without raising GST paper. Sale 18 in a walkthrough is exactly that billed path, done on purpose after the result is confirmed.
8. Brokerage is a typed cell, not a rule
Someone remembers 1% this week and 1.25% next week. The garden payable is rebuilt in a hurry. Software should take brokerage from the billing company on the settlement, from the same sold lots, so Aruna’s net is explainable from the auction price.
9. Monday cannot ask “offered with no result”
Excel can filter a column if everyone used the same status words. They do not. A desk file should list lots on the catalogue with no auction result, sold lots with no order, orders with no invoice, and settlements still in draft. That is how a partner stops shouting across the room.
If your workbook needs a legend to explain which tab is true, you do not have a system. You have a negotiation.
Walk Sale 18 with the billed story: 1810 to Maharastra at the auction price, then the order, then the invoice, then Aruna’s settlement. Ask where Excel would have forked. Then decide whether the house wants another workbook — or one lot that does not argue with itself.
Who this note is for
Read this if the house still lives in a shared workbook and someone has started searching “tea trading software vs Excel.” Catalogue clerks, auction staff, and accounts each think their tab is true. Gardens and buyers should not be in that file at all.
How TeaLedger helps
TeaLedger replaces the four-tab argument without asking you to throw away judgement. The lot is a record, not a row you VLOOKUP. Catalogue, auction result, buyer order, GST invoice, and garden payable all point at sale + garden + lot number. Confirming Sold writes the result only. Generate Orders is a later click. Settlement builds Aruna’s payable from the same sold lots, brokerage off the company.
Excel cannot give Aruna and Maharastra different keys. TeaLedger can. Excel cannot refuse a bill when the buyer is over a credit limit. TeaLedger can. Excel cannot list “offered with no result” unless everyone typed the same status word. TeaLedger can, because Sold / Unsold / Withdrawn are fields, not cell colours.
Walk Sale 18 and ask where the old sheet would have forked — usually at invoice time or at the garden net. That is the comparison that matters, not a prettier grid.
What people search — and what the file must show
Search phrases: tea trading software vs Excel, replace Excel tea auction, tea sale sheet software, tea brokerage Excel. If an AI summary says “just export GST from the sheet,” treat it as a warning. The sheet is where lot 1810 becomes two numbers. The software must keep one.