Who this is for
Owner of a WooCommerce store selling subscriptions whose renewals are created late, in bursts, or not at all.
Subscribers complain they were not charged or invoiced on the due date, or renewal orders only appear when someone opens the admin.
The result
On a copy of your store, a test subscription made due now has its renewal order created inside an agreed window and its next renewal scheduled, and the scheduler setting or server change that makes this reliable is written down.
What is included
- The scheduled tasks behind renewals: pending, past-due, failed and stuck entries
- How the scheduler is started on your host: page-load trigger or a server job, and whether the site can call itself
- Whether subscriptions are on automatic or manual renewal and why any fell back to manual
- A test renewal on the copy, and the exact setting or server change needed on live
You receive
- A note naming why renewals were late or missing, with redacted scheduler evidence
- The store-side corrections made on the copy and the server or host change needed
- A test table: test subscription, due time, when the order was created, next renewal date
- A list of overdue live subscriptions for you to review, produced from the evidence you send
- Steps to apply the changes to the live store and to undo them
What is not included
- Charging or renewing live subscribers, which you do under your own account
- Failed-payment retry rules, dunning emails and card decline causes
- Changing prices, plans or subscription terms
- Switching to a different subscription plugin
- Refunds and customer communication about missed renewals
What we need from you first
- How many renewals were late, by how long and since when
- Whether late renewals appear when someone opens the admin
- Whether any plugin, host or WordPress setting changed before it began
- Whether your host runs a server job for WordPress scheduled tasks
- WooCommerce, Subscriptions and gateway versions, if you know them
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- A test subscription made due now gets its renewal order created inside the agreed window on staging
- After the renewal, the next renewal date is scheduled and the test subscription is in the expected status
- No scheduled subscription payment task on staging is pending past its due time by more than the agreed margin
- The written scheduler setting matches what the host confirms is running
You review the test table and the evidence and sign off before payment. Changing the live scheduler and reviewing overdue subscribers are separate steps you take.
When we would stop or decline
- Renewal orders are created on time and the fault is a declined payment
- The host will not allow a server job or the site cannot reach itself over the network and the host cannot change that
- A different subscription plugin is installed
- There are signs of a compromise on the store
Questions
Will you renew my live subscribers?
No. We never charge or renew a live subscriber. You review the overdue list we give you and act on it under your own account.
Do I need a server job?
Not always. A low-traffic site often does, because the default trigger depends on visitors. The evidence decides.
What if the payment fails after the order is created?
Then this job does not apply. That is a payment problem for the gateway log and your failed-payment settings.
Price and terms
From £395 · untested offer price. After the agreed checks pass and you sign off; no payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.