The Problem
GTT (Good Till Triggered) orders are a fantastic tool for disciplined, level-based investing. You set your target price, quantity, and walk away. But here’s a real scenario many of us have faced:
- I place a GTT Buy for Stock X at ₹500, qty 100 → implied amount: ₹50,000
- Over the next few weeks, I deploy that ₹50,000 into other trades — F&O positions, other stocks, etc.
- Three months later, Stock X hits ₹500.
- The GTT triggers → Order gets rejected due to insufficient funds.
The GTT executed at exactly the right price, but I missed the trade entirely. The whole purpose of setting it was defeated.
The Proposed Solution
Add an optional “Reserve Funds” toggle on the GTT order placement screen (and editable from the GTT dashboard later).
How it would work:
- When enabled, the equivalent amount (Qty × Trigger Price) is earmarked on the Funds dashboard — shown as “Funds reserved for GTT” similar to how margin blocked for F&O positions is displayed separately.
- This is purely a soft earmark / visual indicator — it doesn’t need to be a hard regulatory block. Just a clear display so the user is aware not to over-deploy those funds.
- Optionally, a warning could appear when the user tries to use funds that would dip into the earmarked amount.
Why It Should Be Optional (and OFF by default)
I fully understand that the primary appeal of GTT is that you don’t need to keep funds idle. Many users place GTTs specifically because they want to stay invested elsewhere in the interim. This feature should not change that behavior at all.
- ☐ Reserve funds for this GTT order (unchecked by default)
Only users who want the safety net opt in. Everyone else’s experience stays exactly the same.
Who Benefits
- Long-term investors who set GTTs months in advance and actively trade in the meanwhile
- F&O traders who use GTT for equity accumulation but frequently tie up funds in margins
- Anyone managing multiple GTTs across different stocks with varying trigger timelines
This feels like a relatively low-complexity UI addition that could prevent a genuinely frustrating experience. Would love to hear if others have faced this and what the team thinks about feasibility.
Thanks,