How to create a QR code: menus, payments, and cards

If a hair salon's price list is still taped to the wall, corners curling, old prices crossed out and rewritten in pen, a customer ends up asking the front desk what something actually costs. That same information could reach anyone who lifts a phone to a square pattern in a couple of seconds. The mechanics of how to create a QR code are simpler than most people assume; the harder part is using the right code, in the right place, for the right purpose.

This piece covers how a QR code is actually generated, why static versus dynamic matters for a business, the use cases that pay off most — menus, payments, digital business cards, review collection, wifi, and packaging that opens a chat — and how to track whether it's working.

How a QR code actually gets created

A QR (quick response) code is a type of barcode that packs a link, a block of text, or wifi credentials into a pattern of black and white squares. Running a generator isn't complicated: enter the destination content — a URL, a message, a vCard file — and the tool converts it into a scannable pattern. Most browser-based generators are free, need no installation, and take seconds.

In practice, the process comes down to a few steps:

• Decide the content: figure out whether the code should open a web page, a menu, a wifi network, or a contact file before you generate anything.
• Pick a tool: choose a generator that matches what you need, particularly whether it lets you edit the destination later — which ties directly into the next section.
• Choose static or dynamic: this decision determines whether you can ever change the destination after printing.
• Test before you print: scan the code at its actual print size, on at least two different phones, to confirm it opens cleanly.

1Decide content2Pick a tool3Generate the code4Test and print

Static or dynamic? This is the difference that matters for a business

A static QR code has its destination baked directly into the pattern. Once generated, that destination can't change — a new menu price means a new code and new printed copies. In exchange, static codes are usually free and work indefinitely, since they don't depend on any third-party service staying online.

A dynamic QR code, by contrast, points to a short redirect link; the printed pattern stays the same, but you can change what's behind that link whenever you want. When a restaurant updates a seasonal menu, nobody reprints the table signage — only the destination behind the code changes. Most dynamic QR services charge a subscription for that flexibility and throw in basic stats, like scan counts.

To be honest, a dynamic code is overkill for a one-off event flyer; static does the job just fine. But for something that changes regularly, like a storefront window or a table-top menu, a dynamic code saves you from reprinting hundreds of cards every time a price shifts. The real risk: if the service shuts down, or the subscription lapses, every printed code stops working at once — so picking a provider likely to stick around isn't a minor detail.

From menus to payments: where QR codes earn their keep

Menu codes: table-side ordering and instant updates

A bakery that swaps a laminated menu for a small QR code on each table only has to update a web page when a price changes — no reprinting involved. To be honest, this isn't ideal for every customer; some older diners simply don't want to scan a code, so keeping a printed backup at the counter is a sensible hedge.

Payment codes: fast, contactless collection

QR codes generated by banks and payment apps open a fixed amount, or a blank payment screen, directly inside a customer's banking app — practical for a market stall or a small business that doesn't want to carry a card terminal. One caution worth naming: swapping a fake sticker over a legitimate payment QR code at checkout is a known scam, so it's worth glancing at the code now and then.

QRcodeMenuPaymentBusiness cardWifi

Digital business cards: one square code instead of paper

A QR code generated in vCard format saves a name, phone number, and email directly to a contact list the moment it's scanned — or it can point to a small page listing social links and current listings. A solo agent at a two-person real-estate office who hands over this code instead of a paper card lets a prospect browse listings and recent sales on the agency's Instagram before they've even walked back to their desk.

To be honest, paper cards haven't become pointless: at a trade show with weak signal, or with someone whose phone isn't in hand, a classic card still works faster. Think of a QR business card as a complement to paper, not a replacement for it.

Collecting reviews and loyalty: getting the customer one tap closer

A QR code by the register that opens a Google review page directly saves a customer the trouble of searching for the business first — the less friction there is, the more likely someone actually leaves a review. The same logic applies to a code on a table card that collects an email address for a small discount; those addresses can later feed into email marketing campaigns.

One thing worth watching: cramming a menu, a review link, and a newsletter signup into the same code leaves a customer unsure what they're even scanning for. A code works best carrying one clear action; separate codes for separate goals look a little busier but confuse far less.

Wifi sharing and packaging that opens a chat: small but effective uses

Embedding wifi credentials in a QR code lets a guest join a network without typing a password by hand — in a café, boutique hotel, or coworking space, that convenience matters to anyone who's typed a sixteen-character password on a phone keyboard.

Another use case: a code on a shipping box or insert card that opens a WhatsApp chat the moment it's scanned, with a pre-filled message like "hi, about order X." Setting this up properly usually needs a WhatsApp Business API connection, and someone on the team actually watching for replies — otherwise the invitation on the box turns into a chat nobody answers for hours, undoing the trust the first purchase just built.

How do you actually track a QR code?

A static code has no built-in analytics; there's no direct way to see how many people scanned it, though counting redemptions of an attached offer gives an indirect read. Dynamic codes work differently: the code routes through a redirect service, which typically logs scan counts, timestamps, and a rough device type — much like a shortened link.

Adding campaign parameters to the destination link makes it possible to tell which table, or which storefront, a scan actually came from — useful when the same menu exists as several printed copies in different spots. Once a scan turns into an actual conversation, logging where it came from inside a system that unifies every channel shows, months later, which touchpoint genuinely pulled its weight.

Design and print mistakes that make a code unreadable

Even a well-generated code becomes useless if it's printed badly. The most common problems:

• Printing it too small: a code that scans fine on a table card can become unreadable once squeezed into the corner of a catalog page.
• Low contrast: a code in light gray on white, or in a brand's pale palette, might look elegant but scans noticeably worse.
• Cutting the quiet zone: trimming the blank margin around a code for a tighter layout stops cameras from reading its edges correctly.
• Glossy or laminated surfaces: reflections under strong lighting make it harder for a camera to get a clean read.

A QR code nobody can scan is just black-and-white wallpaper.

Before printing hundreds of table cards or shipping labels, printing a proof at actual size and testing it on a couple of phones takes a few minutes — and it's cheaper than reprinting the whole batch.

Frequently asked questions

Creating a QR code takes minutes; the real work is deciding which code lives where, for what purpose, and who answers after the scan. From a menu to a shipping box, a business card to a payment counter, every square code can be the start of a conversation — provided someone is there to answer it. Seeing every touchpoint on one screen, the way Rocketly does, means never having to guess which code is actually pulling its weight.