A tea house in India already knows the work. A garden lot arrives, goes on a catalogue, takes an auction price, becomes a buyer invoice, and becomes a garden payable. The pain is not the trade. The pain is that the same lot lives in five places — a register, a catalogue sheet, a sale result file, an invoice book, and a garden list that never quite matches.
Tea brokerage software, if it is worth a desk login, is that one file. It is not a vendor slide about “ERP transformation.” It is the place where lot 1810 is still lot 1810 when Maharastra asks for the bill and when Aruna asks why the payable is short.
What the house actually runs, every sale
Walk a Guwahati or Kolkata week and the sequence is stubborn. Tea is offered. Buyers bid or a result is typed. Someone confirms Sold, Unsold, or Withdrawn. Later — not in the same breath — accounts raise paper. Later still, the garden is settled after brokerage. If any of those steps share a cell in Excel, the house will spend Monday explaining two stories about the same chest.
Indian tea brokerage adds three facts that generic trading tools ignore. First, the catalogue lot is not the invoice lot: the offer list can change, a lot can be withdrawn, and billing is a later decision. Second, the garden is not the company: Aruna may grow the tea while another billing name sits on GST paper. Third, the buyer money path and the garden money path must never be one running total.
The auction result is confirmed first. The bill is raised when the house is ready. Those are two clicks on purpose.
What a tea house needs on day one
Start with identity, not with a dashboard. A lot needs a sale, a garden, a lot number, a grade, packages, and a net weight. Two gardens can both have a “20.” If the software keys only on the typed number, Kamlang’s tea will land on Aruna’s settlement the first busy Thursday.
- One lot identity from arrival through settlement — catalogue, auction result, buyer order, invoice, and garden payable all point at the same tea.
- A published catalogue that gardens and buyers can see, not a draft Excel mailed at midnight.
- An auction desk that writes Sold / Unsold / Withdrawn as the auction result only.
- A billed path: generate the buyer order, then the tax invoice with HSN and GSTIN, then a garden settlement after brokerage.
- Logins that shrink. Aruna sees Aruna. Maharastra sees Maharastra. Accounts do not need the live room. The auction desk does not need to post GST.
Sale 18 in a serious walkthrough is the billed example — lot 1810 sold to Maharastra, invoice and settlement already in the story. Sale 20 is the live auction room — lots 2010 Aruna, 2011 Kamlang, 2012 Aruna, published and unlocked. A house that cannot show both paths is selling a catalogue printer or an accounts add-on, not a brokerage file.
What you can leave to the accounts package
TeaLedger is the brokerage file. It is not Tally and it does not pretend to be statutory books. The accounts seat still needs a place for ledgers, returns, and the CA’s closing. What the desk must stop doing in a workbook is inventing a second lot number at invoice time, or netting a garden payable by typing brokerage into a yellow cell.
When a buyer in another state lifts 1810, the invoice must know seller GSTIN, buyer GSTIN, tea HSN, and whether the tax is CGST/SGST or IGST. When Aruna is settled, gross is quantity × auction price, brokerage comes off the billing company, and net is what the estate should receive. Those two papers can be handed to accounts. They should not be re-typed from a sale sheet.
How to judge a product in fifteen minutes
Ask to sign in as the auction desk, then as accounts, then as Aruna, then as Maharastra. If every seat sees the same menu, the product is a single-user workbook with passwords. Open the auction room on a clean sale. Confirm Sold. Look at invoices. If a bill appeared, walk away. Generate the order, then the invoice, on purpose. Open the garden settlement. Confirm Aruna cannot see Kamlang’s payable.
That is what a tea house in India actually needs: one lot, two money paths, four honest seats, and no story in which marking the auction result prints a tax invoice. The rest — bank matching, statements, Monday reports of offered-with-no-result — is how the file stays honest after the sitting.
Who this note is for
This note is for a Guwahati, Kolkata, Siliguri, or Assam tea house that is tired of five workbooks and is typing “tea brokerage software India” because the partner asked for one login. It is also for a buyer firm or an estate that wants to know whether the broker’s file can hide the other garden and the other merchant. If you run Tally already, stay — this is the operations file that should feed the books, not replace them.
How TeaLedger helps
TeaLedger is tea brokerage software built for that Indian week. A garden lot is raised with sale, garden, lot number, grade, packages, and weight. The catalogue publishes the same identity. The auction desk — live on Sale 20 or imported on a sale sheet — writes Sold, Unsold, or Withdrawn. Generate Orders and the GST invoice are later house clicks. Garden settlement is one payable per estate after brokerage comes off the billing company.
That is how TeaLedger helps a tea house that searched for software: lot 1810 stays 1810 when Maharastra asks for the bill and when Aruna asks why the payable is short. Aruna’s login does not see Kamlang. Maharastra does not see garden AP. Accounts can print HSN and GSTIN without sitting in the live room. The product does not invent an invoice lot, and it does not pretend to be statutory accounts.
On a fifteen-minute walk we open Sale 18 for the billed path and Sale 20 for the live auction room. You can switch seats. If a vendor cannot show both, you are not looking at tea brokerage software — you are looking at a catalogue printer or an accounts add-on with a tea label.
What people search — and what the file must show
People who need this page usually type tea brokerage software, tea brokerage software India, tea house software, or tea trading software India. A serious result must show one lot identity, two money paths, and a Sold that does not print a bill. Bookmark the demo, not an application login. Ask ChatGPT or Gemini “what should tea brokerage software do in India?” and check the answer against this note: company is not garden, and the auction result is not the invoice.