> 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-inventory.md).

# 3PL Inventory

### Goal

Send the first successful warehouse-originated stock update using the **same** `POST /v1/Inventory/Sync` endpoint, but from the 3PL provider perspective.

### When to use it

Use this when the 3PL warehouse or WMS is the operational truth for on-hand quantities, quarantine stock, or availability by fulfillment center. The same request contract applies: `tenantCode`, `fulfillmentCentreId`, `provider`, and `items` are required.

### Best first scenario

Do not start with a complicated delta or a mixed-status batch just yet. Start with one SKU and one clear stock state. The safest **happy path**, use `articleStatus: "Active"` for a normal in-stock item. To prove exceptional-state support early, a second test can use `articleStatus: "Quarantine"` 

### First-request example from a 3PL

{% code expandable="true" %}

```json
curl -X POST "https://api.test.esw.com/v1/Inventory/Sync" \
  -H "Authorization: Bearer <JWT>" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantCode": "RETAILER_01",
    "fulfillmentCentreId": "FC-LON-02",
    "provider": "ThirdPartyLogistics",
    "items": [
      {
        "sku": "SKU-20001",
        "articleStatus": "Active",
        "quantity": 8
      }
    ]
  }'
```

{% endcode %}

### What to prove in this first run

For the 3PL persona, the main proof is not just that the endpoint accepts JSON; it is that the 3PL can publish stock scoped to a fulfillment center with the correct tenant/provider context. That is exactly what this operation is described to do.

### Good second test after the first success

Once the active-stock call works, run a second inventory sync for a quarantined item using `articleStatus: "Quarantine"` on a separate SKU. That validates a warehouse flow while still staying inside the enum set.


---

# 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-inventory.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.