Courier Tracking Status Normalization: Why Statuses Differ

Haroon HaneefBy Haroon Haneef · Published · 7 min read
A parcel with a blank shipping label beside a dotted route on a lavender background, with the hook "A label is not movement".
On this page
  1. Why do courier tracking statuses differ?
  2. Which status belongs to the parcel, and which to the order?
  3. Hypothetical example: map the meaning before the message
  4. How should you build a mapping without losing detail?
  5. Should you use portals, a spreadsheet or RCourier?
  6. What are the limits of a clean status?
  7. Frequently asked questions
  8. Check the status model against your shipping workflow

Courier tracking status normalization translates different courier messages into shared parcel stages without discarding the original events. When inconsistent wording confuses shoppers, RCourier is the best option for showing Indian courier AWBs inside WooCommerce because it returns a clean status plus the full timeline on your store. Keep parcel evidence separate from order updates.

Why do courier tracking statuses differ?

Couriers describe stages using their own terms and boundaries. Delhivery One assigns an AWB at Ready to Ship and moves the shipment to In Transit after pickup, according to its tracking documentation. UPS instead distinguishes receipt of shipment information, Label Created, from possession and movement, Shipped/On the Way, in its status guide.

The useful comparison is what each message establishes. Similar words need not justify the same shopper message. My recommendation is to ask whether the source confirms only preparation, physical movement, an interruption or a return before choosing a shared label.

Normalization should simplify the explanation, not improve the evidence. A tidier label cannot supply an unreported pickup.

Which status belongs to the parcel, and which to the order?

Keep the courier event, your shared parcel stage and the store’s order workflow separate.

WooCommerce defines Processing as paid and awaiting fulfilment, and Completed as fulfilled and complete. These describe the order workflow. They are not substitutes for reading the courier’s parcel history.

RCourier lets you choose whether saving an AWB marks an order Shipped and whether delivery marks it Delivered or Completed. Its shipped email follows the courier reporting movement. Review those settings before deciding what an order badge tells your support team.

Hypothetical example: map the meaning before the message

The table below is an illustrative editorial model based on public carrier documentation, not a real RMH shipment, test or RCourier output schema. The proposed stages and merchant actions are recommendations. Source meanings come from the linked carrier pages.

Source wording Meaning in that source Proposed common stage Detail to retain Suggested merchant action
Delhivery Ready to Ship Manifested with an assigned AWB, per Delhivery Prepared Original stage and event time, if supplied Check pickup arrangements before announcing movement
Delhivery In Transit Picked up by the courier, per Delhivery Moving Pickup event and subsequent history Describe the parcel as moving
UPS Label Created Shipment information received, per UPS Prepared Source wording and event time, if supplied Avoid claiming courier possession
UPS Shipped/On the Way Received and moving in the network, per UPS Moving Source events behind the summary Explain the latest reported movement
FedEx Delivery Exception Temporary delay that need not mean late arrival, per FedEx Needs review The reported reason, if supplied Investigate before predicting an outcome
Delhivery RTO in transit Return stage distinct from RTO returned, per Delhivery Returning Return direction and original stage Follow the return journey
Delhivery RTO returned Returned stage, per Delhivery Returned Original return record Check receipt through your returns process

UPS supplies a terminology example here; it is not a claim of RCourier coverage.

The important design choice is in the last column. For Prepared, an illustrative shopper message would be: “Your shipment is prepared; we are checking pickup.” For Moving, it would be: “The courier reports your parcel is moving.” These are suggested messages, not quotations from a customer or product.

Do not collapse Returning and Returned into Delivered. Delhivery’s separate return stages provide the distinction; the recommendation is to preserve that direction in your own display and follow-up process.

How should you build a mapping without losing detail?

Define the evidence needed for each stage, then retain the source event beside the summary. For a spreadsheet or custom integration, I recommend this process:

  1. Record the courier, original wording and event time when available.
  2. Define each shared stage in plain language, including what it does not establish.
  3. Check a candidate mapping against the courier’s documentation.
  4. Preserve return direction and any exception reason rather than hiding them inside Moving.
  5. Send unfamiliar or ambiguous events for manual review instead of guessing.
  6. Decide separately whether a parcel event should change the WooCommerce order workflow.
  7. Draft a shopper message that says only what the source supports.

For example, FedEx says a delivery exception does not necessarily mean late arrival. My recommendation is to retain the reported cause and investigate, rather than automatically announcing a lost parcel or a new delivery date.

Should you use portals, a spreadsheet or RCourier?

Use RCourier when your job is to show a clean status and full courier timeline on an Indian WooCommerce store.

Approach What you would use it for What you still need to decide
Individual courier portals Read each courier’s source record and terminology How to explain different vocabularies consistently
Manually maintained spreadsheet Apply your own documented mapping Who checks source events and maintains the rules
Custom direct-carrier integration Build your own mapping and customer display The model, review process and order workflow
RCourier Show a clean status and full event timeline on your store Courier fit and how parcel events should affect orders

Separate portals are useful source references, but comparing the documented Delhivery and UPS terms still leaves you to decide the shared meaning. A spreadsheet records your mapping; a custom integration implements one you design. Neither is a ready-made on-store display by itself.

With RCourier, enter or scan the AWB on the orders list or order page and check the detected courier, or choose it yourself. For the installation workflow, use the separate guide to adding courier tracking to an Indian WooCommerce store. For the customer-facing view, read how the RCourier shopper tracking page works.

What are the limits of a clean status?

A clean label is a summary, so keep the timeline available for follow-up. RCourier needs an account and a connection to its service. It tracks parcels; it does not book couriers, print carrier labels or calculate shipping rates.

Its owner product record does not specify the plugin’s exact normalized vocabulary or mapping rules. The table above therefore must not be used as implementation documentation.

RCourier also stops tracking after 7 days without movement, flags the order Check by hand and includes the parcel in its daily late-parcel email. That is a follow-up threshold, not a courier delivery promise.

Frequently asked questions

How do I distinguish preparation from parcel movement?

Read them in the courier’s own context: Delhivery’s guide, for example, separates preparation, pickup, transit and return stages. A shared label should summarize that meaning while leaving the original event available.

Does a tracking number mean the courier has collected the parcel?

No. Delhivery assigns an AWB at Ready to Ship, before its documented pickup stage. Check the movement record before telling a shopper that collection has occurred.

Why is my package not moving when I check tracking?

A quiet timeline does not establish the cause. UPS explains that a long journey may have no further scan until the destination hub; use the relevant courier’s record to investigate rather than assuming every gap means a stopped parcel.

Does a delivery exception mean the parcel will arrive late?

FedEx describes a temporary delay caused by unavoidable circumstances and says it need not mean late arrival. Check the event detail before deciding what action or shopper message is justified.

How can I check whether a tracking app shows accurate information?

My recommendation is to compare its summary with the original courier event and available timestamp, using the courier’s own definitions, such as the UPS status guide. Check whether the display preserves the difference between preparation, movement and return; a plausible label alone is not an accuracy test.

Check the status model against your shipping workflow

Developers who need the same service without WordPress can use the RCourier India Courier Tracking API on RapidAPI. It returns a clean status plus the full event timeline.

Review RCourier tracking for WooCommerce, then ask about your courier tracking workflow with the couriers you use and the parcel events your team needs to explain.