SYSTEM / 003

KapdaBook

Textile business management SaaS demo that brings inventory, suppliers, purchases, sales, alerts, reports, and catalog sharing into one focused dashboard.

Inventory modelSupplier flowsReportsProtected routesBilingual foundation
KapdaBook interface

Context

What this system is

Small and mid-sized textile businesses often manage stock, supplier payments, and sales through notebooks, WhatsApp, and spreadsheets. KapdaBook translates those workflows into a practical dashboard for tracking products, fabric details, supplier dues, sales, purchases, low-stock alerts, and seasonal planning.

Ownership

What I was responsible for

This is a self-directed system — I owned the architecture, engineering, and product decisions end to end.

Architecture · Engineering · Product

The Problem

What made it necessary

Small and mid-sized textile businesses often manage stock, supplier payments, and sales through notebooks, WhatsApp, and spreadsheets.

Architecture

How it's structured

  1. 01

    Role-focused dashboard structure with quick actions for adding stock, recording sales, viewing alerts, and sharing catalogs.

  2. 02

    Textile-specific inventory model that accounts for product variants, stock quantity, fabric type, design number, pricing, suppliers, and seasonal demand.

  3. 03

    Protected demo routing with local authentication and shared app state so dashboard, inventory, reports, alerts, and catalog views stay coherent.

Engineering Decisions

What shaped the system

  1. 01

    Componentized UI sections make operational areas such as inventory, suppliers, purchases, sales, alerts, and reports easier to extend independently.

  2. 02

    Mock business data is shaped around backend-ready entities, keeping the frontend demo close to a future database-backed implementation.

  3. 03

    Reports and charts separate business insight views from transactional screens so analytics can evolve without crowding daily workflows.

Trade-offs

What was optimized for

Used local demo authentication and mock data to keep the portfolio demo lightweight while still showing realistic product flows.

Prioritized textile-specific workflows over a generic inventory layout, which makes the app more useful for its target business domain.

Outcome

Domain-specific workflows and centralized state keep inventory, sales, and reports consistent across routes.

More Systems

Related systems

BuilderOS screenshot
Real Estate

BuilderOS

Convert more real estate leads using AI-powered follow-ups and inventory matching.

SuratEstate screenshot
Real Estate

SuratEstate

Help buyers explore localities, projects, and properties with a guided search experience.

ClinicAI screenshot
Healthcare

ClinicAI

Run appointments, patient context, consultations, and clinic operations in one place.