Product overview

One connected flow for everyday shop work.

BillCountr connects the bill, stock movement, customer due and final report so staff do not repeat the same work across disconnected tools.

Primary surface

Android app for daily shop work

Owner surface

Web dashboard for control and reports

Core workflow

Bill → stock → ledger → report

Connectivity

Local-first work with silent sync

What you need to know

Clear details, without the jargon.

01 · Billing

Create the right kind of bill

Start with a walk-in sale or select a customer, search or scan products, adjust quantity, and choose how the customer pays. A finalized bill becomes the source for its invoice output, stock movement, ledger effect, report facts and audit history.

  • GST-compliant invoice or simple estimate
  • Cash, UPI, partial payment or udhaar
  • Discounts and additional charges when enabled
  • Print or share from the finalized snapshot

02 · Stock

Know what is available now

Products carry the practical details a shop needs—SKU, barcode, category, unit, selling price, current quantity and low-stock threshold. Sales, purchases and adjustments feed one movement history.

  • Units such as kg, pcs and boxes
  • Low-stock visibility from minimum quantity
  • Configurable temporary negative stock
  • Recoverable deletion where recycle-bin rules apply

03 · Customers

Keep customer history useful

Customer records connect contact details, area, finalized purchases, payments and open dues. The history answers both what a customer bought and which invoices still need settlement.

  • Customer purchase history from invoice snapshots
  • Area or city tags for collection routes
  • Paid, due and cancelled bill visibility
  • Customer-scoped ledger and balance

04 · Udhaar

Settle the bill that was actually paid

A received payment can be allocated to one or more selected unpaid invoices. BillCountr reduces each invoice’s open due through appended ledger entries without rewriting the original invoice.

  • Manual invoice-specific allocation
  • Partial settlement across selected invoices
  • Remaining due stays visible per invoice
  • Printable or shareable payment receipt

05 · Suppliers

Connect incoming stock to its source

Supplier profiles and purchase records support the other half of stock movement. A received purchase increases inventory and keeps the source visible for later review.

  • Supplier contact information
  • Purchase and stock-receiving records
  • Unit and quantity validation
  • Audit history for sensitive adjustments

06 · Reports

Review facts instead of recalculating bills

Reports aggregate the stored facts produced when a bill is finalized. This keeps sales, tax, paid amount and due amount consistent with the invoice the customer received.

  • Daily, weekly and monthly sales views
  • Stock, movement, tax and due reports
  • Filters by date, category, area or staff where relevant
  • PDF and spreadsheet-ready exports

07 · Control

Show each person only their work

Owners, managers, cashiers and auditors get role-appropriate navigation and actions. Organization feature toggles remove unused complexity while the API enforces the same restriction.

  • Named roles and granular permissions
  • Feature toggles for optional workflows
  • Shop, tax, billing and invoice settings
  • Immutable audit records for sensitive actions

08 · Surfaces

Use the right screen for the job

The mobile app is the primary retail interface for billing, stock, ledger and offline work. The web dashboard is the owner’s desk for reports, settings, staff, imports, exports and deeper review.

  • Fast Android-first counter experience
  • Browser POS where needed
  • Web administration and reporting
  • Shared calculations and domain language

Common questions

Quick answers.

Is BillCountr an accounting ERP?

No. BillCountr is a focused retail operating system. It records the billing, stock, payment, udhaar and report facts needed to run the shop without exposing an accounting-heavy ERP workflow.

Does BillCountr process UPI or card payments?

No. It records payment modes such as cash, UPI, partial and udhaar. Payment-gateway processing is outside the current product scope.

Can a small shop hide features it does not use?

Yes. Organization-level feature toggles are designed to hide disabled complexity in the interface and block the same capability in the API.

Do old invoices change when settings change?

No. Finalized invoices keep their calculation and settings snapshot. Later setting changes affect new work, not the historical bill the customer received.

Ready for daily shop work

Enter your shop in one step.

Sign in to your shop