Multi-Slave Trade Copier:
One Source, Multiple Followers

Platform support update (September 25, 2026): TradeCopier supports MT4, MT5, cTrader, NinjaTrader 8, DXTrade, TradeLocker, MatchTrader and VertexFX. The inspected self-service menu showed MT5, TradeLocker and cTrader; ask support for setup instructions for the other platforms. Confirm your exact broker, account mode, copying direction, instrument and order actions before live use.

A multi-slave trade copier sends eligible trading events from one source account to more than one follower account. “Slave” is older terminology for a follower; it does not imply that the accounts, brokers or fills become identical. Each destination has its own connection, sizing rule, instrument specifications, order response and position state. Plan and verify them separately.

Publisher disclosure: TradeCopier publishes this guide about its own product. The account names and quantities below are fictional planning examples, not a customer result or live performance test. Plan facts and cited platform references were checked September 23, 2026; the self-service account choices were checked September 24, 2026. Confirm the current connection and plan terms before trading.

Check the account limit before adding followers

TradeCopier's published pricing lists a permanent Free plan with one trading group and three total trading accounts. It is not a seven-day trial, and the Free plan does not have paid account add-ons. At the time of this review, Pro lists five groups and 15 accounts, while Pro Plus lists 20 groups and 60 accounts; extra-account add-ons are offered on paid plans. These are finite advertised limits. Check the live page and confirm how source and follower connections are counted for your setup.

For example, a proposed source A with followers B and C uses three account aliases. That fits the stated Free account number only if all three connections are eligible and the current account-counting rules match the proposal. Source A with B, C and D uses four aliases and exceeds the stated Free account number. This arithmetic says nothing about whether the platform pair, broker, instrument or order type is supported.

Make a one-to-many route table

Before connecting accounts, keep one row per intended follower. Include the account owner, platform and broker/server, account mode, instrument name, connection method, intended source-to-follower direction, sizing rule and selected limit. The current platform guide describes MT5, TradeLocker and cTrader as the choices observed in the inspected self-service account flow. TradeCopier supports MT4 and NinjaTrader 8; request their current setup instructions and demonstrate the exact follower route. Even among the visible choices, confirm each intended broker, account mode, instrument, order action and direction instead of treating a platform name as universal compatibility.

For account-group membership, approvals and change rollback, use the separate account-groups checklist. This page focuses on checking each follower's trade lifecycle once a one-to-many design has been approved.

Set a rule for each follower, then check its broker constraints

A lot multiplier is a quantity instruction, not a risk guarantee. Suppose a fictional 0.20-lot source order is proposed for B at 0.50 times and for C at 1.00 times. The unrounded proposed quantities are 0.10 and 0.20 lot. Neither should be described as the same monetary exposure until the follower's contract size, tick value, volume minimum, maximum, step, account currency and existing positions have been checked. The MetaQuotes symbol-properties reference documents these as distinct instrument fields. The lot-multiplier guide covers the calculation separately.

Symbol names alone do not prove contract equivalence. B may call an instrument EURUSD while C appends a broker suffix; a metal, index or futures symbol can differ more substantially. Review the symbol-mapping workflow, verify the selected destination instrument and contract, and use a manual override only when the correct match is known. If a follower has no valid mapping or a quantity cannot satisfy its trading rules, record the exception instead of assuming that a copied order executed.

Run a controlled test for B and C separately

1. Record the proposed source event and expected B/C symbol, side and quantity before sending it. Use an appropriate permitted demo environment where available. Confirm that both routes and account permissions support the event.
2. Observe whether each follower received a request. Preserve the copier event and any error from the activity log; a green or sent status is not a broker fill.
3. At each follower broker, compare accepted or rejected order state, every linked execution deal, filled and remaining quantity, protection levels and resulting position. MetaTrader 5 distinguishes orders, deals and positions. Its OrderSend reference also cautions that a successful request return does not by itself prove execution.
4. Test the actions actually needed by the workflow: an opening instruction, a protection change, a partial and full close, and pending-order creation or cancellation if the exact route supports them. Record unsupported actions rather than assuming that a basic open proves the whole lifecycle.
5. Introduce a safe connection interruption in a test environment if the route permits it. Reconcile both followers' broker states before retrying an event with an uncertain outcome; an unconfirmed response is not evidence that no order executed.

Compare B and C independently. One accepted destination request cannot validate the other, and matching source/follower order counts do not prove matching exposure. Different brokers can quote, reject, partly fill or process protection instructions differently. No fixed replication-accuracy percentage, profit improvement or time saving follows from having multiple followers.

Review combined exposure and ongoing operation

A copied market idea can create correlated positions on both followers. Record the account-specific modeled downside, pending instructions and current positions, then review the combined exposure in a common currency if the same owner is responsible for both accounts. Separate trading groups do not eliminate shared market or broker risk. The risk-management worksheet offers a multi-layer review method.

When a follower is added, removed or moved between groups, record which operator remains responsible for its open positions and pending orders. Do not assume that disconnecting an account closes positions or that reconnecting replays, repairs or cancels earlier events. Confirm the current product behavior, preserve a before-and-after broker snapshot, and leave uncertain outcomes open until reconciled.

To start, compare the current plan capacity and route details, then use TradeCopier's getting-started flow for the live connection instructions. A usable one-to-many setup is a documented route with observed outcomes for every follower, not a promise of unlimited accounts or identical broker fills.