Solutions · For labels that outlive vendors

QR codes for equipment labels & manufacturing

An equipment label outlives everything: the campaign, the vendor, sometimes the company that printed it. A technician scanning a fifteen-year-old label in a plant room doesn't care whose SaaS subscription lapsed — the code either resolves or it doesn't, and the wrong choice made today decides that.

So this is the one page where we'll talk you out of dynamic codes: for serial plates and asset tags whose meaning never changes, use a static code. The data is encoded in the grid itself, nothing sits in the middle, and it will scan for as long as the label physically survives — with no dependency on us or anyone. Save dynamic codes for the things that genuinely change: manuals, safety sheets, calibration procedures.

The playbook

Step 1

Static for identity, dynamic for documents

The asset tag is static — serial, location, or a fixed URL, encoded permanently. The 'manual & service history' code beside it is dynamic, so revision C replaces revision B on every machine the day it lands, without touching a single label.

Step 2

Vector labels for industrial printing

Export SVG, PDF or EPS for label stock, engraving or panel printing. High error correction plus a tested quiet zone means the grid survives scuffed laminate and a torch-lit scan at arm's length.

Step 3

Unlimited, on purpose

Static codes are unlimited on every plan and never expire, because charging per asset tag would push you toward fewer labels — the wrong direction for the one use case where coverage is the point.

Built with:Static codesDynamic repointingPrint-ready exportsAll features →

Questions this buyer asks

What happens to static codes if PIXELQODE shuts down?

They keep working, forever. A static code has no redirect and no dependency on any service — the destination is in the grid itself. That's the honest reason we recommend them for equipment, and it's a promise no dynamic code from anyone can make.

Can we bulk-create codes for an asset register?

Yes — CSV import creates a code per row with names and folders from the sheet, and the Excel export gives you back the full register with each code's slug and destination for your CMMS.

Nearby jobs

For the menu on the table

Restaurants & cafés

The laminated code on every table keeps working while the menu behind it changes daily.

Built with:Dynamic repointingStatic codesFoldersScan analytics

See the playbook
For codes that ship on product

Retail & packaging

A code on a box lives for the whole print run. The place it points to doesn't have to.

Built with:CSV importDynamic repointingSVG / EPS export

See the playbook

Print it once. Change it whenever.

Unlimited static codes on every plan. Dynamic codes you can repoint after printing, and every design feature on every tier.

All solutions