We are pleased to announce the release of version 1.41, which includes the following updates:

• Introduction of upsell records in the Django framework.
• A new subscription table that includes details on failed payment reasons.
• Availability of new demo videos to assist users in navigating the updated features.

These enhancements aim to improve user experience and streamline processes.

A new article has been added regarding the payment field, and the billing management article has been edited for clarity and conciseness. This resource addresses common inquiries related to payment failures, including:

• Reasons why subscription payments may fail and recommended actions
• Instructions for customers on how to update their payment method after a failed payment
• Notification procedures for failed payments
• Guidance on retrying subscriptions following a failed payment

Please review the updated article to ensure accurate communication regarding payment failures.

• Introduction of cancellation reasons for subscriptions.
• Implementation of an upgrade notification message.
• Addition of new email templates for user communication.
• Launch of a new campaign feature for analytics.
• Enhancement of the analytics dashboard for improved insights.
• Resolution of a bug related to editing subscription plans.
• Updates to the Monthly Recurring Revenue (MRR) limit requests feature.

• Introduced a new Monthly Recurring Revenue (MRR) limit: Users reaching $300 in revenue will have their accounts locked, prompting an upgrade to their plan. A temporary 100% discount code for two months will be provided to facilitate a smooth transition.
• Implemented A/B Testing for pricing structures. Details for Version A and Version B are available in the provided documentation.
• Updated pricing display in the application listing to reflect the new changes.
• Note: Due to the A/B Testing for pricing, different features may be locked for various users. It is essential to log in as the user to determine their specific plan and feature access.

This release introduces significant updates aimed at enhancing user experience:

• Monthly Recurring Revenue (MRR) Limit: A new feature has been added to subscription plans that allows for the setting of an MRR limit. For example, if a user reaches $1,000 in monthly subscription revenue on the Essential plan, their plan will be locked, requiring an upgrade. This limit can be configured for all plans. Visual representations of the limit and the locking mechanism have been included for clarity.

• Discount Request Form: A new discount request form has been added to the pricing page, designed for businesses that may require financial assistance. Upon submission of the form, the user's email will be directed to the appropriate support team for follow-up and discount processing.

• Customization Portal Lock: The customization portal now features a locking mechanism to enhance security and user management.

Further details regarding these features will be communicated in due course.

We are pleased to announce the release of version 1.31.0, which includes several important updates:

• Introduction of email customization features, allowing users to tailor email communications.
• Resolution of issues related to the first plan ticket functionality.
• Fix for the customer portal login bug, enhancing user access.
• Removal of the button for sending email links to customers from the sub-contract interface.

For further details on email variables, please refer to the relevant documentation.

This update provides instructions on how to update the merchant's shop logo in the portal and in customer emails.

• For the Portal: Upload the merchant logo file in the designated area.
• For Emails: Insert the merchant logo link in the logo source code of the emails sent to customers. Use the following code snippet to display the logo:

```html {% if shop.logo %} {% else %}

{{ shop.name }}

This ensures that the correct logo is displayed in both the portal and customer communications.

• Updated migration articles with additional steps for pre- and post-migration processes.
• Successfully completed migrations for three clients this week.
• Identified and addressed several errors occurring during the migration modal for clients transitioning from a specific platform.
• Recommended to verify all pre-migration steps are completed before proceeding with data access requests.
• Emphasized the importance of checking specific steps for clients using a particular payment processor.
• A documentation will be created to compile observed errors for future reference and use.

We are pleased to announce the implementation of the suspension feature in the Django framework. This feature allows administrators to suspend merchants effectively.

Key updates include:

• Navigate to the admin panel and select a shop.
• Scroll to the bottom of the page and select "Make Suspension Candidate."
• Proceed to select "Suspend" to complete the process.

Upon suspension:

• Merchants will no longer have access to their management panel and will instead see a notification banner.
• All selling plans and contracts associated with the merchant will be deleted.

Please exercise caution when utilizing the suspension feature, as it significantly impacts the merchant's access and data. Further details regarding the process will be provided.

The new release includes the introduction of the migration modal, which is now accessible on the home page for new shops and under Settings > Migration. Documentation has been updated accordingly.

Please note that there is a known issue with the modal that affects its functionality. A hotfix is scheduled for deployment to address this issue. Users experiencing errors during the pre-migration check will be informed that the issue is being resolved and will be fixed in the next update.