Status Code Reference

Leopards Courier Tracking Status Codes — Complete Guide 2026

Every LCS tracking status explained — what it means, typical timeframes, and what action (if any) you should take.

Last verified: Leopards Courier Services (LCS)Based on official LCS tracking dataUpdated 2026Covers all 17 statuses

Check Your Current Status

Enter your CN number to see the live status of your Leopards Courier parcel.

Enter Consignment / Tracking Number

Track orders from Daraz, Shopify, OLX, Facebook sellers & any Leopards Courier booking

What Are LCS Status Codes?

Every time your Leopards Courier parcel is scanned at a facility, loaded onto a vehicle, or handed to a rider, the system records a status code. These codes appear in your tracking timeline and tell you exactly where your parcel is in the delivery journey.

Status codes are organised into four categories: Success statuses (delivered and on the way), In-transit statuses (from booking through hub processing), Exception statuses (problems requiring action), and COD statuses (cash-on-delivery tracking).

See the full tracking guide if you need help reading your tracking results or understanding your CN number.

3

Success Statuses

6

In-Transit Statuses

5

Exception Statuses

3

COD Statuses

Delivered & Success Statuses

These statuses indicate your parcel is in the final stages of delivery or has been successfully delivered.

Delivered

Success

The parcel has been successfully delivered to the recipient. Proof of Delivery (POD) is recorded with recipient name and timestamp.

What Happens Next

No further updates. For COD shipments, remittance processes within 24–48 hours.

Typical Timeframe

Final status

Your Action

If you have not received the parcel but see Delivered, call LCS immediately with your CN.

Status text variations:

DeliveredSuccessfully DeliveredDelivered to Consignee

Out for Delivery

Final Leg

A delivery rider has been assigned your parcel and has picked it up from the hub. The parcel is on the final leg to your address.

What Happens Next

Rider will attempt delivery. Expect a call to confirm address or gate code.

Typical Timeframe

2–8 hours on OFD day (9 AM–7 PM)

Your Action

Keep your phone reachable. Ensure someone is available at the delivery address.

Status text variations:

Out for DeliveryOn Delivery RouteWith RiderOn the Way

Attempted Delivery

Attempted

A delivery attempt was made at your address. The rider was unable to complete delivery — gate locked, no one available, or address unclear.

What Happens Next

Another delivery attempt will follow on the next business day. Up to 3 attempts total.

Typical Timeframe

Re-attempt within 1 business day

Your Action

Call LCS at +92 21 111-300-786 to update address or schedule a specific time.

Status text variations:

Delivery AttemptedAttemptedDelivery TriedNo One Home

In-Transit Statuses

From the moment a parcel is booked until it reaches the destination hub, these statuses track the journey. Learn more about the Arrived at LCS3 status specifically.

Booked / Shipment Picked Up

Booked

The parcel has been registered in the LCS system and physically collected from the sender. Your CN is now live and trackable.

What Happens Next

Parcel will be transported to the origin sorting hub within a few hours.

Typical Timeframe

2–8 hours before next update

Your Action

No action needed. Allow 12–24 hours for first scan to appear.

Status text variations:

Shipment BookedPicked UpCollected from ShipperBooked

Arrived at Hub / At Origin Hub

At Hub

The parcel has arrived at the origin city sorting facility. It is being scanned, sorted, and prepared for intercity transport.

What Happens Next

Parcel will be loaded onto an intercity transport vehicle and depart for the destination.

Typical Timeframe

4–8 hours before departure

Your Action

No action needed. Normal processing time at origin hub.

Status text variations:

Arrived at HubAt Origin HubOrigin FacilityArrived at LCS Facility

Departed Hub / In Transit

Departed

Parcel has left the origin or intermediate hub and is on the move between cities. Updates only appear at scan checkpoints.

What Happens Next

Next scan when parcel arrives at an intermediate or destination hub.

Typical Timeframe

12–36 hours between intercity scans

Your Action

No action needed. Transit gaps are completely normal — especially for long-distance routes.

Status text variations:

DispatchedIn TransitShippedDeparted HubOut for Transfer

In Transit

In Transit

Parcel is actively moving between two facilities. This is the intercity leg and no new scans appear until the next hub.

What Happens Next

Arrival scan at the next hub — could be a midpoint or the destination hub.

Typical Timeframe

6–48 hours depending on distance

Your Action

No action needed. This is normal and expected for all intercity shipments.

Status text variations:

In TransitOn the WayBetween HubsIntercity Movement

Arrived at LCS3 / Destination Hub

At Hub

Parcel has reached the destination city hub (e.g. LCS3 in Karachi). It is being sorted and assigned to a local delivery rider.

What Happens Next

Parcel moves to "Out for Delivery" status when a rider picks it up.

Typical Timeframe

6–24 hours before delivery assignment

Your Action

Delivery is very close. Stay reachable by phone.

Status text variations:

Arrived at LCS3Arrived at HubAt Destination HubArrived at LCS Facility

At Destination Hub

At Hub

The parcel has been confirmed at the final delivery hub in your city. Sorting for your specific zone is underway.

What Happens Next

Assignment to a delivery rider and Out for Delivery status.

Typical Timeframe

2–8 hours

Your Action

Delivery expected same business day. No action needed.

Status text variations:

At Destination HubFinal HubDestination FacilityCity Hub

Exception & Problem Statuses

These statuses require action from you or the sender. Do not ignore them — most can be resolved with a quick call to LCS. See our failed delivery guide for detailed steps.

Failed Delivery

Failed

A delivery attempt was made but unsuccessful. Common reasons: wrong address, gate locked, recipient not available, address not found, or refused by security.

What Happens Next

Up to 3 delivery attempts total. If all fail, parcel is returned to sender (RTO).

Typical Timeframe

Re-attempt next business day

Your Action

Call LCS at +92 21 111-300-786 before 10 AM to arrange re-delivery or address correction.

Status text variations:

Failed DeliveryDelivery FailedExceptionDelivery Unsuccessful

Returned to Sender

RTO

After 2–3 failed delivery attempts, Leopards Courier has initiated a return. The parcel is heading back to the original sender.

What Happens Next

Parcel returns to origin city. Delivery to sender within 3–7 business days.

Typical Timeframe

3–7 business days for return

Your Action

Contact your seller — they will receive the return. Coordinate a re-shipment with correct address.

Status text variations:

Returned to SenderRTOReturn to OriginReturn InitiatedReturned to Shipper

Hold at Hub

On Hold

The parcel is being held at a hub or branch for a specific reason — address query, incomplete documentation, or special handling requirement.

What Happens Next

Parcel held up to 5 business days. If unresolved, may be returned to sender.

Typical Timeframe

Hold up to 5 business days

Your Action

Call LCS helpline immediately to understand and resolve the hold reason.

Status text variations:

Hold at HubOn HoldHeld at FacilityAwaiting Clarification

Address Issue

Address

The delivery address is incomplete, unclear, or could not be located by the rider. The parcel cannot be delivered without a valid address.

What Happens Next

Parcel held at the branch. Delivery will resume once address is corrected.

Typical Timeframe

Depends on how quickly address is corrected

Your Action

Call LCS helpline with the correct, complete address including area, street, house number, and landmarks.

Status text variations:

Address IssueAddress Not FoundWrong AddressIncomplete Address

Refused by Consignee

Refused

The recipient at the delivery address refused to accept the parcel. This is recorded as a refusal in the system.

What Happens Next

Parcel returned to sender. No further delivery attempts are made after a refusal.

Typical Timeframe

Return initiated immediately

Your Action

Contact your seller if you did not refuse the parcel — someone at the address may have refused it in error.

Status text variations:

Refused by ConsigneeRefusedConsignee RefusedDelivery Refused

COD-Specific Statuses

Cash on Delivery (COD) shipments have additional status codes that track the payment collection and remittance cycle. These are relevant primarily for sellers and eCommerce merchants.

COD Collected

COD

Cash on Delivery payment has been collected from the recipient at the time of delivery. The amount is confirmed and being processed.

What Happens Next

Remittance deposited to seller account within 24–48 business hours.

Typical Timeframe

24–48 business hours

Your Action

For COD remittance queries, contact your LCS account manager.

Status text variations:

COD CollectedCOD ReceivedCash CollectedPayment Collected

COD Pending

COD

The parcel has been delivered but the COD amount has not yet been confirmed in the system. Processing is underway.

What Happens Next

COD status will update to Collected once verified.

Typical Timeframe

2–12 hours for system update

Your Action

No immediate action needed. Check again in a few hours.

Status text variations:

COD PendingCash PendingPayment PendingCOD Awaiting Confirmation

COD Remitted

COD

The collected COD amount has been transferred to the seller's account. The financial cycle for this shipment is complete.

What Happens Next

No further updates. Seller can verify the credit in their bank account.

Typical Timeframe

Final status

Your Action

Confirm receipt in your LCS portal or bank statement. Contact LCS if amount is incorrect.

Status text variations:

COD RemittedRemittance DoneAmount TransferredPayment Remitted

Status Update Timeline — Typical 3–5 Day Journey

Here is what a typical Leopards Courier shipment looks like from booking to delivery across cities in Pakistan.

Day 1 — AM

Booked

Seller books the parcel. LCS rider collects it. Booking SMS sent to sender with CN number.

Day 1 — PM

At Origin Hub

Parcel scanned into origin city sorting facility. Grouped with other parcels for same destination city.

Day 1–2

In Transit

Intercity vehicle departs. No new scans during road/air transit. This is normal — not a delay.

Day 2–3

Arrived at LCS3

Parcel arrives at destination city hub. Processing and route assignment begins.

Day 3

Out for Delivery

Rider picks up your parcel. Delivery attempt made during business hours (9 AM–7 PM).

Day 3

Delivered

Parcel handed to recipient. POD recorded. COD collected if applicable.

What To Do If Your Status Seems Wrong

If the status on your tracking is not what you expect — stuck for too long, showing an incorrect location, or not updating — follow these steps. Also see the tracking not updating guide for more fixes.

1

Wait and Re-check

Tracking can take 12–24 hours to update after booking, and intercity transit can have 24–36 hour scan gaps. Refresh after a few hours before taking action.

2

Verify Your CN Number

Double-check for character confusion: zero (0) vs letter O, or letter I vs number 1. Even one wrong character shows "no data".

3

Call LCS Helpline

If status has not changed for 48+ hours, call +92 (21) 111-300-786. Have your CN ready. An agent can see internal notes and escalate if needed.

4

Contact Your Seller

If the parcel shows as returned or the status is confusing, inform your seller. They have direct account access with LCS and can raise a complaint ticket faster than individual customers.

Status-Specific Action Guide

Quick reference: find your current status, understand what it means, and know exactly what to do.

StatusWhat It MeansWhat To Do
BookedParcel registered, not yet scannedWait 12–24 hours for first update
In TransitMoving between citiesNo action — check again in 24 hours
Arrived at LCS3At main Karachi hubExpect delivery within 6–24 hours
Out for DeliveryRider has your parcelStay reachable; be at address by noon
DeliveredHanded to recipientIf not received, call LCS immediately
Failed DeliveryAttempt unsuccessfulCall LCS before 10 AM for re-delivery
Hold at HubParcel held — reason unclearCall helpline to resolve hold reason
Returned to SenderAll attempts failedContact seller to re-arrange shipment

Frequently Asked Questions

Real answers about Leopards Courier tracking status codes in Pakistan.

"Booked" means Leopards Courier has registered your parcel and a rider has collected it from the sender. Your CN is now live and trackable. The parcel is at the origin city and will reach the sorting hub within hours. Use our home tracking tool to check the live status, and see the CN number format guide if you need help reading your consignment number.
"In Transit" lasts 6–48 hours depending on distance. Same-province routes take 6–12 hours; cross-country routes like Karachi to Peshawar can take 24–48 hours. No new scans appear during this phase — that is completely normal. If your parcel has been in transit for more than 72 hours, see the tracking not updating guide for steps to take.
"Arrived at Hub" means the parcel reached a Leopards facility. At an intermediate hub, expect another 4–8 hours before departure. At the destination hub, delivery is typically assigned within 6–24 hours. Check LCS delivery time estimates to gauge when your parcel will arrive based on your route.
"Arrived at LCS3" means your parcel is at the main Leopards sorting hub in Karachi. Processing takes 6–24 hours before a rider is assigned; up to 36–48 hours during peak periods like Eid. For a detailed breakdown of what happens at this hub and typical wait times, read the dedicated LCS3 hub explained guide.
Once "Out for Delivery" appears, a rider has your parcel and is on route. Expect delivery within 2–8 hours — riders operate 9 AM to 7 PM. Keep your phone reachable for a confirmation call. Track the live progress using the home tracking tool and check delivery time estimates if you need a more precise window.
The parcel returns to the local branch and a re-attempt is made the next business day — up to 3 attempts total. Call the LCS helpline before 10 AM to arrange same-day re-delivery or visit the nearest branch with your CN and CNIC. For a full step-by-step process, read the failed delivery guide.
"Returned to Sender" (RTO) means all delivery attempts are exhausted and the parcel is heading back to the shipper. Delivery to the recipient cannot be resumed on the same shipment. Contact your seller — they need to re-book. If the issue was a wrong address, see the failed delivery guide to understand how to prevent RTO on a re-shipment.
"Exception" flags any deviation from normal delivery progress — incomplete address, refused delivery, documentation issue, or courier access problem. Call the LCS helpline immediately to get the specific reason. If your tracking has been on Exception for more than 24 hours without resolution, follow the steps in the stuck tracking guide.
Leopards Courier makes up to 3 delivery attempts. After the third failed attempt, Return to Sender (RTO) is initiated and the parcel is sent back within 3–7 business days. Between attempts the parcel is held at the local branch. To maximise chances of success on the next attempt, read the failed delivery guide for address correction and re-delivery tips.
First verify your CN for character errors (zero vs O, I vs 1). If the last scan shows intercity transit, a 24–48 hour gap is normal. Beyond 72 hours with no movement, call the LCS helpline and inform your seller. Our tracking not updating guide covers 7 specific causes and fixes for a stuck Leopards tracking status.
A Hub Scan records the parcel's arrival or departure at an LCS sorting facility. A Delivery Scan is recorded on the final mile — when a rider picks up the parcel, attempts delivery, or completes delivery at the doorstep. Delivery scans matter most to recipients. Use the tracking tool to view your full scan timeline, or read the how to track guide to understand each scan event.
Yes — the tracking result shows every scan event with facility name, city, and timestamp. This is visible on the Leopards website, the LCS app, or any tool that uses your CN number. Enter your CN in the tracking tool on this site for a clean timeline view. See the 5 tracking methods guide for all the ways to access scan history.
LCS3 is the main Leopards Courier hub in Karachi, located in the SITE industrial area. All Karachi-bound parcels pass through LCS3 for sorting and rider assignment. It handles the highest daily volume in the Leopards network. For everything about what happens at this specific hub and how long parcels stay there, read the LCS3 hub explained page.
"COD Received" or "COD Collected" means the delivery rider has collected the Cash on Delivery payment from the recipient. The amount is recorded and being processed for remittance to the seller — typically within 24–48 business hours. For sellers managing multiple shipments, the bulk tracking tool lets you monitor COD status across all CNs at once.
"Held at Branch" means your parcel is waiting at a Leopards Express Centre. Visit during business hours (9 AM–5 PM, Mon–Sat) with your CN number and a valid CNIC. Find the nearest branch using the branch locations directory. If you believe the parcel should have been delivered rather than held, file a complaint through the LCS complaint system.
International parcels via Leopards Courier International (LCI) show additional codes like "Clearance in Progress," "Held at Customs," or "Customs Released" — codes that do not appear on domestic shipments. Scan gaps of 3–7 days during air transit are normal. Use the tracking tool with your LCI CN, and refer to the full tracking guide for CN format differences between domestic and international shipments.
"Delivery Rescheduled" means the planned delivery date was moved before any attempt was made — due to hub volume, rider availability, or an address query. Unlike Failed Delivery, no physical attempt occurred. The parcel stays at the branch or hub. No action is needed unless you want to expedite — in that case call LCS or file a complaint. Check delivery time estimates for revised arrival expectations.
POD is auto-recorded at delivery with recipient name, timestamp, and CNIC for COD parcels. To obtain a formal POD document, call the LCS helpline with your CN or download it from the LCS merchant portal if you are a seller. If there is a dispute about whether delivery actually occurred, file a formal complaint — POD is the key evidence reviewed in all delivery dispute cases.
"Failed Delivery" means a rider physically attempted and could not complete delivery. "Exception" is broader — it covers any abnormal situation including address issues flagged before an attempt, documentation holds, or parcel damage. Both need resolution. For Failed Delivery, follow the failed delivery guide. For Exception, call the helpline immediately to identify the specific cause.
Both update tracking in near real-time on scans. TCS tends to have slightly more intermediate scan points due to its larger hub network; Leopards can show longer intercity transit gaps. For delivery-day scans both are comparably fast. Leopards has more competitive rates for high-volume eCommerce; TCS has stronger small-city coverage. Use the bulk tracking tool if you are comparing multiple shipments across couriers.