> 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/shopify/shopify-native/integration/integration-overview.md).

# Integration Overview

How Shopify checkout, webhooks, and ESW order import fit together.

{% hint style="danger" %}

#### Managed Process

* Integration is implemented by ESW.
* Contact your ESW onboarding manager.
  {% endhint %}

Shopify’s native checkout for the shopper purchase flow.

After checkout, the app imports Shopify order into ESW as an **offline order**.

ESW then drives the downstream operational flow.

***

* Logistics and shipping orchestration
* Compliance
* Order tracking and post‑purchase workflows

### High-level flow

![](https://content.gitbook.com/content/OZrcZKoZhyUFlsuSu228/blobs/HubGq2n1QH0G2QEJm6M6/image)

{% stepper %}
{% step %}

### Shopper checks out in Shopify

The shopper completes checkout in Shopify.

Shopify creates the order in your store.
{% endstep %}

{% step %}

### Shopify notifies your integration

Your integration receives order events through Shopify webhooks.

Typical topic: `orders/create`.
{% endstep %}

{% step %}

### Your integration imports the order into ESW

Map Shopify order data to the ESW order model.

Submit it to ESW as an **offline order** (or your ESW-required type).
{% endstep %}

{% step %}

### ESW fulfills and updates flow back to Shopify

ESW handles fulfillment execution.

Shipment, tracking, and status updates should be reflected back in Shopify.
{% endstep %}
{% endstepper %}

### Related topics

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Order Management</td><td><a href="broken://spaces/69bGsllGv04t8wHIHruV/pages/87129aebd2293f4c97a2bd786b43a3faf3aa3011">Broken link</a></td></tr><tr><td>Product Catalog Sync</td><td><a href="broken://spaces/69bGsllGv04t8wHIHruV/pages/95e056cc6dfc121c604f5ea3d9c3b8ac0f214a8d">Broken link</a></td></tr><tr><td>Pricing Import</td><td><a href="broken://spaces/69bGsllGv04t8wHIHruV/pages/beb4a39dc642fb7c9ff52bb6402c350bb98ff47c">Broken link</a></td></tr><tr><td>Shipping Methods, Rates, EDD for New Markets</td><td><a href="broken://spaces/69bGsllGv04t8wHIHruV/pages/32dd5cfcb789743704bc52d748fd8a08e1a5a130">Broken link</a></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.esw.com/shopify/shopify-native/integration/integration-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.