Is your feature request related to a problem? Please describe.
Currently, Subscribie shows the shop owner Abandoned checkouts sign-ups- this is useful from a analytics/marketing perspective permitted (because it shows attempted but not completed checkouts), however, can cause clutter if they acumulate- e.g. an attempted/started checkout from 3 months ago may not be very useful.

Describe the solution you'd like
As a shop owner, I can archive abandoned sign-ups. Note the nuaiance , this is issue is not to archive a subscriber, only the ability to archive an associated Subscription which has not completed it's checkout flow.
tldr: Add the HasArchived mixin to the Subscription model. See additional context below.
Describe alternatives you've considered
Additional context
What do we call these: Abandoned checkouts
Consider user mistakes, how can a shop owner view archived subscription attempts?
Note we have a pattern for allowing the archival (soft-delete) of database records, see
and example usages:
|
class Document(database.Model, HasArchived, HasReadOnly, HasCreatedAt): |
|
class Plan(database.Model, HasArchived, HasCreatedAt): |
Is your feature request related to a problem? Please describe.
Currently, Subscribie shows the shop owner Abandoned checkouts sign-ups- this is useful from a analytics/marketing perspective permitted (because it shows attempted but not completed checkouts), however, can cause clutter if they acumulate- e.g. an attempted/started checkout from 3 months ago may not be very useful.
Describe the solution you'd like
As a shop owner, I can archive abandoned sign-ups. Note the nuaiance , this is issue is not to archive a subscriber, only the ability to archive an associated Subscription which has not completed it's checkout flow.
tldr: Add the HasArchived mixin to the Subscription model. See additional context below.
Describe alternatives you've considered
Additional context
What do we call these: Abandoned checkouts
Consider user mistakes, how can a shop owner view archived subscription attempts?
Note we have a pattern for allowing the archival (soft-delete) of database records, see
and example usages:
subscribie/subscribie/models.py
Line 1275 in 4ba736e
subscribie/subscribie/models.py
Line 655 in 4ba736e