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 FieldsClickpost Enum ValuesDelhivery Question IDDescription
catCATEGORYQA_CATEGORY
descriptionDESCRIPTIONQA_DESCRIPTION
quantityQUANTITYThis will go as a soft check if selected. No Delhivery question ID needs to be mapped here.
quantityHARD CHECK QUANTITYQA_QUANTITYHard Check – Quantity is sent as a VARCHAR question
skuSKUQA_SKU
imagesITEM_IMAGESQA_ITEM_IMAGES
colorCOLORQA_COLOR
sizeSIZEQA_SIZE
rvp_reasonRETURN_REASONQA_RETURN_REASON
skuEANQA_EAN
brandBRANDThis will go as a soft check if clicked. No Delhivery question ID needs to be mapped here.
brandHARD CHECK BRANDQA_BRANDHard Check – Brand is sent as a MULTI question
special_instructionSPECIAL_INSTRUCTIONQA_SPECIAL_INSTRUCTION
imeiIMEIQA_IMEI
CHECK_USEDQA_CHECK_USED
CHECK_PRICE_TAGQA_CHECK_PRICE_TAG
CHECK_PACKAGING_BOXQA_CHECK_PACKAGING_BOX
CHECK_DAMAGEDQA_CHECK_DAMAGED
article_numberARTICLE_NUMBERQA_ARTICLE_NUMBER
serial_noSERIAL_NUMBERQA_SERIAL_NUMBER

To enable QC for Delhivery Reverse and Delhivery MPS Reverse, you can reach out to the support team at [email protected]