> For the complete documentation index, see [llms.txt](https://order-editing.gitbook.io/oe-help-book/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://order-editing.gitbook.io/oe-help-book/integrations/integrating-order-editing-with-your-tech-stack.md).

# Integrating Order Editing with your Tech Stack

Order Editing is designed to work seamlessly with your tech stack. Whether you use a third-party logistics provider (3PL), warehouse management system (WMS), enterprise resource planning (ERP) software, or other e-commerce tools, Order Editing can integrate to ensure smooth order processing and fulfillment.

#### Why Integrations Matter

Proper integration setup is crucial for Order Editing to function correctly with your business operations. Without proper integration configuration, orders may be pulled for fulfillment too early, edits may not sync properly, or your external systems may not recognize post-purchase changes.

<table data-view="cards"><thead><tr><th align="center"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><strong>Fulfilment &#x26; Logistics</strong></td><td><a href="/pages/ALFRMxhCcEAF1szbUMGL">/pages/ALFRMxhCcEAF1szbUMGL</a></td></tr><tr><td align="center"><strong>Enterprise Resource Planning (ERP)</strong></td><td><a href="/pages/aEJjTDfAuUJZWCWvA0Hv">/pages/aEJjTDfAuUJZWCWvA0Hv</a></td></tr><tr><td align="center"><strong>Integration Platform as a Service (iPaaS)</strong></td><td><a href="/pages/lhKgpJxqVRCCk1YVvn4l">/pages/lhKgpJxqVRCCk1YVvn4l</a></td></tr><tr><td align="center"><strong>Order Management System (OMS)</strong></td><td><a href="/pages/YKAxSSCKeukAk2VgdZjN">/pages/YKAxSSCKeukAk2VgdZjN</a></td></tr><tr><td align="center"><strong>Inventory Management Systems (IMS)</strong></td><td><a href="/pages/PqSff5vDUGmL6YyM6dTt">/pages/PqSff5vDUGmL6YyM6dTt</a></td></tr><tr><td align="center"><strong>Third-party Business Platforms</strong></td><td><a href="/pages/OLhqgjk8TL9C9g3WQHS9">/pages/OLhqgjk8TL9C9g3WQHS9</a></td></tr></tbody></table>

***

### How do we integrate?

95% of business systems operate by reading one of three different data points to determine when to download orders:

1. Payment status of "Paid"
2. Condition tag "Released" applied
3. Fulfillment status of "Unfulfilled"

Order Editing leverages these download filters to create the editing period by temporarily preventing these conditions from being met when an order is placed using Shopify Flow.

<a href="/pages/TtIIysq5s9Bhit5ELPYi" class="button primary">Learn more how we integrate</a> <a href="/pages/t84b81R6oqneEnmrWm5y" class="button primary">What is Shopify Flow?</a>

***

### Finished integrating?

Almost there! The next step is complete a test.

<a href="/pages/QzaeYpCvg0f9xE6ysaSz" class="button primary">Go to our test guide</a><br>


---

# 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://order-editing.gitbook.io/oe-help-book/integrations/integrating-order-editing-with-your-tech-stack.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.