Edit Order
Edit Order API allows the enterprise to edit specific details for a shipment that has already been manifested.
Overview
This API enables enterprises to edit specific details for a shipment that has already been manifested. This API only works for the following mentioned fields, for the respective mentioned carrier partners
Usecases Supported
- Conversion of order from QC to NON-QC
- You can use this API to convert a shipment from QC to Non QC flow in case the shipment pickup has to be done and QC check if failing within carrier systems. Once this API is called, Carrier partner will pick the shipment next day without doing QC.
- Conversion of Order from COD to Prepaid.
- Conversion of Order from Prepaid to COD.
- Update Eway Bill Number
Process Flow for COD to Prepaid Conversion:
The COD to Prepaid conversion API allows you to convert a shipment from COD to Prepaid till a particular state of the shipment [in general: Out For Delivery].
- Once the COD order is placed by the customer, show them an option to convert the order from COD to Prepaid on My orders section, via SMS/Whatsapp communications.
- When the customer makes the payment for the order, if the label is generated for the shipment, you can call the COD to Prepaid conversion API for the corresponding courier partner to convert the order to Prepaid.
- Once the courier sends a confirmation, you can make the transaction successful. In case you receive any failure from the courier partner, revert the transaction and disable conversion on the product.
Eway Bill Update Process
What is an Eway Bill Number?
An Eway Bill Number is a unique identifier mandated by the government for the transportation of goods valued at more than ₹50,000.
Flow
- During the order creation process, enterprises may not have the Eway Bill Number readily available. As a result, they often input empty or placeholder values in the API.
- Subsequently, enterprises generate the Eway Bill Number from the designated portal. This number then needs to be updated at the carrier partner's end.
- ClickPost's edit order API facilitates enterprises in updating the Eway Bill Number post-order creation, ensuring compliance and smooth logistics operations.
Important Notes:
- Enable webhooks enabled from the courier partners on Clickpost and you are consuming the same for getting the status updates. You would want to disable the payment link as soon as the order is marked as Out for Delivery.
- Before you start using the APIs, have a discussion with your courier partner POCs to keep them aligned that you are planning to use “edit order API” (couriers call the COD to Prepaid conversion API as Edit order) to convert orders from COD to Prepaid.
Geography
This API supports conversions for carriers in India.
Please refer to the list of supported carrier partners below
Supported Carrier Partners for COD to Prepaid
Carrier Partners who support conversion of COD orders to PREPAID and are active on this API:
- Delhivery
- Ecom Express
- Xpressbees
- Shadowfax
- Shadowfax HLD
- Loadshare
- Shipsy
Carrier Partner who are in pipeline
- Ekart
- Smartr
Carrier Partner who support conversion of order from QC to Non-QC:
- Shadowfax Reverse
Supported Carrier Partners for Prepaid to COD
- Delhivery
Carrier Partner who support update of Eway Bill Number
- Ekart
- Bluedart
URL
GET <https://www.clickpost.in/api/v1/edit-order/
>
Query Parameters
Field Name | Data Type | Field | Description | Max Length | Example |
---|---|---|---|---|---|
username | String | Mandatory | Username of the registered enterprise | 100 | "test-enterprise" |
key | String | Mandatory | Unique license key for the enterprise user | 100 | "00000000-0000-0000-0000-000000000000" |
Request Payload
Field Name | Data Type | Field | Description | Max Length | Example |
---|---|---|---|---|---|
courier_partner | Integer | Mandatory | Partner ID of the carrier partner. https://track.clickpost.in/courier_partner | 123 | |
order_type | String | Mandatory | Order type of the shipment 1. COD 2. PREPAID | 100 | "PREPAID" |
awb | String | Mandatory | The Air Waybill of the shipment that needs to be edited | ||
qc_type | Enum | Optional | The values it takes 1. doorstep 2. null doorstep denotes Quality Check should be done at the doorstepnull denotes that a Quality Check is not required | "doorstep" | |
sku | String | SKU of the item. If the customer wishes QC on the entire shipment they should ignore this field. If they wish QC on a specific shipment they should pass the SKU value of the shipment. | |||
cod_value | Float | Amount to be collected at the doorstep for cash on delivery mode. (Only required when prepaid to cod conversion is being done) | "123.50" | ||
ewaybill_serial_number | String | Eway Bill Number which needs to be updated against a shipment | 12 | 234567799999 | |
invoice_number | String | Invoice Number of the shipment | "INV12123" | ||
invoice date | Date | Date of the invoice | 2024-01-20 |
Response
The sample response can have the following fields
Field Name | Data Type | Description |
---|---|---|
meta | Object | Metadata for the result, e.g. status code, error messages. |
Response Meta
Field Name | Data Type | Description |
---|---|---|
status | Integer | Status code of the response (including, but not limited to HTTP Status codes) |
message | String | Error message (if any errors) for the request. |
success | Boolean | Whether the request is successful or not. |
Sample Payload
{
"awb_number": "20719799",
"order_type": "PREPAID",
"courier_partner": 220
}
{
"awb_number": "999999999",
"qc_type": "doorstep",
"courier_partner": 11
}
{
"awb_number": "20719789",
"order_type": "COD",
"cod_value" : 123.50,
"courier_partner": 3
}
{
"awb_number": "76973977426",
"ewaybill_serial_number":"234567799999",
"invoice_number":"new123",
"invoice_date":"2024-01-20",
"courier_partner": 5
}
Sample Response
{
"meta": {
"message": "ACCEPTED",
"success": true,
"status": 200
}
}
Updated 14 days ago