Ticket Ordering & Approval System

Overview

Ticket Ordering & Approval System is an internal ordering platform built for a logistics and transportation company. It manages the full lifecycle of a production order: from the initial request, through multi-layer approval, into production, until the finished order is returned to the requester as inter-unit entities. The system centers on a complex RBAC model and advanced form creation so requesters can compose accurate orders without friction.

The Problem

Production requests at the company were handled across manual, disconnected steps with no reliable way to enforce approval order or track where an order stood. Different units needed different levels of access, and requesters had to fill in orders accurately without a guided form, which caused rework and delays before production could start.

My Role

I was the sole developer, owning requirements, data modeling, and implementation. The core challenge was modeling an order as an entity that moves between units, enforcing multi-layer approval before production can begin, and building an RBAC layer granular enough for different unit roles while keeping the order form easy to use through advanced form creation.

Process

I modeled an order as an entity that moves between units, from the first request through multi-layer approval into production, until the finished order returns to the requester. I built RBAC granular enough for each unit role and used advanced form creation so requesters can compose accurate orders without friction.

Key Features

1. 01End-to-end ticket lifecycle from request to return
2. 02Multi-layer approval before an order enters production
3. 03Complex RBAC across unit roles
4. 04Advanced form creation for accurate ordering
5. 05Inter-unit ticket entities that track ownership across steps

Challenges

The hardest parts were enforcing approval order before production can start and keeping ownership visible as an order passes between units. Granular RBAC and a guided form had to stay easy to use while still preventing invalid orders.

Outcome

The system replaced disconnected manual handling with a single tracked flow where every order has a clear approval path and a visible position across units. Production can only start after multi-layer approval, and the RBAC and form layers reduced ordering errors.