WordPress · WooCommerce
I fix the exact points they raised, check the guidelines they have not flagged yet, and write the reply you send. Fixed scope, fixed price, agreed before I start.
The review team writes in English whatever your language. Paste their message and this page tells you which of the seven reasons you are actually facing — and what each one wants from you.
Runs entirely in your browser. Nothing is sent anywhere, nothing is stored, there is no server behind this.
The reader above gives you the category. Forward me the actual email and I will tell you in writing what they are objecting to in your case — free, no strings, no call.
Your submission has been held and the email does not make it obvious what to change. I go through it clause by clause, fix the code, and prepare the resubmission.
You need one specific feature. Nothing on the market does exactly that, and the closest match brings forty options you did not ask for.
Cheaper than being held, and far less stressful. I run the checks the review team runs, before you upload, so the first answer you get is the one you want.
In writing. For a held plugin, forward the email you received — that is usually all I need to quote.
One page: what I deliver, what is explicitly not included, the price and the delay. Fixed before I start.
WordPress coding standards, translation ready, Plugin Check run clean. You get progress in writing, not meetings.
Full source, documentation, and the reply to send from your own account. 30 days of bug fixes included.
Because I have been through it, on my own plugin, and got it wrong twice before getting it right.
Guideline 5 trialware, a trademark collision, the Contributors line, a broken Plugin URI, undocumented external services — I have had all of them raised against my own submission, and a second refusal on the replacement name after that. Resolving it meant deleting a feature mode entirely, standing up a Cloudflare Worker, and wiring licence webhooks. Knowing the answer took an hour. Shipping it took nine days.
These are rules you only learn by being refused. Most WordPress developers have never read the guidelines closely, because they have never had to.
Eight e-commerce extensions across five platforms — WordPress, WooCommerce, Shopify, BigCommerce and Ecwid — handling the whole chain each time: development, billing integration, and marketplace submission.
I make no claims about install counts or revenue, because they would be meaningless here. What the work proves is the range: five ecosystems, real billing integrations, and one submission taken through the review process end to end.
My side: a few days for documentation, headers, contributors and URLs. A Guideline 5 rewrite is longer, because it changes your product, not just your code. Their side is one to six weeks and nobody can shorten it.
No, and be wary of anyone who does. The review team decides. What I can do is make sure every point they raised is answered and that the guidelines they have not raised yet will not catch you on the next pass.
For the code, no — the ZIP or the repository is enough. The submission itself stays in your hands: I write the reply, you send it from your own wordpress.org account.
By preference, no. Everything runs in writing, which also means you have a record of what was agreed. If a call is genuinely needed, it is a short one.
You do, completely. No obfuscation, no licence server, nothing calling back to me.
Describe the problem in plain words — for a held plugin, forward the email you received. I will come back with a written scope and a fixed price. If it turns out an existing plugin already solves your problem, I will tell you that instead.
Email me directly Or order on Fiverr
projectafievez500@gmail.com — I reply in writing, usually within a day. Fiverr works too if you prefer its buyer protection; it costs you the same.