Kurly · Arazzo Workflow
Kurly fulfillment inbound receiving flow
Version 1.0.0
Register a SKU, book it inbound to a Kurly fulfillment centre with an idempotency key, pull the inbound label and transaction specification, then poll request-level status, item-level status and exception reports. Grounded in the operations captured in openapi/.
View Spec
View on GitHub
CompanyTechnologyLogisticsFulfillmentSupply ChainDeliveryE-CommerceGroceryShippingOrder ManagementInventoryTrackingSouth KoreaArazzoWorkflows
Provider
Workflows
bookAndMonitorInbound
Book goods inbound to a Kurly centre and monitor receiving to completion.
The cancellation window closes as soon as a Kurly operator confirms the request, so cancel decisions must be made while status is 요청완료. Exception reports can be issued after receiving completes, so report polling outlives status polling.
1
issueAccessToken
2
registerSku
Register the goods master. Returns 200 even on partial success — walk the per-item result list rather than trusting the status code.
3
searchInboundPlans
Align the booking with an existing inbound plan where one applies.
4
createInboundRequest
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).
5
downloadInboundLabel
Download the inbound label PDF while the request is still in a downloadable state (확인대기 / 입고대기 / 입고중). Omit the SKU code for all products on the request.
6
downloadSpecification
Download the transaction specification (거래명세서).
7
pollRequestStatus
Request-level work status — 입고중, 입고완료, or 강제종료. Polled, because KLS pushes nothing.
8
9
pollExceptionReports
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.
Source API Descriptions
openapi
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.