Monthly data note — October 2026
Black Friday alert: study identifies obstacles in QR Code access attempts
QR Plus examines 377,000 attempts recorded in October and highlights why businesses should test materials, monitor usage limits and maintain the conditions needed to keep campaigns running.
Preparing a campaign includes checking the path to its content
Businesses preparing window displays, packaging, labels and advertisements for Black Friday need to check the complete path from the QR Code to the advertised content. A QR Plus Radar study found codes not found or usage limits reached in 13.6% of access attempts recorded on the platform in October 2026.
Between October 1 and 31, 377,049 attempts were observed, of which 51,309 received one of these two results. The finding highlights checks that should accompany the production and distribution of materials: verify the code, test the destination and check whether the contracted service can handle the volume expected during the campaign.
The analysis covers different kinds of content accessed on the platform. The records do not identify which attempts related to offers or Black Friday. The study provides an operational reference for businesses using QR Codes in November campaigns.
Two different obstacles to accessing content
| Recorded result | Attempts | Share |
|---|---|---|
| Code not found | 30,787 | 8.17% |
| Usage limit reached | 20,522 | 5.44% |
| Combined total | 51,309 | 13.61% |
A “code not found” result means that the platform did not locate a code available to serve that request. The record alone does not establish whether an incorrect address was used, the code was taken out of circulation or another condition made it unavailable.
A “limit reached” result means that a usage rule was triggered. Depending on the service conditions, this may prevent access at that moment or require an additional step before the content is displayed.
These situations call for different checks by the business. Verifying the address and the status of the code helps identify content availability problems. Monitoring allowances, settings and contractual conditions helps anticipate usage restrictions.
Testing should cover the finished material and the destination page
Before producing a print run or distributing a piece, businesses should test a sample at the size and with the finish intended for the campaign. Contrast, clear space around the code, reflections, folds and reading distance can affect camera recognition.
Checking must continue after the scan. Verify that the code opens the correct address, that the content remains available and that the page presents the offer and its terms clearly on a phone.
This distinction matters: a failure to recognize the image may prevent any request from reaching the platform. Therefore, the observed 13.6% does not measure printing problems or the proportion of physical materials that fail. Testing the material is an additional precaution against obstacles that occur before those captured in the study.
After approving the artwork, repeat the check on an actual finished piece. This helps detect both scanning difficulties and the printing of a code different from the approved one.
Settings, limits and billing need to keep pace with the campaign
A campaign can increase access volume without the business reviewing the conditions of the service it uses. Preparation should therefore include checking contracted limits, usage to date and options for increasing capacity during November.
Businesses should also verify code activation, subscription validity and billing status when these conditions determine service continuity.
Keeping payments up to date does not replace capacity planning: an allowance can be exhausted even when the subscription is in good standing. Likewise, the study cannot attribute every limit-reached result to nonpayment or a particular setting.
Businesses should know in advance what happens when a restriction is reached and which procedures can restore or expand access.
Technical reliability and access to content are different measures
Across the activities monitored by QR Plus Radar in October, 127 technical failures were recorded among 737,946 events. This represents 0.017% of events, or 99.98% without a recorded technical failure.
This indicator uses the operational classification of failures, such as internal errors and problems in services on which the platform depends. Codes not found and usage limits are counted separately: a system can respond technically to a request while reporting that content is unavailable under the conditions of that access attempt.
The percentage is not a measurement of continuous availability and does not establish that all content was accessed. When assessing a provider, businesses should also consider availability monitoring, clear rules, support and service capacity during the campaign.
Checks before putting materials into circulation
- Test the QR Code on a finished piece with the final size and finish.
- Check the opened address and content availability on different phones.
- Verify that the code is active and that the offer information is up to date.
- Review allowances, usage, validity and billing for the contracted service.
- Understand support procedures and options for increasing capacity.
- Repeat the checks during the campaign, especially after content changes or increases in access volume.
Methodology and scope
The study uses the validated October 2026 monthly closing of QR Plus Radar, covering all 31 days. The monthly archive was generated on November 3, 2026.
The dataset comprises code resolution attempts in the instrumented platform services, including repeat attempts and automated traffic. It does not represent distinct people or QR Codes, or the entire Brazilian market.
The “code not found” and “limit reached” categories totalled 51,309 occurrences among 377,049 attempts, equivalent to 13.61% of the total. The numerical highlight rounds this result to one decimal place.
Among attempts technically classified as likely human, 46,333 of 360,516 did not have a successful resolution recorded, a share of 12.85%. This subset is calculated by subtracting successful resolutions classified as likely human from all attempts in that same classification.
Results describe each recorded attempt. They cannot quantify abandonment, lost sales or permanent denial of access. Camera recognition failures that did not generate a request to the platform are outside this dataset.