Wireframe
WIREFRAME · Screen 3 · Codes and unit binding · admin / production
Codes and unit binding
The Indigo / agency side. Generate a batch of unique codes for an order, bind each to a unit, hand the vendor a print-ready sheet.
Why this matters A unique code per unit is the crux, not one shared static QR. This screen is where each code becomes meaningful: it is tied to a specific stand and order before it ever ships, so a scan in the field resolves to a known unit and the dashboard can count it against what was ordered.

New code batch

Brand X
MUM-Q3
Free-standing unit (FSU)
200
●North ●South ●East ●West
Generate 200 codes

The chain a code creates

Order MUM-Q3
  → Unit (FSU)
    → Code (unique QR)
      → Install record (on scan)

Generated batch · 200 codes · order MUM-Q3

200 generated 0 scanned yet Not yet exported
QR
FSU-0142
QR
FSU-0143
QR
FSU-0144
QR
FSU-0145
QR
FSU-0146
QR
FSU-0147
QR
FSU-0148
QR
FSU-0149
192 more
Export print sheet (PDF) Download codes (CSV)

Decision to settle with Irwin

Who prints and affixes the 200 codes, and when does a code bind to a unit? Two clean options:

  • Bind at print. System assigns code to unit up front; vendor pastes code N on stand N in order. Simplest, needs the vendor to keep sequence.
  • Bind at source. Vendor scans a code, scans / tags the stand, the two link on the spot. More robust to mix-ups, one extra step at the vendor.
Indigo PoP wireframe · codes and binding · worked example only