Delhivery QC

The QC process is the same for Delhivery B2C APIs, i.e., Delivery Reverse (Courier Partner ID: 25)

Here's the QC field mapping between Clickpost and Delhivery Reverse:

Kindly note that this mapping is for QC1.0, 2.0 (deprecated), and 3.0 (Only 6 QC are allowed by the carrier if more than 6 are passed, it is marked as non-QC) as delhivery has a different QC version that needs to be configured accordingly.

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_PRODUCT_IMAGEQA_IMAGE_MISMATCH
CHECK_DAMAGEDQA_CHECK_DAMAGED
QA_PRODUCT_DAMAGEDIt is configurable to specific customers' requests.
article_numberARTICLE_NUMBERQA_ARTICLE_NUMBER
serial_noSERIAL_NUMBERQA_SERIAL_NUMBER
Tag_Loop_PresentTAG_LOOP_PRESENTQA_TAG_LOOP_PRESENT
barcodeSERIAL_NUMBER_ON_TAG_LOOPQA_SERIAL_NUMBER_MISMATCHIt is configurable to specific customers' requests.

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


Did this page help you?