From two Kolkata counters to a retail OS we operate

MaterialOS started as the operating system for a family-run building materials supplier in Kolkata: two shops, daily counter sales, and udhaar that could not wait until month-end. That pattern shows up across India. Paper registers and single-user phone apps work until staff join, a second shop opens, or the owner needs stock, sales, and customer credit in one place without calling someone at the other counter. Low stock surfaces at billing time. Udhaar sits in notebooks, WhatsApp, and memory. Vyapar fits one person on one phone. Tally lives on a desktop. Teams with staff on multiple phones needed something else.

The hard part was not an inventory screen. It was drawing a day-one boundary for a shop OS: stock truth, sales, purchases, suppliers, udhaar, GST invoices, and multi-shop reporting, without drifting into a generic ERP. We also had to lock rules that only show up under real use: what staff can see (purchase cost hidden from billing staff), when owner approval fires (below-margin sales, credit over limit), FIFO payment allocation instead of manual khata fixes, and which capabilities sit on Growth and Pro (per-customer pricing, expense tracking, approval workflows). Vague boundaries would have meant rework once shopkeepers ran day-one ops.

• Live product at materialos.in with Starter (1 shop, 3 staff), Growth (3 shops, 8 staff), and Pro (unlimited shops and staff) plans
• Core retail workflows: stock, sales, purchases, udhaar, GST invoicing, and 14 reports
• Five roles, margin and credit approval flows, FIFO collections, and tier-gated per-customer pricing
• 30-day Pro trial with every feature unlocked and no credit card; after trial, read-only access until subscription via Razorpay on web
• Android app for counter billing and Bluetooth thermal printing; A4/A5 invoices from browser
• Vertical-ready positioning for building materials, kirana, pharmacy, and electronics retailers