recurrabee — FAQ

recurrabee is a subscription management app for Shopify. It runs on top of Shopify’s native Subscription Contracts API with a real state machine, dunning logic, a Checkout UI extension for self-serve, and a merchant-facing ops console.

recurrabee is in beta. Talk to us at /contact if you want early access — we onboard merchants directly during the beta period.

Most subscription apps store contracts as loose rows and patch edge cases in the UI. recurrabee is built around a proper finite state machine: every transition (active → paused → past-due → cancelled) is guarded, logged, and replayable. Dunning, mid-cycle swaps, and skips are first-class, not retrofits.

Yes. Contracts live in Shopify, not in a parallel store. recurrabee extends Shopify’s subscription primitives rather than replacing them — so checkout, billing, and customer accounts stay native.

Configurable retry schedule with exponential backoff, branded dunning emails (via ZeptoMail), and automatic state transitions when retries exhaust. Failed payments enter a past-due state that merchants can action from the ops console.

Yes. The Checkout UI extension and customer account block let subscribers pause, skip, swap, or cancel without contacting support. Permissions are merchant-configurable.

Shopify Subscription Contracts require merchants to be approved for the subscription APIs — typically Shopify Plus or an approved plan. If you’re not sure, reach out and we’ll help you check.

Yes. recurrabee emits Flow triggers on every state transition so you can automate downstream workflows (tagging, Klaviyo flows, internal alerts).

Pricing is set during beta on a per-merchant basis. Contact us and we’ll walk through it.

Existing subscription contracts remain in Shopify — they’re Shopify’s records, not ours. We disable our billing cycles and webhook subscriptions, retain internal data for 30 days for reinstall continuity, then purge.