[Open API] Notice of Customer Cancellation Request Rejection Feature & API Specification Changes for Non-Returnable Categories

[Open API] Notice of Customer Cancellation Request Rejection Feature & API Specification Changes for Non-Returnable Categories

Hello, this is Coupang Open API.

Following the introduction of the "Customer Order Cancellation Request" feature in MyCoupang App for categories with statutory right of withdrawal limitations (non-returnable items), the processing method and API specifications for "Reject customer cancellation request" via Open API will be updated as follows.

1. Target Categories & Conditions
This API specification update applies to orders that match the target non-returnable Category IDs and shipping/product condition filters listed below.

Category Identifiers:

kan_category_id: 5128, 9733
displayCategoryCode: 53375, 71693, 71694, 71695, 71696, 72279, 76838

kancategoryname: Pure Gold / Other Pure Gold

Shipping Method / Category Filters:

Fresh / Frozen: COLD_FRESH

Direct Shipping: VENDOR_DIRECT

Custom-made: MAKE_ORDER

2. Key Changes & Processing Options
When rejecting a customer's cancellation request for a non-returnable order in the "Cancel Stage B (Stop Shipment)" status, sellers can now reject the request using the new reason "Items in Preparation" in addition to the existing "Already Released" option.

Standard Returnable Orders:

Behaves as before. (Processed as Already Released/Return upon inputting tracking information)

Non-Returnable Orders:

Calling the same API will now process the request as a "Reject customer cancellation request" instead of generating a simple return request.

To allow rejection of cancellation requests during the preparation phase—such as when raw material processing, custom manufacturing, or fresh food packaging has begun but a tracking number has not yet been issued—the deliveryCompanyCode and invoiceNumber fields will become Optional.

3. API Specifications & Request Spec Changes
[Affected API]
PATCH /v4/vendors/{vendorId}/returnRequests/{receiptId}/completedShipment (Already Released & Cancellation Rejection Processing)

[Unchanged APIs]
PUT/PATCH .../stoppedShipment (Confirm Stop Shipment / Approve Cancellation)

Other order cancellation-related API endpoints

[Request Spec Details]
vendorId, receiptId: Required (Same as before)

deliveryCompanyCode, invoiceNumber: Required → Optional

Note: If a tracking number has already been issued, you may still input the invoice information when calling the API as before.

4. Impact & Precautions for Sellers and ERP Developers
If only using returnable categories: No API code modifications are required.

If currently calling this API for non-returnable products:

Previously, calling this API immediately transitioned the order to a return request state. Following the update, it will be processed as a "Reject customer cancellation request."

Rejected orders will not be canceled and must be delivered normally. ERP systems programmed on the assumption of an immediate "Return Request" will need to be updated.

New endpoint integration: No new API URLs are introduced; please continue using the existing endpoint.

5. Implementation Schedule
Effective Date: October 6, 2026 (2026-10-06) (Full rollout following A/B testing and ramp-up)

Developer Documentation: Coupang Open API Developer Portal

Thank you.