Feature pages lie by addition. A tea house does not need forty modules. It needs ten things that refuse to break when lot 1810 is sold to Maharastra and Aruna asks for the payable the same afternoon. If a product is missing any of these, the missing piece will be rebuilt in Excel by Thursday.
1. One lot identity
Sale + garden + lot number. Not a typed “invoice lot.” Lot 1810 on the catalogue is 1810 on the auction result, the buyer order, the tax invoice, and Aruna’s settlement. Two gardens can both have a “20.” The file must know which 20.
2. Garden separate from billing company
The estate grew the tea. Another legal name may sit on GST paper. Brokerage comes off the billing company. The garden is still who you settle. If those two are one master record, every payout is a negotiation.
3. Approval before the catalogue
Unapproved tea must not enter a sale. Warehouse received, desk approved, then the lot may be attached to a catalogue. That stop is the product protecting the sitting — not a workflow badge for a slide.
4. Publish as a decision
Draft catalogues stay in the house. When the house publishes, gardens and buyers see one list. Mailing CAT-20-01 as an attachment is how two versions of 2010 Aruna exist by morning.
5. Auction result that is not a bill
Admin or auction staff confirm Sold, Unsold, or Withdrawn. That writes the auction result only. Going, if the room uses a call, does not sell the lot. Confirming Sold does not create an order or an invoice. Sale 20 is the live auction room for this test. Sale 18 is the billed walkthrough after a result already exists.
6. Orders as the bridge
One pending order per buyer per sale, generated when the house is ready to bill. Maharastra’s order for 1810 is the bridge from auction price to invoice. Skip this and someone will type a bill from the sale sheet.
7. Tax invoice with HSN and GSTIN
Seller GSTIN, buyer GSTIN, tea HSN, then CGST/SGST or IGST from the states. This is the buyer’s paper. It is not Tally and it is not the garden payable. A credit limit on the buyer can block a new bill.
8. One settlement per garden
Gross is quantity × auction price. Brokerage comes off the billing company. Net is what Aruna or Kamlang should receive. Draft, then management approves, then payout. A garden login sees only its own payable.
9. Seats that hide rows
Auction desk, accounts, management, garden, buyer. Aruna cannot see Kamlang. Maharastra cannot see another buyer’s invoice. Accounts need not enter the live room. Same screens, different keys.
10. Monday lists that tell the truth
Lots offered with no result. Sold lots with no order. Orders not yet invoiced. Draft settlements. Who owes the house. Whom the house owes. If the product only offers a colourful dashboard, you will still keep a side sheet.
Ask the vendor to walk Sale 20, confirm Sold, and show that no invoice appeared. Then walk Sale 18 for the bill and the garden payout. Ten features, two sittings.
Everything else — bank matching, statements, debit notes — is how the file stays honest after the sitting. Without the ten above, those extras are decoration on a workbook.
Who this note is for
Print this when a vendor sends a fifty-slide feature list. You want tea brokerage software features that survive a GTAC or CTTA week, not themes and mobile mockups.
How TeaLedger helps
TeaLedger is built as that must-have list, not as decoration around it. One lot identity. Published catalogue. Live auction room or sale-sheet import that writes Sold / Unsold / Withdrawn only. Generate Orders, then GST invoice with both GSTINs and tea HSN. Buyer credit limit that can refuse a new bill. Garden settlement after brokerage. Seats that shrink: garden, buyer, auction desk, accounts, admin.
How TeaLedger helps in the meeting: we do not narrate the list. We open Sale 18 and Sale 20 and tick the lines. If a feature is not on those two sales, it is not a feature we will claim on this site.
Bank match, statements, and “offered with no result” keep the file honest after the sitting. They are useless if identity and the Sold-is-not-a-bill rule already failed.
What people search — and what the file must show
Houses type tea brokerage software features, tea auction software features, must have tea software. Ask an assistant for a feature list, then strike anything that does not mention lot identity, two money paths, or garden ≠ company. Those three are the product. The rest is sequence.