> 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/customs-catalog-api/fulfillment-api/overview.md).

# Overview

The Fulfillment API provides a set of structured, RESTful integration endpoints that replicate standard EDI-based fulfillment data flows between retailers and third-party logistics (3PL) systems. These APIs enable the automated, real-time exchange of catalog, inventory, order, and shipment data across platforms—ensuring consistency, transparency, and scalability for global operations.

While each API corresponds to an EDI transaction type (e.g., `832`, `846`, `850`), the implementation is fully API-first, providing modern payload formats (typically JSON) and transport mechanisms optimized for performance and reliability.

#### Integration Purpose <a href="#integration-purpose" id="integration-purpose"></a>

These APIs establish a unified, scalable fulfillment backbone managed by ESW. They standardize communication across the entire order lifecycle, reduce manual synchronization, and enable multi-node, cross-border operations with the precision and efficiency required for global commerce.

#### What this API Does <a href="#api-functional-overview" id="api-functional-overview"></a>

<table data-view="cards"><thead><tr><th>Flow</th></tr></thead><tbody><tr><td><strong>Inventory Update</strong> <br>Real-time inventory visibility: stock, locations, availability.</td></tr><tr><td><strong>Order Creation</strong><br>Send customer order details to initiate fulfillment.</td></tr><tr><td><strong>Order Validation / Acknowledgement</strong><br>Accept/reject orders after 3PL validation (supports partials).</td></tr><tr><td><strong>Order Shipped</strong> <br>Shipment confirmation with tracking, carrier, and package data.</td></tr></tbody></table>


---

# 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/customs-catalog-api/fulfillment-api/overview.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.