Free Narrow CPR Stock Scanner: Daily Shortlist for Breakout Trades
Narrow CPR · Stock Scanner
There are no items in your cart
Add More
Add More
| Item Details | Price | ||
|---|---|---|---|
A practical guide for Indian traders who already have a rule-based strategy
Trading strategy automation means converting your written entry, exit, stop-loss and risk rules into software that can scan, alert, backtest or place orders for you. It works only when the rules are fully objective. Typical builds include TradingView Pine Script indicators and strategies, custom screeners, backtesting tools, broker/API integrations and risk-control tools. Automation does not create an edge; it enforces one you already have.
Private strategy automation is the process of coding a trader's own rule-based strategy into a confidential tool, such as a Pine Script system, screener or broker-connected executor, so that the rules are applied consistently without emotional interference.
Most traders do not fail because their strategy is bad. They fail because they follow it inconsistently: skipping a valid setup after two losses, moving a stop-loss, or chasing a trade that was never in the plan. Automation removes that inconsistency.
In my years of teaching CPR, Price Action and intraday setups, the pattern is the same. A trader writes rules, trades them for a few weeks, then drifts. Coding the rules forces honesty: software cannot "feel" a trade is good. If a rule cannot be coded, it was never a rule.
Automation is not one thing. Most Indian traders need only one or two of the layers below, not a full auto-trading robot.
| Tool | What it does | Best for |
|---|---|---|
| TradingView / Pine Script indicator | Plots levels, signals and alerts on your chart | Discretionary traders who want clean, consistent signals |
| Pine Script strategy | Simulates entries, exits and stops on historical data | Testing a rule set before risking capital |
| Custom screener | Scans NSE/BSE stocks for your exact conditions | Finding setups without watching 200 charts |
| Backtesting tool | Measures win rate, drawdown, expectancy across many trades | Validating or rejecting an idea with data |
| Broker/API integration | Sends orders to your broker from signals | Traders with a proven, fully mechanical system |
| Execution and risk-control tools | Enforces daily loss limits, position size, order checks | Anyone who breaks their own risk rules |
A strategy is ready for automation when every decision can be answered with yes or no from data on the screen. If you say "wait for a strong candle" or "use judgement near resistance", the code cannot follow it until you define "strong" and "near".
This is an illustration of the thinking, not a trade recommendation.
| Discretionary version | Codeable version |
|---|---|
| "Buy when price breaks above CPR with strength" | Buy when a 15-minute candle closes above the CPR top, volume is above its 20-period average, and price is above VWAP |
| "Keep a sensible stop" | Stop-loss below the CPR pivot or the signal candle low, whichever is closer |
| "Book profit near resistance" | Exit at R1 or when a candle closes back inside the CPR |
| "Avoid choppy days" | No entries after 2:30 PM or when the previous day's range is below a set threshold |
The safest order is rules, code, backtest, paper trade, then small live use. Skipping a step is how traders discover errors with real money.
A good-looking backtest is often a badly built backtest. These are the errors I see most.
| Mistake | Why it misleads | Practical fix |
|---|---|---|
| Over-optimising parameters | Curve-fits past data and fails live | Keep few parameters; test on data you did not tune on |
| Ignoring costs | Brokerage, STT, charges and slippage erase thin edges | Include realistic costs in every test |
| Look-ahead or repainting | Signal uses data not available at that moment | Trigger only on closed candles; verify on replay |
| Too few trades | Results are luck, not statistics | Test across multiple years and market conditions |
| Ignoring drawdown | Profit looks fine but the losing streak is unbearable | Judge the strategy by worst drawdown, not only total return |
Connecting code to a broker API adds risk that charts never show. Orders can be rejected, partially filled, duplicated or sent during a data glitch.
Retail algo access in India sits under SEBI and exchange rules that are implemented through brokers. These requirements have been evolving, so confirm your broker's current policy on API access before building anything execution-related.
If you share your rules with a developer, treat them like intellectual property. Before sharing, agree in writing on three points:
Share only what is needed to build the tool, and test the finished version yourself before trusting it.
If you are still building the foundation, learn the method first. Structured Trading Direction courses cover CPR, Price Action and risk management, which is exactly the groundwork rules need before code. My book, Leading Indicator for Intraday Trading, is a companion for the same purpose.
Yes. You write the rules clearly and a developer codes them into Pine Script, a screener or an API tool. The quality of the result depends mostly on how precise your rules are.
Start with Pine Script. It lets you see signals and test rules on charts with no order risk. Move to broker APIs only after the rules are proven.
No. Automation only applies your rules consistently. A strategy without an edge will lose money faster when automated.
It can be protected through an NDA and a written agreement on code ownership. Share only what is required and confirm these terms before you start.
A backtest tests a strategy on past data to judge its performance. A screener scans the current market for stocks that match your conditions today.
Retail algo access is available through brokers under SEBI and exchange frameworks, and the rules have been changing. Check your broker's current requirements before automating order execution.
Automation rewards clarity, not complexity. Write objective rules, code an indicator first, backtest with real costs, paper trade, and go live small with hard risk controls. Keep your strategy confidential and remember: software enforces discipline, it does not create an edge.
Want a tested method before you write your rules? Explore the CPR Brahmastra webinar, read what students say on the testimonials page, or browse more lessons on the Trading Direction blog.
View the CPR Brahmastra Webinar