> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/flycode-and-shopify/setup-and-requirements.md). # Setup & Requirements Connecting FlyCode to a Shopify store: nothing to change in Shopify, a few-minute login-and-approve setup, and no developer required. Setting up FlyCode on Shopify is a connection, not a project. This page answers the three setup questions merchants ask. ## Do I need to change anything in Shopify to use FlyCode? No. FlyCode works on top of your existing setup. You keep your subscription app, your checkout, your theme and your billing flows exactly as they are. FlyCode receives failed payment events from the store and the subscription app, decides how to recover each one, and executes the retry through the existing payment connection, then syncs the result back. The one configuration step is in your subscription app rather than in Shopify: at go-live you turn off or align the app's native retry schedule and failed-payment emails so that two systems do not act on the same renewal. ## How do I connect FlyCode to my Shopify store? Log in with your Shopify account and approve the connection when prompted. FlyCode requests the permissions it needs to read subscription and payment events and to retry failed charges, and nothing else. The setup takes a few minutes and does not require changes to your store or subscription app. If you use Recharge or Skio, follow the matching guide for the one or two settings to adjust inside the app: [Integrate FlyCode with Recharge](https://docs.flycode.com/docs/integrations/step-by-step-integrate-flycode-with-recharge) and [Install FlyCode on Skio](https://docs.flycode.com/docs/integrations/how-to-install-flycode-on-skio). Once connected, FlyCode begins working on renewals already in a failed state as well as new failures. ## Do I need a developer to integrate FlyCode with Shopify? No. FlyCode does not require custom code, theme edits or developer work. Most merchants complete the setup on their own in one sitting, and FlyCode support is available by email, Slack and phone if you want someone to walk through it with you or to review your subscription app's dunning settings before go-live. ## Related * [Compatibility & App Support](https://help.flycode.com/flycode-and-shopify/compatibility-and-app-support) * [Getting Started](https://help.flycode.com/what-is-flycode/getting-started) * [Free churn analysis for Shopify subscriptions](https://www.flycode.com/churn-audit-failed-payments) --- # 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://help.flycode.com/flycode-and-shopify/setup-and-requirements.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.