Guides
Short, practical walkthroughs for the things people actually do with PeekInside.
Labelling a move
The original use case. One code per box, and the box tells you what's inside without being opened.
- Create a Moving boxcode. Give it a box number, the room it's packed in, and the room it's going to.
- List the contents as you pack. Tick items off as they go in.
- Mark it Fragile if it is — scanners see a warning badge before they pick it up.
- Print the label from the Print Studio and tape it to the box. Avery 5160 gives you 30 per sheet.
- On moving day, scan a box and tap Mark as delivered, then Unpackedas you empty it. You always know what's still sealed.
Because the code is dynamic, adding three more things to a box later is an edit, not a new label and a crossed-out Sharpie list.
Running stock on QR codes
One code per bin, shelf or SKU, counted where the stock actually is.
- Create a Stock item code with the item name, SKU, unit and bin location.
- Set Reorder at to the level where you want a warning. Leave it at 0 to turn the warning off.
- Stick the label on the bin.
- Scan to count: + and − for small corrections, or type an exact figure after a full count. Every change stamps the time it was counted.
- Below the reorder point the scan page shows a low-stock badge, so anyone walking past can see it needs ordering.
For a whole warehouse at once, build the bins in a spreadsheet and use Bulk create → CSV import.
Printing labels that line up
Label sheets are unforgiving — a small offset ruins 30 labels at once. This takes two minutes and saves a sheet.
- Pick your exact Avery product in the Print Studio. The number is on the box.
- Turn on Cut guides and print one page on plain paper.
- Hold it against a real label sheet up to a window. The dashed outlines should sit on the die-cuts.
- If everything is shifted, it's almost always the printer: set scaling to 100% / Actual size, never “Fit to page”, which shrinks the sheet by a few percent and drifts further from true down the page.
- Turn cut guides off and print for real.
Making codes scan reliably
- Keep contrast high. The studio warns you below 3:1 — pale-on-pale looks lovely and doesn't scan.
- Don't crowd the quiet zone. The margin around a code is part of the code.
- Print at least ¾" square for a phone at arm's length, and bigger for anything scanned from a distance.
- Going to a commercial printer? Export SVG— it has no resolution, so it can't be printed soft.
Locking a code
Marking a code Privatemeans only you — or your team — can open it. Anyone else hits an access-denied screen, but the scan is still recorded with its IP and approximate location. That's the setting to use for anything you'd want a trail of if it went missing.
Bulk creating from a spreadsheet
- Open Bulk create → CSV import and download the template.
- It has a worked example row for every content type. Keep the header exactly as-is — mismatched files are rejected rather than half-imported.
- Fill only the columns your
typeneeds and leave the rest blank. Lists use|between items and::between parts of an item. - Upload. Any bad rows are listed with the line number, and nothing is created until they're fixed.