
Key Takeaways
- 1What takeaway billing software has to do
- 2Parcel order billing in a restaurant: the counter flow
- 3Dine-in vs parcel: the steps compared
- 4Packing charges as a menu item
- 5Running dine-in and parcel together at peak time
Quick Answer
Takeaway billing software should let the cashier start a parcel order with no table, bill and collect payment at once, print a kitchen ticket marked PARCEL and hold the order under the customer's name until it is packed. Add packing charges as a menu item so they appear on the bill and in reports. Dhandhaan handles parcel and dine-in on the same counter for ₹12,999 a year per branch, with no charge per bill.
This guide is for restaurant owners and counter managers in India whose parcel business has grown alongside the dining hall: the South Indian restaurant where a third of the evening orders walk out in bags, the pav bhaji counter with a parcel window, the thali dining hall that packs lunch for nearby offices. By the end you will know how a parcel order should flow at the counter, how it differs from a dine-in order, and how to run both at peak time without one slowing the other.
What takeaway billing software has to do
A parcel order looks like a smaller version of a dine-in order. At the counter it behaves differently in four ways.
- There is no table. Nothing to mark as occupied, nothing to free at the end. The order belongs to a person standing at the counter or arriving later.
- Payment comes first. The customer pays when ordering, so the bill is final at the start, not after the meal.
- The kitchen must pack, not plate. Chutney goes in a pouch, gravy in a sealed container. The cook needs to know before the food is made.
- The customer waits or returns. Someone has to match the packed bag to the right person without a table number to go by.
Software that treats a parcel as "Table 99" gets all four wrong. The parcel sits in the table list, the kitchen ticket looks like any other, and the parcel sales are mixed into dine-in numbers. Restaurant billing software should treat parcel as its own order type.
Parcel order billing in a restaurant: the counter flow
A clean parcel flow has six steps. Each takes a few seconds when the system is set up for it.
- Start a parcel order. The cashier chooses the parcel or takeaway order type. No table is selected.
- Enter the items by short code or touch, with sizes and add-ons, and add the packing charge item if you charge one.
- Take payment and settle. Cash, UPI QR for the exact amount, card, or a split. Settling assigns the final invoice number.
- The kitchen ticket prints at the right station, marked PARCEL.
- Hold if needed. If the customer will collect later, or the order is waiting on something, the parcel is held with a customer label.
- Pack and hand over. Staff match the bag to the receipt or the label and hand it across.
The kitchen ticket marked PARCEL
The word PARCEL on the kitchen ticket is a small thing that prevents the most common parcel mistake: food plated for a table that should have gone into a container. With the ticket marked, the cook picks up the right packaging from the first step, and the person at the pass knows the order goes to the counter, not to a captain.
Because each menu item is mapped to a kitchen printer, a parcel of two dosas and two coffees prints one ticket at the dosa counter and one at the beverage counter. Both carry the parcel marking, so both stations pack. See the kitchen order ticket setup guide for how the mapping is done.
Holding a parcel with a customer label
Not every parcel is paid and handed over in one go. A regular customer calls at 7:30 PM and says he will collect at 8:15. A customer orders, then goes to fetch the car. A large order is waiting for one more instruction.
In each case the cashier puts the parcel on hold with a label, such as "Mehul 8:15" or the last four digits of a phone number. The held order leaves the billing screen, the cashier serves the next customer, and the order is recalled by its label when the customer arrives. Without hold, cashiers either keep the order open and block the counter, or write it on paper and enter it later, which is how items get missed.
Dine-in vs parcel: the steps compared
The table sets the two flows side by side as they work in Dhandhaan restaurant POS software. Use it to train new counter staff.
| Step | Dine-in | Parcel or takeaway |
|---|---|---|
| Starting the order | Pick a table; the table turns to running status | Pick the parcel order type; no table |
| Who enters it | Captain on the Android app, or the cashier | Cashier at the counter |
| Kitchen ticket | Shows the table; items added later print as ADDITIONAL | Marked PARCEL so the kitchen packs |
| Adding items later | Common: second round, desserts | Rare: the order is usually complete at the start |
| Bill | "Print Bill" gives a provisional bill; the table stays occupied | Billed at once |
| Payment | At the end of the meal; "Settle" assigns the invoice number and frees the table | At the time of ordering; settling assigns the invoice number |
| Waiting | Guest is seated at the table | Customer waits at the counter, or the parcel is held with a label |
| Extra charges | Service charge if the branch has it switched on; the cashier can remove it | Packing charge added as a menu item |
| Handover | Served at the table | Packed and handed over at the counter |
Both order types draw invoice numbers from the same sequence for the branch, so the invoice register stays continuous for your accountant.
Packing charges as a menu item
Containers, pouches, foil and bags cost real money, and many restaurants recover part of it with a packing charge. There are three ways to do it, and only one of them is clean.
Raising parcel prices quietly means two prices for the same dish and confusion at the counter. Typing a manual amount on each bill is slow and nobody can audit it. The clean way is to create "Packing charge" as a menu item with a fixed price, and add it to parcel orders like any other item.
This has practical advantages. The charge is printed on the bill as its own line, so the customer sees what it is. The item-wise sales report shows how much packing revenue you collected in the month, which you can set against what you spent on packaging. And you can create two or three variants using sizes, for example small, large and bulk, if a single dosa and a family order should not carry the same charge.
Two cautions. Decide a simple rule, such as one packing charge per order or per container, and write it down for the cashiers, because the software will add whatever the cashier enters. And ask your accountant which GST rate to set on the packing charge item; do not assume.
Running dine-in and parcel together at peak time
At 8:30 PM on a Saturday the dining hall is full, captains are sending orders from every floor and there are ten people at the parcel counter. This is where restaurants lose orders. A few arrangements keep the two streams from colliding.
- Let captains carry the dine-in load. When table orders are entered on captain phones, the counter PC is free for parcels and settlements. See the guide to the captain ordering app.
- Give parcels a fixed handover spot with its own shelf, away from the pass where table orders go out, so packed bags are not picked up by captains.
- Keep packing material at each station. If the dosa counter and the main kitchen both get PARCEL tickets, both need containers within reach.
- Use hold for anything not collected immediately, so the cashier's screen shows only the customer in front.
- Show the UPI QR on a customer-facing screen or print it on the bill, so payment does not wait for the cashier to turn a phone around.
- Reprint, do not rewrite. If a parcel ticket is lost in the rush, reprint it from the system; a handwritten slip has no record.
Reading parcel sales separately
Parcel and dine-in have different costs. Parcel uses packaging but no table time; dine-in uses seats, captains and dishwashing. Owners should know how much of the day's sale is parcel, at which hours it peaks and which items travel most.
Because parcel is a distinct order type, its orders can be told apart from table orders, and the packing charge item gives a quick count of parcel activity in the item-wise report. Read these with hour-wise sales to decide whether the parcel window needs its own person from 7 PM to 10 PM. Ask to see the parcel view of the reports during your demo, and check which sales reports owners should review.
How Dhandhaan handles this
Dhandhaan is restaurant POS and billing software built by JK Tech Hub in Rajkot. For takeaway it provides the following.
- Two order types, dine-in and parcel or takeaway. A parcel is a counter order with no table and is billed at once.
- Parcel hold with a customer label, recalled when the customer returns.
- Kitchen tickets routed by item to the correct printer, with each printer numbering its tickets from 1 every business day. Tickets can be reprinted and cancelled items print a CANCELLED ticket.
- Menu items with sizes and add-ons, which is how packing charges and their variants are set up.
- Cash, UPI QR for the exact bill amount paid straight into the restaurant's own UPI ID, card recorded manually, and split payment.
- Sequential invoice numbers per branch that restart each financial year.
- Reports in Excel and PDF, including hour-wise sales, item-wise sales, payment mode split, cashier-wise sales and a day-end report.
- A local server per branch, so parcel billing continues when the internet is down.
The price is ₹12,999 a year for a single branch and ₹23,999 a year for multi-branch. There is no charge per bill, which matters when parcel orders add hundreds of small bills a month.
What it does not include at present: live integration with food delivery apps, so orders received on those apps are entered at the counter by hand as parcel orders. It also has no customer accounts or loyalty, no delivery rider tracking, no inventory of packaging material and no kitchen display screen; the kitchen works from printed tickets.
What we saw on a multi-branch build in Gujarat
JK Tech Hub built Dhandhaan for a multi-branch South Indian and fast food restaurant business in Gujarat that was moving off a hosted POS. Parcel is a large part of that kind of business, and the build taught us three things.
The kitchen there has separate counters with their own printers. A parcel order often touches two of them, so the parcel marking had to appear on every ticket, not only the first one.
Outages at peak hours were the main complaint with the earlier system. A parcel queue is the least patient queue in a restaurant, because those customers have not sat down and can leave. Running each branch on a local server meant the parcel counter kept billing when the internet dropped.
We kept the rule that a table stays occupied until its bill is settled, while a parcel never occupies anything. Keeping the two apart stopped parcel orders from cluttering the table screen that captains rely on.
How to decide
Estimate what share of your orders is parcel. Under one in ten, you only need the parcel order type and a packing charge item. Between one in ten and one in three, add hold with labels and a fixed handover shelf. Above that, plan a separate parcel counter or window, and check the hour-wise report to staff it.
When you see a demo, ask the vendor to bill a parcel, hold a second one under a name, bill a table in between and then recall the held parcel. If that takes more than a minute, it will not survive a Saturday night.
Related reading and next step
- Dhandhaan restaurant POS software: features and price
- QSR and fast food billing: how to speed up the counter
- Restaurant table management: merge and split tables
- UPI QR on the restaurant bill with zero fee
- Restaurant GST bill format and invoice numbering
To run a parcel and a table order side by side on your own menu, ask for a demo or a quote through the contact page or on WhatsApp at +91 7265004040.
Tags
Continue exploring
Pages on JK Tech Hub related to this article.
