# A simple order system with chat, email and a sheet

Canonical: https://onlineitbd.com/blogs/shop-orders-with-chat-and-sheets/
Language: en
Author: Online IT BD Team
Published: 2026-11-01
Updated: 2026-11-01
Tags: Shop

A simple order flow for small shops: chat plus email plus sheets. Setup steps, columns, and honest limits before software.

An order system is the clear set of rules for where each order goes, who sees it, what is checked before delivery, and whether the money matches. A small shop can run these rules with chat, email and one sheet, before buying any software.

If you search in Banglish, this is the "order management sheet" question. The answer starts with a rule, not an app.

## Why software is not needed at the start

At the start the problem is not a lack of software. It is orders getting lost. If nobody can say who ordered what, who paid, and who returned an item, buying software does not fix it. Set the rule first, then the tool.

Chat, email and one sheet give three benefits. One, the cost is low. Two, your team starts with what it already knows. Three, you can see with your own eyes where the problem appears. Later, when you move to software, you also know what you need.

## What every order needs

An order is complete only when it has enough information to deliver. Ask for all of it at once, not in separate messages.

* The customer's name.
* One mobile number that is answered.
* The full address: area, house, and a landmark.
* Product name and quantity.
* Product price, delivery charge and total.
* Payment: cash on delivery or advance.
* Order number.
* Order date.
* Any special instruction.

At the end, write the total and the product list again. When the customer says yes, the order is confirmed. This one step stops many mistakes.

## Which columns the sheet needs

The sheet is the main order book. Fewer columns are easier to write, but if useful information is missing you will search for it later. Start with these columns.

| Column | How to write it | Why it matters |
| --- | --- | --- |
| Order number | Date plus the day's count | Stops the same order being written twice |
| Date and time | When the order was taken | Finding old orders |
| Name | Customer name | For delivery and recognition |
| Mobile | The number that is answered | Confirming before delivery |
| Address | Area, house, landmark | So the courier can find it |
| Products | Name and quantity, separate lines | Stops the wrong product |
| Total | Product, delivery and discount separately | The accounts match later |
| Payment | Cash on delivery or advance | Shows where the money comes from |
| Status | New, sent, delivered, returned | The daily work list |
| Note | Special instruction | Fewer misunderstandings |
| Taken by | Team member's name or initials | Shows who to ask if something is wrong |

A simple order number rule: the last two digits of the date plus the count for the day. For example, on 28 October, the seventh order of the day could be 2810-07. You can give this number to the customer, so the question "where is my order" is easier to answer.

## Rules for taking orders in chat

The biggest problem with chat orders is that the conversation spreads out. One message has a name, another has the address, a third asks the price. At the end it is hard to match who said what.

So write one fixed reply and send the same one every time. A sample:

> Thank you. I am writing the order down. Please send these together:
>
> 1. Name
> 2. Mobile number
> 3. Full address
> 4. Product and quantity
> 5. Total with delivery charge
> 6. Payment: cash on delivery or advance
>
> I will write the product and the total back to you. When you reply yes, the order is confirmed.

Keep this sample written down so the whole team answers in the same way. The customer also learns what to send, so you do not have to ask again and again.

## Checking cash on delivery orders

To reduce returns on cash on delivery, contact the customer once before delivery. In a short message or call, confirm the product, the address, and that payment will be made on handover.

After the check, write in the sheet when you made contact and what the customer said. Give the delivery person a short list: order number, name, address, total and note. When an item comes back, write the reason. Without a reason, the same mistake repeats.

## What to match at the end of the day

At the end of each day, match five numbers: how many orders came in, how many were sent, how many were delivered, how many came back, and how much money was received. When these five match, the day's accounts are in order.

Keep a copy or export of the sheet every day. A sheet in one place can be changed by mistake, so a daily copy is safer. Decide who can edit the sheet. If everyone can edit, you cannot tell who caused a mistake.

## Who runs it

One person should own the order system. That person matches the sheet every day, looks at return reasons, and gives the owner a short report at the end of the week. Rules break less when one person is responsible.

Even with two or three people on the team, give one person the main job. Others can take orders, but the final match belongs to one person.

## When software is worth it

Look at signs, not at numbers. When these signs appear, chat and a sheet are no longer enough.

* The same order is written twice.
* Stock and the sheet do not match.
* Several people take orders and nobody can tell who took what.
* A daily report takes a long time to build.
* Deliveries grow and a hand written list becomes hard.
* You are increasing ads, so orders will grow.

When these signs appear, look at a [SaaS tool](/products/saas/) or a [custom order system](/products/services/). But make the rule clear first, or the new software will have the same problem.

## Limits of this system

To be honest, chat and a sheet do not do everything.

* A sheet does not reduce stock by itself.
* Two people writing the same order at the same time can create two rows.
* A sheet does not always show who changed what.
* The customer does not get an automatic SMS or reminder.
* Money does not match a payment gateway by itself.
* If the chat service changes its rules or the account has a problem, contact can stop.
* Messages at night or on holidays are answered late.
* Without one owner, the rules break.

Knowing these limits keeps expectations right. Where a limit creates a real problem, that is where software or automation earns its place.

## In short

The core of an order system is one rule: every order in one place, with the same information, under the same numbering. Take orders in chat, write them in the sheet, match at the end of the day. Once this habit exists, software is easier to add, and the work runs without it too.

Write how your shop takes orders today and [email us](mailto:onlineitbd.com@gmail.com?subject=Quote%20request%2C%20shop%20order%20system). We can build a simple sheet, or set up an [automation pack](/products/automations/) so some steps run by themselves.

## Questions and answers

### Is a sheet safe?

A normal sheet is safe when access is limited and the rules are followed. Give edit rights only to those who need them and view rights to the rest. Do not share the password, and keep a copy at the end of the day. The less a customer's full data spreads, the better.

### How many orders before software is needed?

Look at signs, not at a number. If the same order is written twice, stock does not match, or a report takes a lot of time every day, software can be needed even with few orders. On the other hand, with clear rules a sheet can run for a while even when orders grow.

### Who should run this system?

Give one person the main job. That person matches the sheet daily, writes return reasons, and sends a short report at the end of the week. Others can take orders, but the final match sits with one person, and mistakes drop.