Shipment statuses
Every shipment and order status, what it means, and how each courier's own status codes map to it.
- Product
- APIShipping Engine API
- Section
- Reference
- Reading time
- 10 min read
Every shipment has one status from the list below. Build your logic on status. The courier's own
value is passed through as data.mapping_code in webhooks for display and
troubleshooting. For how statuses connect, see Order and shipment lifecycle.
Shipment statuses
status | Meaning | Terminal | Can cancel | Webhook event | Label (EN) | Label (ID) |
|---|---|---|---|---|---|---|
WAITING_FOR_PAYMENT | Created, not paid. Seen on orders whose payment failed. | No | Yes | — | Awaiting payment | Menunggu pembayaran |
CONFIRMED | Paid, courier not booked yet. | No | Yes | — | Processing | Diproses |
PENDING_PICKUP | Booked. The courier will collect the parcel from the sender. | No | Yes, the courier is asked first | shipment.dispatched when booked, then shipment.pending_pickup | Waiting for pickup | Menunggu dijemput kurir |
PENDING_DROPOFF | Booked. You drop the parcel off at a courier counter. | No | Yes, the courier is asked first | shipment.dispatched | Waiting for drop-off | Menunggu diantar ke agen |
IN_TRANSIT | The courier has the parcel. | No | Request only, most couriers refuse | shipment.in_transit | In transit | Dalam perjalanan |
PROBLEM_SHIPMENT | The courier reported a problem (failed delivery, damage, loss, failed instant pickup). Not final. | No | Request only | shipment.problem_detected, or shipment.pickup_failed | Delivery issue | Kendala pengiriman |
DELIVERED | The receiver has the parcel. | Yes | No | shipment.delivered | Delivered | Terkirim |
CANCELLED | Cancelled by you or the courier, or booking was rejected. | Yes | Already cancelled | shipment.cancelled | Cancelled | Dibatalkan |
RTS_CONFIRMED | The courier will return the parcel to the sender. | No | No | shipment.rts_confirmed | Returning to sender | Dikembalikan ke pengirim |
RTS_TRANSIT | The parcel is on its way back. | No | No | shipment.rts_transit | Return in transit | Retur dalam perjalanan |
RTS_PROBLEM_SHIPMENT | A problem on the way back. | No | No | shipment.rts_problem_shipment | Return issue | Kendala retur |
RTS_DELIVERED | The parcel is back with the sender. | Yes | No | shipment.rts_delivered (and shipment.rts_billed if a fee applies) | Returned to sender | Diterima kembali oleh pengirim |
Rules that always hold
DELIVERED,RTS_DELIVEREDandCANCELLEDare final.- Once a shipment is in a return status (
RTS_*), it never goes back to the normal path. - A failed pickup attempt that the courier will retry keeps the shipment in
PENDING_PICKUP. - A status change without its own event is sent as
shipment.status_updated. Accept unknown events and unknown statuses without failing: new ones may be added.
"Can cancel" refers to cancelShipment. "Request only" means
Shipping Engine asks the courier, and the courier decides. See
Cancellations and refunds.
Order statuses
An order groups shipments and is paid once. Its status tells you whether it was paid, not where the parcels are.
Order status | When you see it | Label (EN) | Label (ID) |
|---|---|---|---|
DRAFT | Created, but payment or courier booking failed. Any charge has been refunded. | Not paid | Belum dibayar |
CONFIRMED | Paid and sent to the couriers. A successful POST /b2b/orders returns this. | Confirmed | Dikonfirmasi |
CANCELLED | Every shipment in the order was cancelled with cancelOrder. | Cancelled | Dibatalkan |
The order status list also contains WAITING_FOR_PAYMENT, FAILED and COMPLETED. Orders created
through the API don't rely on them. An order stays CONFIRMED while its parcels are delivered or
returned, so always use the shipment status for delivery progress.
Courier status mapping
Each courier reports progress with its own codes. Shipping Engine translates them into the statuses
above. The tables list every courier value Shipping Engine recognises, as it appears in
data.mapping_code. Values are matched without regard to upper or lower case.
Use status, not mapping_code
Couriers add and rename codes. A value that isn't listed may still be recognised from its description,
or may leave the status unchanged. mapping_code can also be null. Use it to show detail, never to
decide what a shipment's status is.
Anteraja (ANTERAJA)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | 100 |
IN_TRANSIT | 200, 210, 220, 334, 332, 330, 230, 240, 450, 470, 471, 472, 473, 500 |
DELIVERED | 250 |
CANCELLED | 420, 430 |
Blitz (BLITZ)
pickup_failed and dropoff_failed are attempts that Blitz retries, so the status doesn't change to a problem.
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | created, pickup_started, pickup_failed |
IN_TRANSIT | pickup_done, dropoff_started, dropoff_failed, midmile_pickup_done, arrived_blitz_hub |
DELIVERED | dropoff_done |
CANCELLED | cancelled_by_blitz, cancelled_by_business |
PROBLEM_SHIPMENT | allocation_failure, pickup_failure, delivery_failure |
RTS_DELIVERED | returned_to_business |
Dash (DASH)
FAILED_PICKUP means the parcel never left the sender, so the shipment is cancelled and refunded. FAILED_DELIVERY and DISPOSED (the parcel was written off by Dash) are problems. Contact support about them.
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | QUEUEING, ALLOCATING, PENDING_PICKUP, PICKING_UP, PREPARING, VERIFIED, NOT_VERIFIED, ARRIVED_AT_PICKUP_POINT |
IN_TRANSIT | PENDING_DELIVERY, IN_DELIVERY, ARRIVED_AT_DESTINATION |
DELIVERED | COMPLETED |
CANCELLED | CANCELLED, FAILED_PICKUP |
PROBLEM_SHIPMENT | FAILED, FAILED_DELIVERY, DISPOSED |
RTS_CONFIRMED | PENDING_RETURN |
RTS_TRANSIT | IN_RETURN, ARRIVED_AT_RETURN_POINT |
RTS_PROBLEM_SHIPMENT | FAILED_IN_RETURN, ON_HOLD |
RTS_DELIVERED | RETURNED |
GrabExpress (GRAB)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | ALLOCATING, PENDING_PICKUP, PICKING_UP |
IN_TRANSIT | PENDING_DROP_OFF, IN_DELIVERY |
DELIVERED | COMPLETED |
CANCELLED | CANCELED, CANCELLED |
PROBLEM_SHIPMENT | FAILED |
RTS_TRANSIT | IN_RETURN |
RTS_DELIVERED | RETURNED |
ID Express (IDX)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | Scheduled to Courier, Pickup Failure, Pickup Failed |
IN_TRANSIT | Dropped Off at Store, Pick up scan, Pick up, Loading scan, Sending scan, Sending, Arrival scan, Arrival, Unloading scan, Delivery Scan, OnDelivery |
DELIVERED | POD scan, POD Entry, POD |
CANCELLED | Cancel Order New, Cancel Order, Automatic Cancel |
PROBLEM_SHIPMENT | Problem on Shipment scan, Problem on Shipment, Create Return Bill |
RTS_CONFIRMED | Return Confirm, Confirm Return, Bill Returned |
RTS_DELIVERED | Return POD Scan, Return POD |
JNE (JNE)
JNE codes are matched on the status code first, then on the status text.
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | REQ, PR1, PR2, F01, F02, F03, F04, MP |
IN_TRANSIT | RC1, PU1, PU2, RC2, OP1, OP2, TP1, TP2, TP3, TP4, TP5, IP1, IP2, IP3, OP3, BI1, BI2, BI3, OP4, HL3, R14, T14, WH1, WH3, T01, T02, T03, T05, T13, 102, 403, S01, PU0, OPX, OMX |
DELIVERED | DB2, DB1, CR3 |
CANCELLED | CR2, F05 |
PROBLEM_SHIPMENT | CR4, CR5, CR6, U01, U02, U03, U04, U05, U06, U07, U09, U10, U11, U12, U13, U14, PS1, PS2, PS3, PS4, R24, R25, R37, HL7, D37, HL1, HL2, HL4, DP3, DP4, KRK, KRP, KRT, FOM, WH4, U21, U22, U23, U24, U25, X1, X2, X31, X32, X4, X5, X71, X72, X8, X9, X6, X10, T04, T06, T07, T08, T09, T10, T12, 305, 307, 914, 915, OS, UB2, UB1, F06, U08 |
RTS_TRANSIT | D15, D16, T11, WH2, CR1 |
RTS_DELIVERED | R01, R02, R03, R04, R05, R06, R07, R08, R09, R10, R11, R12, R26, CR8 |
J&T Express (JNT)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | 101, 151 |
IN_TRANSIT | 100 |
DELIVERED | 200 |
CANCELLED | 162, 163 |
PROBLEM_SHIPMENT | 150, 152 |
RTS_CONFIRMED | 401 |
RTS_DELIVERED | 402 |
Lalamove (LALAMOVE)
DRIVER_ASSIGNED is a Lalamove event, not an order status. It keeps the shipment in PENDING_PICKUP, adds the driver details and sends shipment.pending_pickup. EXPIRED and REJECTED (no driver found, or the order was refused) send shipment.pickup_failed.
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | ASSIGNING_DRIVER, ON_GOING, DRIVER_ASSIGNED |
IN_TRANSIT | PICKED_UP |
DELIVERED | COMPLETED |
CANCELLED | CANCELLED, CANCELED |
PROBLEM_SHIPMENT | EXPIRED, REJECTED |
Lion Parcel (LION)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | SHPCRT, SHPSCD, CRRSRC, CRRSCD, CRROTW, CRRCNC, CRRNFD |
IN_TRANSIT | BKD, PUP, STI-SC, STI, INHUB, OUTHUB, BAGGING, CARGO PLANE, CARGO TRUCK, CARGO TRAIN, CARGO SHIP, TRANSIT, STI-DEST, STI DEST-SC, KONDISPATCH, STLDISPATCH, HND, DEL, STO-SC, INTHND, INT-STI, OCC-EXP, OCC-IMP, PICKUP_TRUCKING, DROPOFF_TRUCKING, DRPCRT, OCC, CRRPIC, CRRDON |
DELIVERED | POD |
CANCELLED | CNX, ADMCNC, CSTCNC |
PROBLEM_SHIPMENT | DEX, SCRAP, SHORTLAND, MIS-ROUTE, STT ADJUSTED, HAL, ODA, MISSING, DAMAGE, NOT RECEIVE, NOT RECEIVED, CLAIM, REROUTE, STT REMOVE, CODREJ, CI, STT Adjusted after POD, MISBOOKING, REJECTED |
RTS_CONFIRMED | RTS |
RTS_TRANSIT | RTSHQ |
Ninja Xpress (NINJA)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | Pending Pickup, Pending Pickup, Shipper Dropoff |
IN_TRANSIT | Picked Up, In Transit To Origin Hub, Arrived at Origin Hub, Arrived at Transit Hub, Arrived at Destination Hub, In Transit to Next Sorting Hub, On Vehicle for Delivery, At PUDO, Pending Customer Collection, Parcel Measurements Update, Delivery Exception, Pending Reschedule, Delivery Exception, Reattempt Scheduled |
DELIVERED | Delivered, Delivered, Collected by Customer, Delivered, Left at Doorstep, Delivered, Received by Customer |
CANCELLED | Cancelled |
PROBLEM_SHIPMENT | Delivery Exception, Max Attempts Reached, Delivery Exception, Parcel Overstayed at PUDO, Pickup Exception, Pending Reschedule |
RTS_CONFIRMED | Delivery Exception, Return to Sender Initiated |
RTS_DELIVERED | Returned to Sender, International Transit, Returned to Sender at Origin Facility |
Paxel (PAXEL)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | RTP, COL, RAP, CONFIRMED |
IN_TRANSIT | PAPV, POL, COD, POD, ODL, UNDLM |
DELIVERED | PDO |
CANCELLED | PRJL, CCS |
PROBLEM_SHIPMENT | HAPH |
RTS_DELIVERED | RTN |
SAP Express (SAP)
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | ENTRI (SEDANG DI PICKUP), ENTRI (PENDING PICKUP), ENTRI (SEDANG PICKUP ULANG) |
IN_TRANSIT | PICKED UP PAKET, ENTRI VERIFIED, MANIFEST OUTGOING, OUTGOING SMU, INCOMING, DELIVERY |
DELIVERED | POD - DELIVERED PAKET |
CANCELLED | VOID PAKET, VOID_PICKUP PROSES PICK UP, VOID_PICKUP |
PROBLEM_SHIPMENT | POD - UNDELIVERED PAKET |
RTS_CONFIRMED | OUTGOING RETURN, INCOMING RETURN, DELIVERY RETURN |
RTS_DELIVERED | SHIPMENT RETURN TO CLIENT |
SPX (Shopee Express) (SPX)
1000 means SPX is still creating the order. 5001 is a failed pickup attempt that SPX retries. 2002 to 2005 only occur on cross-border shipments.
Shipping Engine status | Courier value (mapping_code) |
|---|---|
PENDING_PICKUP | 1001, 1000, 5001 |
IN_TRANSIT | 2001, 2006, 2002, 2003, 2004 |
DELIVERED | 4001 |
CANCELLED | 7001 |
PROBLEM_SHIPMENT | 3001, 5002, 5003, 2005 |
RTS_TRANSIT | 6001 |
RTS_PROBLEM_SHIPMENT | 6002 |
RTS_DELIVERED | 6003 |
Was this page helpful?