Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(dunning): Add dunning campaign to customer, database changes #2698

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

ancorcruz
Copy link
Contributor

@ancorcruz ancorcruz commented Oct 16, 2024

Roadmap Task

👉 https://getlago.canny.io/feature-requests/p/set-up-payment-retry-logic
👉 https://getlago.canny.io/feature-requests/p/send-reminders-for-overdue-invoices

Context

We want to automate dunning process so that our users don't have to look at each customer to maximize their chances of being paid retrying payments of overdue balances and sending email reminders.

We're first automating the overdue balance payment request, before looking at individual invoices.

Description

The goal of this change is to create set the relationship between customers and dunning campaigns.

A customer could have one dunning campaign applied, or, inherit its organization default campaign (none applied) or, be excluded from dunning at all (with a boolean flag).

Also, when deleting a dunning campaign, all customers with the campaign assigned must be reset.

 ## Roadmap Task

👉 https://getlago.canny.io/feature-requests/p/set-up-payment-retry-logic
👉 https://getlago.canny.io/feature-requests/p/send-reminders-for-overdue-invoices

 ## Context

We want to automate dunning process so that our users don't have to look at each customer to maximize their chances of being paid retrying payments of overdue balances and sending email reminders.

We're first automating the overdue balance payment request, before looking at individual invoices.

 ## Description

The goal of this change is to create set the relationship between
customers and dunning campaigns.

A customer could have one dunning campaign applied,
or, inherit its organization default campaign (none applied)
or, be excluded from dunning at all (with a boolean flag).

Also, when deleting a dunning campaign, all customers with the campaign
assigned must be reset.
@ancorcruz ancorcruz merged commit 0393360 into main Oct 17, 2024
6 checks passed
@ancorcruz ancorcruz deleted the feat/auto-dunning-customer-1 branch October 17, 2024 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants