Short desk guides — then a 15-minute walk. Pick who you are, open one note, book a demo. The lot stays itself. Sold is not a bill.
Not sure where to begin? Pick your seat.
In this note you will check
Latest note
Twenty questions for any tea software vendor. If they fail the Sold-is-not-a-bill test, stop the meeting.
Or browse by topic
Fifteen minutes is enough: Sale 18 for the billed path, Sale 20 for the live auction room. No slide deck.
A sale sheet import should write Sold, Unsold, or Withdrawn on the real lot — it should never mint a tax invoice or a nickname invoice lot.
A seller portal gives Aruna its own lots and own payable — and hides Kamlang — so the estate can check the desk without learning a second system.
Tally books what already happened. TeaLedger is where the lot, the auction result, the buyer invoice, and the garden payable are born.
A buyer portal shows Maharastra the published catalogue, the open lot to bid, and own invoices — never Aruna’s payable or another buyer’s paper.
Tea invoice software prints the buyer’s tax paper from a sold lot — HSN, both GSTINs, and CGST/SGST or IGST — it is not statutory accounts and not Tally.
TeaLedger is the tea house file: lot, catalogue, auction result, buyer bill, garden payout — one login door, two money paths.
Settlement software builds one payable per garden from sold lots: quantity times auction price, brokerage off the billing company, net to the estate.
Garden software for a broker desk starts by splitting the estate from the billing company — Aruna grew the tea; another name may sit on the invoice.
Catalogue software is the published offer list — Aruna and Maharastra should see the same lots, not two versions of a midnight Excel.
Tea auction software runs the live room and writes Sold, Unsold, or Withdrawn as the auction result — the buyer bill is a later house click.
Same product, different key. Admin runs the house. Auction staff run the room. Gardens and buyers see only their rows.
Before you print Maharastra’s bill for lot 1810, check GSTIN, HSN, state split, and that the invoice points at the sold lot — not at a typed alias.
A tea house needs seats, not a shared password: auction desk, accounts, management, garden, and buyer each hide a different book.
Assam estates need their lots and their payable — not the broker’s entire book. Garden is not company, and Kamlang must not see Aruna.
Excel can store a rate; it cannot lock a result after an order, hide Kamlang from Aruna, or refuse a bill when Sold is confirmed.
A garden payable that is typed from memory, netted on the buyer invoice, or keyed on lot number alone will never match the sale sheet.
Ahmedabad buyers live on many gardens and a tight credit story. The software must show own bills, own bids, and a limit that can refuse a new invoice.
Buy auction software only after you have seen Sold write a result, not a bill, and after a garden can watch its own lot without bidding.
Computerising a tea desk fails when the house copies Excel habits into software: one login, one ledger, and Sold that prints a bill.
Siliguri is a logistics city first. The software must keep the dispatched lot as the same tea that is later sold, billed, and settled.
The catalogue offers tea; the invoice bills tea. Treating those as two typed numbers is how lot 1810 becomes an argument.
Choose the file that can run a GTAC or CTTA week without renaming lots at invoice time or merging Aruna with the billing company.
The words a tea house uses at the desk — and the mistakes that happen when software uses them as synonyms.
Kolkata houses already know CTTA precision. The software question is whether the sale result and the GST invoice are still two different papers.
If the product cannot keep one lot identity, two money paths, and a Sold that is not a bill, the rest of the feature list is decoration.
Broker “ERP” that merges the sale, the buyer invoice, and the garden settlement into one document will fight the desk the first week a lot is withdrawn.
GTAC volume does not forgive a typed lot number. Guwahati houses need a live room, a result that is not a bill, and a garden payable that matches the sale.
Excel will hold a sale sheet; it will not keep lot 1810 as the same tea on the catalogue, the auction result, the buyer bill, and the garden payable.
A tea house in India needs one file for the lot, the catalogue, the auction result, the buyer bill, and the garden payable — not five sheets that argue at month-end.