Skip to content
  • There are no suggestions because the search field is empty.

Pickup Failure: Complete Causes and Resolutions

This article lists all known pickup-failure scenarios, explains why they occur, and provides precise steps to fix them. Use it as a comprehensive troubleshooting reference.

 

1. Integration Credentials Expired

What it means
The logistic shipment service provider (Ex: Delhivery, Shiprocekt, Bluedart etc) rejects the request because stored credentials are invalid or expired.

How to confirm
Integration page shows credential issues or authentication failures.

Fix
Re-authenticate or update credentials using an admin user, then retry the pickup.

2. Provider-Side Errors (Returned Directly From the Integration)

Errors returned from the provider will appear on-screen. They reflect a failure in the provider’s system or with the request payload.

Common examples

a. “No courier service available between X and Y”

Sample:

{'message': 'No courier service available between 500053 and 440018', 'status_code': 400}

Cause
Route/pincode combination not serviceable.

Fix
Switch to a different logistic integration that supports both pincodes.

b. “Return order creation failed.”

Cause
Logistic Carrier cannot create a return order while assigning the pickup.

Fix
Retry later or reattempt after verifying shipment details at Logistic Carrier’s end.

c. Missing Warehouse Integration

Sample:

Logistic Integration's warehouse is not mapped with warehouse in EcoReturns ...

Not possible to proceed without integration.

Cause
Warehouse in EcoReturns is missing the required Logistic carrier's warehouse location ID.

Fix
Open the warehouse in EcoReturns and add the Logistic Carrier's warehouse location ID in the Warehouse Code field. Retry after saving.

d. Wallet Balance Too Low

Sample:

{'status_code': 350, 'message': 'Please recharge your ShipRocket wallet. The minimum required balance is Rs 100', ... }

Cause
Insufficient wallet balance to assign an AWB.

Fix
Recharge the logistic carrier's wallet to meet the minimum required threshold.

3. Pincode Not Serviceable

Cause
The selected logistic shipment service provider does not service the shipment’s pincode or route.

How to confirm
Errors like “non serviceable pincode” appear during request creation.

Fix
Choose another logistic provider that supports the pincode.

4. Pickup Fails Without Clear Explanation

Cause
Logistic shipment service provider sometimes returns non-diagnostic responses, e.g.:

{
  'awb_assign_status': 0,
  'response': {'data': 'Failure "I"'}
}

Fix
Retry the pickup.
In most cases, the second attempt assigns the AWB successfully.

5. Ecoship Internal Processing Exceptions

Example

Crashing while saving package due to exception '570002 is non serviceable pincode'. Package might have been partially saved.

Cause
Failure during the internal Ecoship pickup-generation flow.

Fix
Report to care@saara.io with the request details. Meanwhile use a different logistic carrier to schedule pickup while we look at this.

6. Generic Integration Errors in Request Detail

Any API-level failure from the provider appears at the top of the Request Detail section. These are exact passthrough messages.

Fix
Interpret the provider message.
Correct invalid data, wait if the provider is down, or use another integration if issue persists.

7. “Expecting value: line 1 column 1 (char 0)”

Cause
Malformed or empty JSON response, usually originating within EcoReturns rather than the logistic provider.

Fix
Report to care@saara.io with the request ID/RAN for investigation.