---
title: "Finishes picking a transfer (the scan dialog's \"Complete\"): the transfer leaves the warehouse (In Transit)."
method: POST
path: "/api/v1/sales-orders/{id}/complete-pick"
tags: ["SalesOrders"]
---

# Finishes picking a transfer (the scan dialog's "Complete"): the transfer leaves the warehouse (In Transit).

`POST /api/v1/sales-orders/{id}/complete-pick`

## Request

- Base URL: `https://app.flexonthejob.com`
- URL: `https://app.flexonthejob.com/api/v1/sales-orders/{id}/complete-pick`
- Auth: HTTP bearer

Requires `ManageSalesOrders` and an `Idempotency-Key` header. Body optional:
`{ "transferId": 904 }`; omitted = the order's single `Pending` transfer. Every
line of the transfer must be fully picked (`/pick`). The transfer becomes
`InTransit`, the history records "Transfer dispatched (via API key '…')" and the order's
`status` is recalculated — `Packed` once every line is picked and covered. Stock
stays reserved to the transfer until `/deliver`.

## Path parameters

- `id` integer, required

## Request body

- SalesOrderTransferStepApiRequest: Body of `POST /api/v1/sales-orders/{id}/complete-pick` and `/deliver`; optional. Example: `{ "transferId": 904 }`.
  - `transferId` integer, nullable: The order's transfer to act on. Omit when the order has exactly one transfer in the state the step needs (`Pending` for complete-pick, in transit for deliver). Example: `904`.

## Response `200`

Transfer in transit; the recalculated order status.

- SalesOrderStepResponse: Response of the sales-order fulfilment steps (`/pick`, `/complete-pick`, `/ship`, `/deliver`, `/complete`, `/cancel`).
  - `salesOrderId` integer: The sales order's id. Example: `318`.
  - `status` string: Order status after the step: `Pending`, `Picking`, `Packed`, `Shipped`, `Delivered`, `Complete` or `Cancelled`. Recalculated from the order's transfers, so always read it rather than assuming the next status. Example: `Packed`.
  - `fulfillmentStatus` string, nullable: Aggregate status of the order's transfers (`None`, `Pending`, `InTransit`, `AtWaypoint`, `Completed`, `Cancelled`…), as `fulfillmentStatus` on the order. Example: `InTransit`.
  - `transferId` integer, nullable: The transfer the step acted on (resolved when the request did not name one); null for `/complete` and `/cancel`. Example: `904`.
  - `message` string, nullable: Human-readable confirmation, as the app shows it. Example: `Transfer status updated to In Transit.`
  - `unitsPicked` integer: `/pick`: units marked picked by this call (0 for other steps). Example: `10`.
  - `itemsReturned` integer: `/cancel`: delivered units returned to inventory (0 for other steps). Example: `0`.
  - `transfersCancelled` integer: `/cancel`: transfers cancelled (0 for other steps). Example: `1`.

## Other responses

- `400`: Missing `Idempotency-Key`.
- `401`: Unauthorized
- `403`: Forbidden
- `404`: No such sales order in this organization, or `transferId` is not one of its transfers.
- `409`: The transfer is not `Pending` (detail: `Transfer is already in InTransit status`), some lines are not fully picked (the detail names them), the order has no `Pending` transfer, or the key's creator is unknown.
- `422`: Several `Pending` transfers and no `transferId` (`errors.transferId` lists them).
- `429`: Too Many Requests

---

[API](https://skmtc.dev/flexonthejob/apis/flex-api.md) · [All operations](https://skmtc.dev/flexonthejob/apis/flex-api/llms.txt) · [OpenAPI document](https://skmtc.dev/flexonthejob/apis/flex-api/revisions/19c8f4d27acf?raw)