tadrikTadrik Care / Case study
More than 20 live stores, updated every week. The numbers we can prove.
No store names and no client quotes. This is what we look after, what our checks caught when we tried to break them, and what they can't do yet.
01 / The stores we look after
Production stores, with one engineer on call.
- Live stores
- More than 20, all on WooCommerce.
- Updates
- Every week.
- Hosting
- Moved in 2026 from managed hosting to a self-managed server, including DNS and TLS cutover, an SMTP relay and uptime monitoring.
- On call
- 1 engineer, our founder: patching, backups and incident response.
- Names published
- 0. Those stores stay private, and yours would too. NDA on request, signed before you send a store.
Two things to be clear about. These stores aren't Tadrik Care customers, and the automated checks below haven't been run on them. And we don't publish counts of updates or breakages from them yet, because we'd only publish a number we can back with a record.
02 / The checks, tested
We tried to break checkout 3 ways. None reached the live store.
A store in Docker on real WordPress and WooCommerce, with a test plugin we wrote so each version misbehaves in its own way. Run on 29 October 2026: 26 checks passed, 0 failed.
| Test update | What it does | What the check saw | Result |
|---|---|---|---|
| Version 2.0 | Nothing wrong | Clean | Reached the live store |
| Version 5.0 | Crashes the checkout page | 24.3% of the page changed, HTTP 500 | Held. Live store unchanged |
| Version 4.0 | Removes a payment method | 11.9% of the page changed | Held. Live store unchanged |
| Version 3.0 | Clean on the copy; we forced the live check to fail after it went live | Live check failed | Rolled back. Plugin folder checksum identical to before |
Version 5.0, page by page
| Page | Pixels changed |
|---|---|
| Home | 0.0% |
| Product | 0.0% |
| Cart | 0.0% |
| Checkout | 24.271% |
The limit is 1.0%. Three of the four pages didn't change by a single pixel, so a check of the home page alone would have passed this update.
Version 5.0, checkout
| Check | Live | Copy |
|---|---|---|
| HTTP status | 200 | 500 |
| Critical error text | None | Shown |
| Form fields | Present | Gone |
| Place order button | Present | Gone |
| Payment methods | 2 | 0 |
03 / A real update
Real plugins through the same steps, in 5 minutes 11 seconds.
The first real run, 29 October 2026, on the test store on our own server. These are the published plugin updates, not test versions.
| Plugin | From | To | Change on 4 pages | Result |
|---|---|---|---|---|
| WooCommerce | 11.1.2 | 11.2.1 | 0.0% | Installed |
| B2BKing | 5.2.60 | 5.2.61 | 0.0% | Installed |
| Wholesale Prices | 2.3.0 | 2.3.1 | 0.0% | Installed |
04 / Why updates matter
1 store in 4 is waiting on an update it needs.
We checked 3,600 live UK and US WooCommerce stores. 858 of them (24%) run a plugin or WooCommerce version with a published vulnerability rated 7 or higher out of 10, and a fixed version is already out. The research and its method.
05 / What this doesn't show
The limits, up front.
- No agency has finished a month with us yet. Tadrik Care opened in late October 2026, so there are no customer results here.
- The check doesn't place an order. It puts an item in the cart, loads checkout and looks for errors, missing fields, the Place order button and payment methods.
- Not tested yet: rolling back a theme or WordPress itself, and copies of stores with live payment gateways or webhooks.
- Testing on a copy catches most breakage, not all of it. A backup is taken before every update goes live, so we can restore it if something gets through.
Send us a store. The first report is free.
Add up to three stores on one short form and we'll tell you what we'd update first. No calls. NDA on request, signed before you send a store. Who you'd be working with.