A WordPress plugin for WooCommerce stores

It's just a WordPress update. What could go wrong?

ShouldCheck is a WordPress plugin that reads another plugin before you install, update or activate it. It tells you in plain words what needs a closer look.

Download plugin See a sample review

Install it like any plugin: Plugins › Add New › Upload.

Hello!

Sound familiar?

Two minutes of doubt. Four hours of oh no.

Good morning

You're having your coffee, looking over your online store on WordPress and WooCommerce. A notice shows up: an update is available for a plugin.

Two minutes

You haven't touched anything, but the notice makes you anxious. Those two minutes before you hit Update. You want someone to tell you whether you should press it.

Boom

"Ummm… let me do it and get back to work." Then your store is suddenly down.

What broke?

You didn't install anything new. You only upgraded a plugin that was working fine. Oh. The same thing happened last time you turned on auto-updates.

Four hours

You call the developer. It takes four hours of your prime business time. That's lost sales and lost customer trust.

If only

You wish something had told you what pressing that button would do. Or, when an auto-update runs, emailed you what changed and whether everything is alright.

There should be someone who checks before you do.

Store or blog, one site or thirty. The two minutes feel the same.

See a sample review

Sample review

A second opinion before you click.

Pick a situation to see what ShouldCheck tells you.

Not checked: how the plugin behaves while running, and how it works with your theme and other plugins.

Illustrative prototype with fictional plugins. Not connected to a real WordPress site.

How it works

Look. Understand. Decide.

Look

Start a review from Add New, an update, an inactive plugin or a ZIP upload up to 25 MB.

Understand

Findings come back ranked, in plain language, with what could not be checked.

Decide

Continue, investigate, or test on staging. Nothing changes until you press the button.

What it checks

Six things, read from the code.

Download plugin

1.Compatibility

Declared WordPress and PHP versions against your site, and when it was last tested.

2.Possible clashes

Function and class names that also appear in plugins already running.

3.Outside access

Which outside servers the plugin appears to contact.

4.WooCommerce checkout (if you run a store)

Checkout block support, order data access and payment callbacks.

5.What was not checked

Every review lists what it could not see, such as runtime behavior.

6.Reads, never runs

Code is read, not executed. Nothing is installed or activated until you say so.

ShouldCheck never says a plugin is safe. Reading code can't prove that.

Where it helps

For the moments you'd rather not guess.

Store owners

The week before
a big sale

Check payment plugins first, then run a test checkout on staging.

Any WordPress site

The plugin that
looks perfect

See what it contacts and what it may clash with, before it is on your site. No store needed.

Agencies and freelancers

Monday updates
across many sites

Review before you touch a client's site. Update the quiet ones now.

Looking ahead

Imagine waking up to all clear.

Automatic verification, remote alerts and AI-assisted investigation are planned.

These are plans, not features of the current plugin.

Questions

Good to know.

Is this a WordPress plugin?

Yes. You download it and install it from your dashboard under Plugins › Add New › Upload, like any other plugin.

Do I need WooCommerce?

No. Compatibility, clashes and outside access apply to any WordPress site. The checkout and payment checks apply to WooCommerce stores.

I'm not technical. Can I use this?

Yes. Reviews are in plain words, and every finding says what to do next. You don't need to read code.

Is ShouldCheck a security scanner?

No. It reads a plugin's files to point out things worth a look before you act: compatibility, name clashes, outside access and WooCommerce checkout code. It doesn't certify security.

Will it tell me a plugin is safe?

No, on purpose. Reading code can't prove that. The best result is "Nothing stood out", which means the checks found nothing to flag.

Does it install or update anything on its own?

No. A review only reads. Installing, updating or activating happens when you press the button.

What if it gets something wrong?

It can. It reads patterns and can't see how code behaves while running. Every review lists what was not checked, so you know where to test.

Still have a question? Email Satyen.

About the developer

Built after too many broken updates.

I'm Satyen Aghor. I help teams make better product and design decisions, mostly in payments, commerce and loyalty.

While building the Pepmo store on WooCommerce, plugin updates kept breaking things. Staging and trials ate months. The breakage hit the UI and payments while orders mattered most. I still like WooCommerce for its ease and extensibility. WordPress and Woo have had my heart for 15+ years. ShouldCheck is my attempt to help merchants who end up where I was.

Sky is my dog. Handsome, smart, a bit stubborn. The care between us is what this plugin stands for.

20+ years across product, UX, branding and business strategy. 4+ years inside a cross-border payments company, first as full-time Chief Design Officer, then nearly three years as Fractional CDO. I worked with engineers on payment flows and evaluated and integrated PayU, Juspay and Razorpay.

LinkedIn Email

Woof woof!