WhatsApp QR Kodlarını Çevrimdışı Pazarlama Stratejilerinize Dahil Etme

WhatsApp QR codes turn a printed surface into a conversation. Someone points a phone camera at a code on your menu, your shelf talker or your trade-show panel, and a chat with your business opens with a message already typed. No app switching, no typing a phone number, no landing page in between. That is why WhatsApp QR codes have become the most practical bridge between offline marketing and a channel where more than three billion people already have an account — a figure Meta itself reported for WhatsApp's monthly active users in 2025.

The idea is easy; the execution is where campaigns quietly fail. A code printed 12 mm wide on a business card, reversed out of a dark brand colour, cropped tight against a fold and exported as a low-resolution PNG will not scan — and you find that out after 20,000 pieces have come off the press. Print is unforgiving in a way a web banner never is: you cannot patch it.

This guide covers what actually decides whether an offline campaign works: minimum print size and the distance rule behind it, the four-module quiet zone the standard requires, contrast thresholds, how error correction changes the physical density of your code, and a device-testing routine to run before you commit to a print run. It also corrects a claim that circulates widely and is not true — Meta does not give you scan analytics for WhatsApp QR codes.

What a WhatsApp QR code actually encodes

A WhatsApp QR code is not a special barcode format. It is an ordinary QR symbol — the same ISO/IEC 18004 symbology used on parcels and boarding passes — that happens to contain a WhatsApp URL. The camera decodes the URL, the operating system recognises the domain, and WhatsApp opens on the chat. That distinction matters, because every physical rule that governs a shipping label governs your marketing piece too.

The short link behind the code

When you generate a code through Meta's tooling, what gets encoded is a short link in the form https://wa.me/message/ followed by a random alphanumeric identifier. That identifier masks your phone number and keeps message syntax out of the URL, so the printed link is short, stable and shareable as text as well as as a code.

You can also build a plain click-to-chat URL yourself in the form wa.me/ followed by your number in full international format — country code included, with no plus sign, spaces, brackets or dashes. If you attach a prefilled message to that style of link, the message text has to be percent-encoded, which is fiddly to do by hand; running the string through a URL encoder first avoids the broken links that come from stray spaces, ampersands and emoji. If a colleague hands you an unfamiliar short link and you want to see where it resolves before it goes to print, a URL unshortener will expand it.

Prefilled messages and platform limits

The prefilled message is the most underrated part of the setup. It is the first line the customer sends you, and Meta caps it at 140 characters. Use it as a routing label rather than a greeting: “I’m at the Camden store and want help with sizing” tells your team where the scan came from; “Hi” tells them nothing.

Two platform limits matter before you plan a large campaign. A single business phone number can hold a maximum of 2,000 QR codes and short links in total — generous, but not unlimited if you print a unique code per store or per SKU. And codes export as either SVG or PNG, with Meta explicitly recommending SVG as the best quality for print materials.

How to create a WhatsApp QR code for a print run

Work in this order. The sequence matters, because the destination has to be settled before anything is exported, and the export format has to be settled before anything reaches a designer.

1. Decide the destination and the prefilled message. One code per placement, with a prefilled message that identifies that placement in plain language and stays inside 140 characters.
2. Generate the code. In the WhatsApp Business app, the QR code and short link live in the business tools section; on the WhatsApp Business Platform, codes are created through the message QRDL endpoint of the Business Management API. Either way you get the same wa.me short link.
3. Export as SVG. Vector artwork scales to any size without softening the module edges. If your printer insists on raster, supply a PNG rendered at the final physical size at 600 dpi or higher, never an upscaled screen grab.
4. Set the physical size from the scanning distance, not from the space left over in the layout. The next section gives the arithmetic.
5. Reserve the quiet zone in the layout file as an object, so that a later crop, bleed adjustment or text reflow cannot eat into it.
6. Check contrast against the substrate you are actually printing on, not against white on your monitor.
7. Test the proof on real handsets before signing off, using the routine further down this page.

If you need a code that points somewhere other than WhatsApp — a booking page, a PDF menu, a wifi credential — a general QR code generator covers those destinations, and the same print rules below apply unchanged.

Print size: work backwards from scanning distance

The working rule across the barcode industry is a 10:1 ratio between scanning distance and code width. A code that someone reads from one metre away needs to be roughly 100 mm wide. This is a floor, not a target: it assumes a decent camera, reasonable light and a steady hand, and every one of those assumptions fails somewhere in the real world.

The table below applies that ratio to common offline placements. The module size column shows how large each individual black square becomes for a version 4 symbol (33 × 33 modules), which is the size a typical WhatsApp short link produces at a mid error-correction setting. The final column is the total footprint you must reserve in the layout, code plus the quiet zone on both sides.

Placement	Typical scan distance	Minimum code width	Module size (33×33)	Quiet zone each side	Total block to reserve
Business card, product label	0.2 m	20 mm (0.79 in)	0.61 mm	2.4 mm	25 mm
Table tent, dine-in menu	0.3 m	30 mm (1.18 in)	0.91 mm	3.6 mm	37 mm
Flyer, brochure, packaging	0.4 m	40 mm (1.57 in)	1.21 mm	4.8 mm	50 mm
Shelf talker, counter sign	0.6 m	60 mm (2.36 in)	1.82 mm	7.3 mm	75 mm
A2 poster, window decal	1.0 m	100 mm (3.94 in)	3.03 mm	12.1 mm	124 mm
Exhibition stand panel	2.0 m	200 mm (7.87 in)	6.06 mm	24.2 mm	248 mm
Hall banner, vehicle livery	5.0 m	500 mm (19.7 in)	15.15 mm	60.6 mm	621 mm

Read the last row again before putting a QR code on a motorway billboard. At a realistic 20 metres the ratio demands a two-metre code, and the audience is moving at speed with no safe way to hold up a phone. Billboards are the classic place where WhatsApp QR codes get specified and never scanned. Static, close-range surfaces — menus, packaging, receipts, shelf edges, stand panels — are where they earn their keep.

Two adjustments. Add 20–30 per cent to the minimum width on any surface that curves, creases or flexes, and size up again if the code sits behind glass, on reflective laminate or under a spotlight, because glare removes usable contrast from part of the symbol. When you must resize supplied artwork rather than re-export it, set exact pixel dimensions in an image resizer instead of dragging a handle in a layout file.

The quiet zone: four modules, and no exceptions

The quiet zone is the blank margin around the symbol. It is not decorative white space that a designer can trade away — it is part of the symbol, and decoders use it to find the code's boundary. The standard specifies a minimum clear margin of four modules on all four sides of a standard QR code, and that requirement holds at every version, from the smallest 21 × 21 grid to the largest 177 × 177. Micro QR codes, which you are unlikely to use for marketing, need two.

Because the quiet zone is measured in modules rather than millimetres, its physical size changes with the code. Work it out by dividing the printed width by the number of modules per side, then multiplying by four. A 33-module code printed 40 mm wide has 1.21 mm modules and therefore needs a 4.8 mm clear margin — which is why the table above lists a total block noticeably larger than the code itself.

The quiet zone must match the tone of the light modules and contrast clearly with the dark ones, which rules out the three most common design mistakes: running a coloured panel edge through the margin, letting copy sit inside it, and placing the code so close to a trim line, fold or die-cut that finishing destroys it. On textiles, corrugated board or anything with ink bleed, exceed the four-module minimum rather than meeting it exactly.

Contrast: dark on light, and measurably so

QR decoders read reflectance differences, so the requirement is not “on brand”, it is “dark modules on a light background, with enough separation between them”. The print-quality standard for two-dimensional symbols, ISO/IEC 15415, grades this as symbol contrast — the reflectance difference between the brightest and darkest module — on this scale:

Grade	Symbol contrast	What it means in a print run
A	70% or higher	Target for any code that must scan first time, every time
B	55% to under 70%	Acceptable on flat, well-lit, close-range surfaces
C	40% to under 55%	Marginal; expect failures in dim venues and on older handsets
D	20% to under 40%	Unreliable; do not sign off a print run at this level
F	Below 20%	Effectively unscannable

Three rules follow. Keep the dark modules genuinely dark — a mid-tone brand colour that looks confident on screen often lands in grade C on uncoated stock. Keep the background genuinely light, preferring paper white to a tinted panel. And avoid inverted codes unless you have tested them across a wide spread of devices; many decoders handle inversion and some still do not. You can filter out obviously bad colour pairings early by running the two hex values through a colour contrast checker, though it measures on-screen accessibility rather than print reflectance, so it is no substitute for a printed proof.

Error correction: higher is not automatically better

QR codes carry redundant data so that a symbol can still be decoded when part of it is damaged, dirty or covered. The standard defines four levels, and the percentage refers to the share of codewords that can be restored:

Level	Recoverable	Symbol version for a wa.me short link	Modules per side	Best used for
L (Low)	7%	Version 3	29	Clean, flat, protected surfaces where you want the largest possible modules
M (Medium)	15%	Version 3	29	The sensible default for most print work
Q (Quartile)	25%	Version 4	33	Packaging, labels, anything that scuffs or curves
H (High)	30%	Version 5	37	Codes with a centre logo, or harsh environments

The symbol versions above were generated from a 36-character wa.me short link, which is representative of what Meta's tooling produces. Notice what happens across the table: moving from level M to level H takes the same short link from a 29-module grid to a 37-module grid. At a fixed printed width, that shrinks every module by roughly a fifth. On a 30 mm table tent, modules go from about 1.03 mm to about 0.81 mm — small enough that ink spread on uncoated card starts to close the gaps between them.

The trade is real: higher error correction buys tolerance to damage and pays for it in module size. Level M is the right default for clean print. Step up to Q or H only when a logo covers part of the code, the surface will get scuffed, or you have size to spare — and never step up to H while keeping the code small to make a layout work, which gives you the worst of both.

Test on real devices before the print run

Every failure described above is cheap to catch on a proof and expensive to catch on a pallet. Build testing into the sign-off, not into the post-mortem.

1. Print at final size on the final stock. A laser proof on office paper tells you almost nothing about how the code will behave on uncoated kraft, matte laminate or vinyl.
2. Scan with the native camera app on at least one recent iPhone, one recent Android handset and one older device that is three or four years old. The native camera is what your customers will actually use; a dedicated scanner app is more forgiving than the real-world case.
3. Reproduce the real lighting. Test in the actual restaurant at service light levels, in the actual aisle under the actual fixtures, on the stand under exhibition spots. Dim venues and hard glare are where marginal codes fail.
4. Test at the real distance and angle. Scan from where a customer would stand, not from 15 cm away, and try it at 30–45 degrees off perpendicular.
5. Verify the destination, not just the decode. Confirm that WhatsApp actually opens, that the prefilled message is correct and complete, and that the message is not truncated by the 140-character limit.
6. Check the fallback path. Print the wa.me link in readable type near the code so that anyone whose camera fails, or who is on a device without WhatsApp, can still reach you.
7. Decode a scan of the printed piece as a final check. Photograph the proof, then run the image through a QR code reader to confirm the exact string that comes out matches the string you intended to encode.

Where WhatsApp QR codes earn their place offline

Print collateral and business cards

Brochures, flyers and business cards are close-range surfaces, which makes them ideal. A code on a card lets a prospect open a chat while you are still standing in front of them, and the prefilled message can carry the context of the meeting. Keep it to 20 mm minimum, and keep it off the fold.

In-store signage and shelf edges

Shelf talkers and counter signs let a shopper ask about sizing, stock or ingredients without hunting for a member of staff. These are read from roughly half a metre, so 60 mm is the working minimum. Give each department or aisle its own code and prefilled message, so the incoming chat tells your team where the customer is standing.

Events and exhibitions

Stand panels, lanyard cards and pop-up banners all work, provided you size for the distance people actually stand at — a banner read from across an aisle needs 200 mm or more, with a quiet zone that survives the banner’s own graphics. The advantage over a paper lead form is that the conversation continues after the hall closes.

Packaging, labels and receipts

Packaging is the strongest use case and the hardest surface. Curved bottles, flexible pouches and small labels all argue for level Q error correction, a generous quiet zone and a size above the theoretical minimum. Thermal receipts and delivery notes deserve the same caution, because receipt printers produce low contrast at low resolution; test on the actual printer and size up. In exchange you get a direct route for warranty registration, reordering, usage support and feedback, printed on something the customer keeps.

Measuring the campaign when scans are not reported

Here is the correction that matters most, because the opposite is repeated constantly in marketing advice: Meta does not provide analytics for WhatsApp QR codes and short links. Its own documentation states that analytics are not available for these, because the data logged is deliberately limited to protect user privacy. Any plan that depends on a built-in scan count, engagement rate or conversion figure from WhatsApp rests on something that does not exist. You can still measure the campaign properly — you just have to design the measurement in rather than wait for it to arrive.

1. Give every placement its own code and its own prefilled message. The inbound message text becomes your attribution field — store window, aisle 4, Hall 2 stand, packaging insert.
2. Count first-contact conversations by that message text in your inbox or CRM, segmented by week. That is your scan-to-conversation metric, and it is a better number than a raw scan count because it excludes accidental scans.
3. Tag any web destinations with campaign parameters. Where a chat hands off to a booking page or checkout, build the link with a UTM builder so the offline placement is still identifiable in your analytics after the handover.
4. Run holdout regions or staggered launches. Print the code in half your stores first. The difference in inbound conversation volume between the two groups is a cleaner read on incremental effect than any platform dashboard would give you.
5. Record the operational numbers you do control — response time, resolution rate, conversations that reach a sale — and hold them steady as volume grows. A campaign that triples inbound chats and doubles response time has not succeeded.

Common failure modes and how to fix them

People do not know what the code is for

A bare code with no explanation converts poorly. State the benefit in a short line directly above or below it, readable from the same distance as the code: “Scan to ask us about stock”, “Scan for your warranty”. Add a visual cue such as an arrow or a WhatsApp glyph, placed outside the quiet zone, and give people a concrete reason to scan — a faster answer, a discount, or something they cannot get otherwise.

Device and lighting variation

Camera quality, operating system version and lighting vary across your audience in ways you cannot control. The mitigations are the ones already listed: test across old and new handsets, keep symbol contrast in grade A or B, respect the quiet zone, and always print the wa.me link as readable text so there is a manual path to the same conversation.

Privacy and consent

A scan starts a conversation, and that conversation is personal data. Say before the scan what you will do with it, collect explicit consent before adding anyone to a marketing list, keep transactional chat separate from marketing opt-in, and store what you collect under the same retention and access controls as the rest of your customer data. Treat regional rules as binding, not optional.

Nobody is on the other end

The most common failure is not technical. A code that opens a chat nobody answers within the hour is worse than no code, because it turns an interested customer into a disappointed one. Staff the inbox, set expectations with a greeting that states real hours, and route by the prefilled message so the right person picks it up.

Frequently asked questions

What is the smallest a WhatsApp QR code can be printed?

The practical floor for close-range print is about 20 mm (0.8 in) square, on top of which you must add a four-module quiet zone on every side. Below that, module sizes fall under half a millimetre and ink spread starts to merge them. Size everything else from the 10:1 rule: divide the expected scanning distance by ten to get the minimum code width.

How big does the white border around a QR code need to be?

Four modules on all four sides for a standard QR code, per ISO/IEC 18004. Because it is measured in modules, divide the printed width by the modules per side and multiply by four to get the millimetres. A 33-module code printed 40 mm wide needs 4.8 mm of clear margin all round, and that margin has to match the light modules in tone.

Which error correction level should I choose for print?

Level M (15% recoverable) is the right default for clean, flat print. Move to Q (25%) for packaging, labels and curved or scuffable surfaces, and to H (30%) only when a logo covers part of the symbol or the environment is harsh. Remember that each step up adds modules, so at a fixed width every module gets smaller — going to H without also going larger makes the code harder to read, not easier.

Can I put my logo in the middle of a WhatsApp QR code?

Yes, within limits. The logo has to sit in the centre, must not touch the three corner finder patterns or the quiet zone, and the covered area must stay comfortably inside what the error correction level can restore. Use level H, keep the logo below roughly a fifth of the symbol area, and test the result on real handsets rather than assuming the maths covers you.

Does WhatsApp tell me how many people scanned my QR code?

No. Meta's documentation states that analytics are not available for QR codes and short links, because logging is deliberately limited for user privacy. Measure instead by giving each placement a unique prefilled message and counting first-contact conversations by that text, and by tagging any onward web links with campaign parameters.

Can I change where a printed WhatsApp QR code points?

You can edit or delete the prefilled message attached to a wa.me short link at any time, so the opening message on a printed code is changeable after the fact. The destination number behind that short link is not something you can repoint, so if you expect the routing to change, encode a link you control and redirect it, rather than a link you do not.

Getting it right the first time

WhatsApp QR codes work offline because they remove every step between seeing your brand on a physical surface and talking to a human on a channel the customer already uses daily. That advantage is real, and it survives contact with reality only if the printed symbol scans on the first attempt, in the actual lighting, at the actual distance, on the phone the customer happens to own.

Get the physical specification right — size from distance at 10:1, four modules of quiet zone, symbol contrast in grade A or B, level M error correction unless the surface argues otherwise, vector artwork exported at final size — and test on real devices before anything goes to press. Then design the measurement in yourself, because the platform will not hand it to you. Those two disciplines are the difference between a code that generates conversations and a code that generates a reprint.