Every handoff resets the search.
- 01Carrier portal holds one status.
- 02Email holds the exception context.
- 03Spreadsheet holds the customer promise.
- 04Operations reconciles them manually.
Enterprise SaaS · 2025 Case study / Enterprise SaaS · synthetic shipment data
Logistics Track & Trace System.
Enterprise logistics platform that unified fragmented operations into one real-time shipment record, with carrier and warehouse events normalized across every handoff and exception.
TechnologiesReactTypeScriptNode.jsPostgreSQLRedisWebSockets
!Evidence boundary: this public case study demonstrates the architecture and workflow. It does not assert performance outcomes without published baselines.
Shipment event rail · 01Mock network · PH / APAC
Synthetic event stream
Stream · LiveEvery handoff, one trail.
Active shipments09
On-time sample70%
Open exceptions02
PMJ-24089Vehicle exception escalated
Project architecture summaryDemonstrated capabilities from the case study. Mock dashboard values are illustrative and are not project results.
1Normalized shipment record across every handoff
LiveException visibility from event to resolution
6Technologies in the published stack
01 / The operating shift
One record through every handoff.
The interface concept turns fragmented updates into a shared event trail. Operations sees what moved, what changed, and what needs intervention without chasing carrier portals or status messages.
One shipment. One operational truth.
- 01Events normalize into a shared timeline.
- 02Delay risk is visible beside the route.
- 03Every handoff keeps context attached.
- 04Exceptions rise before routine updates.
02 / Interactive product concept
The shipment control tower.
A redesigned demo dashboard · fixed synthetic dataset · no account connection. Filter the manifest, pick a reference, and read its milestones and event trail.
Status view
Visible shipments10mock records
Active09not delivered
On-time70%delay ≤ 2h
At risk03watch + exception
Exceptions02delay > 8h
Shipment manifest
10 recordsEvery reference, one row
| Reference | Lane · Mode | Status | Progress | ETA / Actual | Delta |
|---|---|---|---|---|---|
Manila → CebuSea | In transit | Aug 14 · 16:30 | On time | ||
Shenzhen → ManilaSea | Exception | Aug 15 · 11:00 | +9h | ||
Davao → Cagayan de OroRoad | Out for delivery | Aug 13 · 18:40 | +1h | ||
Singapore → ManilaAir | Arrived hub | Aug 14 · 09:15 | On time | ||
Cebu → IloiloSea | Watch | Aug 15 · 14:20 | +4h | ||
Manila → BatangasRoad | Delivered | Aug 13 · 10:12 | -1h | ||
Hong Kong → ClarkAir | Linehaul | Aug 14 · 05:50 | +2h | ||
General Santos → ManilaSea | Port loading | Aug 17 · 20:00 | On time | ||
Subic → LagunaRoad | Exception | Aug 14 · 19:30 | +13h | ||
Bangkok → CebuAir | At origin | Aug 15 · 07:30 | On time |
Selected shipment
Inspector
In transit
PMJ-24081
Manila → CebuModeSea
CarrierIsland Freight
ETA / ActualAug 14 · 16:30
ETA deltaOn time
- BookedEvent confirmed
- Origin gateEvent confirmed
- LinehaulEvent confirmed
- Destination hubIn transit
- DeliveredAwaiting event
- Position event received · Verde Passage
- Linehaul milestone confirmed
- Departed Manila South Harbor
Selected · PMJ-24081Selected PMJ-24081, synthetic shipment from Manila to Cebu. In transit with 72% progress.Synthetic data · not a live carrier integration
03 / Signal architecture
Events in. Exceptions out.
A conceptual view of how the published stack can turn source events into an operations-ready interface. This diagram demonstrates product logic, not production architecture verification.
Carrier & warehouse events
Scans, milestones, proofs, and exception updates enter the record.
API · EDI · WebhookNode.js event gateway
Inputs are validated and normalized into one event language.
Node.js · TypeScriptShipment state
Current state and event history stay joined to one reference.
PostgreSQLFast state updates
Operational changes reach connected views without a manual refresh loop.
Redis · WebSocketsException-first UI
Routine movement stays quiet; delayed handoffs move to the top.
React04 / Published technology stack
Six pieces. One operating surface.
The stack below is retained exactly from the live project page. The role descriptions explain the redesign concept and should not be read as audited implementation details.
React
Operations interface and shipment inspection views.
TypeScript
Typed event contracts across interface and services.
Node.js
Service layer for ingestion and integrations.
PostgreSQL
Shipment state, history, and relational records.
Redis
Fast access to operational state and event coordination.
WebSockets
Connected status updates across the control tower.
Release 07 / 07 · Enterprise SaaS · 2025 · Last in the series Back to all releases
Pixelmojo · AI product studio
Operations that see every handoff.
Fragmented status is a design problem before it is a data problem. Bring us the workflow and the events behind it.