Receive a renewal report in Slack

This allows you to track at a glance the proportion of:

orders renewed successfully
orders with upcoming payment attempts
closed orders, for which the various payment attempts have failed

Context reminder for subscription renewals

Active subscriptions have a next payment date from which a scenario with multiple payment attempts begins.

4 payment attempts spaced 3 days apart are configured by default.

It is possible to customize this scenario by choosing:

the number of payment attempts
the number of days between each attempt

Subscription renewal orders are processed at night, when customers are offline.

For a given subscription:

if the transaction is successful, the order is synced with a paid status in Ciklik and pushed to the PrestaShop back-office, the subscription is updated with a next payment date on the next subscription cycle
if the transaction fails, the order is synced with a pending status in Ciklik and is not pushed to PrestaShop, there will be another payment attempt for this subscription according to the defined scenario
if the transaction of the last payment attempt fails, the order is synced with a failed status in Ciklik and is not pushed to PrestaShop, the subscription is updated with a next payment date on the next subscription cycle

In case of payment failure, an email is sent to the subscriber to allow them to validate their order by completing the 3DS verification if needed through the secure payment link contained in the email. For more details on this subject, see this article || .

It is also possible to disable these automatic emails from the Ciklik back-office and build your own email sequence with marketing automation tools like Klaviyo.

Note that other errors (out of stock product, communication with PrestaShop) may occur during subscription renewals.

A report of these errors is then sent to you by email with the list of affected subscriptions according to the nature of the error.

New payment attempts are scheduled for the next day.

Connect Ciklik to your Slack workspace

To track the status of orders related to subscription renewals, you can connect your Ciklik account with your Slack workspace.

Go to your site details from your Ciklik account, then select the Slack Connection action.

You are then redirected to the Slack application to enter the URL of your workspace.

If you have multiple Slack workspaces, select the one you want to link at the top right of the Slack window.

Confirm then select the channel in which you will receive notifications of daily orders related to subscription renewals.

Analysis of the subscription renewal order report in Slack

We will use here an example of a daily report from a fictitious site for which 5 subscription renewal orders were processed overnight.

The first part of the report mentions the proportion of orders:

paid, here none out of 5
failed, here 2 out of 5, corresponding to orders closed because all payment attempts for these 2 orders have failed
pending, here 3 out of 5, orders for which other payment attempts are scheduled

The second part of the report illustrates the proportion of orders in the subscription renewal scenario:

2 pending orders correspond to the first payment attempt for subscriptions (renew)
3 orders (1 pending and 2 failed) correspond to subsequent renewal attempts (retry), of these 3 orders, 2 are closed because it was the last payment attempt