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.

• The support inbox system has been restructured to improve response times and prioritize customer interactions.
• Three distinct inboxes have been established:
• SB-FP: Subify First Plan Tickets
• SB-C: Subify Chats
• SB-E: Subify Emails
• Priority is given to tickets in the SB-FP inbox, followed by chats in the SB-C inbox, and then emails in the SB-E inbox.
• Conversations from customers with premium service plans will be marked for priority handling within each inbox.
• This change aims to reduce response times and enhance the overall support experience.
• Acknowledgment of the need for clearer separation between email and chat communications has been addressed.
• There may be temporary issues with existing conversations remaining assigned to previous inboxes, which will be resolved promptly.
• Feedback and questions regarding this update are encouraged.

• A new protocol has been established for handling stores identified as suspicious.
• A notification will be sent to merchants whose stores do not comply with our terms and conditions.
• The notification will inform the merchant that their contracts have been stopped and their selling plans deleted due to non-compliance.
• Merchants will be directed to review the terms and conditions through a provided link.
• If merchants believe the action was taken in error or wish to discuss the matter further, they will be instructed to contact support via email.
• Merchants can be suspended based on the discretion of the team, and the notification will be sent accordingly.
• Common indicators of suspicious activity include requests to remove all subscription-related data from product pages or checkout processes.
• A sample of a suspicious store has been provided for reference.
• Please ensure to manually remove any active subscription plans from the panel before sending the notification.

• Users can now add a widget to the home page or customer landing pages independently.
• To implement the widget, follow these steps:

1. Access the theme editor and create a section titled "Featured Products" if it does not already exist. 2. Select the newly created section and, on the right side of the page, choose "Select Product" to add a product with a selling plan. Ensure the selected product has a selling plan to display the widget correctly. 3. Navigate to the top of the page, click on the menu, and select "Edit Code." 4. In the Sections directory, locate and select "featured-product.liquid." 5. Insert the provided code into "featured-products.liquid," preferably after the line: {%- assign product = section.settings.product -%}. 6. Click "Save" and preview the changes to confirm the widget appears in the featured product section.

• To remove the widget, simply delete the inserted code.
• For customization of the featured product widget, the class ".page-index" can be utilized.

• Introduction of customization capabilities for the customer portal within the application panel.
• Enhanced translation options for improved user experience in the customer portal.
• Additional permissions implemented for the customer portal to enhance functionality.