> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/fulfillment-api/resources/first-successful-requests/3pl-warehouse-wms.md).

# 3PL warehouse / WMS

### Goal

Confirm the first successful pick-pack result using `POST /v1/PickPack/Confirm`. This endpoint is used by a 3PL to confirm that an order has been picked, packed, and is ready for shipment. The request requires `confirmationId`, `eswOrderReference`, `tenantCode`, and `pickPackResponse`; inside `pickPackResponse`, `status` is required.

### When to use it

Use this when a warehouse has completed pick-and-pack and needs to report the outcome for an order. The response model supports top-level statuses such as `AcceptedForProcessing`, `PartialResult`, `Confirmed`, `Failed`, `BadRequest`, `BadAddress`, and `TimeOut`. It also supports item-level results through `itemsResult`.

### Best first scenario

For a first success, avoid partials and failures. Send a simple fully successful confirmation with `pickPackResponse.status` set to `Confirmed`, and include one item result marked `Success`. The item-level status enum supports `Created`, `Success`, `Failed`, and `PartialResult`.

### First-request example

{% code expandable="true" %}

```json
curl -X POST "https://api.test.esw.com/v1/PickPack/Confirm" \
  -H "Authorization: Bearer <JWT>" \
  -H "Content-Type: application/json" \
  -d '{
    "confirmationId": "conf-10001",
    "confirmationDateTime": "2026-03-13T15:30:00Z",
    "eswOrderReference": "ESW-ORDER-10001",
    "tenantCode": "RETAILER_01",
    "pickPackResponse": {
      "status": "Confirmed",
      "failureReason": "None",
      "itemsResult": [
        {
          "productCode": "SKU-10001",
          "quantityConfirmed": 1,
          "quantityFailed": 0,
          "status": "Success",
          "failureReason": "NotDefined"
        }
      ]
    }
  }'
```

{% endcode %}

### Why this is the right first request

One order, one confirmed item, no exception flow.  `401 Unauthorized` for this endpoint, so this is the best place to validate that your auth setup is working, not just your JSON.

### What <mark style="color:$success;">`first success`</mark> looks like

A successful outcome is 202 Accepted. Common early failures are:

* <mark style="color:$danger;">`401 Unauthorized`</mark> if the Bearer token is missing/invalid
* <mark style="color:$danger;">`400 Bad Request`</mark> if required fields are missing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.esw.com/fulfillment-api/resources/first-successful-requests/3pl-warehouse-wms.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.