Overview
Shipment tracking is visibility infrastructure. It answers the questions that customers, operations teams, and account managers ask dozens of times every day: where is this shipment, when will it arrive, has it been delivered, and if something has gone wrong, what happened and where? When these questions can be answered instantly — from a dashboard that aggregates tracking data across every carrier, updated in real time as events occur — operations run more efficiently, customer service overhead is reduced, and the exceptions that require action are surfaced before they become customer complaints.
When they cannot be answered without logging into multiple carrier portals, checking tracking emails manually, or calling the carrier's customer service line — operations slow down, customer service time is consumed by enquiries that self-service visibility would have resolved, and shipment exceptions go undetected until the customer raises them.
Shipment tracking software consolidates tracking data from every carrier the operation uses into a single, searchable, alerting visibility platform. It replaces the manual carrier portal checks with automated data retrieval, the reactive customer service with proactive exception alerting, and the fragmented per-carrier view with the aggregate operational picture that multi-carrier logistics management requires.
We build custom shipment tracking systems for logistics businesses, e-commerce operations, 3PL providers, and any organisation managing shipments through multiple carriers that needs consolidated tracking visibility specific to their carrier portfolio, their operational workflows, and the systems their tracking data needs to feed.
What Shipment Tracking Software Covers
Multi-carrier tracking aggregation. The fundamental function — collecting tracking events from every carrier in the operation's portfolio and presenting them through a single interface. Each carrier delivers tracking data differently: some through webhook push, some through polling APIs, some through file-based feeds. Each carrier uses different event codes, different status descriptions, and different data structures for the same underlying events. Aggregation normalises this diversity — converting carrier-specific event codes into a consistent status taxonomy, aligning timestamps to a common timezone, and presenting the tracking history of every shipment regardless of carrier through the same interface.
Multi-carrier aggregation is the difference between a tracking platform that covers the operation's full shipment portfolio and a tool that works for one carrier and requires manual workarounds for the others. As the carrier portfolio changes — new carriers added, existing carriers replaced — the tracking platform accommodates the change through carrier integration configuration rather than requiring the operations team to develop new visibility approaches for each carrier addition.
Real-time event processing. Tracking events happen continuously — collections scanned, hub processing completed, vehicles loaded, delivery attempts made, deliveries confirmed. The value of tracking data degrades rapidly: an event that happened an hour ago and has not been retrieved yet is an event that is already invisible to anyone who needs to act on it. Real-time event processing — webhook-based receipt for carriers that support push, high-frequency polling for those that do not — minimises the latency between a physical event and its visibility in the tracking platform.
Event processing handles the data quality issues that carrier tracking data introduces: duplicate events from carriers that deliver the same event multiple times, out-of-order events that arrive in a sequence that does not reflect the actual event chronology, events with malformed or missing data fields, and the occasional carrier system errors that produce nonsensical tracking entries. Clean event processing surfaces the genuine tracking record rather than the raw carrier feed.
Operational tracking dashboard. The primary interface for operations teams — a searchable, filterable view of all active shipments with their current status, their last tracking event, and any exception flags that indicate the shipment requires attention. The dashboard surfaces the operational picture without requiring individual shipment lookups: the shipments that are in transit, the shipments out for delivery today, the shipments with delivery exceptions, the shipments that have not moved in an unexpected period, and the deliveries confirmed in the current period.
Filtering by carrier, by status, by destination, by customer, by despatch date, and by exception type allows the operations team to focus on the subset of shipments that requires their attention rather than reviewing the full portfolio to find the exceptions. Bulk actions — escalating a set of exception shipments, exporting a filtered view for reporting — reduce the per-shipment time that exception management otherwise requires.
Customer-facing tracking portal. Customers who can check their own shipment status do not need to contact customer service to check it. A customer-facing tracking portal — branded to the organisation's identity, accessible via a tracking reference or order number, presenting status in customer-friendly language rather than carrier event codes — deflects the tracking enquiries that inbound customer contact currently handles.
The tracking portal presents the shipment's journey in the format that customer expectations have been shaped by: a timeline of events from despatch to current status, a map view showing the current shipment location where carrier data supports it, the estimated delivery date based on current progress, and the self-service options available if the delivery cannot proceed as planned.
Portal personalisation — presenting the tracking experience in the brand language of the organisation rather than the carrier — reinforces brand consistency at the post-purchase touchpoint where many businesses present a generic carrier experience that undermines the brand presentation the purchase journey delivered.
Proactive exception alerting. Shipment exceptions — failed delivery attempts, customs holds, damaged goods flags, carrier system errors, shipments that have not progressed as expected — are the events that require operational action. Waiting for customers to report exceptions before discovering them is a reactive posture that generates customer dissatisfaction before the operation has had the opportunity to resolve the problem.
Exception detection monitors the tracking event stream for the patterns that indicate a problem: failed delivery attempts that have not been followed up, shipments that have spent unexpectedly long periods at a single scan point, tracking feeds that have gone silent for longer than the expected inter-event interval, delivery deadline breaches, and carrier error events that flag specific handling problems.
When exceptions are detected, alerts route to the appropriate person — the customer service team for customer-facing exceptions, the operations team for carrier failures, account managers for key account shipments — through configured channels: in-platform notification, email, Slack, or SMS. Proactive alerting gives the operations team the opportunity to resolve exceptions before the customer is affected rather than after.
SLA and delivery performance monitoring. Contracted delivery performance — the service levels the carrier has committed to, the delivery deadlines the customer was promised — needs to be monitored continuously and reported accurately. SLA monitoring tracks each shipment against its expected delivery date, flags shipments that are at risk of missing their SLA before the deadline rather than after, and records SLA performance data that carrier performance reviews and customer reporting depend on.
Carrier performance reporting — on-time delivery rates by carrier, by service level, by destination region, and by time period — provides the data that carrier contract negotiations and carrier selection decisions require. A carrier that consistently underperforms against its contracted service level is a commercial issue that the data makes visible and quantifiable.
Delivery confirmation and proof of delivery. For shipments where the delivery confirmation is operationally significant — the invoice cannot be raised until the goods have been received, the customer's return period starts from delivery, the liability for the goods shifts on confirmed delivery — delivery confirmation data from the carrier's tracking feed needs to be available in the systems that act on it. Delivery confirmation integration pushes confirmed delivery events to the OMS, the billing system, or the returns management system as they occur.
For own-fleet deliveries managed through the last-mile delivery application, proof of delivery capture — electronic signature, photograph, GPS-confirmed delivery location — provides the delivery evidence directly rather than depending on carrier tracking.
Historical tracking data and reporting. Tracking data has value beyond its operational immediacy. Historical tracking records support the investigation of delivery disputes months after the fact, provide the data for carrier performance trend analysis, and feed the operational reporting that management requires. Historical tracking data stored and searchable — by shipment reference, by customer, by carrier, by date range, by status — makes the tracking record accessible for the purposes that arise after the delivery has been completed.
Carrier Coverage
The value of a shipment tracking platform depends on the completeness of its carrier coverage. A platform that covers 80% of the operation's shipments leaves 20% of shipments invisible and the operational picture incomplete.
Dutch and Benelux carriers. PostNL tracking via the Track and Trace API — the standard tracking interface for the Netherlands' dominant domestic carrier. DHL Parcel Benelux tracking. DPD Netherlands tracking including out-for-delivery and delivery confirmation events. GLS Netherlands tracking via the GLS API.
International carriers. DHL Express international tracking via the DHL Express tracking API. FedEx international tracking via the FedEx Track API. UPS tracking via the UPS Tracking API. TNT tracking for carriers operating under the TNT brand.
Aggregation platforms. SendCloud tracking aggregation — for operations using SendCloud as their carrier booking platform, tracking data from SendCloud's unified tracking interface covers all carriers booked through SendCloud. MyParcel tracking for shipments booked through the MyParcel platform.
Custom carrier integration. For carriers not covered by standard integrations — regional carriers, specialist freight carriers, international carriers in specific markets — custom carrier integrations built against the carrier's specific tracking API or file feed extend the platform's coverage to the operation's full carrier portfolio.
Integration Points
Order management systems. Shipment creation in the tracking platform triggered by order despatch in the OMS — the tracking reference linked to the order, the delivery address and expected delivery date populated from the order data. Delivery confirmation and tracking status pushed back to the OMS — order status updated automatically as tracking events are received.
E-commerce platforms. Shopify, WooCommerce — customer notification of despatch and delivery triggered from the tracking platform based on tracking events, with the tracking link included in the customer notification so the customer can follow their shipment without contacting customer service.
Customer service platforms. Tracking data available within the customer service platform — the customer service agent can see the full tracking history for any shipment without switching to the tracking platform or the carrier portal. Zendesk, Freshdesk, HubSpot — the CRM and helpdesk platforms that customer service teams use integrated with the tracking data.
Last-mile delivery system. Own-fleet delivery tracking data from the last-mile system aggregated alongside carrier tracking data — presenting a unified tracking view that covers both carrier-managed and own-fleet deliveries.
Warehouse management. Despatch confirmation from the WMS triggers shipment creation in the tracking platform — ensuring that every despatch is tracked from the moment it leaves the warehouse.
Finance and billing systems. Delivery confirmation data fed to billing systems — confirmed delivery events triggering the invoice creation or the accounts receivable update that delivery confirmation authorises.
Technologies Used
- Rust / Axum — high-throughput tracking event ingestion, real-time event processing, exception detection engine
- C# / ASP.NET Core — carrier API integration, complex tracking logic, OMS and WMS connectivity
- React / Next.js — operational tracking dashboard, customer-facing tracking portal, SLA monitoring views, carrier performance reporting
- TypeScript — type-safe frontend and API code throughout
- SQL (PostgreSQL, MySQL) — shipment records, tracking event history, SLA data, carrier performance analytics
- Redis — real-time event processing state, exception alert queuing, tracking status cache
- PostNL / DHL / FedEx / UPS / DPD / GLS APIs — carrier tracking data integration
- SendCloud / MyParcel APIs — aggregation platform tracking integration
- Shopify / WooCommerce APIs — e-commerce platform despatch and notification integration
- Twilio / MessageBird — SMS tracking notification delivery
- SendGrid / SMTP — email tracking notification delivery
- Slack API — operations team exception alert delivery
- AWS S3 — proof of delivery image storage for own-fleet deliveries
- REST / Webhooks — carrier webhook receipt and OMS/WMS integration
The Operational Value of Tracking Visibility
The cost of inadequate tracking visibility is distributed across the operation in ways that are individually small but aggregate to significant operational overhead. The customer service agent who spends five minutes per tracking enquiry across fifty enquiries per day is spending over four hours per day on queries that a self-service tracking portal would resolve in seconds. The operations manager who checks carrier portals manually to identify shipment exceptions is doing work that automated exception alerting should be doing. The account manager who cannot tell a key account customer where their shipment is without making calls is providing a service level that damages the relationship.
Custom shipment tracking software that consolidates carrier tracking data, provides self-service customer visibility, and surfaces exceptions proactively recovers this distributed cost — reducing customer service overhead, improving account management capability, and giving the operations team the visibility to manage exceptions rather than react to them.
Every Shipment, Visible
Tracking visibility is the operational foundation of delivery execution. When every shipment is visible — regardless of which carrier is carrying it, regardless of where it is in the journey — the operation can manage its delivery performance rather than discovering its delivery failures through customer complaints.