Quick answer
Review both Accept Manual Renewals and Turn off automatic payments after updating WooCommerce Subscriptions. Version 9.2 resolves a contradictory combination by re-enabling manual renewals during migration where needed. Do not infer a customer's next payment method from one checkbox; inspect the subscription and gateway history.
Start with the subscription that raised the question
A customer asking why they received a payment request is a different investigation from an administrator noticing a changed setting. Capture the subscription ID, renewal order ID if one exists, next payment date, selected gateway, and the timestamp of the update. Redact personal details before sharing the record.
Establish whether a renewal actually occurred. A scheduled date in the interface does not prove that a charge was attempted, and a gateway failure does not prove the store intentionally switched to manual renewals. Those distinctions determine whether you should inspect configuration, scheduled work, or a payment-provider response.
Preserve both settings together
Before changing anything, record both payment options on the same screen. Look for the previous configuration in a backup or deployment record. Avoid restoring an entire production database merely to read an old setting; inspect the backup separately.
The updated manual-renewal check requires both relevant options to be enabled. The one-time migration preserves the previous behavior of stores with contradictory settings. That is a configuration reconciliation, not evidence that someone secretly changed payment policy. Explain the difference clearly in your internal change note.
Separate existing records from new purchases
Create two rows in your test plan: an existing manual subscription and a new test purchase. Add an automatically renewing subscription as a control when your staging setup can represent it safely. Do not assume that changing a checkout option rewrites the commercial history of every existing record.
For each row, document what you expect before pressing any action button. For example, a manual renewal may require a customer payment step, whereas an automatic renewal depends on the gateway and its saved payment relationship. Consult the installed gateway's current documentation rather than forcing one model onto every payment method.
- Check the subscription payment method and renewal notes.
- Match an existing renewal order to the gateway record by ID and timestamp.
- Check scheduled work without repeatedly triggering the same renewal.
- Read the actual email text the customer would receive.
Use staging without accidentally collecting money
Verify the payment provider's sandbox mode before creating a test renewal. Also contain webhooks, transactional mail, and third-party order automation. A copied store with a test-mode label is not sufficient if a custom integration still sends live requests.
If a provider cannot reproduce an existing subscription safely in a sandbox, use a new sandbox subscription for behavior testing and read-only evidence for the historical production record. Document that limitation. Do not replay a production billing request in order to make the test look complete.
Diagnose a mismatch at the right layer
If the options are correct but a renewal is delayed, inspect the scheduled action and its error. If the action completed but payment failed, inspect the gateway response. If payment succeeded but the subscription still looks unpaid, reconcile webhook processing and order linkage. These are different failures with different recovery paths.
When a customer has already paid an invoice manually, reconcile that payment before considering another automatic attempt. Support staff should have a single owner for the case and a record of which action has already been taken. Repeated attempts by different team members create a much larger problem than a confusing checkbox.
Close the change with customer-facing evidence
Record the final settings, the expected behavior for existing subscriptions, and the behavior of a new checkout. Include a sample customer message so billing staff know what to say. Do not promise automatic charging unless the gateway relationship and subscription record support it.
Monitor the next scheduled renewal through its normal path. A settings screenshot verifies configuration; an order, provider result, and reconciled subscription verify the outcome. Keep those evidence types separate in the handoff so the next person does not repeat a payment test unnecessarily.
Illustrative diagnostic worksheet. Use your own test results.When to bring in help
Use WooCommerce troubleshooting support when settings, order notes, and gateway records disagree. Share a redacted subscription ID and timeline. Never send full payment credentials or retry a charge simply to produce a clearer screenshot.
Related troubleshooting
Investigate failed renewals and stock restoration.
Helpful references
WooCommerce Subscriptions 9.2 advisory. Subscriptions settings guide.