Overview
Toleron Logistics is an API-first shipment tracking and management system built to give customers real-time shipment information while providing administrators with tools to manage shipments and tracking events.
The Problem
Toleron needed more than a basic tracking page. A shipment needed to have a unique tracking ID, current status, location, estimated delivery, and a complete history of what happened along the way. The admin side also needed to create shipments, update their progress, and manage tracking information without manually editing website content.
Approach
I built the backend as a custom WordPress plugin and exposed the system through REST APIs. Rather than storing shipments as regular WordPress content, I created dedicated database tables for shipments and their tracking events. This gave the system a structure that made more sense for logistics data. The frontend could then communicate with the backend through the API while WordPress handled the underlying data and management operations.
Development
Shipment Tracking Every shipment receives a unique tracking ID, such as TLN-8F23K9. Customers can use that ID to retrieve the shipment's current status, location, estimated delivery, recipient details, and tracking history. Tracking Timeline Instead of overwriting the shipment every time something changes, each update is stored as an individual event. An event can contain a status, location, note, timestamp, and proof image. The API then turns those events into a chronological tracking timeline for the frontend. Admin Management Admins can create shipments and add new tracking events through protected API endpoints. Creating a shipment automatically generates its tracking ID and creates the initial tracking event. When a new event is added, the system updates the shipment's current status and last known location while keeping the event in the historical timeline. Proof of Delivery For delivered shipments, the system can also accept a proof-of-delivery image and attach it to the tracking event.
Challenges & Fixes
One of the key decisions was figuring out how to represent shipment history properly. A single shipment record could store the current status, but it wouldn't be a good place to keep every update that happened throughout the delivery. I separated the data into two parts: *shipments* for the current state of the shipment. *events* for its tracking history. Whenever an event is added, the system records the history and updates the shipment snapshot at the same time. That gave us both a clean current status and a complete timeline.
Outcome
Toleron became a dedicated shipment tracking system rather than a simple tracking webpage. The system handles shipment creation, unique tracking IDs, live status information, historical tracking events, proof of delivery, and admin management through a custom API-first backend.
Gallery
/