> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/connected-apps/shopify/splitting-shopify-orders-by-fulfillment-location.md).

# Splitting Shopify Orders by Fulfillment Location

A Shopify order may contain items that need to be fulfilled by different businesses or locations. Instead of processing the entire order as a single transaction, Xoro can split the order based on the fulfillment location assigned to each item in Shopify.

When an order is split, each fulfillment is processed independently in Xoro while remaining linked to the original Shopify order. The way the split fulfillment is created in Xoro depends on whether the Shopify channel is configured to process orders as **Sales Orders** or **Invoices**.

The following workflows explain how split fulfillments are handled in each configuration:

* **Shopify Fulfillment as Split Orders** — Processes each fulfillment as a separate **Sales Order** in Xoro.
* **Shopify Fulfillment as Fulfilled Invoices** — Processes each fulfillment as a separate **Invoice** in Xoro.


---

# 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://docs.xorosoft.com/xoroerp-1/connected-apps/shopify/splitting-shopify-orders-by-fulfillment-location.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.