How to Forecast QR Scan Volume for a Campaign

You can forecast QR scan volume with a simple model: estimate how many people will see the code, multiply by the share who will scan it, then adjust for timing and placement. The result is a range, not a single number. You then check that range against real scan data in the first week and tighten it. This guide walks through the method, a worked example and the monitoring that keeps the forecast honest.

TL;DR

• Forecast scans as reach × scan rate × timing curve, and always give a low, expected and high case.
• Your own past scan data beats any industry average. If you have none, run a small pilot before the big print run.
• Don’t read raw scan counts as a straight line. Use baselines, rolling medians and seasonal comparisons to separate real growth from normal variance.
• Set alerts for sudden drops or spikes so a broken redirect or damaged signage shows up in days, not months.
• Dynamic QR codes are what make forecasting possible, because only they record scans and let you fix a destination without reprinting.

Table of Contents

• Why forecasting scans is different from forecasting web traffic
• The basic formula
• A worked example
• Adjust for seasonality and context
• Forecast the full funnel, not just the scan
• Why consumer expectations belong in your forecast
• Monitor against the forecast from day one
• Our perspective: forecasts only work if the code survives
• What you need in place to forecast well
• Build your forecasting baseline with QRlytics
• Common forecasting mistakes
• FAQ
• Sources

Why forecasting scans is different from forecasting web traffic

A web page can be tested and tweaked daily. A printed QR code is fixed the moment it leaves the printer. That makes a forecast more valuable: it shapes how many flyers you order, how many staff you rota for an event, and whether the landing page can cope with the load.

Three things make QR scans harder to predict than clicks on a digital ad:

1. You rarely know true reach. A poster in a lobby is “seen” by an unknown share of the people who walk past.
2. Scanning needs effort. The person has to take out a phone, open the camera and aim it. Placement, lighting and size matter far more than on a screen.
3. Scans bunch up. Most scans arrive soon after a print drop, an event or a promotion, then fall away.

A good forecast respects all three. It uses ranges for reach, a scan rate you can defend, and a timing curve instead of an even daily average.

The basic formula

Start with this:

Expected scans = estimated reach × scan rate × number of exposure periods

Then split the result across time using a curve that matches your campaign type.

Step 1: Estimate reach per placement

Work placement by placement, not campaign by campaign. Reach means people who realistically see the code, not people who receive the material.

Write down the assumption next to each number. When the forecast misses, you want to know which assumption was wrong.

Step 2: Choose a scan rate

Scan rate is the share of people who see the code and scan it. It is the most uncertain input, and it varies a lot by context. A code on a table where someone sits for 40 minutes will outperform one on a moving bus.

Pick the source in this order:

1. Your own previous campaigns with a similar placement and offer.
2. A pilot: print a small batch, track it for one to two weeks, and measure scans against the audience that saw it.
3. Cautious assumptions if you have neither. Use a low rate for your low case and a higher one for your high case, and treat the spread as a measure of how little you know.

Be wary of single industry averages quoted without context. They mix very different placements, and a number built on restaurant menus tells you little about a billboard.

Step 3: Apply the offer and the clarity of the call to action

People scan when they expect something in return. In research from Uniqode, 56% of shoppers scan expecting a promotion or discount. That is a consumer survey, not a guarantee about your audience, but the direction is clear: a code with a stated reason to scan usually outperforms a bare code.

A practical way to use this: when two placements are otherwise similar, set the scan rate higher for the one with a clear offer printed beside the code, and lower for the one without. Then let your pilot confirm the gap.

Step 4: Shape the timing curve

Divide the total across days or weeks. Common shapes:

• Launch spike: most scans in the first days after a mailing or event, then a long tail.
• Steady drip: packaging and signage in permanent locations, with scans following sales or footfall.
• Peaks around dates: promotions tied to a weekend, holiday or sale period.

If you have a previous campaign’s daily scan export, use its shape directly. Express each day as a percentage of the total and apply those percentages to the new forecast.

A worked example

The numbers below are illustrative, to show the arithmetic. They are not benchmarks.

A coffee chain with 12 shops plans table tents offering a free pastry with a loyalty sign-up. Each shop serves about 1,500 customers a week, and each customer sits at a table about half the time.

• Reach per shop per week: 1,500 × 50% = 750 people at tables
• Reach across 12 shops over 4 weeks: 750 × 12 × 4 = 36,000

The team ran a one-week pilot in two shops. Scans were tracked from a dynamic code, and about 3% of table customers scanned.

The pilot also showed that scans per shop varied by a factor of two, mostly because of where the tents sat. So the team added a placement check before the full launch. That adjustment is worth more than any decimal point in the scan rate.

Note what the forecast now does. It sets a staffing and pastry budget for the high case, a reporting target for the expected case, and a trigger for investigation if scans fall under the low case.

Adjust for seasonality and context

A forecast built from a quiet fortnight will be wrong for a holiday week. Two habits help:

• Compare like with like. Compare a Saturday with previous Saturdays, not with the weekly average.
• Use rolling medians. The Mobilo Card guide on QR analytics advises against treating raw scan counts as a linear trend and suggests baselines, rolling medians or season-adjusted comparisons to tell real campaign growth from ordinary variance.

If your campaign lands in a heavy shopping period, remember that scanning intent is high but so is competition for attention. The same Uniqode research reports that nearly two-thirds of consumers are likely to scan a QR code during Black Friday and Cyber Monday, yet many brands failed to deliver on what users expect after the scan. A forecast of scans means little if the landing page disappoints, so forecast the next step too: how many scans become sign-ups, sales or visits.

Forecast the full funnel, not just the scan

Scans are an input. What you care about is what happens next. Extend the model one step:

Expected outcomes = expected scans × landing-page conversion rate

In the coffee example, if 40% of scanners complete the loyalty sign-up, the expected case gives about 432 new members from 1,080 scans. That is a number a finance team can approve against.

The Mobilo Card guide makes a related point: favour conversion-first measures, such as the percent of scans that create or enrich CRM records, over raw scan totals. Our own guide on tracking from scan to conversion covers the metrics worth setting up before you launch.

Why consumer expectations belong in your forecast

A scan rate is not a fixed property of a placement. It reflects what people believe will happen when they scan. If your earlier campaign sent scanners to a dead page or an expired offer, your next campaign’s scan rate will quietly suffer, and your forecast will overshoot.

Before you commit to a number, check three things:

• The destination loads quickly on a phone and matches what the print promised.
• Any offer is live for the full forecast window.
• The link will still work months from now, when the last printed copy is still in circulation.

Teams that publish their own growth data often show how much follow-through matters. One example is this case study of a QR business growing its monthly clicks, which shows what month-by-month tracking looks like in practice.

Monitor against the forecast from day one

The forecast is a hypothesis. The first week of data tells you whether it holds.

Set alerts, not just dashboards

Don’t rely on someone opening a dashboard. Mobilo Card recommends automated anomaly alerts for sudden drops or spikes, for example a 40% week-over-week change. Such alerts often reveal operational failures, such as broken redirect URLs or expired offers, before they become lost pipeline. The same guide mentions rules such as alerting when scan volume falls below 60% of a comparable day. Those are starting thresholds, so tune them to your own variance.

Diagnose by batch and location

When scans fall short, the cause is often physical: damaged signage, poor lighting or awkward placement. The same source suggests mapping scan performance against specific batches or locations to find the pattern. This is why giving each placement or print batch its own code pays off. One code on every poster tells you the total. A code per batch tells you which posters failed.

Re-forecast weekly in the first month

After seven days, compare actuals to your three cases:

1. Within the range: keep the plan and narrow the range.
2. Below the low case: check the destination, placement and offer clarity before blaming the audience.
3. Above the high case: check the landing page can cope, and consider extending the offer or print run.

Our perspective: forecasts only work if the code survives

We build QR codes for campaigns that outlive their launch week. A forecast assumes the code will keep working for the whole period you modelled. That assumption fails more often than people expect, because many free generators stop a code when a subscription lapses or a payment fails. The printed material is still on the shelf, but the scans go nowhere, and the data you would use to learn from the campaign disappears with them.

That is why we guarantee that codes created during an active subscription keep working permanently, whatever happens to billing later. It turns a forecast from a bet on your own luck into a plan you can revisit. You can change the destination URL on a dynamic code, schedule its lifecycle, and read scan data in real time without touching the print.

Our advice for forecasting is simple. Start with a pilot, keep the model small, record your assumptions, and let the first week of real scans correct you. A rough forecast that you update beats a precise one you never check.

— The

What you need in place to forecast well

You need a few capabilities before the first scan arrives:

Our guides on QR code tracking for marketers and on scaling QR code campaigns go into setup in more detail. If your forecast is lower than you need, our piece on ways to boost QR code scans lists changes to test.

Build your forecasting baseline with QRlytics

If you have no historical scan data, the quickest fix is to start collecting it. The Free plan costs $0 per year and needs no credit card, so you can create a QR code with analytics and run a pilot before committing to a print run. When you need unlimited codes, advanced analytics or API access, see the Pro plan on our pricing page. For campaigns where the destination might change, use a dynamic QR code.

Common forecasting mistakes

• Using total scans as the only metric. Repeat scans inflate the count. Track unique scanners where you can.
• One code for everything. You cannot diagnose a shortfall you cannot locate.
• Forecasting with one number. Always present low, expected and high cases.
• Ignoring the long tail. Printed material stays in circulation. Don’t close the books after the launch spike.
• Forgetting link maintenance. Broken links and expired offers are among the pain points consumers cite, so a forecast that assumes a perfect experience is optimistic. Our guide to preventing QR link rot explains how to avoid it.
• Treating the forecast as fixed. Update it weekly while the campaign is young.

FAQ

How accurate can a QR scan forecast be before launch?

Before any data exists, expect a wide range. A pilot of one to two weeks on a small batch narrows it considerably, because it replaces a guess with a measured scan rate for your audience and placement. After the first week of the full campaign, you can usually tighten the range further.

What if I have no historical scan data?

Run a pilot. Print a small batch with a dynamic code, record scans against the audience that saw it, and use that rate for your low, expected and high cases. Static codes cannot help here because they do not record scans.

How do I forecast scans for a code that will be in print for a year?

Split it into a launch spike and a steady tail. Use the shape from a past campaign if you have it, and compare like with like when you check results, for example the same weekday or season. Review monthly, and keep the destination editable so the code stays useful as offers change.

Which scan drop should trigger an investigation?

There is no universal threshold. Published guidance suggests alerts such as a 40% week-over-week change, or volume falling below 60% of a comparable day. Start there, then tune the thresholds to how much your scans normally vary.

Sources

• How To Set Up QR Code Analytics and Measure Campaign Success, Mobilo Card
• 74% of Consumers Likely to Scan a QR Code During Black Friday, Cyber Monday, Uniqode Report Finds, PR Newswire

Recommended

• Marketers: Scale QR Code Campaigns, Track 4 Metrics, Avoid Reprints
• Track Scan to Conversion: QR Analytics & Campaign Sheet for Marketers
• Ways to boost QR code scans for marketers
• QR Scan Times by Time Zone: 3 Timestamps That Shape Campaign Reports