Send a brief
Menu

What is the Magento Marketplace?

The Adobe Commerce Marketplace (formerly “Magento Marketplace”, now at commercemarketplace.adobe.com) is Adobe’s official extension, theme, and service store for Magento 2 and Adobe Commerce. Third-party vendors submit extensions; Adobe runs a two-stage review, Tech Review (Magento Coding Standard, PSR-12, MFTF tests) and Marketing Review (listing copy, screenshots, demo). Approved extensions go live for purchase; Adobe takes a 30% commission. As of 2026: ~3,500 extensions, ~1,200 themes, ~800 services live.

Send a brief WhatsApp first
  • Official URL commercemarketplace.adobe.com
  • Review stages Tech Review + Marketing Review
  • Adobe cut 30% commission, vendor keeps 70%

Five steps from vendor signup to live listing

The Marketplace submission flow is documented but slow on first contact. Here is the end-to-end path from a vendor's point of view.

  1. 01Sign up at commercemarketplace.adobe.com as a Developer

    Create an Adobe ID and register the developer / company profile at commercemarketplace.adobe.com. Adobe asks for company legal name, tax / VAT identity, payout banking details, and a support contact email that will be exposed publicly on every listing. Solo developers can register as an individual but most agencies register as a company so payouts route through the business bank account.

  2. 02Submit composer.json + zipfile + version manifest via the developer portal

    In the developer portal click Add Extension, then upload three artefacts: a valid composer.json with module name, version, Magento compatibility ranges, and licence; a zipfile of the extension source (no vendor/, no node_modules/); and a version manifest declaring what changed since the previous release. Pricing, support contract terms, and demo URL are entered in the same form.

  3. 03Tech Review (~7 business days), automated + manual

    Adobe’s Tech Review runs the Magento Extension Quality Program (MEQP) suite automatically: phpcs --standard=Magento2 against the Magento Coding Standard, phpstan, PSR-12 formatting, the MFTF acceptance tests you shipped, plus a malware / obfuscation scan. A human reviewer then checks for breaking-change risk, security issues (CSRF, SQLi, XSS), and ACL coverage on admin controllers. Any failure bounces the submission back with a report.

  4. 04Marketing Review (~3 business days), listing copy + screenshots

    Once Tech passes, Marketing Review checks the public-facing listing: title length, description grammar, feature bullet quality, at least three screenshots at 1280×800 or larger, a working demo URL, pricing that matches the support contract, and the user-guide PDF link. Trademark misuse (calling something “Adobe Official” when it’s not) is the most common Marketing rejection.

  5. 05Live on Marketplace; Adobe pays out monthly (70% to vendor)

    After both reviews pass the listing goes live and customers can buy with a credit card via Adobe’s checkout. Adobe handles billing, refunds, VAT collection, and 1099 / W-8BEN tax paperwork. Payouts run monthly on net-30 terms: a sale on June 5 pays out around August 5. Vendor receives 70% of the list price; Adobe keeps 30%. EQP-certified extensions get a featured badge and higher search ranking.

Four situations where the Marketplace is the obvious answer

Marketplace isn't the only way to get a Magento extension, but in 2026 these four scenarios are unambiguous wins for buyers and vendors alike.

  • Buy instead of build when the feature is < 2 weeks dev

    Marketplace extensions are operating expense, not capital expense. If a feature would take a dev team less than ~2 weeks to build from scratch, buying a Marketplace extension for $200, $800 is almost always cheaper than the engineering hours. Always check the licence (single store vs unlimited domains) and the support contract length (12 vs 24 months) before committing, but for “solved-problem” features like blog modules, reward points, or one-step checkout the buy decision is obvious.

  • Verify a vendor before purchasing

    A Marketplace listing equals an Adobe-verified vendor identity. Adobe has confirmed the legal entity, the tax ID, and the support contact email; the extension has cleared Tech Review (no known malware, no obvious SQLi); and the vendor has agreed to Adobe’s refund policy. A random GitHub repo offers none of that. If you’re evaluating two equivalent extensions and one is on Marketplace, default to the Marketplace one unless the GitHub option has overwhelmingly better reviews.

  • Sell your own extension, visibility + billing handled

    Listing on Marketplace solves three hard problems for an extension vendor: discovery (Marketplace search and category browse drive ~60% of extension sales for most vendors), billing (Adobe handles credit cards, VAT, refunds, and chargebacks), and trust (the Adobe logo on a listing converts better than a random vendor website). The 30% Adobe commission is real money, but for a new extension brand it pays for itself in the first 6 months via Marketplace traffic alone.

  • Earn EQP certification (Extension Quality Program)

    Only extensions listed on the Marketplace are eligible for the Extension Quality Program (EQP) certification. EQP-certified extensions get a green badge on the listing, higher placement in search results, and explicit endorsement from Adobe for enterprise / Adobe Commerce buyers. EQP requires the extension to pass MFTF acceptance tests Adobe runs against the Magento Coding Standard, ship with a documented support contract, and maintain a security-patch cadence under 30 days.

Three Marketplace mistakes that waste time and money

Every Marketplace-related issue I've been asked to debug came from one of these three mistakes. Check them before purchase or submission.

  • Buying without checking the last-update date

    Many Marketplace listings are technically still “available” but functionally abandoned. The vendor hasn’t shipped a release in 18+ months, the support email auto-replies with a holding message, and the extension hasn’t been re-tested against Magento 2.4.7 or 2.4.8. Before purchase, check three things on the listing: Last update date (should be under 12 months old), the Compatible Magento versions list (must include your version), and the most-recent customer reviews. If any of the three look stale, treat the extension as abandoned.

  • Ignoring composer dependency conflicts

    Marketplace listings advertise a Magento compatibility range (e.g. magento/product-community-edition: 2.4.5 - 2.4.8) but transitive composer dependencies often break it. A Marketplace extension that requires laminas/laminas-mail: ^2.20 can collide with another module pinned to ^2.18, and composer require blows up. Always run composer require --dry-run on a dev environment first; never install a Marketplace extension straight onto a live store.

  • Submitting an extension without running MEQP locally first

    A surprising number of vendors submit extensions to Tech Review without running the Magento Coding Standard or MEQP suite on their own laptop. The Tech Review then fails on day-one with hundreds of phpcs violations, the vendor wastes ~7 business days waiting for the rejection report, and the submission cycle restarts. Always run phpcs --standard=Magento2 app/code/Vendor/Module and vendor/bin/phpstan analyse locally and clean every violation before submitting.

Where the Marketplace sits in the wider Magento ecosystem

Five neighbour concepts most readers want to look at next. Click through for the full deep-dive.

Read the entryRead the entry

Magento Marketplace: frequently asked questions

Is the Magento Marketplace still active under Adobe?
Yes, very much so. Adobe rebranded the old magentomarketplace.com domain to commercemarketplace.adobe.com after the Adobe acquisition closed and migrated every existing listing, vendor account, and customer purchase record to the new domain. The submission workflow, the 30% commission, and the Tech + Marketing review pipeline are unchanged from the pre-Adobe era. As of 2026 the Marketplace lists roughly 3,500 extensions, 1,200 themes, and 800 services across both Magento Open Source and Adobe Commerce. The only meaningful change since the Adobe takeover is the addition of Adobe Commerce-specific listings (B2B modules, Adobe Sensei AI, Adobe Stock integrations) that don't apply to Open Source.
What is the 30% Adobe Marketplace commission really for?
Four things, bundled. (1) Credit-card processing, Adobe runs the checkout, eats the chargeback risk, handles refunds, and absorbs the ~3% Stripe / Braintree merchant fee that would otherwise come out of your margin. (2) VAT / sales-tax collection, Adobe collects EU VAT, UK VAT, US sales tax, Australian GST, and remits it to the appropriate tax authority; vendors don't need to register in every jurisdiction. (3) Vendor verification, Adobe confirms the legal entity, tax ID, and bank details before any vendor can sell, which is what makes the Marketplace badge meaningful. (4) Marketing, Marketplace search, category pages, and the “Featured” rotation drive organic discovery the average extension vendor cannot replicate on their own site.
How long does Marketplace submission take end-to-end?
For a clean submission with no rejections: about 10 business days, ~7 days in Tech Review plus ~3 days in Marketing Review. In practice first-time vendors usually iterate twice. The first submission almost always fails Tech Review on Magento Coding Standard violations the vendor didn't catch locally, which costs another 7 business days. The second submission often fails Marketing on screenshot sizing, demo-URL availability, or trademark misuse, which costs another 3 days. Budget 4-6 weeks for the first extension you list; subsequent extensions from the same vendor account typically clear in the advertised 10 business days because the vendor has internalised the standard.
Are Marketplace extensions safe to install on production?
Mostly, with caveats. Adobe’s Tech Review catches obvious security issues (SQL injection, unsanitised input, missing ACL on admin controllers, hard-coded credentials, eval / base64 obfuscation) before an extension is approved. That eliminates the worst class of malicious extensions you'd find on a random forum. But Tech Review is not a full security audit, it doesn't catch subtle logic bugs, side-channel data leaks, or insecure dependency versions in vendor libraries. For a public-facing production Magento store, the right workflow is: install on dev first, run bin/magento dev:di:info and bin/magento module:status to see what the extension touches, review the controllers and observers manually, and only then promote to staging and production.
Marketplace vs Hyvä Themes marketplace, do I need both?
They solve different problems. The Adobe Commerce Marketplace at commercemarketplace.adobe.com is Luma-first; every extension is expected to work with the default Magento Luma frontend, and Hyvä compatibility is a vendor-by-vendor add-on (often via a separate “Hyvä compatibility module” sold separately). The Hyvä Themes marketplace at hyva-themes.com/marketplace is Hyvä-specific; every extension there is built Hyvä-first using Alpine.js and TailwindCSS, with no Luma compatibility layer. If you run Luma, only the Adobe Marketplace is relevant. If you run Hyvä, you typically shop both: the Hyvä Marketplace for Hyvä-native modules, and the Adobe Marketplace for modules where a Hyvä compatibility shim exists.
Can I sell themes and services on the Marketplace, not just extensions?
Yes, the Marketplace has three top-level categories, Extensions, Themes, and Services, each with its own submission workflow. Themes (~1,200 listed in 2026) go through a similar Tech + Marketing review but the Tech portion checks template syntax, LESS / Tailwind hygiene, and accessibility rather than PHP code quality. Services listings (~800 in 2026, things like “Magento Performance Audit” or “Hyvä Migration Sprint”) are reviewed on capability claims, case-study links, and Adobe Solution Partner status; pricing is shown as a starting point rather than a fixed product price. All three categories share the same 30% Adobe commission and monthly payout terms.

Want a Marketplace-ready extension built?

Send your extension spec: I will scope a Marketplace-ready build with Magento Coding Standard, MFTF tests, EQP submission, and reply with a fixed-price quote plus earliest start date. 24-business-hour turnaround.

Send a briefWhatsApp