Subscription management for Shopify
Subscription contracts that don't break when the business grows. Beta
A Shopify-native subscription engine with clear contract state, subscriber self-service, and a merchant-facing operations console.
Currently in beta — onboarding select Shopify brands.
The problem
Most subscription apps treat contracts as loose rows and patch edge cases in the UI. That falls apart the moment a merchant needs dunning retries, mid-cycle swaps, or partial skips — the kind of state that demands a real state machine instead of ad-hoc booleans.
Our approach
We built recurrabee around a guarded contract lifecycle (active → paused → past-due → cancelled), reliable billing-cycle processing, and subscriber self-service that keeps merchants from handling every routine change manually.
Outcome
Merchants run tens of thousands of contracts with clear operational guarantees — every state transition is logged, replayable, and testable. Dunning flows recover revenue that legacy apps silently wrote off.
How it works
- Contracts. recurrabee keeps subscription changes inside a governed contract lifecycle.
- Billing cycles. Due billing runs with configurable dunning on failure.
- Self-serve. Subscribers pause, swap, skip, or cancel through a guided account flow.
Highlights
- State-machine-backed contract lifecycle
- Dunning + retry with configurable policies
- Subscriber self-service for routine contract changes
- Merchant operations views for exceptions and recovery
Common questions
What does recurrabee do?
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.
Is recurrabee in production yet?
recurrabee is in beta. Talk to us at /contact if you want early access — we onboard merchants directly during the beta period.
How is this different from other subscription apps?
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.
Does it use Shopify's native Subscription Contracts?
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.
How does dunning work?
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.
What's new
v0.1.0 ·
Initial beta release
Guides
7 step-by-step guides on installing, configuring, and operating recurrabee.
Want early access?
We're onboarding a small group of stores during beta. Tell us about your stack.
Request access