Blog / Code & convert EAs · MQL5 Market · Expert Advisors

Part 5: After Approval: Updates, Versioning, Reviews and Support

Learn how to update your MQL5 Market EA, manage versions, respond to reviews, fix bugs, and support buyers after approval.

· 6 min read

Getting your Expert Advisor approved and published on the MQL5 Market is an important milestone. But publication is not the end of the development process.

Buyers may discover bugs, request clarification, or report behaviour that differs from what your product description promises. MetaTrader may also introduce platform changes that affect your EA.

A responsible seller needs a plan for maintaining the product, releasing updates, and supporting customers after publication.

This is the last part of the series. Part 1 starts with why EAs fail validation, and Part 4 covers the product page. The rules quoted below are from the MQL5 Market rules as of November 2026; check the current version, since they change.

1. Fix problems reported by buyers

Not every negative review means your EA has a programming error. A buyer might misunderstand an input parameter, use an unsupported configuration, or expect behaviour that the strategy was never designed to provide.

However, you should take genuine bug reports seriously.

The MQL5 Market rules require sellers to fix critical errors detected in a product. They also require sellers to keep the product's stated functionality working when changes to the MQL5 or MQL4 language make modifications necessary.

Buyers can request corrections when a critical error occurs or the product fails to deliver its stated functionality, provided no more than one month has passed since the purchase date.

When a buyer reports a problem:

  1. Read the report carefully and identify the affected functionality.
  2. Request the information needed to reproduce the issue, such as the symbol, timeframe, account type, input settings, and relevant Journal or Experts logs (how to read them).
  3. Reproduce the problem in your own environment.
  4. Identify the cause rather than simply adding a workaround.
  5. Correct the issue and test the revised build before releasing it.

Avoid dismissing reports with generic replies such as "It works on my computer." If you cannot reproduce the issue, explain what information is missing and how the buyer can provide it.

2. Release updates through the MQL5 Market

When you have fixed a bug or added functionality, publish the revised EX5 file through the product's version management section.

The usual process is:

  1. Open MQL5.com and go to your products in the Market.
  2. Select the relevant product.
  3. Open the Version tab.
  4. Choose New Version.
  5. Upload the updated compiled EX5 file.
  6. Describe the changes included in the release.

The new version is published only after it passes the automatic Market validation.

If validation detects an error, correct the problem and submit another build. Do not assume that a product's previous approval automatically covers every subsequent version.

You can also hide a published product from the Market showcase while you fix detected errors.

3. Keep version numbers and change records organised

Version control helps you and your customers understand which build they are using.

Use a consistent versioning system. For example:

  • 1.00 — Initial release.
  • 1.01 — Fixed an order-management error.
  • 1.10 — Added a new trading-session option.
  • 2.00 — Introduced a substantial strategy or functionality change.

The exact numbering convention is your choice, but it should be consistent and meaningful.

You can also specify the version in your MQL5 source code:

MQL5
#property version "1.10"

The value is a string of up to 31 characters. Set it in the main .mq5 file: the compiler ignores properties declared in included files.

When releasing an update, explain what changed in the Market's update description. The product's What's New section gives users access to the history of published changes.

Avoid vague descriptions such as "Improved EA" or "Fixed some issues."

Instead, write something specific:

Version 1.10

  • Corrected position-management logic.
  • Improved handling of unavailable historical data.
  • Added an adjustable trading-session filter.

Clear change records help customers understand whether an update addresses an issue they have experienced or introduces functionality they want.

4. Understand how customers receive updates

Publishing a new version does not mean every existing installation changes immediately.

According to the MQL5 Market rules, buyers update installed products manually at their own discretion. In MetaTrader 5, they install the new version from the Market section, among their purchased products.

Installing the new version replaces the previous file.

There are two important implications for sellers:

First, updates are free to existing buyers. The Market rules give buyers the right to free product upgrades.

Second, the previous version is not saved. Buyers who want to keep the existing file need to back it up themselves before installing an update.

For this reason, test each release carefully. A rushed update can replace a working version with a build that introduces new problems.

5. Handle reviews and product feedback professionally

Reviews can influence how potential customers perceive your product.

Only users who have purchased a product or downloaded its full free version can leave reviews under the Market rules.

When feedback appears, respond professionally.

If a buyer reports a genuine issue, acknowledge it and explain what you are investigating. If a user misunderstands how an input works, clarify the setting without blaming them.

For example:

"Thank you for reporting this. Could you share the symbol, timeframe, input settings, and relevant Journal messages? I'll use those details to investigate the behaviour."

If you have already released a correction, explain which version contains the fix.

Do not argue with reviewers, make unsupported claims about their trading results, or promise that an update will make the EA profitable.

The best long-term approach is to improve the product and provide useful support rather than trying to manipulate feedback.

6. Provide support through approved MQL5 channels

Buyers need a reliable way to contact you when they encounter problems.

MQL5 Market provides product comments and the MQL5 messaging system for communication between sellers and buyers.

Use these channels to:

  • Answer configuration questions.
  • Explain input parameters.
  • Request logs and reproducible test cases.
  • Communicate bug fixes.
  • Clarify compatibility requirements.
  • Explain what has changed in an update.

Be careful about directing buyers to external support channels. The Market rules prohibit links to Telegram groups and other messengers for product support. Keep support within the approved MQL5 communication channels.

Also, avoid collecting unnecessary personal information from customers through your EA or support process.

7. Maintain the product between releases

A published EA should not be treated as finished software that never needs attention.

Keep your development environment organised and retain your own copies of:

  • The latest source code.
  • The compiled EX5 file.
  • Previous stable builds.
  • Version and change records.
  • Important bug reports and their resolutions.
  • Relevant test results.

Periodically review the EA against changes in MetaTrader, MQL5, and the trading conditions it supports.

When you make a substantial change, test the affected functionality rather than assuming that a small modification cannot affect existing features.

A disciplined maintenance process makes it easier to investigate problems and release reliable updates.

Final thoughts

Publishing your EA is the beginning of a relationship with its buyers, not the end of your responsibilities as a developer.

Fix critical issues, maintain compatibility, keep version records, communicate changes clearly, and provide support through the appropriate MQL5 channels.

A well-maintained product gives buyers more confidence and helps protect the reputation you worked to establish when publishing it.

When a buyer's report points to a bug you can't find, PositionAlpha's Fix an EA can help: paste or upload the EA and describe the problem, with the log lines if you have them. The AI returns the complete updated .mq4 or .mq5 file and explains the problems it found and each change it made. Compile the result in MetaEditor and test it in the Strategy Tester and on a demo account before you release it as a new version.

Build a bot from your idea

Describe your trading idea and the AI writes MT4 or MT5 code for you to review and test, with a plain-English explanation and setup steps. Your first bot is free.

More from the blog