Grid Settings
The Grid step controls how a bot builds into a position after an entry. This is where you decide whether the position structure will be simple, layered, aggressive, or tightly controlled.
What this is
This article explains the current grid configuration modes and the fields that shape order distribution.
When to use it
Use this article if:
- you are defining DCA or ladder behavior
- you are not sure whether to use parametric or manual mode
- you want to understand how level distribution and order sizing work
Before you start
Before configuring the grid, make sure you already set:
- exchange account
- market type
- symbol or all-coins mode
- leverage and sizing
- entry filters
Important current product behavior:
- the grid supports parametric and manual modes
- grid_orders and levels are capped at 40
- parametric mode generates levels from a compact set of inputs
- manual mode requires explicit level arrays
- optional level_filters are supported
Step by step
Step 1: Choose the right grid mode
Use Parametric if you want the system to generate the ladder from a few inputs. Use Manual if you already know the exact level plan.
As a rule:
- parametric is faster to test and iterate
- manual is better when each level matters individually
Step 2: Configure a parametric grid
The current parametric mode includes fields such as:
- grid_orders
- overlap_pct
- indent_first_pct
- pull_up_pct
- order_type
- martingale_pct
- log_distribution
How to interpret them:
- grid orders controls how many generated levels you get
- overlap controls the width of the ladder
- indent first controls how far the first level starts from the trigger
- pull up adjusts the ladder shape when enabled
- martingale changes how size grows across levels
- log distribution changes how spacing is distributed
Step 3: Configure a manual grid
Manual mode is the right choice when each level needs explicit control.
In practice, manual mode is defined through arrays such as:
- indent_pct
- volume_pct
- optional level_filters
Make sure the arrays describe a coherent ladder instead of a random set of levels.
Step 4: Add level filters only when they are necessary
The product supports optional grid.level_filters , which lets you attach extra logic to specific levels.
Use level filters only when the strategy really needs them. They make the grid harder to reason about and harder to debug.
Step 5: Match the grid to exit and risk
Before leaving the Grid step, check whether the grid still makes sense with:
- take-profit targets
- stop-loss design
- trailing-stop behavior
- daily risk limits
A wide, aggressive grid paired with a tight stop or restrictive daily caps usually creates contradictory behavior.
What you should see
By the end of the Grid step, you should have:
- one clear grid mode selected
- a level structure you can explain in plain language
- a grid that fits the rest of the strategy instead of fighting it
Common mistakes
- choosing manual mode before you know the exact level plan
- adding too many levels without understanding the capital impact
- using martingale growth without reviewing exits and daily risk
- adding per-level filters too early
- forgetting to re-backtest after major grid changes
Related articles
- How Entry Filters Work
- Exit Settings And Risk Management
- Why Backtest Is Required Before Launch
- How To Read Backtest Report