The Brand Colour Challenge
Most brand guidelines were not written with QR code generation in mind. They specify a primary, secondary, and accent colour — none of which may be appropriate for QR module colouring without modification.
Understanding your brand palette's luminance values is the first step to creating a QR code that is both on-brand and scannable.
Mapping Palette to QR Roles
| Brand Colour Role | QR Code Role | Condition |
|---|---|---|
| Primary (if dark) | Module foreground | Must be darkest available colour |
| Secondary (if light) | Module background | Must provide 4:1+ contrast with foreground |
| Accent | Frame border / CTA text | Outside the QR matrix — unrestricted |
| White/off-white space | Module background | Usually the safest choice |
Worked Examples by Brand Archetype
Dark blue brand (e.g., financial services):
- Primary: #0D47A1 (dark blue) → safe as foreground against white (12.5:1 contrast)
- White #FFFFFF → background
- Accent gold #FFD600 → frame text only
Green brand (e.g., sustainability/food):
- Primary: #1B5E20 (dark green) → safe as foreground (11.6:1)
- Pale green #F1F8E9 → background
- White with green frame border → clean and on-brand
Red brand (e.g., food/retail):
- Primary red varies widely. #B71C1C (dark red) works (7.8:1). #F44336 (medium red) is marginal (4.5:1 against white) — use Level H error correction.
- Avoid bright red (#FF0000) — only 4.0:1 at the boundary.
Yellow/orange brand (e.g., energy/consumer):
- Yellow (#FFEB3B) as foreground against white = 1.1:1. Never usable as foreground.
- Solution: Use dark charcoal (#212121) or dark brand navy as module colour, with yellow as frame background or CTA highlight.
Creating a Style-Consistent QR Without Compromising Contrast
1. Start with your darkest brand colour as the foreground
2. Use white or your lightest background as the module background
3. Apply brand colour to the surrounding frame/label design — not the modules
4. Add your logo in the centre using Level H error correction
5. Scan test on three devices
This approach consistently produces QR codes that are recognisably on-brand while maintaining scan reliability.
When to Request a Brand Guideline Update
If your brand's entire palette is mid-tones or pastels, the QR code simply cannot use those colours for module foreground without failure. The correct action: document the constraint in your brand guidelines with a note that "QR code applications use [dark colour] foreground on white background per scan reliability requirements." This is a normal brand extension rule — like how logo colours change on dark backgrounds.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- Run unfamiliar destinations through the [QR safety checker](/qr-safety-checker) before you share a code widely.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
