What is Magento Marketplace EQP?
Short answer EQP, the Extension Quality Program, is the standard review every extension submitted to the Adobe Commerce Marketplace goes through. It has two parts. The technical review runs automated code checks (malware scan, package verification, coding sniffs, plagiarism check, install and Varnish tests, MFTF tests) and a manual QA pass by an Adobe tester. The marketing review checks the listing copy, images and docs. An extension is only listed once it passes both.
- Upload the package in the Developer Portal 01
- Automated code checks: sniffs and plagiarism 02
- Installation, Varnish and MFTF tests 03
- Manual QA by an Adobe tester 04
- Marketing review, then the listing goes live 05
Most common mistake Submitting before the code sniffs are clean
Five stages from upload to a live Marketplace listing
EQP is not an extra tier on top of a listing, it is how a listing gets approved. Here is the path every submission takes, based on Adobe’s Commerce Marketplace seller docs.
-
01
Upload the package in the Developer Portal
You upload a zip of your Composer package on the Adobe Commerce Marketplace Developer Portal. Two checks run straight away: a malware scan and package verification (it must be a zip with a valid
composer.json, no*version constraints on Magento packages, and no leftoverFIXMEorTODOcomments). Only a package that passes both gets a submission ID. -
02
Automated code checks: sniffs and plagiarism
Adobe runs its own set of coding sniffs based on the Adobe Commerce coding standards and returns a report with each issue and its file and line. A copy-paste detector compares your code and listing content against existing Marketplace extensions and the Commerce codebase. Code taken from Magento Open Source must keep the OSL 3.0 licence and credit Adobe.
-
03
Installation, Varnish and MFTF tests
The extension is installed on each PHP version you declare, with Varnish turned on, then switched to production mode. Cacheable pages must still come from Varnish. Adobe then runs its own MFTF (Magento Functional Testing Framework) tests, plus any MFTF tests you ship with the package, on each supported PHP version.
-
04
Manual QA by an Adobe tester
A tester installs the extension with Composer, compiles it in production mode, follows your user guide and checks that it does what the listing says. Missing or incomplete documentation is a common reason to fail. For a new version of an extension that is already listed, the Semantic Version Checker can let Adobe skip manual QA when only patch-level changes were made.
-
05
Marketing review, then the listing goes live
Separately, Adobe reviews your listing copy, images and documentation for quality and against its marketing guidelines. Adobe’s docs are clear that you must pass both the technical and the marketing review before the product is listed. If either review fails, you get the reasons, fix them and resubmit.
Four times you will run into EQP
Whether you build extensions or buy them, these are the moments when knowing the review process saves time.
-
Publishing your first extension
There is no way onto the Marketplace that skips EQP. If you plan to sell or give away an extension on
commercemarketplace.adobe.com, build for the review from day one: clean Composer package, code that passes the coding standard, a PDF user guide and a version that installs cleanly in production mode. -
Shipping a new version of a listed extension
Every new version you upload goes through the technical review again. Small patch releases can move faster when the Semantic Version Checker confirms only patch-level changes, but the malware scan, code checks and install tests still run.
-
Choosing an extension as a store owner
Because every Marketplace listing has passed EQP, buying from the Marketplace means the code was scanned for malware, checked against coding rules and installed by Adobe before you saw it. That is a baseline, not a full security audit of your store. Still test on staging before you install anything on a live store.
-
Adding support for a new Magento or PHP version
When you declare support for a new Magento release or PHP version, the install, Varnish and MFTF tests run against it. Run the same checks locally first so a new release does not hold up your update in the review queue.
Three mistakes that get a submission sent back
Most rejected submissions I have helped fix came down to one of these three. Check for them before you upload.
-
Submitting before the code sniffs are clean
Run
phpcs --standard=Magento2from the Magento Coding Standard package locally and get to zero errors before you upload. A failed sniff report sends the submission back and costs you another trip through the queue. -
A thin or missing user guide
The technical review needs a user guide (as a PDF, or a PDF that links to your docs) that covers every feature. Manual QA follows that guide step by step. If a setting or screen is not documented, the tester cannot check it, and the review fails.
-
Never testing with Varnish and production mode
Many extensions work in developer mode and break the full page cache in production. Adobe installs your extension with Varnish on, compiles it in production mode and checks that cacheable pages stay cacheable. Test the same way before you submit.
Magento Marketplace EQP: frequently asked questions
-
Is EQP mandatory for selling on Magento Marketplace?
Yes. EQP is not an extra tier you opt into, it is the review process itself. Every extension submitted to the Adobe Commerce Marketplace goes through the EQP technical review and the marketing review, and Adobe’s seller docs say you must pass both before the product is listed. -
What does the EQP technical review check?
A malware scan and package verification on upload, then Adobe’s coding sniffs, a copy-paste (plagiarism) check, installation and Varnish tests on each supported PHP version in production mode, Adobe’s own MFTF tests plus any MFTF tests you include, and a manual QA pass where a tester installs the extension and follows your user guide. -
What does the marketing review check?
Your listing content: the description, images and documentation. Adobe checks them for quality and against its Marketplace marketing guidelines. It runs as its own review, and the listing only goes live once both the marketing and the technical review have passed. -
Is there an “EQP Certified” badge?
No. Adobe’s Marketplace seller docs describe EQP as the review every listing passes; they do not describe a separate EQP badge or a paid EQP tier. Older articles that call EQP an optional certification describe something Adobe’s current docs do not. -
What happens if my extension fails EQP?
Adobe tells you why it failed and what to fix: a code sniff report with file and line, a failed install or Varnish test notice, or the manual QA findings. You fix the issues, upload again and the submission goes back through the review. -
Do new versions of my extension go through EQP again?
Yes. Each new version you upload is reviewed. When the Semantic Version Checker confirms a new version only has patch-level changes, Adobe can skip manual QA for it, but the automated checks still run.
Getting an extension ready for Marketplace review?
Send the extension repo. I will run the same kind of checks Adobe runs (coding standard scan, production-mode compile, Varnish and MFTF test gaps, user guide review) and reply with a written fix list, a fixed-price quote and the earliest start date. Reply within 24 business hours.