ORD stands for “Order Received by Distributor.” It’s the carrier status code that confirms your shipment has been physically picked up and logged into the carrier’s network.
ORD is the first hard data point confirming your fulfillment operation was handed off correctly. When it’s missing or stalled, everything downstream is running blind.
What the ORD Status Actually Tells You
ORD isn’t a delivery update. It doesn’t tell you where the package is going or when it will arrive.
What it confirms is narrower and more specific: the carrier has physical custody of the shipment, and their system has a record of it.
An unresolved ORD event past your expected carrier pickup window points to one of three places: a missed pickup, a label that was never scanned, or a carrier system delay that hasn’t propagated yet.
Knowing which one determines your next move.
How the ORD Status Gets Generated
Here’s the sequence that produces an ORD event from the moment your fulfillment center hands off a package:
Shipment tender to the carrier’s system. When your fulfillment operation hands off a package, the carrier’s OMS logs the transaction and assigns an order tracking number. This is the pre-scan record. The carrier knows the shipment is coming, but ORD hasn’t fired yet.
Physical label scan at the origin facility. A barcode scan at the pickup location or carrier dock is what actually triggers the ORD status. Until that scan happens, your shipment has no confirmed position in the carrier’s network, regardless of what your pick and pack operation recorded internally.
Status broadcast to tracking APIs. Once the scan fires, the carrier’s tracking API pushes the ORD event outward simultaneously: to your eCommerce platform, your fulfillment dashboard, and any third-party tracking tool connected to that carrier.
Subsequent scans advance the status. The ORD event doesn’t follow the package forever. Once it reaches an in-transit hub and gets scanned again, the live status advances to the next leg. ORD moves to the event history but remains the foundational record for any carrier claim or dispute.
What to Do When ORD Status Stalls
An ORD event that hasn’t fired 24 hours after your expected carrier pickup window needs immediate attention, not a wait-and-see approach.
Check whether the pickup actually happened. A missed carrier cutoff at your fulfillment center means the ORD event won’t generate until the following business day. Confirm the pickup log before escalating to the carrier.
Verify the label scan, not just the tender. Shipment tender and label scan are two separate events. If your package was handed to the carrier but never scanned at their facility, ORD won’t trigger, and the shipment is invisible to their tracking system.
Cross-reference your WMS timestamp. If your warehouse management system shows the order as packed and staged, but no ORD event has fired, the disconnect is at the handoff point. That’s a carrier-side issue, not a warehouse one, and the resolution path is different.
Escalate past 48 hours. A stalled ORD beyond two business days typically signals a lost tender, a mislabeled package, or a carrier system delay requiring a formal tracer request. For subscription box operators running batched shipments, a stalled ORD on a large cohort needs same-day escalation, not next-day follow-up.
Stop Letting Tracking Gaps Become Customer Problems
A missing ORD event is almost always a handoff problem. It can be a pickup window missed, a label that didn’t scan, or a fulfillment operation that doesn’t monitor carrier events closely enough to catch it before a customer does.
Fulfyld hands shipments off to carriers within a defined daily window and confirms ORD events before they become support tickets. DTC brands and B2B sellers running time-sensitive fulfillment operations don’t have room for a 48-hour gap between pack and first carrier scan.
Get a quote today and find out what same-day carrier handoff looks like for your order volume.