Orders in, with that party's rate
WhatsApp, voice and PDF lines match your items, then show that party's rate, credit days and Tally outstanding before you book.
Book every order before a buyer goes quiet.
WhatsApp, voice and PDF orders become a draft with that party's rate, credit and Tally outstanding. Stock stays by lot and godown. Quiet buyers get a nudge.
Setup fee back if it doesn't work in 45 days
Where the desk leaks orders and cash
-
Per order, typed by hand
WhatsApp, voice notes and PDFs are re-keyed in 4–5 minutes, and item names are matched from memory.
-
Quoted off the wrong list
The party's rate and scheme sit in a sheet. The bill is argued after the goods leave.
-
Printed twice, sent twice
A delivery order printed twice can ship twice. Stock and the ledger both go wrong.
-
The weekly buyer stops
A party who ordered every week goes silent. Nobody notices until a broker names a rival.
One system for the whole trading desk
Start with the workflow that leaks the most. It reads Tally, runs on your WhatsApp number, and is built for sales and operations.
-
-
Stock by lot, bag and godown
Total, booked and sellable for every lot and godown. Dried bags, a split bag and loose kilos stay on the same lot.
-
Delivery orders that print once
Preview it, require a marka, and print once per user. Buyer and broker get the copy on your WhatsApp, with dispatch on that DO.
-
Quiet buyers and open dues
When a party breaks their usual rhythm, draft a nudge. Overdue balances get a reminder. A person sends anything sensitive.
We also build
- Credit hold before goods leave
- Scheme and slab rates
- Import container tracking
- Returns booked against the DO
- Roles and after-hours locks
- A reason on every deletion
- Something else? Ask us
Orders, stock and DOs, off the spreadsheet.
A Mumbai dry-fruit and spice trader ran orders on paper DOs, stock in Tally and payments in Excel. We built an order and stock app on top of Tally, shaped call by call with the people who use it.
- 01Masters pulled from Tally, which stays the books
- 02Logins for DO, audit, marka, delivery and admin
- 03Order confirmations to buyer and broker on WhatsApp
- 9 working sessions with their team
- 5 department logins, desk to godown
- 1 print per delivery order, per user so one DO can't turn into two deliveries. Now in daily use, with launch testing under way.
From first call to first DO
-
Map the desk
A 30-minute call on orders, rates, DOs, stock and dues, from the broker's call to the godown.
-
Connect Tally and WhatsApp
Parties, items and godowns come from Tally. Messages go out on your WhatsApp Business number.
-
Pilot one workflow
One workflow is live in 3 to 6 weeks on real orders. Your team checks every screen before it posts.
-
Add the next workflow
Quiet-buyer nudges, dues, imports or returns, once the first workflow has earned its keep.
Tally stays the books, and you approve every write
We build the system. You decide who sees rates, stock and dues, and what gets written back to Tally.
-
Messages from your own number
Confirmations, dispatch notes and buyer nudges go from your WhatsApp Business account. Lot numbers and internal rates stay off the buyer's message.
-
Tally stays the books
We read parties, items and outstanding from Tally and link each delivery order to its invoice. Nothing is written back until a person approves.
-
Rates, roles and a full log
Each login sees only its job, after-hours locks stay on, and a buyer is quoted only their own rate. Every deletion needs a reason.
What traders ask us
Do we have to stop using Tally?
No. Tally stays your books. We pull parties, brokers and items from it, show outstanding and credit days on the order, and link each delivery order to its Tally invoice. Nothing is written back until a person approves. Your accountant's work does not change.
Can it handle bags that lose weight, or split bags?
Yes. Enter the total weight or the bag count and the app works out the other, and you can override it. Tare is set once per lot. A bag can be split across sales, and a sale can mix full bags with loose kilos.
Will our godown staff manage it?
Yes. Screens are built for the people using them: big-print delivery orders a driver can read, and separate logins for delivery orders, audit, marka and godown. Each login shows only that job, and the layout works on a small phone.
Can it stop an order when a party is over their limit?
Yes. The order screen shows the Tally outstanding, credit days and usual payment speed before you confirm. New parties need a GSTIN, or PAN and FSSAI, before they can be booked. A blacklisted party raises a warning with the reason. An order over the limit can be held until someone you name approves it.
Can it read WhatsApp messages and PDFs?
Yes. WhatsApp messages and photos, PDFs and spreadsheets. It matches your item codes first, then that party's past orders, then uses AI for the rest. Anything it is not sure about is shown to a person before it becomes an order. Voice notes, and orders written in Hindi or Hinglish, are scoped on the first call if that is how your buyers write.
How long until it is running?
One workflow is live in 3 to 6 weeks. Most traders start with order entry and delivery orders, then add stock, payments, quiet-buyer nudges and imports.
Let's find your first workflow
Book a 30-minute call. We will look at how your orders, stock and dues move today and tell you which sales and operations workflow to build first.
Book a 30-min call