Static QR means no redirect service in the middle.

A static code contains the text or URL itself. Adynamic product puts its own short URL in the code and redirects the scan afterwards. Both scan identically on day one. The difference is entirely about what happens later.

What is actually inside each code

Scan a static code and the phone reads exactly what you encoded —https://example.com/check-in, a part number, a line of text. Nothing is contacted to resolve it. The code is a printed representation of that string and nothing else.

Scan a dynamic code and the phone reads something likehttps://vendor.example/x7Kd2. The vendor's server looks that up and answers with a redirect to your real destination. Your destination is not in the code at all; it is a row in someone else's database, and the code is a pointer to that row.

What dynamic buys you

• You can change the destination after printing. This is the real feature, and for a campaign that will be reprinted it is worth paying for.
• Scan counts. The redirect is a measurement point, so the vendor can tell you how many scans happened, roughly where, and when.
• Shorter payloads. A short vendor URL makes a less dense code than a long destination, which prints smaller and survives more wear.

What dynamic costs you, and when the bill arrives

The redirect is a dependency, and it fails in ways that have nothing to do with your code being correct:

• The subscription lapses. Many vendors stop resolving codes when the plan ends. The image is unchanged and the code is unreadable in the sense that matters.
• A scan quota is hit. Some free and entry tiers cap monthly scans; past the cap, scans fail for the rest of the period.
• The vendor closes or changes. Every code that vendor issued stops resolving at once, and nothing about your artwork can fix it.
• The failure is silent and remote. You do not find out. The person standing in front of the poster, the label, or the machine finds out, and they have no way to tell a dead redirect from a bad print.

None of this is an accusation about any particular vendor. It is the shape of the trade: you are renting the middle of your own code.

Choosing by how long the thing lasts

The useful question is not "which is better" but how long will the surface outlive the decision?

• Reprinted soon — use dynamic. A conference badge, a menu insert, a campaign flyer. You will reprint before the dependency matters, and editability is worth real money.
• Printed once and left there — use static. An equipment label, an asset tag, a plaque, a sticker on a meter, anything screwed to something. These outlive vendor relationships, and the code needs to work when nobody remembers who issued it.
• Handed to someone else — use static. If the file leaves your organisation, so does your ability to keep a redirect alive for it.

The trade-off static asks you to accept

You cannot change a printed static payload. If the destination moves, you reprint. That is a real cost and it is the whole argument for dynamic — so take it seriously rather than assuming static is simply safer.

You can reduce it. Encode a URL you control — a path on your own domain — and you keep the ability to change where it leads without the dependency, because the redirect is yours. Encode a third party's link directly and you have traded one dependency for another.

What this tool does and does not do

BulkQR Local generates static codes only, in the browser, one named SVG per row of your spreadsheet. There is no redirect, no account, no scan tracking, and nothing to keep paying for.

It does not inspect or endorse destinations: a generated code points wherever the CSV told it to, including somewhere harmful, so verify every payload before distribution. Whether a printed code scans depends on payload length, print quality, contrast, size, curvature and wear — test samples with the camera and app your audience will actually use. No generator can promise a code will read.

QR codes for equipment asset tags ·QR codes from a spreadsheet