Common Platform
Orders
Detailed guide for reading order history, Trade Scalper order book, order status, broker messages, and leg details.
Overview
#Orders show what the platform sent to the broker and what response came back.
In Trade Bridge and Trade Bots, the Orders page is called Order History. It shows today’s executions and can also show still-running positional executions carried from an earlier day, because users must be able to monitor open trades until they close. In Trade Scalper, it is called Order Book and currently focuses on today’s Trade Scalper orders; when positional support is enabled, running carried Trade Scalper trades should also remain visible until they close. Closed history remains available in Analytics.
Today’s orders and open positional trades
#The current Orders screen is mainly for current-day activity, but Trade Bridge and Trade Bots can also show running positional executions from an earlier day until they close.
If you need older closed trades, use Analytics. If you need open exposure, use Positions.
Auto refresh
#Orders refresh automatically about every 10 seconds.
Trade Bridge and Trade Bots also listen for live order and execution updates. If an order was just placed, wait a few seconds before refreshing the browser.
Demo preview
#When you are logged out and preview is supported, Trade Bridge and Trade Bots can show demo order data with a demo notice.
Demo orders are only for learning the screen. They are not broker orders and cannot affect your real account.
Trade Scalper login required
#Trade Scalper Order Book contains private account data and is available only after login.
If you are not logged in, the page shows a Login button. Click Login and then reopen Trade Scalper Orders.
Common Order Book Columns
#All product order books use the same core columns: Time, Mode, Broker, Symbol, Leg Ref, Product, Purpose, Side, Qty, Price, Status, and Message.
This keeps Trade Bridge, Trade Bots, and Trade Scalper order review consistent.
Order Book Sorting
#Click any Order Book column heading to sort by that column. Clicking the same heading again changes ascending/descending order.
The default view is newest Time first. Custom sorting is only for the current browser session; refreshing the page returns to the default order.
Loading, empty, and error messages
#Loading orders or Loading... means the page is waiting for API data.
No orders for today or No order history yet means there is no visible current-day order or running execution for this view. Failed to load order book/history means the API may be restarting or temporarily unavailable; reload after the service is back.
Leg-level rows
#Trade Bridge and Trade Bots Orders show leg orders directly, without a higher-level trade row to expand.
Example: if one signal has four legs, the Orders page shows four direct leg/order rows. This makes the exact broker-bound actions visible immediately.
Time column
#Time shows when the leg order was placed or executed, using IST.
Use this when comparing platform records with a chart or broker order book.
Status
#Status can be complete, rejected, cancelled, pending, or another broker/platform status depending on the row.
Read Status with the Message column to understand whether the order reached the broker and what happened next.
Trade Ref
#Trade Ref identifies the full trade or execution.
Orders keeps this hidden for a simpler client view. Use Analytics or admin investigation when full trade-level reference context is needed.
Symbol
#Symbol is the exact instrument sent to the broker.
Always compare this with the intended symbol, expiry, strike, and option type before assuming the order is wrong.
Leg Ref
#Leg Ref identifies one leg inside the Trade Ref.
Example: If one strategy has CE BUY and PE BUY, each leg gets its own Leg Ref. Share Leg Ref with support when the issue is only in one leg.
Order Ref
#Order Ref identifies one platform-side order event.
Orders keeps this hidden for a simpler client view. Use Analytics or admin investigation when a specific platform order reference is needed.
Mode and Product
#Mode shows whether the individual leg/order was Forward Testing or Live. Product shows the broker product type such as MIS, NRML, or CNC.
Read these with Symbol and Purpose before comparing platform rows with broker records.
Purpose ENTRY / EXIT
#ENTRY means the order was used to enter the trade. EXIT, STOP LOSS, or TARGET means the order was used to close or protect it.
Stop-loss and target orders are shown only after they become complete, so users do not see unused protective rows as final orders.
Side
#Side shows BUY or SELL.
Common example: BUY at Rs 100 means the platform tried to buy one option. If the exit is SELL at Rs 130, it closes that BUY position.
Qty
#Qty shows filled quantity where available; otherwise it shows requested quantity.
Example: If quantity 4 was requested but only 2 filled, the value may show the filled amount once broker fill data is received.
Executed Price
#Executed Price shows fill price when available; otherwise it can show the requested price.
Example: If you expected entry at Rs 100 but broker fills at Rs 101, this column can show Rs 101. That is the price used for actual P&L.
Executed
#Executed shows the order placed/executed time in IST where available.
Use this with the broker order book when checking exact timing.
Time
#Time shows when the Trade Scalper order was placed, using IST with seconds.
The newest orders are sorted near the top based on available order timestamps.
Broker
#Broker shows broker label and broker type.
This helps confirm whether the manual order went to the expected , , or account assigned to you.
Order ID
#Trade Scalper Orders keeps broker/order IDs hidden for a simpler client view.
If support needs full order references, use Analytics or admin investigation views.
Symbol, Mode, Product, and Purpose
#Symbol shows the traded contract. Mode shows Live or Forward Testing. Product shows broker product type such as MIS, NRML, or CNC. Purpose explains why the order exists, such as entry or exit.
For beginner review, read these fields together: what was traded, whether it was Live or Forward Testing, product type, and why the order was placed.
Side, Qty, and Avg Price
#Side shows BUY or SELL. Qty shows filled quantity or requested quantity. Avg Price shows broker average fill price where available.
Example: BUY quantity 1 at Avg Price Rs 100 means one unit/lot was bought around Rs 100 according to broker data.
Status and Message
#Status shows brokerStatus when available, otherwise platform status.
Message shows broker or platform text such as rejection reason or refresh error. If unclear, share broker, symbol, time, and the visible message with support. Analytics has full IDs if support asks for them.
Pending
#Pending means the order has been created or sent but is not complete yet.
Do not assume a pending order is filled. Check again until it becomes Complete, Rejected, Cancelled, or another final state.
Open
#Open usually means the broker accepted the order but it has not fully executed yet.
Example: A limit order may remain open while waiting for the market price to reach the limit price.
Partial Complete
#Partial Complete means only part of the quantity was filled.
Example: You placed quantity 4 lots, but only 2 lots are filled. The remaining quantity may still be open, cancelled, or rejected depending on broker behavior.
Complete
#Complete means the broker confirmed the order fill or completion.
For exits, completion usually means the position was closed for that leg/trade. Final P&L still depends on the actual filled price.
Cancelled
#Cancelled means the order was cancelled before full execution.
An order can be cancelled manually, by the platform, or by broker rules. If it was an entry order, check whether any partial fill happened.
Rejected
#Rejected means the broker or platform did not accept the order.
Read the friendly message first. Common reasons include insufficient funds, invalid quantity, wrong product type, expired broker session, exchange rejection, or market closed.
Friendly message
#Friendly message is the simplified reason shown to users.
Read this first before checking raw broker text. It is written to explain the issue in normal language.
Raw broker or platform message
#Raw message is the original detailed text received from the broker or platform.
It can be technical, but it helps support understand the exact failure. Do not share passwords, OTP, API Secret, or broker tokens.
Support Reference
#Support references are useful when contacting support.
Orders keeps only simple visible context. Analytics and admin investigation views show full trade/order references when needed. Do not share passwords, OTPs, API secrets, or full broker credentials.
Example order flow
#Example: You BUY one option at Rs 100 with quantity 1. The platform creates an entry order and sends it to the broker.
If broker accepts and fills it at Rs 100, status becomes Complete. If funds are insufficient, status becomes Rejected and the message explains the reason. If you later exit at Rs 130, a separate exit order appears with its own status.