SN

Operational Platform / Full-Stack Ownership

Sales & Inventory Management

I built and deployed an end-to-end operating system for my family distribution business, connecting products, stock movement, retailers, sales, collections, returns, reports, roles, and production maintenance.

Live system Frontend repo Backend repo Operational Platforms

3

months from scratch to live

INR

3L+ sales tracked

65K+

inventory units managed

Live

users in daily operations

Context

What existed before my work

This is the product and technical situation I was responding to, not just a list of tools.

The business needed more than a spreadsheet. Sales, stock, retailers, collections, returns, warehouses, and reports had to connect in one dependable operational platform.

Because this system serves real users inside a family distribution business, I had to think like the engineer, product owner, operator, and production maintainer at the same time.

System Map

How the work connects

I want each project page to show the system, not only describe it.

01

Product catalog

SKU, price, case pack

02

Inward stock

Supplier, invoice, warehouse

03

Inventory ledger

Balances, batches, movement

04

Retailer sale

Stock lookup, route, sale items

05

Collection

Payments, splits, outstanding

06

Reports

Trends, monthly overview

Production usage

Live internal system at distribution.bimari.org

Business scale

INR 3L+ sales tracked and 65,000+ inventory units managed

Ownership depth

Product, database, APIs, frontend, deployment, and maintenance

My Ownership

Exactly what I owned

These are grouped by responsibility so the case study reads like real product ownership, not scattered bullet points.

Product and workflow design

  • Mapped the business flow from product catalog and inward stock to sales, collection, returns, and reporting.
  • Designed the application around real operational tasks instead of generic CRUD screens.
  • Built a role-aware dashboard experience for users who need fast entries and clear visibility.

Full-stack engineering

  • Built the React frontend, routing, protected screens, forms, tables, charts, alerts, and operational UI components.
  • Built the Express backend with authentication, JWT protection, role checks, controllers, services, validation, and SQL access.
  • Designed and implemented the SQL data model for products, suppliers, warehouses, inventory balances, batches, stock ledger, inward receipts, sales, returns, reports, users, roles, routes, retailers, and refrigerators/assets.

Deployment and stewardship

  • Deployed the system live at distribution.bimari.org and continue to maintain it.
  • Handled production setup, database setup, security-sensitive authentication flows, and ongoing improvements.
  • Use live operational feedback to refine workflows, reports, and data quality.

Key Modules

The parts of the system that carry the story

Each module is a concrete proof point: product surface, backend, integration, workflow, or leadership responsibility.

Product catalog and inventory core

I built product management, warehouse-aware inventory balances, inward receipts, batch handling, stock ledger movement, and update flows so stock data can remain coherent as the business operates.

ProductsWarehousesInventory balancesStock ledger

Inward stock workflow

The inward flow captures supplier, warehouse, invoice, item, quantity, and damage-related data so incoming inventory becomes traceable instead of disappearing into manual notes.

SuppliersInward receiptsBatchesData integrity

Sales and collections

I built sale creation, stock lookup, retailer information, payment split/collection, sale history, sale details, payment updates, and return handling around real distribution workflows.

SalesPaymentsCollectionsReturns

Retailers, routes, and assets

The platform includes retailer search/creation, route assignment, profile operations, and refrigerator/asset tracking, which gives the system operational depth beyond product and sale screens.

RetailersRoutesAssetsOperations

Reports and trends

I implemented sales reports, monthly overview, trend views, and chart-driven summaries so the business can see performance instead of only recording transactions.

ReportsTrendsChart.jsMonthly overview

Auth, roles, and production control

I built login/register, JWT-protected routes, bcrypt password handling, role-based checks, and protected frontend routes to make the platform usable as a real internal system.

JWTbcryptRolesProtected routes

Hard Problems

Constraints, tradeoffs, and fixes

This is where the case study becomes credible: what was difficult, and how I responded.

Operational software has to match the business, not the other way around.

I modeled the system around product movement, retailer sales, collections, returns, routes, and reports so the platform follows the actual distribution workflow.

Inventory accuracy depends on every transaction path.

I connected inward receipts, stock balances, sale creation, returns, batches, and ledger-style movement so inventory can be reasoned about from multiple angles.

A live internal tool needs production stewardship after launch.

I deployed the system, maintain it in production, and keep improving workflows based on real operational usage.

Leadership

What I carried beyond code

This project shows ownership without a large team: I carried product thinking, architecture, engineering, deployment, and maintenance end to end.

I translated business operations into software architecture, which is a different kind of leadership than managing engineers but just as important for product judgment.

Because the system is live in my family business, I am accountable for reliability, usability, and production continuity.

Lessons

What this proves about how I think

The best internal tools are not small apps; they are operational systems with data integrity, role design, reporting, and maintenance responsibilities.

Building for family-business operations sharpened my ability to move from real-world ambiguity into structured software.

This project broadens my portfolio beyond Amealio by proving independent end-to-end execution in a live production environment.

Stack

Technologies and integrations

React 19React RouterTailwind CSSFramer MotionChart.jsAxiosExpress 5MySQLTiDB-style SQLJWTbcryptZod

Next

This is the level of ownership I want to keep building from.

My strongest work happens when I can move across product, engineering, integrations, and AI workflows with real responsibility.

Back to projects