The Subify platform has been updated to version 2.27. This release does not include any new features. Users can review the associated changes and bug fixes in the release notes.

Release 2.24 has been deployed. The following changes are now visible to users:

• Two minor updates have been implemented that enhance the merchant experience.

For more details, please refer to the official documentation.

The following updates are included in Release 2.23:

• Added a Help tab with an "Email Us" section for improved user support.
• Reordered the display of selling plans for enhanced clarity and accessibility.

For additional details, please refer to the release documentation.

The following updates have been made in Release 2.22:

• No major changes are introduced that will be noticeable to users or merchants.

For detailed information regarding the release, please refer to the official documentation.

The following outlines the key aspects of widget customization:

• Overall Structure:
• The widget is composed of HTML elements and tags that contain various types of content.
• Customization is limited to the content text; HTML tags themselves cannot be altered.

• Styles:
• Styles are applied to HTML tags to enhance visual appearance.
• Customization of styles is permitted.

• Logical Code:
• This component manages the functionality of the widget, such as updating text and IDs based on selling plan changes or applying discounts.
• Users are not permitted to modify the core logic of the widget. Developers may extend the SDK's logic using the provided documentation, but cannot change the fundamental logic.

• SDK Features:
• The SDK is designed to facilitate widget selection and usage for users without coding knowledge.
• Selling plans created by the backend are intended for use within the platform and do not require the SDK for implementation.
• Merchants with a developer experienced in front-end development can utilize Liquid or API to access and display backend-created selling plans, bypassing the need for the SDK.

We are pleased to announce the release of Subify version 2.21. This update includes the following enhancements:

• Added the ability to incorporate widgets into additional pages and collection pages.
• Introduced permission settings for widgets, now accessible in the widget tab.
• Enhanced merchant visibility and management capabilities for this feature.

For further details, please refer to the accompanying documentation.

• The Jira workflow has been updated to streamline the process by removing unnecessary statuses.
• Users will now work with a single status: "TO DO P SUB" for issue management.
• The workflow process is as follows:
• An issue is created and enters the "TO DO P SUB" status.
• The issue will be reviewed and moved to one of the following statuses:
• DONE
• PENDING SUPPORT
• CANCEL
• TO DO TECH SUB
• If an issue returns to the support team (PENDING SUPPORT), it can be reverted back to "TO DO P SUB" for further action.
• The previous "CHECK-IN" statuses have been removed as they were not utilized effectively.
• The "QA PASSED" status indicates that testing has been conducted on an issue, and the task will be marked as DONE only after all release-related tasks are completed.
• The Intercom board workflow has also been reviewed to ensure synchronization with these changes, and additional columns have been removed.
• All issues currently marked as PENDING SUPPORT will be addressed and updated accordingly.

The latest release of Subify has been deployed. This update includes enhancements to the user interface and user experience for the subscription plan creation process. No new features have been added in this release. Further details will be provided in an upcoming video presentation.

The migration workflow for the system has been updated. Additionally, insights regarding the migration process from a previous version have been compiled and shared in a video. Feedback on these updates is encouraged.

The following changes have been implemented in this release:

• The wizard feature has been removed for all users.
• A quarterly feature has been added, with further details provided in the accompanying documentation.
• Selling plans created will now be live by default, unless the user chooses to deactivate them.
• Subscription plan statuses have been updated from "Draft" and "Live" to "Active" and "Inactive," with functionality remaining unchanged.
• Users can no longer set paid features while in draft mode; all paid features will be locked until an upgrade is performed.

These changes have been made in response to recent user feedback and testing results, which indicated an increase in user churn. The removal of the wizard feature aims to improve user experience and retention. Additionally, the previous draft status for selling plans and the ability to set paid features in draft mode were found to be confusing for users, contributing to churn.

We appreciate your understanding and cooperation as we implement these changes, and we anticipate positive outcomes following this release.