> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/shopify-app.md). # Shopify App - [Overview](https://docs.pyck.cloud/shopify-app/shopify.md): How the Shopify app connects your store to pyck - [Setup](https://docs.pyck.cloud/shopify-app/setup.md): Installing the Shopify app and connecting your first pyck tenant - [What a sync overwrites in pyck](https://docs.pyck.cloud/shopify-app/data-mapping.md): Which fields a sync overwrites in pyck, which it leaves alone, and how files are handled - [Designing pyck schemas for Shopify](https://docs.pyck.cloud/shopify-app/schema-design.md): How to design pyck schemas so the Shopify app can write into them, and how to name the fields you add - [Sending data to several pyck tenants](https://docs.pyck.cloud/shopify-app/routing.md): Directing products, customers and orders at particular pyck tenants - [Running a test tenant before go-live](https://docs.pyck.cloud/shopify-app/test-tenant.md): Trying pyck on your real orders without shipping anything, then switching to your live warehouse - [Warehouse stock](https://docs.pyck.cloud/shopify-app/stock.md): Letting pyck drive the stock counts your Shopify locations show - [When something looks wrong](https://docs.pyck.cloud/shopify-app/troubleshooting.md): Common symptoms in the Shopify app and what they mean --- # 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.pyck.cloud/shopify-app.md?ask=&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.