AA

Vult Media · Professional work

01 2024—Now In production

Enterprise logistics systems

Co-architecting and shipping correctness-critical workflows across a large 3PL platform—from order approvals and warehouse verification to runtime billing rules.

Project record

1.5M+ line platform
23K+ line workflow owned
30+ integration suites enabled
4 production systems
  • TypeScript
  • React
  • Tailwind CSS
  • shadcn/ui
  • Express
  • ElysiaJS
  • TanStack Query
  • TanStack Router
  • Drizzle ORM
  • Better Auth
  • SQL
  • MongoDB
  • RabbitMQ

01 / Ownership

The part I owned

I co-designed backend conventions that still govern the platform, then fully owned several of its hardest modules across product modeling, APIs, UI, database behavior, and test infrastructure.

02 / Engineering decisions

What made the system hold together.

01

Keep the server authoritative

Warehouse receiving is turn-based and operationally sensitive. Every step revalidates current state on the server rather than accepting the browser's version of reality.

02

Make billing rules data-driven

Conditional charge formulas and per-client rate-card overrides are evaluated at runtime, keeping complex commercial rules explicit instead of scattering them through application branches.

03

Build testing as shared infrastructure

Factories, seeders, and orchestrators let multiple domains assemble credible integration scenarios without re-solving setup for every suite.

03 / Outcome

What exists now

The work supports a 100+ employee logistics operation across three warehouses while giving the engineering team shared contracts, safer state transitions, and repeatable integration-test foundations.

Note — Client and product details are intentionally generalized; the engineering scope and metrics are retained.

Next case study · 02 Rizmi