Skip to content
Zenocta Solutions

Mobile App Development11 Jun 2026 · 8 min read

How We Built Instobill: Barcode Billing and Stock for Small Shops

The build story of Instobill, our Android and web inventory and billing app: why bill and stock must be one event, how barcode scanning and tax set-up work, and lessons for builders.

ZEBy , Editorial Team

Instobill app social image from Zenocta, showing the app icon with the Zenocta Solutions logo

A customer is waiting at the counter, the barcode will not scan, the price on the shelf is different from the price in the notebook, and the stock register says you have three left when the shelf is empty. A billing app has to work in exactly that moment. This is how we built Instobill, our inventory and billing app for small businesses, and the decisions that kept it fast, accurate and simple enough for a busy shop. It prepares invoices and tax figures; it does not give tax advice.

What problem was Instobill built to solve?

Our Instobill case study describes the starting point clearly: small business owners were tracking stock and generating bills manually or with disconnected spreadsheets. The results were stock-outs, pricing errors and time-consuming end-of-day reconciliation, with no real-time visibility into inventory levels.

Notice how those problems feed each other. A bill written by hand does not update the stock register, so stock drifts from reality, so a customer is sold something that is not there, so the owner spends the evening reconciling paper against shelves. The fix is not a better bill book or a better stock book. It is making the bill and the stock the same event. When you sell something, the stock moves. That one idea is the heart of the app.

We cover the day-to-day version of this problem in billing and inventory software for small retailers. This article is about what we did to solve it.

Who is Instobill for?

The case study says small businesses, and its FAQ adds that the structure can be tailored for grocery, pharmacy, electronics or general retail stock patterns. The Google Play listing is broader: shops, wholesalers, freelancers and small businesses in any country, working on phone, tablet or the web.

The audience shaped two decisions. First, speed: a shop owner serving a customer has no patience for a slow screen. Second, flexibility: businesses in different countries use different tax systems, currencies and document types, so the app needed to adapt rather than assume one set of rules.

The approach and decisions behind the build

Barcode scanning in both directions

According to the case study, barcode scanning speeds up both stock entry and checkout. That is worth stressing: the same camera that rings up a sale is used to add stock. It means one skill, one habit and one piece of hardware, the phone camera, covers two jobs. The technical challenge was making barcode scanning and stock updates reliable and fast enough for real-time use at the point of sale.

Let the app do the tax arithmetic

Billing automatically applies tax calculations so owners can invoice accurately without manual math. The current listing extends this with country and currency choice, and tax presets as a starting point, with a custom option for anyone whose country is not on the list. We are careful with the wording here: presets are a starting point and the app does not file returns. Anyone using it should check the rules for their country.

Mobile-first, and friendly to bad connections

The case study describes Flutter for a mobile-first, offline-friendly interface, with Firebase (Firestore, Authentication, Cloud Storage), barcode scanning through the device camera, and local plus cloud sync for inventory data. Shops do not always have a reliable connection, so we treat the ability to keep working as part of the product, not a technical nicety. You can read more about how we weigh Flutter against other approaches in Flutter vs native app development.

Keep the interface fast and plain

The user experience challenge in the case study is stated as keeping the interface fast and simple enough for busy shop owners to use during live customer transactions. Live is the operative word. A screen that is fine at a desk can be slow when someone is waiting.

How do the features fit together?

7document types, from invoices to debit notes
5PDF templates
140currencies across about 200 countries
Part of the appWhat the listing describes
Billing and documentsInvoices, quotations, proforma invoices, sales orders, delivery challans, credit notes and debit notes; a quotation becomes an invoice in one tap; recurring invoices; returns that put stock back and issue a credit note
Getting paidFull or partial payments, receivables with ageing, customer statements, payment status on every invoice
StockProducts and categories, barcode and QR scanning, low-stock and expiry alerts, several locations, transfers, adjustments with reasons, stock counts, CSV or Excel import, variants, printable barcode labels
Reports and exportProfit and loss, tax summary, sales by day, category and payment method, top customers, expenses, receivables ageing, export to CSV, Excel, PDF, Word or JSON, an accountant pack and a full backup
Smart assistantPlain-words questions answered from your own records, draft quotations from a typed or spoken order, supplier bill scanning, reorder suggestions and unusual-invoice alerts
TeamAdmin and staff roles, so staff can bill without seeing your profit

The relationships matter more than the list. A sale reduces stock; a return puts it back and issues a credit note; a payment updates what the customer owes; a report reads all of it. Because those steps share one record of each product and each invoice, nobody has to reconcile one against another at the end of the day.

How has the product grown since the case study?

The case study lists future scope: multi-outlet inventory sync, supplier and purchase-order management, and sales analytics with best-seller reporting. The current listing shows that several of these themes have since appeared in some form, such as several locations with stock transfers, receiving goods, and sales reports with fast and slow sellers. We say "in some form" on purpose, because the listing and the case study are different documents and we do not want to overstate either.

The listing's latest update notes also show the kind of small, practical changes that matter at a counter: the billing cart now stays when you move to another section and come back, a bill can be downloaded as an image to share, and a product name can be used only once in a shop so there are no duplicate products. On the web, hovering over a cut-off name reveals it in full.

What we take from this

Small fixes like "the cart stays when you leave and come back" are the difference between an app that is tolerated and one that is trusted at the counter. Plan time after launch for exactly this kind of detail.

Which mistakes does this kind of app help you avoid?

The case study names the mistakes it targets: stock discrepancies, pricing errors and tax errors that come from manual, paper-based billing. We would add the quieter ones we see when owners first move to software.

  • Importing messy product lists. Duplicate names and inconsistent categories make every later report harder to trust. Clean the list before you import it.
  • Skipping stock counts. Even good software drifts from the shelf if nobody ever counts. A regular count with a recorded reason for each adjustment keeps the numbers honest.
  • Leaving everyone as admin. If every staff member can see profit and edit prices, a single mistake affects the whole shop.
  • Ignoring returns. A return that does not put stock back leaves the register wrong from that day on.

What would we tell someone building a billing or inventory app?

These are lessons that follow from the decisions above. They are advice, not results.

  • Make the sale and the stock movement one event. Never ask the user to update two places.
  • Test at the counter, not at a desk. Time scanning, search and checkout with a real queue of products.
  • Treat tax as configuration. Offer presets, allow custom rates and tax-inclusive or exclusive prices, and keep the disclaimer that the app does not give tax advice.
  • Plan for weak connections. Decide what must work offline and how data syncs afterwards.
  • Prevent duplicates early. Unique product names and clear import rules save hours of cleanup later.
  • Separate roles. Let staff bill without seeing profit.

A rollout path for a small shop

  1. Load the products. Import from a CSV or Excel sheet, add categories and print or attach barcodes.
  2. Set tax and currency. Pick your country, check the presets against your own records, and confirm with your accountant.
  3. Bill a few real sales. Run it alongside your old method for a short period and compare.
  4. Turn on alerts. Low-stock and expiry alerts, and a reorder habit.
  5. Add staff roles. Give billing staff access without profit figures.
  6. Review the reports weekly. Look at what sells, what is slow and who owes you money.

What is live today?

Instobill is on Google Play and works in the browser with the same account, so it is Android and web. The listing says to start with a free trial and that paid plans unlock more; we repeat only that. It also notes that Instobill helps you prepare invoices and tax figures but does not file tax returns or give tax advice. See the Instobill app page, or browse more Zenocta apps. If you want the owner-level view of what this solves, our post on GST billing software for small business is a useful companion.

How do you get a similar product built?

If you run a shop, a wholesale counter or a service business with stock, we can build billing and inventory around your categories, tax setup and workflow. We start with how you bill and count today, agree a first release, and send a scoped, fixed-price proposal before any work begins. For the wider case, see how MSMEs can reduce costs through digital transformation. When you are ready, contact Zenocta and describe your counter.

Try it live

Open the real thing: demos run in a new tab with sample data, apps link to their own page.

Frequently asked questions

  • 01Can Zenocta build a custom billing or point-of-sale app for my shop?

    Yes. Zenocta builds custom inventory, billing and point-of-sale apps for small and medium businesses. We start with how you bill and count stock today, then send a scoped, fixed-price proposal before any work begins.

  • 02What technology is Instobill built with?

    Instobill is built with Flutter and Firebase, including Firestore, Authentication and Cloud Storage. Barcode scanning uses the device camera, and inventory data uses local plus cloud sync so the app can stay usable on weak connections.

  • 03Can the app be tailored to a retail category?

    The case study says the inventory and billing structure can be tailored for grocery, pharmacy, electronics or general retail stock patterns. The categories, tax set-up and documents are shaped to your business, and the scope is agreed in the proposal.

  • 04Does Instobill give tax advice or file returns?

    No. The Play listing says Instobill helps you prepare invoices and tax figures, but does not file tax returns or give tax advice. Tax presets are a starting point, and you should check the rules for your country.

  • 05Which platforms and plans does Instobill have?

    Instobill is on Google Play for Android and works in the browser with the same account. Zenocta apps are Android and web only. The listing says to start with a free trial and that paid plans unlock more.

0% read ·

Get new guides in your inbox

Practical notes on billing, payroll, apps and AI for growing businesses, written from what we build. No spam.

We email occasional guides. Unsubscribe any time: reply to any email or write to contact@zenocta.com.

Ready to build something real?

Website and app development from ₹8,888. Book a free consultation and get a scoped, fixed-price proposal within 24 hours.