Subscription Renewal · Auto-Renewal / Recurring Commerce¶
A recurring subscription is renewed either automatically or after a customer reminder and confirmation prompt. The scenario covers renewal preparation, payment handling, retry logic, and lifecycle updates so continuity of service or replenishment is preserved.
| Domains | commerce · payment |
| Actors | customer · system · customer-service |
| Process | Subscription Renewal |
| Capabilities | 4 |
| Steps | 8 |
| Events | 9 |
| Lifecycles | 4 |
| Min UCMI | 2.6 |
⚙️ Step-by-Step Flow¶
| # | Step | Actor | Lifecycle | State Change | Event |
|---|---|---|---|---|---|
| 1 | Identify due subscriptions | system | customer-lifecycle |
active → active | customer-identified |
| 2 | Send renewal reminder | system | subscription-lifecycle |
active → renewal-pending | customer-communication-sent |
| 3 | Generate renewal order | system | order-lifecycle |
draft → confirmed | order-created · order-confirmed |
| 4 | Attempt payment authorisation | system | payment-lifecycle |
pending → authorised | payment-authorized |
| 5 | Capture renewal payment | system | payment-lifecycle |
authorised → captured | payment-captured |
| 6 | Renew subscription term | system | subscription-lifecycle |
renewal-pending → active | subscription-renewed |
| 7 | Close renewal order | system | order-lifecycle |
confirmed → completed | order-closed |
| 8 | Send confirmation or retry guidance | system | subscription-lifecycle |
active → active | customer-communication-sent |
⚡ Event Sequence¶
customer-identified → customer-communication-sent → order-created → order-confirmed → payment-authorized → payment-captured → subscription-renewed → order-closed → customer-communication-sent
🔄 Lifecycles Involved¶
🧩 Capabilities Required¶
| Capability | |
|---|---|
subscription-management |
Subscription Management |
payment-processing |
Payment Processing |
order-management |
Order Management |
customer-identity |
Customer Identity |
🖥️ Application Coverage¶
Applications that implement the capabilities required by this scenario.
| Capability | Implementing Applications |
|---|---|
subscription-management |
eCommerce Platform |
payment-processing |
POS · Payment Hub |
order-management |
OMS · eCommerce Platform |
customer-identity |
POS · eCommerce Platform |
📊 Readiness by Profile¶
Capability readiness across assessment profiles.
| Profile | Capabilities Met | Avg Score | Ready? |
|---|---|---|---|
| Acme Electronics | 3/4 | 1.5 | ❌ |
| BuildPro Trade | 3/4 | 2.0 | ❌ |
| Flash Delivery | 4/4 | 2.8 | ✅ |
| Luxe Maison | 2/4 | 2.0 | ❌ |
| Metro Fresh Group | 3/4 | 2.0 | ❌ |
| Stella Fashion Group | 3/4 | 1.8 | ❌ |
| Reference Tier 2 Non-food Retailer | 3/4 | 2.2 | ❌ |
✅ Preconditions¶
- Subscription plan is active and due for renewal based on schedule
- Customer identity is valid and linked to a renewable payment instrument
- Retry policy is configured for failed payment attempts
- Order creation is enabled for the subscription business model
🎯 Success Criteria¶
- Renewal is completed without manual intervention when payment succeeds
- Customer receives timely pre-renewal and post-renewal communication
- Retry logic is applied consistently before subscription pause or expiry actions
- Subscription and order records remain synchronised for audit and support use cases
⚠️ Failure Modes¶
- Payment authorisation fails repeatedly and subscription enters grace or pause state
- Customer account is inactive, preventing renewal execution
- Order is created but payment cannot be captured, requiring rollback or support case
- Reminder communication is delayed, leading to avoidable churn or support contact
UCMI Requirements¶
Minimum UCMI Score: 2.6
| Capability | Minimum Level |
|---|---|
subscription-management |
🟠 2 |
payment-processing |
🟠 2 |
order-management |
🟠 2 |
customer-identity |
🔴 1 |
UC-BoK Scenario Catalog · All Scenarios · Scenario Catalog