MRM MRM MRM MRM
SYSTEM BOOTING
Let's talk
Back to projects
Software Engineering

DistribuTrack Pro — Distribution Management System

An enterprise-modeled distribution management platform with a Qt GUI and JSON persistence, scoring top 5% in academic evaluation.

Difficulty — advanced Complexity — 8/10 Category — Software Engineering
assets/projects/distributrack.jpg
assets/projects/distributrack-2.jpg
assets/projects/distributrack-3.jpg

Overview

A full-scale distribution management system modeled after real industrial supply chains like Coca-Cola and Unilever, built to demonstrate production-style software architecture rather than a toy coursework app. It covers the entire operational pipeline — inventory, ordering, delivery, billing and staff — behind a responsive Qt interface.

Architecture

A multi-layer modular architecture with a Singleton-controlled central system core, coordinating independent subsystems (warehouse, orders, delivery, billing, staff) through well-defined interfaces, backed by JSON-based persistent storage.

Key Features

  • FIFO-based warehouse inventory control ensuring correct stock rotation.
  • Automated order-processing pipeline from placement through fulfillment.
  • Dynamic delivery-agent assignment logic.
  • Integrated billing engine and staff management, including commission/attendance-based salary calculation.

Development Process

  • Modeled the domain first — warehouse, orders, delivery, billing, staff — before writing any GUI code.
  • Applied full OOP (encapsulation, inheritance, polymorphism, composition) to keep subsystems independently testable.
  • Used the Singleton pattern for centralized control modules that multiple subsystems needed to reference safely.
  • Layered the Qt GUI on top of the completed domain logic rather than mixing UI and business logic.

Challenges & Solutions

Challenge

Coordinating five interdependent subsystems (warehouse, orders, delivery, billing, staff) without tight coupling was the central architectural risk.

Solution

Enforced clear module boundaries and used Singleton-controlled central modules only where genuinely shared state was required.

Challenge

JSON-based persistence needed to stay consistent across orders, inventory, staff and transactions without a database engine.

Solution

Structured the JSON schema deliberately around the same domain boundaries as the code, keeping reads/writes predictable.

Results & Impact

The system was recognized in the top 5% of academic performance evaluations for architectural completeness and real-world applicability — validation that the design choices held up under scrutiny, not just functional testing.

Future Improvements

  • Migrate JSON persistence to a proper embedded database.
  • Add role-based access control for staff accounts.
  • Build reporting/analytics dashboards on top of the existing data layer.