VWAP Pullback Scanner
Stocks that ran, came back to VWAP and held above it.
What the setup is
VWAP is the volume-weighted average price of the session so far: the average price paid for every share traded today. Many intraday traders treat it as the line between a stock that is being bought and one that is being sold.
A VWAP pullback is a three-step sequence. The stock makes a move up, it comes back down to VWAP, and it holds above it. The pullback is the entry traders look for, because it offers a price near the average with the earlier strength still in place.
The difficulty for a scanner is the order. "Above VWAP" and "touched VWAP today" are both simple facts, and a stock that sat on VWAP all morning and then ran passes both. A pullback scan has to know that the high came first and the touch came after.
The scan as a sentence
In Fastur you can describe the scan in plain English. For this setup the sentence looks like this:
made a new high in the last 30 minutes, then pulled back to vwap in the last 10 minutes and is holding above it
The assistant turns that into code you can read. The core of it is below. It is a fragment that shows the idea, not a complete script.
| 1 | logicblock HighCameFirst = m1.high[11:30].max > m1.high[1:10].max |
| 2 | logicblock VwapPullback = HighCameFirst and m1.low[1:10].min < d1.vwap * 1.002 and trade.last > d1.vwap |
What each part checks
- m1.high[11:30].max > m1.high[1:10].max
- The highest price of the last 30 minutes was set in the earlier 20 minutes, not in the most recent 10. The high came first.
- m1.low[1:10].min < d1.vwap * 1.002
- Within the last 10 minutes the low came down to within 0.2% of VWAP. That is the pullback.
- trade.last > d1.vwap
- The last trade is above VWAP. The stock touched the line and did not lose it.
The choices that change the results
- How close counts as a touch
- The 1.002 allows a low up to 0.2% above VWAP. A tighter number demands an exact tag. A looser one accepts shallow pullbacks that never quite reach the line.
- How long the windows are
- Ten and twenty one-minute bars suit fast pullbacks. For slower ones, use five-minute bars with the same shape.
- What happens after the touch
- Holding above VWAP is the minimum. Some traders also want higher lows after the touch, which is one more condition comparing recent lows with earlier ones.
- What the earlier move was
- This fragment only requires a recent high. You can ask for more, such as a break of the opening range or of the premarket high, before the pullback counts.
Common mistakes
- Scanning for "near VWAP"
- A list of stocks close to VWAP mixes pullbacks, breakdowns and stocks that have gone nowhere all day. Distance from VWAP says nothing about how the stock got there.
- Ignoring the first minutes
- Just after the open VWAP is built from very few trades and moves quickly. A pullback to it at 09:33 means little.
- No time limit on the sequence
- A high at 09:45 and a VWAP touch at 14:00 happened in the right order and are not a pullback. The windows are what tie the two events together.
Questions
- What is a VWAP pullback?
- It is a move back down to the volume-weighted average price after a stock has run higher, followed by the stock holding above that level. Traders use it as an entry near the session average price.
- How does a scanner detect a pullback to VWAP?
- It checks three things: that a recent high was made in an earlier stretch of bars, that the low of a more recent stretch came down to VWAP, and that the current price is above VWAP. Using two separate windows of bars is what expresses the order.
- Does VWAP reset each day?
- Yes. Session VWAP starts again at the open each day, so a pullback scan only looks at today's price and volume.
Read next
- Why "X happened before Y" matters in a stock scanner
- Why snapshot stock scanners miss the best trades
- Opening Range Breakout Scanner
- Relative Volume (RVOL) Scanner
- Gap and Go Scanner
- Premarket High Breakout Scanner
- High of Day (HOD) Scanner
- VWAP Reclaim Scanner
- The fastur/1 scripting docs
- How plain English scans work
Write a scan, then run it live
Create the logic once, run it live, and let scanner alerts tell you what changed.