Your carrier confirmed the shipment two days ago. Your customer is emailing to ask where it is. Your team is manually checking four different carrier portals to find an answer. That gap, between what your systems know and what your customer can see, is what software for real-time shipment tracking is designed to close.
The setup is not complicated, but it does have a specific order. Getting the sequence wrong is how operations end up with tracking dashboards that show stale data or customer notification emails that fire at the wrong event.
Key Takeaways
- Carrier tracking APIs poll for status updates every 2 to 15 minutes. Any vendor describing this as "real-time" is describing a polling interval, not a push event. True push-based tracking requires EDI or direct carrier webhook integrations, available only on enterprise freight platforms like Project44 and Fourkites.
- AfterShip supports over 1,100 carriers globally; most US e-commerce operations use 5 to 8 carriers. High carrier count is a misleading buying signal. What matters is whether your specific carriers are supported with accurate status normalization.
- The biggest source of tracking failures is not carrier downtime. It is status normalization: UPS calls an event "Out for Delivery," FedEx calls the same event "On FedEx Vehicle for Delivery." Without normalization, your customer-facing tracking becomes inconsistent.
- Custom Glide tracking applications built for operations with non-standard workflows typically cost less to maintain than licensing three separate SaaS platforms that only partially cover the use case.
- Setting up tracking without configuring exception alerts first means your team learns about delivery failures at the same time your customer does.
What Separates Accurate Tracking from a Dashboard That Lies
Most tracking setups fail at the same point: data ingestion and normalization. A platform can pull events from 500 carriers and still show wrong information if it is not mapping carrier-specific status codes to a consistent internal schema.
Before evaluating any software for real-time shipment tracking, confirm two things. First, does the platform support your specific carrier mix? Support for a carrier name is not the same as support for all of that carrier's services. Some platforms support FedEx Ground but not FedEx Freight. Second, how does the platform handle status normalization? Ask to see the status taxonomy before you buy.
The second failure point is update frequency. Platforms like AfterShip, Narvar, and ParcelLab poll carrier APIs on a schedule, typically every 2 to 15 minutes depending on the carrier and your subscription tier. For most e-commerce and regional distribution use cases, this is adequate. For time-sensitive freight or last-mile operations where real-time accuracy is a contractual requirement, you need a platform with direct carrier EDI or webhook connections. That puts you in the enterprise freight category: Project44, Fourkites, or Flexport for managed freight, and Samsara for fleet-based visibility.
Understanding this distinction before you start saves a significant amount of time later. See shipment tracking overview for a breakdown of platform categories by use case.
How to Set Up Real-Time Shipment Tracking in Five Steps
Step 1: Map Your Carrier Mix and Shipment Volume by Type
Before touching any software, document your carrier mix, average daily shipment volume, and shipment types (parcel, LTL, FTL, international). This determines which platform category fits your operation.
Operations shipping primarily with UPS, FedEx, USPS, and DHL US in the parcel range can use a carrier-agnostic platform like AfterShip, Wonderment, or Malomo. Multi-carrier shipping platforms such as EasyPost, Shippo, or ShipStation often include tracking aggregation as part of their label generation workflow, which reduces integration overhead.
Operations with LTL or FTL freight alongside parcel need a platform that handles both. This is where gaps appear in most off-the-shelf setups. Confirm freight carrier support explicitly, not by reading the carrier list, but by testing a live tracking event before committing to a contract. Operations whose freight includes ocean inbound will face a separate set of carrier API and data freshness questions covered in the sea freight tracking software comparison.
Step 2: Connect Carrier APIs or Select Your Aggregation Platform
Once you know your carrier mix, connect to carrier data either directly via individual carrier APIs or through an aggregation platform that manages those connections for you.
Direct carrier API connections give you the most control and the lowest per-event cost at scale, but they require engineering time for each carrier and ongoing maintenance when carriers update their API specifications. This path makes sense for operations above roughly 500 daily shipments with dedicated engineering capacity.
Aggregation platforms like AfterShip or EasyPost handle carrier API maintenance for you. You authenticate once with the aggregator and gain access to their entire carrier network. The trade-off is per-event pricing and a dependency on the aggregator's update schedule. For most small to mid-size operations, this is the right trade-off. For a side-by-side look at how aggregation platforms compare on polling frequency and carrier depth, multi-carrier shipment tracking software covers those differences in detail. See no-code logistics tools for platforms that require minimal technical setup.
Step 3: Configure Status Normalization and Exception Rules
This is the step most setup guides skip, and it is the one that determines whether your tracking data is actually usable.
Status normalization means mapping each carrier's proprietary event codes to your internal taxonomy. At minimum, your taxonomy needs six states: label created, in transit, out for delivery, delivered, exception, and return initiated. Every carrier event needs to map to one of these states before it reaches your UI or triggers a customer notification.
Exception rules define which events require action. Configure alerts for: delivery attempts with no one home after two tries, packages held at a carrier facility for more than 24 hours, packages with no scan activity for more than 48 hours in transit, and any event coded as damaged or lost. These alerts should notify your operations team, not just log to a dashboard. Most platforms support Slack webhooks or email alerts for exception events.
Warning: Do not configure customer-facing notifications before testing your exception rules against live data. If your exception logic misfires, your customers receive incorrect delivery failure messages. Run exception detection in internal-only mode for at least 48 hours before enabling outbound notifications.
Step 4: Build the Customer-Facing Tracking Experience
The tracking page and notification emails are what your customer actually sees. This is where the investment in accurate data from steps 1 through 3 pays off.
Most carrier-agnostic platforms include a white-labeled tracking page and email notification templates. AfterShip, Narvar, and ParcelLab all provide branded tracking portals with configurable notification triggers. For e-commerce operations where post-purchase experience drives repeat purchase rate, Narvar and ParcelLab are worth the premium over AfterShip's lower-cost tiers. Malomo and Wonderment are strong options for Shopify-native operations.
Configure notifications at a minimum for four events: shipment confirmed, in transit, out for delivery, and delivered. For shipments with longer transit times, add a mid-transit update at the 48-hour mark to reduce inbound customer contacts. Each notification should include a direct link to the tracking page, the estimated delivery date, and a support contact for exceptions.
Step 5: Connect Tracking Data to Your OMS or WMS
Tracking data in isolation is only partially useful. Connected to your order management system or warehouse management system, it becomes operational intelligence.
Map delivery confirmation events to your order fulfillment close-out workflow. Map exception events to a customer service queue with the shipment details pre-populated. If you are operating with a 3PL, platforms like Extensiv (formerly 3PL Warehouse Manager), Deposco, or 3PL Central offer tracking integrations that push carrier events directly into your fulfillment records.
For operations using custom-built order management or dispatch tools, the integration layer is often where off-the-shelf tracking platforms fall short. Logistics management software with an open API can bridge most gaps, but operations with non-standard workflows sometimes find that a custom-built tracking layer is more reliable than forcing carrier data through a platform not designed for their specific status mapping requirements.
What to Handle After the Core Setup
Once your tracking pipeline is live, two follow-on problems typically surface within the first 30 days.
The first is delivery accuracy variance by carrier. You will find that some carriers in your mix report status events more reliably than others. Pull a 30-day report on your exception rate, first-scan delay (time between label creation and first carrier scan), and delivered-without-delivery-confirmation rate, by carrier. Use this data to set carrier-specific SLA expectations internally and to identify carriers worth replacing.
The second is customer contact reduction. The goal of a tracking setup is not just visibility. It is reducing inbound contacts from customers asking about their order, a query referred to as WISMO (Where Is My Order). Measure your WISMO contact rate before and after adding proactive notifications. A well-configured notification sequence typically reduces WISMO contacts by 20 to 40 percent within the first billing cycle. If your rate does not drop, the problem is usually notification timing or content, not tracking accuracy.
For operations that want to extend tracking into logistics automation workflows, the next layer is using tracking events to trigger downstream actions automatically: releasing a follow-up order, scheduling a return pickup, or updating a delivery slot without manual intervention.
Start with the five steps above. Get accurate data flowing and exceptions surfacing before you build automation on top of it.
Working Through a Complex Tracking Implementation
Most shipment tracking challenges look manageable until you are the one connecting multiple carriers, syncing data across legacy systems, and maintaining accuracy at scale. The architecture decisions made at the start determine what is possible six months in.
LowCode Agency has built custom logistics and tracking applications for operations ranging from regional distributors to enterprise supply chains. The same integration problems appear regardless of company size: carrier API inconsistencies, data latency, and status normalization across carrier networks.
If you are building something that needs to work without compromise, schedule a consultation with our Senior Partners. We will assess your requirements and tell you exactly what to expect.
Schedule a Consultation
Frequently Asked Questions
Q: What is the difference between real-time tracking and polling-based tracking?
Real-time tracking uses carrier-pushed events (EDI or webhooks). Polling-based tracking checks carrier APIs on a schedule, typically every 2 to 15 minutes. Most consumer and SMB tracking platforms use polling.
Q: Which software for real-time shipment tracking works best for small e-commerce operations?
AfterShip and Wonderment are the most practical entry points. Both support the major US carriers, include white-labeled tracking pages, and require minimal technical setup to go live.
Q: How long does it take to set up a shipment tracking system?
A basic setup using an aggregation platform takes 2 to 5 business days. Full integration with an OMS or WMS, including status normalization and exception alerts, typically takes 2 to 4 weeks.
Q: Can I track LTL freight and parcel shipments in the same platform?
Some platforms handle both, but support quality varies. Project44 and Fourkites cover LTL and FTL reliably. Most parcel-focused platforms like AfterShip have limited or inconsistent LTL support.
Related reading: logistics automation workflows, freight forwarder tracking software, parcel shipment tracking platforms