How Ops Fixes works

Last updated 30 October 2026

Ops Fixes is one person: me, Tran Quang Hieu, a developer in Vietnam. I build small tools that each do one job for people running stores, websites and IT systems: a WooCommerce feed check, an accessibility check for WordPress, monitoring for browser extension changes, and similar.

I build with AI, and I check the work

AI agents write most of the first drafts here: code, tests, research notes and page copy. I decide what gets built, review what they produce, and I'm responsible for everything that ships. Nothing on this site is a reason to trust AI blindly, including this page. It's the testing below that should earn your trust.

How things are tested

How facts are checked

Guides are dated and link their sources: vendor documentation, laws and official pages. Rules and prices change, so the date shows when each fact was last checked. If you find something out of date, email me and I'll fix it.

What I don't do

Support, and when a product ends

Why small tools

Big platforms leave gaps: a check they don't run, an export they don't offer, a rule change nobody explains. A small tool that does one of those jobs well is often more useful than another feature in a large product. When the platform finally covers the gap itself, I'll say so on the tool's page and point you to it.

Questions: support@opsfixes.com