Developer advisory: Subscriptions core code moving into WooCommerce Subscriptions plugin

The details

The underlying “core” code that powers the WooCommerce Subscriptions plugin is now being managed directly within the same repository as the main plugin.

Previously, this functionality lived in a separate codebase (Automattic/woocommerce-subscriptions-core) that was publicly available. Moving forward, it will live directly within the Subscriptions plugin that is distributed via WooCommerce.com.

Why this change?
This change brings Subscriptions back to a single codebase, and is part of a broader effort to:

• Reduce complexity by unifying the code into a single repository
• Eliminate the need to manage versioning and releases across two separate codebases
• Align with how we manage source code for other WooCommerce extensions

This structure better supports the ongoing evolution of Subscriptions, while continuing to deliver the same features and API surface developers rely on today.

ℹ️ This was always a behind-the-scenes technical split created to meet internal needs, not a community-facing project. Bringing it back together reflects how the product is actually used and delivered.

How can I tell if this affects me?

You are affected only if:

• You are directly depending on woocommerce-subscriptions-core in your own Composer setup.
• You have code that depends on or references the Automattic/woocommerce-subscriptions-core package.
• You’re monitoring that repository for updates, bug fixes, or changes.

If you’re using WooCommerce Subscriptions as a plugin, or integrating with it via its public API or hooks, you don’t need to do anything.

There are no breaking changes or behavior differences in how Subscriptions works

What action should I take?

If you were relying on Automattic/woocommerce-subscriptions-core in any way:

1. All Subscriptions functionality is now part of the WooCommerce Subscriptions plugin. You’ll continue to get all updates and features through the plugin release process as usual.
2. You can safely stop using woocommerce-subscriptions-core going forward.
3. Clean up dependencies. If you’re requiring woocommerce-subscriptions-core via Composer or other tooling, please remove it, as the code will no longer be available.

Timeline

The public Automattic/woocommerce-subscriptions-core  repository will be archived on May 20th, 2025. This means that the code will still be available, in read-only mode: but it will no longer be updated. Additionally, the issue tracker will be closed—though you can of course still reach out via our normal support channels.