Delhivery QC
The QC process is the same for Delhivery B2C APIs i.e. Delivery Reverse (Courier Partner ID: 25) and Delhivery Reverse MPS (Courier Partner: 335)
Here's the QC field mapping between Clickpost and Delhivery Reverse:
Kindly note that this mapping is for QC2.0
Clickpost API Fields | Clickpost Enum Values | Delhivery Question ID | Description |
---|---|---|---|
cat | CATEGORY | QA_CATEGORY | |
description | DESCRIPTION | QA_DESCRIPTION | |
quantity | QUANTITY | This will go as a soft check if selected. No Delhivery question ID needs to be mapped here. | |
quantity | HARD CHECK QUANTITY | QA_QUANTITY | Hard Check – Quantity is sent as a VARCHAR question |
sku | SKU | QA_SKU | |
images | ITEM_IMAGES | QA_ITEM_IMAGES | |
color | COLOR | QA_COLOR | |
size | SIZE | QA_SIZE | |
rvp_reason | RETURN_REASON | QA_RETURN_REASON | |
sku | EAN | QA_EAN | |
brand | BRAND | This will go as a soft check if clicked. No Delhivery question ID needs to be mapped here. | |
brand | HARD CHECK BRAND | QA_BRAND | Hard Check – Brand is sent as a MULTI question |
special_instruction | SPECIAL_INSTRUCTION | QA_SPECIAL_INSTRUCTION | |
imei | IMEI | QA_IMEI | |
CHECK_USED | QA_CHECK_USED | ||
CHECK_PRICE_TAG | QA_CHECK_PRICE_TAG | ||
CHECK_PACKAGING_BOX | QA_CHECK_PACKAGING_BOX | ||
CHECK_DAMAGED | QA_CHECK_DAMAGED | ||
article_number | ARTICLE_NUMBER | QA_ARTICLE_NUMBER | |
serial_no | SERIAL_NUMBER | QA_SERIAL_NUMBER |
To enable QC for Delhivery Reverse and Delhivery MPS Reverse, you can reach out to the support team at [email protected]
Updated 9 months ago