Tally Mobile

Why Recording Sales Orders in Tally Is the Only Way to See Real Demand

Why Recording Sales Orders in Tally Is the Only Way to See Real Demand

You should record sales orders in Tally rather than only invoices, because invoices show what you billed and orders show what you already promised, and promised demand is what stock has to cover before the next truck. Why record sales orders in Tally is a timing question: the ask happens at 11 AM at the counter, the invoice happens when you can dispatch, and in between the godown still thinks 80 bottles are free. A sales order punched on the phone lands in Tally as a Sales Order, so the counter and the books agree the same afternoon. A Guwahati salesman at Fancy Bazaar Chemist at 11:05 punches 40 bottles of 200 ml against 80 on Stock Summary. Free quantity is 40, one day of sales at 40 a day, against an 8-day lead time. Without the order, the owner at 9:10 the next morning still sees 80 and delays the purchase.

Key Highlights

  • An invoice is billed sales; a sales order is promised demand; stockout control uses free quantity, which is stock minus what is already promised
  • A sales order punched on the phone lands in Tally as a Sales Order, so the 11:05 ask is visible before the 8 PM typing session
  • Pending Orders shows orders not yet invoiced and is a paid add-on, available on request; it names the unbilled queue and stops there

In This Article

  • Should I record sales orders in Tally or just invoices?
  • Why record sales orders in Tally between ask and invoice
  • What a sales order makes visible
  • Punch once, on the phone, into Tally
  • Pending Orders and free quantity
  • Demand the pad never writes
  • Frequently Asked Questions

Should I record sales orders in Tally or just invoices?

You should record sales orders in Tally. Invoices alone are the history of what you managed to bill. They arrive after stock has already been promised, picked, or refused. The godown that only reads invoices is always late on demand.

A sales order is the ask, stamped, against a party and items, before the bill. When that order is in Tally, Monday's cover calculation can subtract it. When it is only on a pad in a salesman's pocket, Monday still thinks the 80 bottles of 200 ml are unsold.

Just invoices is how shops already run. It is also how two salesmen sell the last 80 bottles twice, how a purchase waits until the invoice week looks quiet, and how lost sales due to stockout disappear because a refusal never became a voucher.

Why record sales orders in Tally, then: because stockout control for distributors needs promised demand while the stock is still sitting. Invoices are too late for that job. They remain the right document for GST, for the party's ledger, for item-wise sales of what actually went out. They are the wrong document for "what is already committed against today's 80."

Why record sales orders in Tally between ask and invoice

An invoice records a completed sale. Quantity left, rate, tax, party. Item-wise sales totals those quantities. That total is true and incomplete.

It cannot see the 40 bottles punched at 11:05 that will invoice tomorrow if stock lasts. It cannot see the 40 a second salesman will promise at 3 PM against the same 80. It cannot see the chemist who asked, heard "check karke batata hoon," and bought from the next van, because no invoice was ever going to exist.

A quiet invoice day on a fast mover is ambiguous. Either demand fell, or the shelf was empty, or the orders are sitting unbilled. Without sales orders you cannot tell which. With them, unbilled demand is a list, and a zero Stock Summary next to that list is a purchase, not a mystery.

Credit notes show goods that came back. They do not show goods that never went. The invoice register is a success list. Demand includes the asks that have not succeeded yet.

What a sales order makes visible

A sales order in Tally is a queue. Party, items, quantities, date. The godown can pick against it. The owner can subtract it from Stock Summary. The purchase person can see that 80 minus 40 promised is 40 free, which is one day of 200 ml at 40 a day, which is below an 8-day lead time.

That subtraction is the point. Days of cover on 80 bottles looks like 2 days. Days of cover on 40 free looks like 1. The reorder point should use free quantity when orders exist. Otherwise you buy late by however many bottles are already promised.

Two salesmen, one SKU, no orders: both look at 80, both promise 40, the afternoon dispatch has 80 to pick and 80 promised, and someone loses. Two salesmen, orders in Tally: the second punch sees 40 already committed if the team looks at pending demand, or at least the owner at 4 PM sees 80 promised against 80 on hand and stops a third promise.

Orders also make next week's festival bookings visible in September. Last year's invoices cannot do that in time. This year's orders can, which is the demand half of seasonal buying.

What a sales order does not do: it does not track the carton from punch to the retailer's door. There is no fulfilment timeline here. The order is a demand stamp in Tally. Dispatch still has to pick, the truck still has to leave, the invoice still has to be raised. The visibility win is the stamp, on the day of the ask.

Punch once, on the phone, into Tally

Most teams take the order twice. Pad at the counter, photograph, operator at 8 PM. The second typing is where the day goes, and it is where demand stays invisible until evening.

Sales order on mobile means the order is punched at the counter against live items and parties, and lands in Tally as a Sales Order. That is the same once-only capture as salesman order taking without re-entry. For collections, the win is less delay before the invoice. For stock, the win is that 11:05 is in the books at 11:06.

The salesman can read Stock Summary and godown-wise stock before he promises. 80 in the company, 0 in Guwahati, 80 in Tinsukia: the promise is a transfer conversation, not a lie at the counter. Godown wise stock on mobile is that location cut.

If he only punches after confirming stock, zero-stock asks never become orders, and you lose the lost-sales reconstruction. For demand visibility, punch the ask. Then say yes, say transfer, or say no. The no with an order is still demand. The no without an order is a chemist walking.

The 8 PM typing session cannot feed Monday 9:10. The truck decisions happen in the afternoon. Orders that land at night are invoices' cousins: too late for the day's purchase list.

Pending Orders and free quantity

Pending Orders shows orders not yet invoiced. It is a paid add-on, available on request.

When it is on, free quantity is Stock Summary minus pending quantity on that item. 80 on hand, 50 pending, 30 free. Cover uses 30. The purchase uses 30. The salesman who wants another 40 is promising stock that is not free.

When it is not on, you can still record sales orders in Tally and read them on the desktop, or keep a notebook of the day's punches. The add-on is the list on the phone. The method does not disappear without it. It gets slower.

Do not describe this as tracking fulfilment end to end. Pending means not yet invoiced. It does not mean picked, loaded, or delivered. An order can sit pending because stock is missing, because dispatch has not billed, or because the chemist cancelled in a WhatsApp the books have not caught. A person still closes or invoices it.

Inventory Velocity still ranks how fast items move. Pending demand on a high-Velocity SKU is the expensive queue. Pending demand on a dead SKU is a surprise that maybe it is not dead. Read both.

Demand the pad never writes

Three asks that never reach Tally if you only invoice.

The chemist who hears "khatam" and leaves. No pad line, no invoice, no order. Notebook if the salesman bothers. Otherwise lost sales that the register will never show.

The salesman who writes 40 on a pad and photographs it at 5 PM. Demand exists on paper from 11:05 to 8 PM. The godown does not have it. A second salesman sells the same 40 at 3 PM.

The festival booking in a WhatsApp: "25 September, 40 tins diya oil." If that does not become a sales order, September's purchase still runs on last year plus guesswork.

Recording sales orders does not capture every walk-out. It captures every ask the team is willing to stamp. That is already more demand than invoices will ever show, and it is the only demand Tally can subtract from stock.

Saturday's count still has to match Stock Summary. The order still has to be honest on quantity. Why record sales orders in Tally is so Monday 9:10 sees the 40 from Sunday's counter, in the same books as the 80 on the shelf.

Frequently Asked Questions

Q: Should I record sales orders in Tally or just invoices?

A: Record sales orders. Invoices show billed sales after dispatch. Orders show promised demand while stock is still in the godown. Stockout control needs that queue so free quantity is stock minus what is already promised, not stock minus nothing.

Q: Why record sales orders in Tally if I already invoice every sale?

A: Because the ask and the invoice are hours or days apart. In those hours two salesmen can promise the same 80 bottles, and the purchase person still sees 80 unsold. The order is the stamp that makes the ask visible in the same books as stock.

Q: Does a sales order on the phone land in Tally?

A: Yes. An order punched on the phone lands in Tally as a Sales Order. The counter and the books agree the same afternoon, instead of a pad that gets typed at 8 PM. That is also how the salesman reads stock before he promises.

Q: What is Pending Orders?

A: Pending Orders is the list of sales orders not yet invoiced. It is a paid add-on, available on request. Free quantity is stock minus that pending quantity. It does not track picking, loading, or delivery.

Q: Can I see demand if the salesman only punches when stock is available?

A: You will see orders for asks that were already going to succeed. Zero-stock asks will not be stamped, so refusals stay invisible. For demand visibility, punch the ask first, then accept, transfer, or refuse.

Q: Do sales orders replace item-wise sales?

A: No. Item-wise sales still totals what was billed. Orders add the queue that has not been billed. You need both: billed history for the average daily rate, and orders for what is already committed against today's stock.

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.

See this in action for your business

15 minutes. We show you your own Tally data on your phone, live.