You see which salesman visits actually produced orders on the Outcomes tab of Field Visits: Booked on these visits lists orders attributed to that salesman, and At the dealers visited lists orders by anyone, payments received, and overdue outstanding at those same dealers. The caveat is that payments sit at the dealer, never credited to the salesman who walked in. Visit to order conversion in field sales, on this Guwahati book, is Tuesday after Station Road: Raju checked in at Gupta Stores with a camera photo, Global Positioning System (GPS) location, device time, his name and the dealer, then booked 14 cartons after check-out. Five salesmen, about 120 dealers, five road names. Field Visits is available on request. Feed defaults to today, filterable by salesman or Everyone. This article walks both Outcomes columns, the free-text note, and what a week of those rows actually shows.
Key Highlights
- Outcomes splits Booked on these visits, orders attributed to that salesman, from At the dealers visited, orders by anyone, payments received, and overdue outstanding at those dealers
- Payments received at those dealers stay dealer-level. They are never credited to the salesman who checked in
- The visit carries an optional free-text note. Raju types what happened at Gupta Stores in his own words
In This Article
- How do I see which salesman visits actually produced orders?
- Booked on these visits, Raju's six orders
- At the dealers visited, the eighteen ledgers
- Visit to order conversion in field sales after a week
- The free-text note on the visit
- After check-out, the order into Tally
- Frequently Asked Questions
How do I see which salesman visits actually produced orders?
On Outcomes. The owner's Field Visits screen has two places to look. Feed is the day's stamps. Outcomes is what those stamps produced.
Feed defaults to today. Filter by salesman or Everyone. He opens Raju, sees Gupta Stores at 10:40, taps the photo, reads the plate. That answers gaya tha ya nahi. Outcomes sits next to that feed. Visit to order conversion in field sales is that second tab: Booked on these visits is the salesman column, At the dealers visited is the ledger column. The two numbers will not match, and that is the point of opening both.
The Salesman app for Tally already has the visit: camera photo, GPS location with accuracy, device time, Raju, Gupta Stores. Outcomes reads the orders and the dealer books around those visits. Beat-wise sales management is Station Road as a named list, then this tab at night. Twenty-four shops. Eighteen got a stamp.
Visit capture is phone-only. The owner's Field Visits screen is phone-only. Beats, Dispatch and Team Sales also work on the web.
Booked on these visits, Raju's six orders
Booked on these visits lists orders attributed to that salesman.
Tuesday, Station Road. Raju checks in at Gupta Stores at 10:40, talks through the scheme, checks out at 10:52, then books 14 cartons. That Sales Order carries his name. Outcomes puts it on Booked on these visits when the owner filters to Raju, today.
Five more orders land the same way on the same beat. Six rows. Eighteen visits. Visit to order conversion in field sales, on this Tuesday, is six against eighteen for Raju. The owner reads the two counts together.
The order can be raised after check-out or any other time. Order creation is not gated on Team Sales. A geo-tagged visit photo versus all-day GPS tracking is still the first stamp. Outcomes reads the orders that already have his name. Filter Everyone and the salesman column is the whole field team for that day.
At the dealers visited, the eighteen ledgers
At the dealers visited lists three things at the shops that got a stamp: orders by anyone, payments received, and overdue outstanding at those dealers.
Gupta Stores is one of Raju's eighteen. Raju's 14 cartons sit in both columns, because they are his order at a dealer he visited. The owner also called Gupta at noon and booked a crate himself. That order is not Raju's. It still sits on At the dealers visited, because anyone's order at that ledger counts there.
A UPI credit lands on Gupta Stores at 3 PM. ₹8,400 against an old bill. That payment is on the dealer. It is never credited to Raju. Booked on these visits does not grow because money came in. Overdue outstanding sits on that column too. Gupta Stores still carries ₹1,20,000 past terms. The owner reads the visit next to the overdue, which is the conversation salesman-wise collection accountability is for on the books, without putting the receipt on Raju's name.
| Booked on these visits | At the dealers visited | |
|---|---|---|
| Orders | Attributed to that salesman | By anyone at those dealers |
| Payments received | Not on this column | At those dealers, dealer-level |
| Overdue outstanding | Not on this column | At those dealers |
The two columns exist because Station Road can look busy when the owner booked the crate, or look dry when Gupta paid an old bill and Raju still booked nothing. Payments stay on the ledger. What a beat is in distribution sales still only names the list.
Visit to order conversion in field sales after a week
Visit to order conversion in field sales earns its keep over a week. The owner sits with five salesmen and about 120 dealers. Station Road: six orders on eighteen visits on Tuesday, four on sixteen on Wednesday, a Friday where Raju stamped twenty shops and booked two. GS Road: Manoj, orders clustered on three kiranas. Fancy Bazaar parties with a weekly photo and overdue still sitting on At the dealers visited.
A shop with Raju's order every visit is one conversation. A shop with stamps, payments, and no order attributed to him is another. How long he was at the dealer still sits on the visit card. Duration does not move a payment onto Raju. Salesman-wise sales reports still answer the billing question. Outcomes answers which visits carried his orders, and what those dealers did anyway.
He WhatsApps at 8:20. "Station Road pe visit to order kaisa raha?" The answer is two columns.
The free-text note on the visit
Check-in already captures the camera photo, GPS location with accuracy, device time, the salesman, the dealer, and an optional note. The note is free text. Raju types "14 cartons, next week scheme" at Gupta Stores, or he leaves it blank. The visit is the photo and the times. The order, if any, is the Sales Order in Tally. A Tuesday of blank notes still has Outcomes. Conversion does not wait on the note. Create beats and assign a salesman from the phone still only puts Raju on Station Road.
After check-out, the order into Tally
Take an order is offered after check-out. Visit check-in and check-out are saved on the phone without signal and upload when signal returns. Creating an order, invoice or receipt needs a working data connection.
At 10:52 Raju has signal on Station Road. He books 14 cartons. It lands in Tally as an ordinary Sales Order, which is the point of salesman order taking without re-entry. Booked on these visits can see it because the order carries his attribution. In a dead-signal lane, visit check-in with no signal saves the stamps on the phone. The order waits for bars.
If the phone reports a mock location, check-in is refused and no visit is recorded. The refused attempt still shows to the owner. Fake GPS on a salesman's phone is that refusal. Outcomes has nothing to convert if the visit never landed. Station Road at night is Feed first, then Outcomes: eighteen photos, six of Raju's orders, payments and overdue on the dealer. That is visit to order conversion in field sales on this book.
Frequently Asked Questions
Q: How do I see which salesman visits actually produced orders?
A: Open Field Visits, then Outcomes. Booked on these visits lists orders attributed to that salesman. At the dealers visited lists orders by anyone, payments received, and overdue outstanding at those dealers. Filter by salesman or Everyone. Feed is the stamps. Outcomes is what sat around them.
Q: What is visit to order conversion in field sales?
A: Reading the two Outcomes columns together. Booked on these visits is his orders. At the dealers visited is everything at those ledgers, including other people's orders and payments that stay on the dealer. Conversion is those two counts against the visits that actually happened.
Q: Are payments credited to the salesman who visited?
A: No. Payments received at the dealers visited sit on the dealer. They are never credited to the salesman. A UPI credit on Gupta Stores at 3 PM does not add a row to Booked on these visits.
Q: Does the salesman pick an outcome type after the visit?
A: No. The visit carries an optional free-text note. He types what happened, or he leaves it blank. The order, if any, is the Sales Order in Tally. The note is not a coded result.
Q: Can an order booked by the owner show on At the dealers visited?
A: Yes. At the dealers visited includes orders by anyone at those dealers. If the owner booked a crate on Gupta Stores after Raju's stamp, that order sits on the dealer column. It does not sit on Booked on these visits for Raju.
Q: Does Outcomes work when the visit is still on the phone?
A: Visit check-in and check-out are saved on the phone without signal and upload when signal returns. Creating an order, invoice or receipt needs a working data connection. Outcomes reads visits and orders that have already landed. A stamp still labelled Saved on this phone is not on the owner's feed yet.
Takkada is a Tally-integrated receivables and auto-reconciliation app for Indian distributors, with 0% MDR UPI collection and WhatsApp dispatch. Book a free demo.