Skip to main content
// ARCHITECTURE CASE STUDY

TrackStock

“Inventory and branch operations, connected from daily counts to delivery receipts.”

Category
Full-Stack Web
Role
Solo Developer
Timeline
Ongoing development
Status
In Business Use
The Problem & Bottleneck

Coordinating stock across HQ and branches means keeping daily counts, requests, dispatches, and delivery receipts in context. Missing quantities, repeat submissions, and corrected counts need to remain distinguishable so staff can review the record.

The Engineered Solution

I designed and built TrackStock around the handoff between HQ and branch staff: role-aware access, daily stock counts, supply requests, dispatch tracking, delivery receipts, and reviewable corrections. The system preserves the difference between an unknown quantity and an explicit zero, and handles repeated submissions without posting the same action twice.

// SYSTEM ARCHITECTURE BLUEPRINT

Event Pipeline & Data Flow

Next.js / React interface → authenticated server routes → Supabase PostgreSQL commands → inventory and audit records → HQ and branch views.
01
Branch Updates

Branch staff check in, record stock counts, and request supplies through their assigned workspace.

02
Validated Commands

Server and database checks enforce access, expected revisions, and consistent handling of retried submissions.

03
Supply Handoffs

HQ reviews requests and dispatches; branch receipts keep delivery and discrepancy states separate.

04
Reviewable Records

Inventory views retain observation context and correction history for HQ and branch review.

// PROJECT HIGHLIGHTS
Solo-built and used in business operations
Highlight 01
Connected HQ and branch inventory workflows
Highlight 02
Recorded demo and actual app screenshots available
Highlight 03
Tools & Technologies
Next.jsReactTypeScriptSupabasePostgreSQL