Freight Procurement and Transport Logistics Platform is a case study about a multi-layer system where the team delivered a shipper portal, a carrier portal, an admin layer, realtime auctions, transport document workflows, carrier KPI tracking, claim-related processes, notifications, and analytics for freight procurement and logistics operations.
This project is presented in a generalized form. Some details and identifying elements are intentionally omitted due to confidentiality requirements and NDA restrictions.
Freight procurement, realtime auctions, and logistics in one platform
The business needed more than a basic freight request form. It required one connected environment where carrier procurement, trip allocation, transport documents, KPI, notifications, claims, and logistics analytics worked together.
As a result, the team delivered not a single logistics interface, but a connected freight procurement platform with multiple operational layers, a dedicated realtime bidding engine, and asynchronous processing for integrations and document flows.
Project Context
The company needed a platform where shippers, carriers, and internal users could work within connected workflows for freight procurement and transport logistics. The goal was to unify auctions, trip allocation, transport documents, KPI tracking, reporting, and internal operational control in one digital system.
Particular attention was paid to the stability of the bidding layer, the transparency of participant actions, and the operational control of logistics workflows under sustained load.
What Was Delivered
Shipper Portal
A dedicated shipper portal was implemented to manage freight requests, launch procurement flows, monitor trip allocation, work with documents, and review KPI and analytics data.
- creation and management of freight requests;
- carrier procurement workflows;
- trip status monitoring;
- transport document handling;
- carrier KPI and analytics;
- claims-related scenarios and performance dashboards.
Carrier Portal
A separate carrier workspace allowed participants to join procurement and auction workflows, receive trips, handle documents, and track operational statuses.
- participation in auctions and procurement scenarios;
- trip handling and workflow tracking;
- document-related actions;
- notifications for bids and status updates;
- action history and KPI visibility.
Administrative Layer
A dedicated admin application was used to manage roles, users, bidding procedures, system parameters, analytics scenarios, transport document templates, and business process versioning.
- roles and access control;
- system settings and platform parameters;
- document templates and versioning;
- bidding logic and internal reference data;
- audit of user actions;
- claim-processing routes and related workflows.
Realtime Auctions and Bidding Engine
One of the most critical parts of the platform was the online auction layer, built on socket-based realtime communication. For this workflow, stability was part of the core product logic, because bid consistency, event synchronization, and bidding transparency depended on it.
- rapid bid updates;
- synchronous auction state changes;
- transparent participant behavior;
- platform stability during active bidding load.
Documents, Notifications, and Claims
Another key layer of the platform handled transport document workflows and legally sensitive logistics scenarios. The system supported document templates, document versioning, event-based notifications, and claims-related processes.
- transport documents;
- document templates and versions;
- notifications for bids, statuses, and operations;
- history and audit trails;
- claims workflows and related processing.
Analytics and KPI
The platform also provided an analytical layer. A dedicated focus was placed on carrier KPI, performance dashboards, procurement analytics, operational reporting, and transport efficiency monitoring.
- carrier KPI tracking;
- analytics dashboards;
- reporting for logistics operations;
- history of bids, events, and actions;
- data for operational and management decisions.
Technology Architecture
The solution was built on a microservice architecture with several connected layers: a shipper portal, a carrier portal, an admin application, realtime bidding components, and an asynchronous integration / processing layer.
- Go, Vue.js, JavaScript;
- PostgreSQL, Redis, RabbitMQ;
- S3-compatible object storage;
- ClickHouse for analytics;
- Kubernetes and GitLab CI/CD;
- Prometheus, Grafana, and centralized logging.
How Redis, RabbitMQ, and the Analytics Layer Were Used
Redis served as a cache layer for faster UI rendering, dashboards, and access to frequently used operational data. RabbitMQ handled asynchronous workflows and cross-service communication, including background jobs, notifications, document processing, integrations, and trip-related events.
ClickHouse was used for event and analytics storage, enabling KPI calculations, performance dashboards, reporting, and fast access to aggregated logistics data.
Integrations and Internal Business Layer
The platform was connected to ERP and other internal corporate systems. This allowed it to participate in the broader business environment: exchanging data, supporting document workflows, contributing to trip allocation, and feeding information into analytics and management processes.
Observability, Stability, and Operations
Operational stability was treated as a core requirement. The platform used Prometheus for metrics, Grafana for monitoring, centralized logging, GitLab CI/CD for delivery, and Kubernetes for service orchestration and scaling of critical components.
This supported stable operation across the most sensitive layers of the product, especially realtime auctions, background processing, and integration workflows.
Business Value
For the business, the platform became a digital core for freight procurement and logistics operations. It centralized work with trips, carriers, documents, KPI, and analytics in one system.
- more transparent carrier procurement;
- faster logistics workflows;
- reduced manual workload for internal teams;
- better-controlled document workflows;
- clearer carrier KPI visibility;
- one connected layer for analytics, notifications, and claims;
- a stronger technical foundation for growing logistics volume.
Result
Instead of relying on disconnected logistics workflows, the company gained a connected freight procurement and transport logistics platform with shipper and carrier portals, realtime auctions, transport documents, KPI, notifications, analytics, and integration workflows. This created a stronger digital foundation for logistics management and future platform growth.
