Custom store API / Order status mapping

Custom store API  /  Status mapping

Order status mapping

Put the Cafe24 status code in order_status on every item. Lillo works out the overall order status from the item statuses.

Cafe24 code → Lillo status

Cafe24 `order_status`MeaningLillo `status`
N00Awaiting paymentpending_payment
N10Paid, preparing itemspaid
N20 N21 N22Preparing / waiting / on holdpreparing
N30In transitshipping
N40Delivereddelivered
C00 C10Cancellation requested / acceptedcancel_requested
C34 C40Canceledcanceled
R00 R10Return requested / acceptedreturn_requested
R40Returnedreturned
E00 E10Exchange requested / acceptedexchange_requested
E40Exchangedexchanged
—Refundedrefunded (standard value only)

Only send the standard status (extension) when your own status doesn't map cleanly to a Cafe24 code. If you send it, it takes priority. The display label is status_label (optional); without it, Lillo uses the Cafe24 label (e.g. “In transit”).

Shipment status

`status`Meaning
standbyWaiting to ship
shippingIn transit
shippedDelivered

Statuses that allow writes (v1.1)

Writes are checked against the item order_status. If it doesn't allow the write, return 409 not_allowed_in_state along with the current order_status.

WriteAllowedBlocked
Cancel cancellationAll target items not yet shipped (N00·N10·N20·N21·N22)N30 and later, C*·R*·E*
Return returnN40 (delivered)Not yet shipped (→ cancel instead), N30
Exchange exchangeN30·N40 (if your policy only allows N40, return 409 for N30)Not yet shipped, C*·R*
Address receiversNot yet shipped, N00–N22N30 and later
Memo memosAny status—
Issue a couponDoesn't depend on order status (only member and coupon validity are checked)—
  • If the item already has C00·C10·R00·R10·E00·E10, return 409 already_requested.
  • Lillo pre-checks the same rules before calling, but your store has the final say.
Order status mapping · Developer docs | Lillo