QR Codes for Business: Practical Uses That Work

The strongest uses replace a tedious manual step. A code on a restaurant table opens the menu without an app. A code on an invoice pre-fills a payment. A code on packaging links to setup instructions or a genuine-product check. A code on an event badge shares a vCard instantly. In each case the code saves the person typing a URL, searching, or copying details by hand — that saved effort is the whole point.

A useful test before printing: does the code lead somewhere that is worth the scan and is mobile-friendly when it opens? A code that lands on a slow, desktop-only page wastes the goodwill it just earned.

It is just as useful to know where codes do not earn their place. A code in a television advert that appears for four seconds is a code nobody scans. A code on a web page, sitting next to the link it duplicates, is noise. A code that opens a PDF laid out for A4 is a frustration on a phone. The filter is simple: is the person holding a phone, standing still, and unable to reach that destination more easily some other way?

Keep strong contrast — dark modules on a light background — and never invert to light-on-dark, which many scanners reject. Preserve the quiet zone: a clear margin at least four modules wide on every side. Size it for its viewing distance, remembering the rough ten-to-one rule, and if you add a logo, use error-correction level H and keep the logo under a quarter of the width. Brand colours are fine as long as the contrast stays high; test the final artwork on both an iPhone and an Android phone.

Print production adds rules of its own. Build the code from 100% black only, never a rich black mixed from four inks: a fraction of a millimetre of registration drift turns crisp module edges into coloured fringes. Place it as vector artwork — SVG, EPS or PDF — so the modules stay sharp at any size; if you must supply a raster file, export it at 300 dpi or better at final size and never resample it upward. Keep the code well inside the trim and clear of the bleed, and never let a fold, a perforation or a staple cross it.

Size is not a matter of taste either. The practical floor for something read at arm's length is about 2 × 2 cm, and even that assumes short content in a low version. A long URL in a version 12 code at that same physical size leaves modules under 0.3 mm — finer than most inkjet work and many offset runs hold cleanly. If the code has to stay small, shorten the content rather than shrinking the squares.

The usual reason businesses reach for a paid dynamic-code service is analytics. Most of that is available without one. Give each placement its own URL — /menu-terrace and /menu-bar, or /q/table-12 — or use the same URL with different UTM parameters, and the web analytics you already run will separate them for you. If you run no analytics at all, plain server logs answer the same question.

This keeps the data inside systems you already control and already describe in your privacy policy, instead of adding a third party that sees every scan. It also outlives the vendor: if you change analytics tools next year, the printed codes keep working, because they point at your own domain rather than someone else's shortener.

QR phishing — quishing — is a cheap and very real attack. A sticker costs nothing, and a code pasted over the legitimate one on a parking meter, a menu or a delivery notice is invisible to the customer until the page has already loaded. Parking operators and restaurants have both been hit repeatedly, and the business usually hears about it from the victim.

Two defences are entirely within your control. Print the destination in plain text beside the code, so a customer can compare what the phone shows with what you promised, and point codes at your own domain rather than a generic shortener, so that comparison actually means something. Then check the physical codes on a schedule: a staff member scanning the entrance code once a week finds a sticker long before a complaint does.

When you need many codes at once — one per product, table, or asset — generating them one at a time is tedious. QRForge's batch tab takes a list of URLs or values, one per line, and produces a code for each, which you can download together. It keeps the whole run consistent in size and style, and because everything is local, a catalogue of internal links never touches an outside server.

Decide on a naming scheme before you start. Batch output is only useful if you can tell afterwards which file belongs to which table or SKU, so feed the list in a fixed order and keep that source list beside the images. And for a run of a few hundred, printing and proofing a sample of ten at final size on the final material is worth more than inspecting every one of them on screen.