MyAlgoGuru Help
Education Glossary Open the app
Help/Reference/Trading Core

Order Management

The single gateway every order passes through — created, risk-checked, submitted to the broker, and tracked to completion, with a full immutable history.

Where you will find this

Order book & history, Order detail & lifecycle.

Purpose

Whether an order comes from the manual terminal, a strategy, or a webhook, it is created, validated and submitted here — and only here. Order Management is the one module that talks to the broker’s order API, which is what makes the platform’s risk and audit guarantees possible.

The controlled path & Algo-ID

Every order runs Manual/Strategy/Webhook → Risk → Order Management → Broker. Automated orders are tagged with your Algo-ID as the exchange requires, and the order’s lifecycle is an append-only history that is never edited or deleted.

The Order Management module is the central business component responsible for the complete lifecycle of all trading orders within MyAlgoGuru.

Every order, irrespective of its source, is managed through this module.

The module provides a common business model for order creation, submission, monitoring, modification, cancellation and completion across all supported brokers.

Objectives

The module will:

  • Provide a unified order lifecycle.
  • Support orders originating from multiple sources.
  • Maintain a single source of truth for order information.
  • Track the complete lifecycle of every order.
  • Abstract broker-specific implementations.
  • Provide consistent order information to all business modules.
  • Maintain complete auditability.

Functional Scope

The module includes:

  1. Order Creation
  2. Order Submission
  3. Order Lifecycle Management
  4. Order Modification
  5. Order Cancellation
  6. Order Status Management
  7. Order Source Management
  8. Order Validation
  9. Order Tracking
  10. Order History
  11. Order Audit

Order Sources

Orders may originate from multiple business modules.

Supported order sources include:

  • Manual Trading Terminal
  • Webhook Signal Execution
  • Strategy Execution Engine
  • Basket Orders (Future)
  • API Integrations (Future)
  • Copy Trading (Future)

All orders will follow the same business lifecycle irrespective of their source.

Order Creation

Every order is created within the Order Management module.

An order will contain all information required for execution.

Typical order information includes:

  • Broker Account
  • Instrument
  • Exchange
  • Buy / Sell
  • Product
  • Quantity
  • Price
  • Order Type
  • Order Source
  • Timestamp

Order Validation

Before submission the platform will validate:

  • Broker Account
  • Broker Session
  • Instrument
  • Trading Product
  • Exchange
  • Quantity
  • Order Type
  • Required business rules

Only valid orders will proceed to broker submission.

Validation failures will prevent execution.

Order Submission

Validated orders is submitted to the selected broker.

Submission will occur independently for every broker account.

Submission success or failure is recorded.

Order Lifecycle

Every order will follow a defined lifecycle.

Typical lifecycle stages include:

  • Created
  • Validated
  • Submitted
  • Accepted
  • Partially Executed
  • Fully Executed
  • Modified
  • Cancelled
  • Rejected
  • Expired
  • Failed

The platform will maintain the current lifecycle state of every order.

Order Status

The latest broker status will always be available.

Typical business statuses include:

  • Pending
  • Open
  • Executed
  • Cancelled
  • Rejected
  • Expired

Order status remains synchronized with broker updates.

Order Modification

Where supported by the broker, users or business modules is able to modify eligible orders.

Modification may include:

  • Quantity
  • Price
  • Validity

Every modification is recorded.

Order Cancellation

Eligible orders will support cancellation.

Cancellation is requested through the Order Management module.

Successful and unsuccessful cancellations is recorded.

Market Orders

The Order Management module will support Market Orders.

Where a broker does not support true Market Orders, equivalent execution behaviour is implemented transparently.

Business modules remains independent of broker-specific implementations.

Limit Orders

The module will support Limit Orders wherever supported by the broker.

Limit order behaviour will follow broker business rules.

Product Types

Supported trading products include:

  • Intraday
  • Delivery

The platform remains extensible for future product types.

Order Ownership

Every order will maintain ownership information.

Ownership includes:

  • User
  • Broker Account
  • Source Module

Ownership information remains permanently associated with the order.

Order Tracking

The platform will continuously track order progress.

Tracking includes:

  • Broker Status
  • Execution Progress
  • Partial Execution
  • Completion
  • Failure

Order tracking will continue until the order reaches a terminal state.

Partial Execution

The platform will support partially executed orders.

Partial executions will update:

  • Executed Quantity
  • Remaining Quantity
  • Average Execution Price

The order remains active until completion or cancellation.

Multi-Broker Processing

Orders belonging to different broker accounts will execute independently.

Failure of one broker account does not impact orders belonging to other broker accounts.

Order History

Historical orders remains permanently available.

You can review historical order information.

Historical records does not be modified.

You can search and filter orders.

Typical filters include:

  • Date Range
  • Instrument
  • Broker
  • Order Status
  • Buy / Sell
  • Product
  • Source Module

Order Audit

Every significant order event will generate an audit record.

Typical audit events include:

  • Order Created
  • Order Validated
  • Order Submitted
  • Order Modified
  • Order Cancelled
  • Order Executed
  • Order Rejected
  • Order Expired

Audit records remains immutable.

Business Rules

  • Every order will originate from one business module.
  • Every order will belong to one broker account.
  • Broker authentication is mandatory before submission.
  • Every order will follow a defined lifecycle.
  • Broker status remains synchronized.
  • Partial executions is supported.
  • Historical orders will never be deleted.
  • Audit records will never be modified.
  • Business modules does not communicate directly with brokers.
  • All trading orders will pass through the Order Management module.

Out of Scope

The following are outside the scope of this module:

  • Trading Strategies
  • Position Calculations
  • Portfolio Analytics
  • Risk Validation
  • Market Data
  • Historical Data
  • Broker-specific API implementations

These are covered by their respective business modules.

Reconciling against the broker

  • The broker’s quantity is treated as the truth, including on a partial fill — what the exchange filled is what happened.
  • Every outbound broker call is recorded with its response, which is what makes a rejection explainable after the fact rather than a mystery.