Define the product before configuring the symbol
Record the intended contract, quote source, execution path, account eligibility and client-facing description. Identify session schedules, relevant currencies and reporting dependencies. A new instrument family can change operational expectations even when it appears beside existing products in the same interface.
MetaTrader 5 supports a multi-asset platform model, but the instruments available to a particular brokerage depend on its actual sources, counterparties, permissions and configuration. Confirm the proposed catalogue item by item instead of inferring market access from the platform name.
Approve a product-readiness matrix
| Area | Question | Release evidence |
|---|---|---|
| Instrument definition | Does every team use the same contract meaning? | Approved specification and destination mapping |
| Account model | Which accounts may use the product? | Tested eligibility and required configuration |
| Sessions and data | When are prices expected and how are gaps detected? | A representative observation and alert review |
| Operations | How are events and reports investigated? | Support notes and a reconciled sample workflow |
The matrix is illustrative. Product approval, client eligibility and any legal or commercial permissions must be handled by the responsible business and external providers.
Test a representative subset
- Select instruments that represent materially different sessions or dependencies.
- Validate specifications and mapping before comparing operating behaviour.
- Exercise the relevant account and reporting workflows in a controlled environment.
- Review a session transition and a dependency interruption before release.
Keep a register of exclusions. If a source lacks a required field, or a connector does not support a required workflow, resolve it before the product is presented as available. Additional symbols should follow the same approval process as the initial set.
Extend the operating handbook
Document who approves specification changes, who investigates a stale stream and who coordinates with each external provider. Support teams need an instrument-aware escalation path, not a generic message that every issue is a server problem.
Use the MT5 White Label brief to establish the account and operational model. The data review and execution connectivity review provide separate acceptance records that should meet at the same approved instrument catalogue.