Business Management Platform
A unified operations platform replacing four disconnected tools — inventory, billing, staff and reporting — with one system that closes the books in real time.
- Client
- Confidential — Retail & Distribution
- Industry
- Retail & Distribution
- Engagement type
- Product design, full-stack engineering, database architecture, deployment
- Technology
- SvelteKit, PostgreSQL, Node.js +3 more
- Year
- 2025
- Platforms
- Web, Android
01 — Context
Where this started.
The client ran a regional distribution business across three warehouse locations. Inventory lived in a spreadsheet updated twice daily. Invoices were generated in one tool, payments tracked in another, and staff attendance recorded on paper. End-of-month reconciliation took three days and involved a finance team and a warehouse manager working from separate exports that frequently disagreed.
02 — Challenge
The hard part.
The challenge was not building software — it was consolidating the ground truth. Each existing system had become the authoritative source for a slice of the business, and staff had built workarounds that depended on the gaps. A replacement had to be more reliable than the workarounds from day one, or adoption would fail.
03 — Strategy
What we decided.
We mapped every manual process and every data handoff before writing a line of code. The architecture decision that made the rest tractable was treating inventory movements as the primary event stream: every sale, purchase order, transfer and adjustment writes to the same ledger. Billing, reporting and stock counts all read from that ledger rather than maintaining their own copies.
04 — Experience
How it works for the person using it.
The operator interface is a single-window design — the most common task at each role is visible without navigation. Warehouse staff see their location's stock and pending receipts. Sales staff see customer accounts, outstanding invoices and payment history. Managers see a live dashboard that updates on every transaction rather than on a nightly job.
05 — Engineering
How it is built.
The backend is a PostgreSQL database with strict transaction boundaries: a sale that would push a product below zero is rejected at the database layer, not caught in application logic. Billing runs as a background worker that generates invoices from confirmed dispatch records rather than a separate data-entry step. The mobile interface for warehouse staff runs as a PWA so no app store deployment cycle is required when the schema changes.
- SvelteKit
- PostgreSQL
- Node.js
- Vercel
- PWA
- Razorpay
06 — Feature stories
The decisions that mattered.
-
Unified inventory ledger
Every stock movement across all locations writes to a single append-only ledger. There is no reconciliation step because all views read from the same source.
-
Automated invoice generation
Invoices are generated from confirmed dispatch records. The sales team issues a dispatch order; the finance team gets an invoice without a separate data-entry step.
-
Role-scoped dashboards
Warehouse, sales and management roles see different data surfaces in the same application. A warehouse manager cannot accidentally alter a billing record; a finance user cannot amend inventory.
-
Real-time reporting
P&L, stock position and outstanding receivables are calculated on the live transaction set. The end-of-month close became a single export rather than a three-day reconciliation.
07 — Results
What we can prove.
- 3 days → 2h
- Month-end close time
- 3
- Warehouse locations on one system
- 0
- Inventory discrepancies in first quarter live
Source: Client operational report, Q1 2026
Source: Client deployment documentation
Source: Client stock audit, Q1 2026
Only verifiable figures appear here. We do not publish uplift percentages or revenue claims we cannot evidence, and we do not restate a client's internal numbers as our own.
08 — Ownership
What was handed over.
At launch, everything below transferred to Confidential — Retail & Distribution. Nothing in this product depends on DevXAI to keep running.
- Full Git repository with commit history
- Infrastructure and store accounts in the client’s own name
- Architecture and deployment documentation
- Walkthrough session with the client’s team
- 30-day post-launch defect warranty
Next project