QR code stickers for cars: what to link and how to make them scan

People look at a modified car and want the details, but a parking lot conversation is a bad place to deliver them. Owners forget parts. Strangers forget the handle. A phone photo of the car does not carry the spec list with it.

A QR sticker hands the details over instead of the pitch. Someone points a camera at it, a page opens, and they can read the mods at their own speed. You get to keep talking about the car instead of reciting part numbers.

This is the one decision that matters most. The common options look like this:

• A social profile. Easy, and people can follow you. But it shows posts, not specs, and the one photo that explains the build is buried.
• A shared document or spreadsheet. It holds the full list, but it is clumsy on a phone, and you have to make the file public to share it.
• A build page. Mods, power numbers, photos, socials and links to the parts, built to be read on a phone. This is what BuildTags is for, but the principle works with any page you control.

Whatever you pick, picture a stranger with ten seconds. They want the car's name, the headline numbers, the mod list and somewhere to follow you. Put those first.

A QR code is just the address written in a pattern. If the pattern contains your Instagram URL, the sticker is only ever good for that URL. Rename the account, move the document, change where the page lives, and the sticker on your window now points nowhere. You cannot edit a printed code.

The fix is a code that points to a short, permanent address that you can aim at a different page later. Some QR generators call these dynamic codes. If you use one, ask what happens to the code if you stop paying or the service closes, because the sticker depends on it.

A BuildTag works this way by design. The QR holds a short permanent code, not a page name or your username. You can rename the build, change your username or rebuild the whole car, and the same sticker keeps working. If you get a replacement printed, it can carry the same code.

Most scanning problems come from a few repeat mistakes:

1. Keep strong contrast. Dark code on a light background is the safest. Pale colours on pale colours, or a code over a busy photo, fail on some phones.
2. Leave the blank margin. Every code needs an empty border around it, called the quiet zone. Do not let artwork, stripes or text touch the code.
3. Do not squash or stretch it. Keep it square.
4. Size it for the distance. A bigger code reads from farther away. A common rule of thumb is that a phone can read a code from about ten times its width. A code you want to scan from beside a car should be bigger than one on a business card.
5. Test it before you stick it. Use more than one phone, in direct sun and in shade. If it will go behind tinted glass, test from outside on a bright day.

Every BuildTag design is test-scanned before it can be ordered, and the quiet zone is protected no matter how much styling goes around the code. It is still worth scanning the one you get in your own lighting before you peel the backing.

Think about where someone would be standing when they scan. Beside the car at a meet, or behind it in a parking lot? Put the sticker at a height and angle they can reach with a phone without walking into traffic.

On a car, the rear quarter window or rear window works well. On a motorcycle, a fuel tank, a tail section, a fairing or a saddlebag lid are the usual spots. Keep it out of your own line of sight, and check your local rules on what you can put on windows. If you are shopping, check whether a sticker is made for the outside of a surface or the inside of glass before you order.

Both are common. Matte usually reflects less light, which helps in direct sun. Gloss looks like paint. Pick the one that suits the car, then do the scan test in bright light. BuildTags come in either finish; the shop shows the sizes and designs, including a motorcycle one called Iron.

A car modification QR code is really your mod list behind a code. A page that does the job has:

• The name or nickname, and the year, make, model and trim.
• Power and torque, with a note on whether they are at the wheels or the crank.
• Mods grouped by type, with the brand and the part name.
• A few good photos, not a hundred.
• Links to where each part is sold, and where to follow the build.

Not sure how to keep that list in the first place? The guide to documenting your car build has a template, and the car show QR code guide covers display cards. To see how the whole thing fits together, read how BuildTags works.