Lazy Trader / Docs

Position Manager

How Position Manager in Lazy Trader binds one chart button to one open position, shows the planned exit structure, and lets you modify levels, stop, and volumes directly on the chart.

Position Manager appears after a trade is already open and creates a separate chart button for each active position inside the current trade plan. The button shows both the plan name and the model name, so even when several trades are open at once you can still see exactly which button belongs to which position.

That one-to-one mapping matters. One button corresponds to one open position under one selected plan and one specific model. It is not a generic management overlay; it is a direct control point for the exact trade that is already running inside the scenario.

Because of that, position handling stays inside the same workflow instead of being pushed into a separate manual routine. The trader keeps the scenario context, the model identity, and the live management controls in one place.

Position Manager in Lazy Trader

What the manager shows immediately

  • Which levels will be used for partial exits and what volume is assigned to each one.
  • Where breakeven is scheduled to trigger and which exact level the stop will be moved to.
  • Where the current stop-loss is located.
  • What profit or loss each level would produce if price reaches it.

Familiar logic for Magic Entry users

Levels can be moved directly on the chart, so the interaction will feel familiar if you have already worked with Magic Entry.

Stop-loss and take-profit levels can also be dragged freely without switching into a different screen.

The workflow stays visual: you do not manage the trade through an abstract parameter table first, but through the same levels you can already see on the chart.

What you can change while the trade is live

  • Add new levels directly into the open position if the remaining volume allows it.
  • Edit level volumes manually through input fields and let the remaining parameters adjust automatically.
  • Reposition take-profit levels and breakeven transitions as the management scenario evolves.
  • Push the stop-loss farther away or remove it entirely if that is part of the chosen trade-management scenario.

What this page describes at the product level

This is not a new entry engine and not a new trade-detection logic. The page only explains how an already open position is visualized and managed inside Lazy Trader.

If Base config defines the shared risk and management rules for a model, Position Manager becomes the live control layer for one concrete open position operating inside those rules.

Related pages for live management

STATUS canvas

Status canvas merges Direction, Start After, End At, Time, and Models into one live state map, so you can see what is aligned, what is still pending, and why the plan is running or waiting.

Open full section

Base config

Base config is the shared risk and management layer that sits under each model and keeps model-specific logic from drifting into risk chaos.

Open full section

MODELS menu

Models are the executable entry modules inside the plan, and the menu is built to let many different model types coexist under one scenario.

Open full section

PLAN menu

PLAN is the root canvas: it is where risk, entry/stop/take, and the links to every other menu become one executable scenario.

Open full section

Other Lazy Trader sections

What Lazy Trader does

Use this page when the main question is not “which button do I press”, but “what role does Lazy Trader play in the workflow at all”.

Open full section

PLAN menu

PLAN is the root canvas: it is where risk, entry/stop/take, and the links to every other menu become one executable scenario.

Open full section

END AT menu

END AT defines when the plan stops looking for new positions, which is different from instantly flattening every already-open trade.

Open full section

TIME menu

TIME is where session logic lives: windows, overnights, weekday permissions, daily close, Friday close, and broker-specific timing constraints.

Open full section

Automatic direction detection

This section explains the combined logic of Direction plus Start After, which is where many users actually shape the market bias of the plan.

Open full section

DIRECTION menu

Direction defines whether the plan is fixed long-only, fixed short-only, or dynamically biased through box, MA, or swing logic.

Open full section

START AFTER menu

Start After does not pick the side of the trade; it defines what must happen before the plan is allowed to begin evaluating entries at all.

Open full section

MODELS menu

Models are the executable entry modules inside the plan, and the menu is built to let many different model types coexist under one scenario.

Open full section

STATUS canvas

Status canvas merges Direction, Start After, End At, Time, and Models into one live state map, so you can see what is aligned, what is still pending, and why the plan is running or waiting.

Open full section

Base config

Base config is the shared risk and management layer that sits under each model and keeps model-specific logic from drifting into risk chaos.

Open full section

Box-Fractal model

Box-Fractal uses a confirmed fractal range as the structural base for entry and stop placement rather than entering at the first raw extremum.

Open full section

Larry-Williams model

Larry-Williams works with range extremes and supports both direct breakout continuation and return-entry logic after a raid back into the range.

Open full section

Classic Structure family

Classic Structure is the shared logic layer for three related pages: trend continuation, primary liquidity sweep, and reversal structure.

Open full section

Classic Structure Trend

Classic Trend participates on a pullback inside the active structure without requiring the structure direction itself to flip.

Open full section

Classic Structure via primary liquidity sweep

This variation opens on the first important structural violation and reads it as a sweep rather than as a full structural reversal.

Open full section

Classic Structure Reversal

Classic Reversal becomes relevant only when structure itself turns; it is not just a pullback model with a different stop.

Open full section

Moving Averages model

The MA model does more than “touch the fast average”: it also validates the nearest eligible fractal to the left before opening.

Open full section

Balanced Price Range (BPR)

BPR is the imbalance-compression model: it works with the overlap between opposite inefficiencies and lets you choose how deep into that balance zone entry should happen.

Open full section

Strategy optimization and tester workflow

Optimization is where the guide stops being descriptive and becomes operational: save several plan configs, iterate them in the tester, and read the journal by model contribution.

Open full section