Why a second counter breaks paper books
It is 10 PM. You still do not know what the other counter sold today — unless you call someone who may have already gone home. That call is not a system. It is memory, a screenshot, and hope the notebook matches.
Paper books and one-phone billing apps break when the second shop starts selling the same SKUs on credit. Each counter keeps its own khata fragment. Stock "available" at yard A is already committed at yard B. The owner becomes the integration layer — walking between counters, merging WhatsApp totals, guessing outstanding.
One ledger means stock, sales, and udhaar roll up or filter by shop without reconstructing the day from chats. You stop being the nightly switchboard.
The 10 PM call you should not need
Picture the usual end of day: shop one closed the register in a notebook; shop two used a billing app on one phone; udhaar for a builder sits in a diary at home. You call to ask "kitna bik gaya?" and "Ram babu ka balance kya hai?" The answers are approximate because no single record saw both counters.
MaterialOS is built for that fracture. Same product from day one: when you have one yard, you run one shop on Starter. When the second counter opens, you add a shop on Growth or Pro — same login, same customer list, same SKU catalog, filtered or rolled up.
The Kolkata two-shop origin is public. We shaped the product inside a real multi-location business — not a slide that said "multi-branch" without credit and stock in the same breath.
What MaterialOS does on day one
MaterialOS ships a multi-shop ledger from day one: share or filter stock and credit across locations on web or phone after sign-in. Starter covers one shop; Growth covers up to three; Pro removes the shop cap.
You do not need two shops to start. One yard on Starter is fine. The same product is ready when the second counter opens — that is the point of "multi-shop from day one." You are not asked to migrate later to a "business" SKU.
Building-materials dealers feel this first: cement and steel move across yards, and builders buy on credit from whichever gate is closer. Read the beachhead page for building-materials dealers if that is your trade. Signup today opens that vertical only; other trades show as coming soon.
Staff assignments keep the counter simple. Sales and inventory roles see their shop; owner, manager, and accountant move across shops when they need the full picture.
Filter versus rollup
Rollup answers "how did the business do today?" — total sales, total outstanding, stock across all locations. Filter answers "what happened at shop STL?" — that counter's bills, that yard's movement, that shop's udhaar exposure.
Owner, manager, and accountant can switch between those views without exporting three CSVs to reconcile at home. Sales and inventory staff stay on their assigned shop so they are not distracted by another yard's numbers while a customer waits.
Fourteen reports sit on the same ledger — including shop-wise profit and customer outstanding — so multi-shop is not a reporting bolt-on. Customer credit is one party record even if they buy from two gates; stock is one SKU catalog even if quantity splits by location.
When a builder pays partially, FIFO allocation applies against open invoices on the ledger they share. You are not merging two notebooks to see what is still due.
Transfer between shops — when you physically move bags from yard A to yard B — should show in stock at both filter and rollup. Owner sees total cement; each yard manager sees only their bin. That is the same ledger doing two questions, not two apps synced by you at midnight.
Growing from one shop to two
Most owners start with one location on Starter. Billing habit matters more than shop count on week one. When the second gate opens, you add a shop record — same customers, same SKUs, new filter.
Staff invites follow the same pattern: sales at yard A never need yard B clutter on their phone. Owner and manager see both. Accountant exports rollup for the CA and filter when reconciling a single gate dispute.
Credit limits apply to the customer, not the shop gate. A builder who buys from both yards has one outstanding headroom — the hard stop at billing works no matter which counter serves them.
Day-one on multi-shop still follows the leave-paper checklist: bills and udhaar before perfect stock at both yards. One shop or two, the order is the same — only the filter view changes.
Shop-wise profit among the 14 reports answers which gate earns — after billing habit exists. Do not wait for perfect margin analytics before you stop the 10 PM reconciliation call.
Same builder, two shops, one phone call: with one ledger you open rollup outstanding before you dial — not after someone reads a diary by torchlight.
Pro trial lets you model two shops before you pay — add a second location in setup, split staff, run filter and rollup for a week. No card required on MaterialOS pricing.
What this is not
This is not a freemium solo billing app. It is a paid ledger for shops leaving paper, with staff and multi-shop controls when you need them. Compare that wedge on MaterialOS vs Vyapar if you are leaving a one-phone setup.
MaterialOS is not a full Tally replacement. Desktop books can stay with your CA while the counter runs on phone. GST registers export for handoff; return submission stays with the accountant.
There is no permanent free plan. Try Pro free for 30 days with no credit card on MaterialOS pricing: Starter ₹799/mo, Growth ₹1,799/mo, Pro ₹3,499/mo — prices exclude GST (+ 18% GST at checkout). After trial, read-only access remains; new sales pause until you choose a plan.
We built MaterialOS because calling the other shop at 10 PM is not a system. Two counters need one ledger the owner can open on any phone.