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

# Shopify

The **Shopify–XoroERP integration** enables businesses to synchronize their online sales channels with their ERP workflows in real time. This integration facilitates **automated syncing of orders, inventory levels, customer information, product details**, and **fulfillment statuses** between Shopify and XoroERP. Once connected, data flows effortlessly between the two systems, eliminating the need for manual data entry and reducing the risk of errors.

Whether it’s pulling order data from Shopify into XoroERP for processing, updating stock levels after fulfillment, or pushing product updates back to the online store, this integration empowers businesses to operate with greater efficiency and clarity. The goal is to ensure your operations stay agile, automated, and in sync so you can focus on growth, not on managing disconnected systems.

This article will walk you through how the integration works, the key fields it supports, and how you can configure it to suit your operational needs within XoroERP.


---

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