WooCommerce Subscriptions 9.2.0 Adds Physical Proration

🇹🇷 Türkçe: Bu yazının Türkçesini oku →

Extension releases usually pass without much noise on the developer side. You get a version bump, a couple of settings toggles change, and life goes on. The ones you notice are the ones that quietly move load-bearing hooks and rewrite the security model underneath a plugin that half your recurring revenue depends on. WooCommerce Subscriptions 9.2.0 is one of those.

I have been running subscriptions for enterprise clients since the days when handling recurring billing meant writing your own cron scaffolding and hoping nobody’s card processor timed out overnight. The plugin has matured a lot since then. But maturity in a subscriptions system is a particular kind of thing — it means people build side systems on top of the exact settings you have today, and every “small” schema change costs someone a week of regression work.

The 9.2.0 advisory landed on the WooCommerce Developer Blog on September 8, and there is more in it than the “settings updates” headline suggests. If you build extensions, custom gateways, or account-page overrides for Subscriptions, read this one carefully — a couple of these changes will hit code you wrote two years ago and forgot about.

What is actually new

The official advisory “WooCommerce Subscriptions 9.2.0: settings updates and dev changes” was published on September 8, 2026 by Vasily Belolapotkov on the WooCommerce Developer Blog. The plugin’s product page on woocommerce.com now lists 9.2.0 as the current version, tested with WordPress 7.1 and WooCommerce 11.1.

The headline feature is that proration finally extends to physical products. Historically both “Prorate Recurring Payment” and “Prorate Subscription Length” only applied to virtual items, which was a source of endless custom filter code on any store that shipped physical goods on a recurring cycle. The woocommerce_subscriptions_apportion_recurring_price filter now accepts two new values, physical-upgrade and physical, and woocommerce_subscriptions_apportion_length accepts physical. The -upgrade variant prorates only when the customer moves up a tier and leaves downgrades untouched; the plain physical value prorates in both directions.

The second change is quieter but arguably more important: link removal and resubscribe links now use individual nonces instead of a shared subscription-scoped nonce, and item removal is gated behind a new edit_shop_subscription_line_items capability. The helper wcs_can_items_be_removed( $subscription, $user_id = 0 ) in wcs-functions.php now validates ownership before returning true. If you have custom account-page templates that build removal links by hand, this is where you will find out.

The settings surface itself has been rewritten. A new Settings_Page class registers fields against /wc/v3/settings/subscriptions in the REST API and hooks into woocommerce_settings_subscriptions at priority 1, replacing the deprecated WC_REST_Subscriptions_Settings. The old select field woocommerce_subscriptions_max_customer_suspensions is now a number input, and the range filter woocommerce_subscriptions_max_customer_suspension_range is deprecated along with it. Gifting has moved from a global toggle to a per-product _subscription_gifting meta key, with a bulk-edit option and an automatic migration for stores that had it enabled storewide.

Two other quiet changes worth noting. WCS_Manual_Renewal_Manager::is_manual_renewal_required() now requires both “automatic payments off” and “accept manual renewals” to be enabled together, which stops the old contradictory state where one was on and the other off. And the plan-selector script wcsatt-frontend is no longer auto-enqueued on custom templates — you have to call WCS_ATT_Display::enqueue_frontend_script() yourself. There is a new filter, woocommerce_subscriptions_paypal_standard_expected_payment_amounts, for stores that need to override PayPal Standard renewal amount validation. The WooCommerce Developer Blog changelog catalogs all of it in one place.

Why it matters for WordPress and WooCommerce people

Subscriptions is not a passive dependency. If you run a Woo store with recurring billing, this plugin is inside your checkout, your emails, your account page, and your reporting pipeline. A version bump that changes nonce scoping, capability checks, filter values, and REST route ownership is not a background update — it is a small integration project.

The physical proration change is the shiny piece for merchants. Every store I have shipped that mixed physical goods with recurring plans — coffee subscriptions, print-and-mail boxes, hardware-plus-software bundles — has ended up with a custom filter somewhere doing exactly what physical and physical-upgrade now do natively. If that describes you, this is a chance to delete code, not add it.

The security tightening is the piece that will bite quietly. Removal and resubscribe links generated before 9.2.0 no longer verify. Customers who kept a “remove item” link open in a tab, or who follow a resubscribe link from an old email, will hit a fresh My Account page instead of a completed action. That is the correct behavior — shared subscription-scoped nonces were always a weak spot — but if your support tickets spike after the update, that is your explanation.

The settings refactor is where extension authors get to earn their invoice. Any settings page override, any admin JS that assumed the field was a select, any code that talked directly to the deprecated WC_REST_Subscriptions_Settings class will need a look. The advisory calls out that rolling back to 9.1.0 or earlier reverts proration defaults to “off” without data loss, and the settings dropdown will simply show no selection — useful to know when you are planning your rollback path, less useful when you discover it in production.

What I would do (or not do) about it

First, do not auto-update this on production. Subscriptions is exactly the class of plugin where the WordPress.org auto-update-off recommendation is not paranoia — it is standard practice. Roll it out on staging with a copy of production data, exercise a real renewal cycle, and click every link on My Account before you touch live.

Second, if you ship physical subscription goods, plan the proration switchover as a small project, not a checkbox flip. The behavior is off by default after the upgrade; you will need to decide whether physical or physical-upgrade matches your merchandising story, and communicate the change to customer service before a single upgrade or downgrade goes through the new path. If you had custom filter code on woocommerce_subscriptions_apportion_recurring_price, delete it — do not layer the native behavior on top of it.

Third, grep your codebase — theme, mu-plugins, custom extensions — for WC_REST_Subscriptions_Settings, woocommerce_subscriptions_max_customer_suspension_range, and any manual construction of removal or resubscribe URLs. Replace direct class references with the new Settings_Page hooks and let the plugin generate the nonced links.

Fourth, if you had storewide gifting enabled, watch the automatic migration on the first admin page load after the update. It writes _subscription_gifting per product; on stores with tens of thousands of subscription-eligible SKUs that is not free. Run it off-hours or take the site into maintenance mode for a few minutes.

What I would not do is jump on this the day it lands on a Black-Friday-critical store. This is a September release, and Woo stores this side of Q4 have a small window to update, test, and burn in. Take the window; do not spend it on a hotfix at 2 a.m. on Black Friday because a customer’s resubscribe link stopped working.

Physical proration was overdue and the security cleanup is welcome. But this is still an extension update on the most fragile surface a Woo store has. Test it like one.