e-way

A management system for a shipping company: job orders, sales and purchase orders, invoices, payments and an approval chain.

Type
Personal projects
Stack
Laravel
Role
Developer.

The problem

Shipping paperwork moves through several hands, and an invoice that disagrees with its job order is a real dispute.

What I decided

  1. Tied every invoice back to the job order it bills, so a mismatch surfaces at creation instead of at payment.
  2. Made approvals explicit states (approve, cancel, confirm, paid) rather than a free-text status.

Where it landed

Invoice and job-order reporting with PDF output, on a schema built from the client's own design.

All projectsNext project: Essense Luxe

Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.