> 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/compatibility-and-app-support.md). # Compatibility & App Support How FlyCode works with Shopify subscriptions and which subscription apps it supports (Recharge, Skio, Stay AI and others), using it alongside existing Recharge or Skio dunning flows, and the support S Shopify subscription merchants usually already have a subscription app and some form of dunning in place. FlyCode is designed to fit into that setup rather than replace it. This page covers how it works with Shopify subscriptions, which apps are supported, how it coexists with existing dunning, and what support you get. ## How does FlyCode work with Shopify subscriptions? FlyCode connects directly to your Shopify store and works alongside your subscription management app such as Recharge, Skio or Stay AI. When a subscription renewal fails, FlyCode receives the failed charge, classifies the decline, and retries it using a machine-learning model trained on your store's own payment history to pick the best moment. Where the customer has another payment method on file it can fall back to that, and it coordinates the recovery emails so customers are not contacted while a retry still has a good chance. All of this happens without disrupting your existing stack: the subscription app remains the system that manages the subscription, and Shopify remains where the order and payment records live. ## Which Shopify subscription apps does FlyCode support? FlyCode is compatible with the subscription apps in the Shopify ecosystem, with step-by-step integration guides for Recharge and Skio and native support for Stay AI. Because FlyCode acts on the failed payment and syncs the result back to the subscription app, adding support for another app does not require changes on the merchant side. If you use an app not listed in the guides, contact FlyCode support to confirm the connection path. ## Can I use FlyCode if I already have dunning flows set up in Recharge or Skio? Yes. FlyCode can enhance your existing dunning flows or replace them. Its coordination engine avoids overlap: it will not send an email after a soft decline that a retry is likely to fix, and it will not message a customer while a retry is already in progress. In practice most merchants turn off the subscription app's own retry schedule and failed-payment emails at go-live so that FlyCode owns retries and (optionally) messaging, while keeping the app's cancellation flows, skip and swap options and everything else unchanged. If you prefer to keep your own email tool for messaging, FlyCode can handle retries only. ## What kind of support do I get as a Shopify merchant? FlyCode customers have access to expert support via email, Slack and phone. The team brings more than 15 years of experience in payments and eCommerce, including the co-founders' backgrounds at payments companies, and helps with setup, go-live configuration of your subscription app's settings, and ongoing review of recovery performance. Enterprise merchants get a dedicated contact. ## Related * [Setup & Requirements](https://help.flycode.com/flycode-and-shopify/setup-and-requirements) * [Backup Payment Methods](https://help.flycode.com/backup-payment-methods) * [Supported payment and subscription platforms](https://docs.flycode.com/docs/integrations/supported-payment-and-subscription-platforms) --- # 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/compatibility-and-app-support.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.