> 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/xoro-shopify-implementation-deep-dive/orders-created-without-payment-shopify-integration.md). # Orders Created Without Payment (Shopify Integration) *** ### Issue Orders are successfully imported from Shopify, but: * The invoice shows as **unpaid** * No deposit is created * The order may not get allocated or processed further *** ### Why This Happens When an order is imported, the system performs two separate actions: 1. Creates the order 2. Attempts to attach the payment (deposit) If the system cannot map the Shopify payment to a configured account, the payment is skipped. As a result: * Order is created * Payment is not recorded *** ### Common Causes This issue usually occurs when: * Shopify payment methods are not mapped to deposit accounts * A new payment method was added, but not configured * Payment waiver setting is enabled * Account mappings were changed or removed *** ### How to Fix #### Step 1: Verify Payment Mapping * Navigate to **Orders → Accounts Settings** * Check all Shopify payment methods * Ensure each method is mapped to a valid deposit account *** #### Step 2: Check Payment Waiver Setting * If enabled, the system allows orders without payment * Disable this setting if payment should be mandatory *** #### Step 3: Resync the Order * After updating the settings, resync the affected order * The system will now correctly attach the payment *** ### Expected Result After Fix * Deposit is created * The invoice is marked as paid * Order proceeds to allocation and processing *** ### Key Note Order creation and payment attachment are handled separately.\ If payment mapping is missing or incorrect, the system will still create the order but skip the payment. --- # 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/xoro-shopify-implementation-deep-dive/orders-created-without-payment-shopify-integration.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.