Build an instrument schedule first
For each instrument, record the source identifier and the broker-facing symbol, decimal precision, contract assumptions, trading sessions and any mapping rules. Also identify the intended use of the data. Price display, analysis, trading and onward distribution may have different technical and contractual requirements.
Ask the source to confirm coverage and usage rights for your exact use case. A symbol appearing in a sample does not establish permanent availability, redistribution permission or the completeness of every associated field. Keep exceptions in the instrument schedule.
Validate data quality at the receiving side
| Check | What to observe | Why it matters |
|---|---|---|
| Freshness | Time since the last usable update during the expected session | A connected feed can still deliver stale prices |
| Mapping | Source symbol, destination symbol and specification | A valid quote attached to the wrong contract is still wrong |
| Continuity | Gaps, reconnect behaviour and session transitions | Recovery should not silently leave instruments without updates |
| Fallback | Source selection and change notification | Operators need to know which source is active |
Choose thresholds from the instruments and business requirements. A universal quote-age threshold would ignore session schedules and differences in data activity.
Test a change of source
Compare the proposed feed alongside the current one in a controlled environment. Investigate differences in specifications and timestamps before treating price differences as a server fault. Keep a sample of mapping decisions and test evidence so the same questions do not reappear at go-live.
- Approve a limited instrument set and its destination mappings.
- Check representative active periods and session transitions.
- Simulate loss of the primary source and observe alerts and recovery.
- Release in stages, with an agreed method to return to the previous mapping.
Define the handover
The deliverable should identify configured instruments, known exclusions, monitoring owners and the action to take when a source is unavailable. Include a change process for new instruments or specification changes. A useful feed service should remain understandable after its initial installer leaves the conversation.
Use the specific MT4 price-feed plan or MT5 price-feed plan when configuring a branded trading environment. The data path and the MT4 White Label or MT5 White Label account model should be reviewed together.