solidusio / solidusio/solidus_subscriptions
Remove ChurnBuster integration
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 49
- Forks
- 53
- Avg merge
- 4h 54m
- Merged PRs (30d)
- 1
Description
Integrating solidus_subscriptions with ChurnBuster seemed like a good idea, but the reality is that it's impossible to make the two work well together: ChurnBuster works well when it's integrated with a natively-supported platform such as Shopify/ReCharge. When that's the case, ChurnBuster can manage the subscriptions directly (e.g., by cancelling them after sending the churn recovery email sequence).
When ChurnBuster is integrated with Solidus and Solidus initiates ChurnBuster campaigns, the timing of emails going out in ChurnBuster and Solidus taking actions such as cancelling the subscription would need to be perfectly synchronized (i.e. Solidus would need to cancel the subscription right when ChurnBuster sends the "subscription cancelled" email). This is impossible to achieve in the real world, which leads to a subpar UX.
Churn recovery with solidus_subscriptions is better done with other services or other third-party tools, but ChurnBuster is definitely not a good option.
My suggestion is to simply remove the integration in the next major version with no deprecation in between.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ChurnBuster integration and all references to it in solidus_subscriptions. Remove the integration as part of the next major version, with no intermediate deprecation, and verify that the remaining subscription functionality still works without it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100