Product subscription and repeat order management system
The customer changes, pauses or continues to subscribe to the goods. The team sees his/her choice change to another order and payment.
The frequency of replenishment, product consumption, payment errors, pause, change, and service history are not in one go. Unnecessary recalls, payment losses, and customer service work are on the increase.
How the solution works
- The customer chooses a periodic order or a separate replenishment reminder.
- Before the new cycle, its changes, pauses and agreed conditions are applied.
- Periodic payment and booking are executed in a prescribed order; the error starts a clear recovery process.
- The customer sees the result and can usually change the next cycle or terminate the subscription.
Key challenges
- Subscriptions and re-purchases are managed separately
Solution capabilities
Client-controlled cycle
The customer can change the frequency, quantity or other allowed choice of delivery and sees from which order change will power.
Handling of a failed payment
The customer is given a clear way to renew the payment, and repeated testing is combined with the payment provider and the sending status.
Addition reminder
If there is no automatic order, the customer receives a reminder in an agreed manner and approves another purchase himself.
Reasons for cancellation
The team separates the product's no longer needed, through frequent supply, price and payment error, to address a specific cause of loss.
Business context
- Subscriptions and re-purchases are managed separately
- The frequency of replenishment, product consumption, payment errors, pause, change, and service history are not in one go. Unnecessary recalls, payment losses, and customer service work are on the increase.
- Re-purchase adapts to customer need
- It is important for the subscription customer to change the quantity himself, to pause the shipment or arrange the payment. The clear impact of choices on another order reduces the likelihood of unexpected shipments and complaints. The brand can maintain recurring sales by giving the customer understandable control.
Core features
- Client-controlled cycle
- Handling of a failed payment
- Addition reminder
- Reasons for cancellation
Key integrations
- E-commerce platform
- Subscribed product, customer choices and self-service actions.
- Payment Service Provider
- A provider identifier, a status of success or failure and an update of the payment method are used for periodic payment.
- ERP/Order System
- Real order, stock and execution status of each cycle.
- Marketing/Communication System
- Reminders, payment recovery communication and permitted retention actions.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Share of unsuccessful recurring payments not restored by maintaining subscription
3–16%Decreasing
This illustrative scenario assumes that 15-40% of the capacity metric is affected by allocation and preparation. That share is assumed to fall by 20-40%. Company data is needed to verify both the addressable share and the resulting change.
Counts the portion of failed periodic payments that failed to be restored within the agreed time while continuing the subscription. The denominator is all failed periodic payments of the same group.
Part of subscription recalls for controlled product, frequency or service reasons
3–16%Decreasing
This illustrative scenario assumes that 15-40% of the capacity metric is affected by allocation and preparation. That share is assumed to fall by 20-40%. Company data is needed to verify both the addressable share and the resulting change.
The reasons for the recall are used to separately assess the cases that could have been resolved by a change in frequency, date, product or pause. The percentage is calculated on the number of all cancelled subscriptions.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- The frequency of replenishment, product consumption, payment errors, pause, change and service history are not in a single course
- Unnecessary cancellations, payment losses and customer service work are increasing
Implementation requirements
Subscriptions describe the rules for suspending, changing the payment instrument and cancelling the order being prepared. The state of the cycle chosen by the customer must coincide with the payment and shipment; purchases without continuing obligation are assessed by the adequacy of reminders and quick order.
Further development options
- Customer-controlled change in delivery frequency
- Separation of payment errors from deliberate cancellation