Fulfillment inbound receiving flow
A 9-step recipe with Kurly. We can help you get access.
Recipe · 9 steps
Fulfillment inbound receiving flow
with Kurly
Book goods inbound to a Kurly centre and monitor receiving to completion.
- issueAccessToken
- Register the goods master. Returns 200 even on partial success — walk the per-item result list rather than trusting the status code.
- Align the booking with an existing inbound plan where one applies.
- Book the inbound. Retry with the SAME X-Idempotency-Key. Field-level validation errors identify the offending field (expiry/manufacturing date, quantity, remarks, lot number).
- Download the inbound label PDF while the request is still in a downloadable state (확인대기 / 입고대기 / 입고중). Omit the SKU code for all products on the request.
- Download the transaction specification (거래명세서).
- Request-level work status — 입고중, 입고완료, or 강제종료. Polled, because KLS pushes nothing.
- Item-level work status per SKU — 입고대기, 입고중, 입고완료.
- Exception reports are issued per issue type and can appear AFTER receiving completes. Reports are immutable — a correction is a void plus a re-issue, so reconcile on report identity.
What you'll need to have ready
- clientId
- secretKey
- idempotencyKey: Value for the X-Idempotency-Key header; reuse on every retry.
- timestamp: Value for the companion X-Timestamp header.
For your developer
Arazzo workflow kurly:bookAndMonitorInbound, 9 operations: issueToken → saveSku → searchReceivingPlans → createReceivingRequest → printReceivingLabel → downloadReceivingSpecification → searchReceivingRequests → searchReceivingItemStatus → searchReceivingReports. Specs on APIs.io.