Tithi Mondal

Article6 min readUpdated

Billing App Design: Screens for Shop Billing and Stock

Billing app design for shops and small traders: the POS screen, stock entry and inventory app UI that cashiers can use fast on a phone or tablet.

By Tithi Mondal, UI/UX Designer

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Billing App Design: Screens for Shop Billing and Stock: cover illustration

Imagine a hardware shop in a small town in West Bengal. Four customers stand at the counter. The owner's son is billing, the owner is answering a phone call, and a supplier is waiting to deliver 30 boxes of fittings. If the billing screen is slow, everything stops. Billing app design is the work of making this screen fast, and of keeping stock numbers correct without extra effort.

Who uses a shop billing app, and in what conditions?

The main user is a cashier or the owner, standing at a counter, with a customer in front of them. The second user is whoever receives stock, often in a back room or a godown with weak network.

Conditions I design for:

  • A mid-range Android phone, a small tablet, or an old Windows computer.
  • A noisy shop, with the screen glanced at, not read.
  • Network that drops. The bill must still be saved.
  • Staff with different comfort levels in English, so labels need to be short and clear.

The owner is a third user, but a different one. The owner opens the app at night to check the day's sales and what is running out. That person needs a summary, not the billing screen. My admin dashboard design article covers that overview, so here I focus on the counter and the stockroom.

What does a POS screen need to show?

A POS (point of sale) screen is the screen where a sale is created. It needs three zones: item search at the top, the bill in the middle and the total with a pay button at the bottom.

The details that matter:

  1. Search first. The cursor is already in the search box. Typing "cem" or scanning a barcode adds the item.
  2. Recent and favourite items. Show the 8 most sold items as large buttons. In a kirana shop, a handful of items make most of the bills.
  3. Quantity changes on the row. Plus and minus buttons, and tapping the number lets the cashier type 12 directly.
  4. A running total that never scrolls away. It is fixed at the bottom and shows rupees in a large size.
  5. Customer is optional. Attach a name or phone number only if needed, for credit sales or WhatsApp receipts.

Keep rupee amounts aligned to the right, with the same number of decimals. Use thousand separators the Indian way, as in 1,25,000, because that is how shopkeepers read numbers. See designing apps for Indian users for more on number and currency habits.

How should payment and the bill be finished?

The payment step must finish a sale in 2 taps for the most common case. Show Cash, UPI and Credit as three large buttons.

For cash, show the amount received field with quick amounts and the change to return in large type. For UPI, show a QR code for the customer to scan, and a clear "Payment received" confirmation that the cashier can trust. Do not leave the cashier guessing if the money arrived. For more on how this step feels to the payer, read UPI payment UX and checkout design.

After payment, offer Print, Share on WhatsApp and New bill as three buttons. New bill is the default and most prominent, since the next customer is waiting.

If the bill is a tax invoice, the business must confirm the required fields and format with its accountant. A designer can lay out the fields clearly, but cannot decide what the law needs. I go through layout in invoice and quotation screen design.

How should stock entry work in an inventory app UI?

Stock entry is the flow where new goods are added to the count. It should take less than a minute for one delivery and allow work to continue when the network is weak.

The simplest flow has these steps:

  1. Tap Receive stock.
  2. Choose the supplier, or type a new name.
  3. Add items by search or barcode, and enter quantity and purchase price for each.
  4. Review the list. Rows with a changed price are highlighted, since a price change affects profit.
  5. Save. Quantities update, and the supplier balance updates if purchase is on credit.

Add a separate, plain Stock adjustment screen for damage, loss or counting mistakes. It needs a reason field. Without it, the owner cannot tell why numbers changed.

Show stock status with words and colour together: "In stock", "Low: 4 left", "Out". Colour alone fails for colour-blind users and on dim screens. The low stock level should be set per item by the owner, because 5 bags of cement and 5 packets of screws are very different.

What screens does the whole app need?

A small shop needs fewer screens than most founders expect. These are the ones that matter.

ScreenPurpose
New billCreate a sale fast
Bills listFind, reprint or cancel a past bill
ItemsAdd or edit products, price, unit, low stock level
Receive stockAdd purchases
Low stockA list to reorder from
CustomersCredit balances and payments received
Day summaryCash, UPI and credit totals for the day

Notice what is missing: complex settings, many report types and role screens. Add them later. My guide on MVP design: what to build first explains how to choose.

Units need care. A shop may sell cement by bag, wire by metre, and rice by kg. The item screen must let the owner set the unit once, and the bill must show it next to the quantity.

What mistakes should a billing app avoid?

The biggest mistake is designing the app for the owner's reports instead of the cashier's speed. A slow counter screen costs money every minute.

  • Too many taps to add an item. Count the taps. If one item takes more than 2, redesign.
  • Edit and cancel without a record. Cancelled bills need a reason and a name of who cancelled.
  • Full page reload on every action. On slow networks, save locally first and sync later. See designing for low-end phones and slow networks.
  • Tiny touch targets. Fingers at a busy counter are fast and imprecise. Buttons should be large.
  • No undo for a wrong quantity. A short "Undo" message after removing a row saves many arguments.
  • Mixing stock and billing in one crowded screen. Keep the stock work separate from the sale.

On a marketplace seller app I designed, the same lesson applied: the person using the screen all day needs the common action first, and everything else one level deeper. The principle is the same at a shop counter.

If you are planning billing or inventory software for a shop, a distributor or a small chain, I can design the screens and flows through my UI/UX design service. You can also write to me through the contact section.

Frequently asked questions

Should a billing app work offline?

Yes, for shops with weak network. Save the bill on the device first and sync later, and show a small status so the cashier knows if anything is waiting to upload.

What is the difference between a POS screen and a billing screen?

They are usually the same thing. POS means point of sale, the screen at the counter where a sale and payment are recorded.

How do I design a barcode scan flow?

Keep the scan button on the new bill screen, add the item with a short sound or vibration, and show a clear message if the code is not found with a quick way to add it.

Do I need to include GST fields in the bill design?

Many Indian businesses do, but the exact required fields depend on the business. Confirm them with your accountant before the layout is finalised.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.

Have a product in mind? Let us design it properly.

Tell me what you are building. I will reply with questions, a rough timeline and a quote.