Fulfillment labels

The exact persist rules inside the label processor were not re-read line by line for this page. The status map is what allows the failure status and the retry edge back to LABEL_CREATING.

Retry

Bull default attempts on this queue are 3 with exponential backoff of 2 seconds, if the processor throws. A catch that records LABEL_CREATION_FAILED and returns normally will not use the remaining Bull attempts. Confirm the processor before you tell an operator to “wait for retry.”

A later transition from LABEL_CREATION_FAILED to LABEL_CREATING is the application-level retry.

Idempotency

Unknown per carrier. A second ship() after the courier already created a waybill can purchase a second label. Wallet token debit is a separate event on order.confirmed, not on label success. Whether a failed label refunds a token is unknown.

Warehouse app

Pick, pack, and dispatch in pnxt-warehouse call the API. Barcode scanning and an offline SQLite queue are described in the workspace README. That local queue is the mobile client’s, not Bull.