Home > > > From Code to Commerce: The Developer's Complete Guide to Getting Your Magento 2 Extension Approved o

From Code to Commerce: The Developer's Complete Guide to Getting Your Magento 2 Extension Approved o

Author : VDC Store | Published On : 08 Apr 2026

Building a Magento 2 extension is only half the job. Getting it approved and listed on the Adobe Commerce Marketplace one of the most trusted destinations for best Magento 2 extensions, best Magento plugins, and Magento 2 B2B extensions is where most developers struggle. The Marketplace is not a free-for-all directory. It enforces a rigorous, multi-stage review process, and first-time submissions fail more often than they succeed.

At VDCstore, we have been through this process multiple times. This guide distills everything you need to know the prerequisites, the review stages, the technical requirements, and the decisions that separate a first-pass approval from weeks of back-and-forth rejection emails.

Why the Magento Marketplace Matters

Before diving into the how, let us be clear about the why. The Adobe Commerce Marketplace (formerly Magento Marketplace) is the official, curated ecosystem of extensions for Magento Open Source and Adobe Commerce stores worldwide. It is the first place merchants look when they need a Best Magento 2 Extension whether it is a Magento 2 marketplace extension for multi-vendor selling, a Magento 2 B2B extension for wholesale pricing and company accounts, or a performance tool for their storefront.

Getting listed here means instant credibility, organic discovery, and access to thousands of active Magento merchants. Adobe shares 85% of the total revenue generated from products sold on the Magento Marketplace with sellers, making it a commercially meaningful channel for independent developers and agencies alike.

But that credibility comes at a price a thorough quality gatekeeping process called the Extension Quality Program (EQP).

Understanding the EQP - The Gatekeeper You Must Impress

The Extension Quality Program (EQP) combines Adobe Commerce expertise, development guidelines, and verification tools to ensure that all extensions and other listings on Commerce Marketplace meet coding standards and best practices. The review process includes both an automated check and manual QA review. During the process, the structure and code of each listing is examined and tested for evidence of virus/malware infection, and any indication of plagiarism. The review includes a deep technical examination and sanity check conducted by the Marketplace team, with a focus on documentation, coding structure, performance, scalability, security, and compatibility with the Adobe Commerce core.

The EQP runs across two parallel tracks - a Technical Review and a Marketing Review - both of which must be passed before your extension goes live.

  • Technical Review – Level 1
    Focuses on code standards, malware scanning, plagiarism checks, and package structure.
    Conducted using automated tools

  • Technical Review – Level 2
    Covers deep code quality, performance, scalability, and security.
    Reviewed manually by the Magento EQP team

  • Marketing Review
    Checks listing content, documentation, screenshots, and pricing consistency.
    Handled by the Marketplace team

  • QA Review
    Tests installation, configuration, and core functionality.
    Performed by Magento QA engineers 

Level 1 is a mandatory check for all extensions on Marketplace. The purpose of the Level 1 automated technical review is to examine the extension package structure for basic coding standards, to detect the presence of viruses or malware, and to identify indications of plagiarism. Extensions that pass Level 2 technical review receive a Top Quality Badge, which is the seal of approval that Magento merchants can trust.

Now let us walk through the entire process from the beginning.

Step 1 - Set Up Your Seller Profile on the Marketplace Developer Portal

Before you can submit anything, you need a valid seller account on the Adobe Commerce Marketplace.

Go to marketplace.magento.com and either log in with an existing Adobe ID or register a new account. Once logged in, navigate to the Developer Portal and complete your seller profile. This includes your company or individual name, contact information, payment details, and tax information. Your profile must be complete before any submission will be accepted.

This is also where you will manage all future product submissions, view review statuses, and receive payment reports from sales.

Step 2 - Build Your Extension to the Correct Standards First

This is where most developers make their costliest mistake they build first and check compliance second. At VDCstore, we always build to the standard from day one.

Before you can submit your Magento 2 Extension to Commerce Marketplace, the code must be complete, tested, and packaged. Before submitting your extension for Marketplace review, see the Technical Review Guidelines and the Marketing Review Guidelines. Use the CodeSniffer tool to verify that your code meets Marketplace guidelines. Testing your extension in advance reduces the time it takes to pass Technical Review.

Magento Coding Standards You Must Follow

Class names must be declared in StudlyCaps. Class constants must be declared in all upper case with underscore separators. Method names must be declared in camelCase. Code must use an indent of 4 spaces, and must not use tabs for indenting.

Beyond naming conventions, the EQP CodeSniffer checks for deeper structural issues. The Magento EQP Coding Standard allows you to automatically check your code against common Magento and PHP coding issues, including raw SQL queries, SQL queries inside a loop, direct class instantiation, unnecessary collection loading, excessive code complexity, use of dangerous functions, and use of PHP superglobals.

Running the EQP CodeSniffer Locally

Before you even think about uploading your package, run the EQP tool against your codebase locally. This will surface all the issues you would otherwise discover during the automated Level 1 review which wastes days.

# Install the Magento EQP coding standard

git clone https://github.com/magento/magento-coding-standard.git

cd magento-coding-standard

composer install

 

# Run the check against your extension

vendor/bin/phpcs /path/to/your/extension --standard=MEQP2 --severity=10 --extensions=php,phtml

 

To make sure your extension will pass CodeSniffer checks of Magento Marketplace Technical Review, run the phpcs command with the --severity=10 option. All severity 10 errors must be fixed in order to successfully pass Level 1 CodeSniffer checks.

If you receive fixable warnings in bulk, use the auto-fixer:

vendor/bin/phpcbf /path/to/your/extension --standard=MEQP2

 

Fix every ERROR before submission. Address WARNINGs where possible a high warning count signals code quality issues that manual reviewers will notice.

  • Raw SQL Queries

    • Issue: Direct database queries

    • Why it fails: Security risk - use resource models instead

  • SQL Inside Loops

    • Issue: Queries inside loops

    • Why it fails: Causes severe performance issues

  • Direct Class Instantiation (new ClassName())

    • Issue: Creating objects directly

    • Why it fails: Breaks dependency injection principles

  • Superglobal Usage ($_POST, $_GET, etc.)

    • Issue: Using global variables

    • Why it fails: Leads to security vulnerabilities

  • Hardcoded Credentials / API Keys

    • Issue: Sensitive data in code

    • Why it fails: Results in instant rejection

  • Missing registration.php

    • Issue: Required file not included

    • Why it fails: Violates package structure

  • Missing or Invalid composer.json

    • Issue: Improper package configuration

    • Why it fails: Cannot install via Composer

  • Plagiarised Code

    • Issue: Copied from other extensions

    • Why it fails: Risk of permanent ban 

 

Step 3 - Package Your Extension Correctly

Package submissions must contain a Magento module, theme, language pack, or metapackage that meets Composer packaging and format requirements. Code must be submitted as a zip archive.

Your zip file naming convention matters. If your extension is VDC/PaymentGateway at version 1.0.0, your archive should be named:

vdc_paymentgateway-1.0.0.zip

 

Important for macOS developers: While zipping, a Mac creates MACOSX hidden folders. To avoid this, you must do the zipping via a console. Hidden macOS metadata files inside a zip archive will cause package verification to fail.

Your package must include the following at a minimum:

  1. registration.php
    This file registers your module with Magento and is mandatory.

  2. composer.json
    Defines your package details, version, and dependencies required for installation.

  3. etc/module.xml
    Declares the module name and version, helping Magento recognize it properly.

  4. README.md / User Guide
    Includes documentation to guide users on installation and usage.

  5. Core Module Files (Block, Model, Controller, etc.)
    These files handle the main logic and functionality of your module.

Step 4 - Create the Listing and Submit for Technical Review

Log in to the Marketplace Developer Portal. Navigate to  Extensions and click Create New Listing. Fill in the initial listing details:

  • Extension Name - Clear, descriptive, free of competitor brand names

  • Short Description - Under 170 characters summarising core functionality

  • Magento Platform Version - Magento 2.x (specify compatibility carefully)

  • Third-Party Integrations - Declare all external services used

  • Marketplace Version Number - Start at 1.0.0

Click Attach Package to upload the listing code package. For Magento Version Compatibility, select the supported version number and compatibility for the extension. The listed options include all minor versions Adobe Commerce supports at time of submission. Select the Licensing options this option requires the user to agree to a license in addition to the terms and conditions.

Once uploaded, the automated Technical Review begins immediately. When the Magento 2 module development is finished and you upload your code, it will go through automated install tests. Once those are passed, it will move to manual QA. This is where your developer will likely be involved, assisting with any errors the Magento QA team may find.

What Manual QA Tests

To pass Manual QA, the extension must meet the following requirements: it installs with Composer, compiles without errors using deploy:mode:set production, has all supporting documentation that complies with documentation requirements, and works with each version of Magento that the extension claims to support. Basic Commerce functionality must work as expected with the installed extension.

Basic QA test scenarios include creating orders as guest and logged-in users, testing product types (Simple, Configurable), and verifying the extension does not break core Magento workflows. If your extension touches checkout, payment, or shipping, expect thorough functional testing in those areas.

Step 5 - Complete the Marketing Review

In the Marketing Review stage, the content, user guides, screenshots, pricing, and installation manuals are examined. It is recommended to keep the prices and features consistent in the content across the submission and your website.

This is where many technically solid extensions fall short. The Marketplace team reviews everything a merchant would see your listing page, your documentation, your screenshots, your pricing, and your release notes.

  1. Short Description
    Keep it under 500 characters - clear, concise, and factual.

  2. Full Description
    Ensure it is professionally written and accurately reflects features.

  3. Category Selection
    Choose the most relevant category to improve discoverability.

  4. Screenshots
    Use high-quality images that represent real functionality.

  5. User / Installation Guide
    Provide complete documentation covering all features (PDF or URL).

  6. Release Notes
    Include version history for transparency and updates.

  7. Pricing Consistency
    Match pricing with your official website to avoid rejection.

  8. Launch Date
    Select “On Approval” or define a future launch date.

Extension documentation must cover all features of the extension. Extension documentation must not direct users to make purchases on sites other than Marketplace.

One commonly overlooked requirement: your documentation must be self-contained enough for the QA team to install and test your extension without needing to contact you. If the manual is vague, reviewers cannot complete QA, and your submission stalls.

Step 6 - Monitor, Respond, and Resubmit if Needed

The approval process can take from 24 hours up to seven days. If your extension is approved, you get a success email. If Magento does not approve your extension, they will send you an email with a list of improvements you must make. Do not delete it.

If your submission fails either review, treat the feedback email as a roadmap, not a rejection. Every item in that list is actionable. Address all flagged issues, re-run your CodeSniffer validation locally, verify the fix in a clean Magento environment, and resubmit. There is no limit on resubmissions, but each one restarts the review queue.

The Full Submission Process - End to End

  1. Create Your Seller Profile
    Set up your Marketplace account - takes about 1 day.

  2. Develop the Extension
    Build your module following EQP coding standards (timeline varies).

  3. Run CodeSniffer & Fix Errors
    Ensure your code is compliant - usually 1–3 days.

  4. Package the Extension
    Prepare a Composer-compliant ZIP file - takes a few hours.

  5. Submit for Technical Review
    Automated checks begin - 1–2 days.

  6. Manual QA Review
    Magento team tests functionality - 2–5 days.

  7. Marketing Review
    Content and listing are evaluated - 1–2 days.

  8. Approval & Launch
    Once approved, your extension goes live immediately.

 

  • Total Ideal Timeline: ~7–14 days

 

Note: Failed submissions reset the clock. Extensions with multiple issues can take 4–6 weeks to reach approval if not prepared correctly the first time.

Common Reasons Extensions Get Rejected and How to Avoid Them

 

  1. CodeSniffer Failure (Severity 10)
    Always run MEQP2 locally to catch critical issues before submission.

  2. Malware or Suspicious Code
    Ensure your codebase is clean, secure, and original.

  3. Plagiarism Issues
    Never reuse or copy logic from other Marketplace extensions.

  4. Composer Installation Failure
    Double-check your composer.json for correct structure and dependencies.

  5. Production Compile Failure
    Test your extension in production mode before packaging.

  6. Incomplete Documentation
    Provide a detailed user guide covering all features and setup steps.

  7. Broken Core Functionality
    Perform full QA testing on a clean Magento setup.

  8. Content Mismatch
    Ensure consistency between your Marketplace listing and website.

  9. Encrypted Code
    Avoid encryption - it’s not supported by the Marketplace. 

How VDC store Can Help

Whether you are building your first Magento 2 extension, developing a Magento 2 B2B extension for enterprise clients, or scaling a portfolio of best Magento 2 extensions across the Marketplace, the submission process demands technical precision at every stage.

At VDCstore, we offer:

  • Magento 2 Extension Development built to EQP standards from day one

  • Pre-submission Code Audits CodeSniffer checks, dependency injection review, security scanning

  • Marketplace Listing Optimisation SEO-friendly descriptions, professional documentation, high-quality screenshots

  • Resubmission Support Analysis and fixing of rejected submissions

  • Custom Magento 2 Plugins built for specific business workflows and third-party integrations

We know what the EQP team looks for, and we build accordingly.

Read More : VDCstore’s SEO Growth Suite for Magento 2: Extensions That Drive Rankings, Traffic, and Revenue  

Final Thoughts

The Magento Marketplace is not designed to be easy to enter and that is precisely what makes a listing on it valuable. Every Magento extension that clears the EQP review process has been held to a standard that protects merchants from poorly written, insecure, or unstable code.

If you are serious about publishing your Magento 2 extensions or best Magento plugins to the Marketplace, treat the EQP as a quality partner, not an obstacle. Run your CodeSniffer before you submit. Write documentation your grandmother could follow. Test on a clean Magento install before you package. Keep your listing content consistent and honest.

Do those things, and your first-pass approval rate improves dramatically.

Read More : Best AI Magento 2 Extensions to Power Your Store in 202