8 October 2026 ordersfix

POST /v1/orders/{id}/accept now does what Accept does in the seller dashboard: it books the courier. The response carries the AWB, the label is ready, tracking starts, and the buyer gets the same emails and SMS as for an order accepted on the website.

What was wrong#

Accept only changed the order's status. The order then sat "accepted" with no courier. An AWB requested afterwards with POST /v1/orders/{id}/awb was booked, but stored without the tracking record courier updates are matched against — so the parcel's progress never reached Biklo: no delivery, no confirmation, and no payout.

What changes for you#

• Call accept as before. Read the AWB from its response (awb.number, awb.tracking_url) and fetch the label from GET /v1/orders/{id}/label.
• If the courier cannot be booked, accept fails and the order stays pending — retry once the reason is fixed: courier_required (422), buyer_phone_missing (422, the buyer has been asked to add one), awb_generation_failed (502).
• POST /v1/orders/{id}/awb still works and is idempotent: it returns the AWB accept booked.

Orders accepted through the API before this change were repaired on our side: the ones without a courier have one now, and every AWB is tracked.