Submit for Technical Review
After passing Business Review, the next step is to complete the code and submit it for Technical Review. The extension is placed in a queue as soon as it is submitted. You will receive confirmation by email, and can track the status of your submission from your Marketplace account.
As part of the Extension Quality Program, we have added an automated production installation test and manual QA. These new checks require additional time for us to properly evaluate all existing extensions. As a result, there might be some delays in the process.
If your extension makes use of Shared Packages — or components — they must first pass Technical Review before they can be referenced by your extension. You will not be able to submit your extension to Technical Review until the shared packages that are used by the extension are available in your account.
The following instructions show how to submit an extension for Technical Review. The process is essentially the same for themes and shared packages.
|1.||Now is the time to complete the extension code. For technical information, see the PHP Developer Guide.|
|2.||Before submitting your extension for Technical Review, see the Technical Review Guidelines. Then, use the CodeSniffer tool to verify that your code meets Marketplace guidelines. For a list of code sniffer rules, see: Magento Extension Quality Program Coding Standard.|
Testing your extension in advance reduces the time it takes to pass Technical Review.
|3.||Prepare, validate, and zip your extension as described in Package a component.|
|4.||Prepare the following preliminary documentation:|
- Release Notes in text format. (You can use simple HTML, but not CSS.)
- User Guide in PDF format
|1.||Log in to your account, and navigate to the Products page of the Developer Portal.|
|2.||On the Extensions tab, the extension that passed Business Review appears in your account. Click the extension title or tile to open the Extension Details.|
|3.||The Extension Title that you entered during the initial interview appears in the form. You can change the title at this time according to the naming guidelines.|
|4.||Enter the Public Version Number as you want it to appear in the Marketplace listing. For example: 1.0.0|
|5.||In the Upload File box, do one of the following:|
- Drag the zip file that you prepared to the box.
- Browse to the zip file.
The zip file icon and extension name appears in the Upload File box.
|6.||Under Compatible Magento Version, click Choose. Then, mark the checkbox of each version of Magento that is supported by your extension.|
The available versions that appear are determined by the information you provided during the initial interview.
|8.||Your extension must include at least one user guide in PDF format. Optionally, you can also upload one reference manual and one installation guide.|
Under Documentation, click Upload. Then, do the following:
|a.||To upload your User Guide, either drag the PDF to the box, or click the box and browse for the file.|
|b.||(Optional) If you have prepared a Reference Manual, scroll down and either drag the PDF to the box, or click the box and browse for the file.|
|c.||(Optional) If you have prepared an Installation Guide, scroll down and either drag the PDF to the box, or click the box and browse for the file.|
|d.||When complete, tap Save.|
If you want to link to additional documentation that is hosted on your site, you can include a link in Long Description field of the Extension profile.
|9.||In the Release Notes box, paste the preliminary draft of your release notes that you prepared. The release notes can be formatted with simple HTML, and can include up to 10,000 characters, including spaces.|
|10.||If other components are used by this extension, click Choose existing shared packages…. Mark the checkbox of each shared package that is used by the extension. Then, tap Continue.|
|1.||When the required fields are complete, tap Submit.|
It might take a few minutes for your package to upload. You will receive email confirmation when the extension is submitted for Technical Review, and will be notified when the review is complete.
|2.||Do one of the following:|
- Tap Continue to display the profile.
- Tap Go to My Products to return to the Products tab of the Developer Portal.
The title of the extension as it is to appear in Magento Marketplace.
- The title should be written in descriptive and concise English.
- Do not include the version number, developer name, or any reference to Magento.
- Do not include the words “Extension” or “Module.” However, the word “Integration” can be used if applicable.
Maximum characters: 50
Maximum words: 5
After an extension has been submitted, the title can be changed only by resubmitting the package. See Complete the Extension Profile.
Public Version Number
The version number of the extension that appears in the Marketplace profile. For example: 1.0.0
The upload file must be a valid zipped composer package with .json file. You can drag the zip file to the box, or browse to select the file. Maximum file size: 30 MB
Compatible Magento Version
Specifies each version of Magento that is supported by the extension.
Academic Free License 3.0
The Academic Free License 3.0 (AFL) is an open source license that permits the free distribution and reuse of proprietary software and derivative works, provided that the source code is made available.
Apache License 2.0
BSD 2-Clause License
The Berkeley Software Distribution 2-Clause License requires the copyright notice to appear in all source code, but imposes minimal restrictions on the redistribution of open source software. The 2-clause license was derived from the original 4-clause BSD license which requires a notice to appear in all advertising and prohibits the use of the contributor names in endorsements without prior written permission.
GNU General Public License 3.0
The GNU General Public License 3.0 (GLP-3.0) is widely used and based on the GNU open source license, and allows for the redistribution of software received from the copyright holder within the provisions outlined in the agreement. Any improved version of the software must be made available for free. To learn more, see: Frequently Asked Questions about GNU Licenses.
GNU Lesser General Public License 3.0
The GNU Lesser General Public License 3.0 (LGPL-3.0) is widely used and based on the GNU open source license. LGPL03.0 is somewhat less restrictive than the standard GLP-3.0, and also requires that you provide installation instructions. To learn more, see: Frequently Asked Questions about GNU Licenses.
The Massachusetts Institute of Technology License (MIT) allows for the reuse, modification, distribution, sublicensing, and sale of proprietary software, provided that all copies include the MIT license and copyright notice.
Mozilla Public License 1.1
The Mozilla Public License 1.1 (MPL-1.1) is an open source license that includes explicit patent rights and allows extensions of the code to be licensed in non-open ways. There is no requirement for a derivative work to be distributed under the same license.
Open Software License 3.0
The Open Software License 3.0 (OSL-3.0) is a worldwide, royalty-free, non-exclusive license that allows sublicensing and derivative work, provided that they are distributed under the same license.
Upload your customer-facing documentation in PDF format. The user guide is required, and you can optionally include a reference manual and installation guide. The maximum file size for each PDF is 5 MB.
Your extension must include one user guide.
Although the installation guide is optional, it might be required by some license types.
The preliminary Release Notes text can include simple HTML, without CSS. Maximum characters: 10,000
If applicable, identifies each shared package that is required by this extension.