TTMT Docs

Appearance

Limit Order Conversion ​

When you're using the layered entry strategy, some of your orders are placed as limit orders waiting for price to retrace. But what happens when a signal provider sends a followup message with an updated entry zone, and the market has already moved into that zone?

TTMT automatically detects these situations and converts your pending limit orders to market orders - ensuring you don't miss the trade while still respecting the signal provider's guidance.

The Problem This Solves ​

Imagine this scenario:

  1. Initial Signal: Buy XAUUSD @ 2650, SL @ 2640
  2. Your Layer 2 limit order is placed at 2648 (waiting for retracement)
  3. Price drops to 2647 but your limit hasn't filled yet
  4. Followup Signal: "Entry zone updated to 2645-2652"
  5. Market is now inside the provider's recommended zone

Without conversion, your limit order at 2648 would just sit there - even though the market is at a better price (2647) and the signal provider has confirmed this zone is valid for entry.

With conversion, TTMT recognizes this opportunity and converts your limit to a market order, getting you filled at 2647.

How It Works ​

When a followup signal arrives with an updated entry zone, TTMT evaluates each pending limit order:

Step 1: Check if Order is "Marketable" ​

An order is marketable when its price is at or past the current market:

Trade TypeMarketable When
BUYLimit price ≥ Current Ask
SELLLimit price ≤ Current Bid

Example: Your BUY limit is at 2648, current Ask is 2647 → The limit is marketable (you're willing to pay 2648, but market offers 2647)

Step 2: Validate Against Entry Zone ​

Just because an order is marketable doesn't mean it should execute. TTMT checks if the current market price falls within the followup signal's entry zone:

Followup Entry Zone: [2645, 2652]
Current Market: 2647

Is 2647 within [2645, 2652]? ✓ YES → Conversion allowed

Step 3: Execute Conversion ​

If both conditions are met:

  1. Cancel the pending limit order
  2. Place a new market order at current price
  3. Preserve the original SL, TP, and volume

Why Both Conditions?

The dual-check protects you from executing at unfavorable prices. If market has moved outside the provider's recommended zone, your limit order is adjusted (capped) rather than converted - preventing you from chasing price.

Decision Flow ​

Conversion requires BOTH conditions:

  1. Order is marketable (limit price ≥ ask for BUY)
  2. Current market is inside provider's entry zone

Key Insight

Both conditions must be TRUE for conversion: the order must be marketable (price is at or past market) AND the market must be inside the signal provider's entry zone. This dual-check prevents executing at unvalidated prices.

Practical Examples ​

Example 1: Successful Conversion ​

Setup:

  • Trade: BUY XAUUSD
  • L2 limit order at: 2648.00
  • Followup entry zone: [2645.00, 2652.00]
  • Current market (Ask): 2647.50

Evaluation:

  1. Is L2 marketable? 2648 ≥ 2647.50 → YES
  2. Is market (2647.50) in zone [2645, 2652]? → YES

Result: L2 is converted to market order and fills at 2647.50

Better Entry

You got filled at 2647.50 instead of waiting at 2648.00 - a 50 point improvement, validated by the signal provider's zone.

Example 2: Conversion Blocked (Market Outside Zone) ​

Setup:

  • Trade: BUY XAUUSD
  • L2 limit order at: 2648.00
  • Followup entry zone: [2650.00, 2655.00] (zone moved up)
  • Current market (Ask): 2644.00

Evaluation:

  1. Is L2 marketable? 2648 ≥ 2644 → YES
  2. Is market (2644) in zone [2650, 2655]? → NO (below zone)

Result: L2 price is capped to a safe distance below market. No conversion.

Protection Active

Even though your limit is technically marketable, TTMT won't execute because the market is outside the provider's recommended zone. This prevents you from entering at prices the provider hasn't validated.

Example 3: Order Not Marketable ​

Setup:

  • Trade: BUY XAUUSD
  • L3 limit order at: 2642.00
  • Followup entry zone: [2645.00, 2652.00]
  • Current market (Ask): 2650.00

Evaluation:

  1. Is L3 marketable? 2642 < 2650 → NO

Result: L3 remains as a limit order. Its price is adjusted to fit the new zone distribution.

Normal Behavior

The limit order isn't at market yet - it's still waiting for price to retrace. TTMT adjusts its price to align with the new entry zone but keeps it as a pending limit.

What Gets Preserved ​

When a limit order is converted to market, TTMT preserves:

AttributeBehavior
VolumeSame lot size as original order
Stop LossUses trade's current SL (may include followup updates)
Take ProfitUses order's assigned TP level
LayerTracked as same layer (L2, L3, L4)
Magic NumberPreserved for trade identification

Edge Cases ​

Freeze Zone Protection ​

If a limit order is very close to market but not yet marketable, it enters the broker's "freeze zone" where modifications aren't allowed. TTMT automatically caps these orders to a safe distance:

Market: 2650.00
Freeze Level: 20 points
Order at: 2649.90 (within freeze zone)

→ Order capped to: 2649.30 (safely outside freeze)

No Entry Zone in Followup ​

If the followup signal doesn't include an explicit entry zone, conversion is disabled. Orders may have their prices capped, but won't be converted to market. This prevents executing without the signal provider's zone validation.

Multiple Orders Converting ​

Each limit order (L2, L3, L4) is evaluated independently. It's possible for:

  • L2 to convert (closest to market)
  • L3 to remain as limit (still waiting for deeper retracement)
  • L4 to remain as limit (deepest layer)

Configuration ​

Limit order conversion is automatic - there's no setting to enable or disable it. The behavior is governed by:

  1. Entry Zone Updates from followup signals
  2. Current market price at the time of followup processing
  3. Broker specifications (freeze levels, stops levels)

Working With Your Signal Provider

Conversion works best with signal providers who send clear followup messages with updated entry zones. If your provider only sends "TP hit" or "SL updated" messages without zones, conversion won't trigger.

This feature works as part of the complete trade lifecycle: