Reference

Column mapping, explained

In QR to Sheets, one scan writes one row, and column mapping decides what goes in each cell of that row. Most workspaces never need it — here is how to tell, and eight ready-made setups if you do.

Updated

First: do you need it at all?

Be honest here, because skipping this feature is the right answer more often than not.

You do not need it

Your codes hold one thing — a student ID, a barcode, an asset tag, a ticket number. The six default columns already record it with a timestamp and the scanner link it came through. Leave column mapping alone and start scanning.

The default row

ABCDEF
scanned_atqr_valuescanner_emailorganizationdevice_typescan_id
2026-08-23 09:14:02STU-4417link:Gate AYour workspacemobilescn_8f2a1c

You do need it

Your codes pack several fields into one value, and you are tired of writing SPLIT() formulas afterwards. Mapping does the splitting as the row is written.

One code, three columns

BADGE-001|John Smith|VIP
DEF
badge_idguest_nametier
BADGE-001John SmithVIP

The one thing that trips everyone up

When you use column mapping, every row still begins with three tracking columns — scanned_at, scanner and device_id. They are always written so you can audit which link and which phone each row came from, even if you did not map those fields yourself. Because they are always there, none of the templates below adds its own time or scanner column, and you do not need to either.

This means your first column lands in spreadsheet column D, not A. If you type your own headers into row 1 starting at A, everything looks shifted and the feature seems broken. It is not — the headers are simply three columns out.

You do not have to remember any of this. Every template below has a Copy header row button that includes the tracking columns already. Paste it into cell A1 and the alignment is correct.

Eight ready-made setups

Each of these is one click inside the app. When you create a scanner link, choose Customize columns and pick a template — the columns are filled in for you and you can edit any of them afterwards.

Attendance register

One row per person per scan, for classes, shifts and roll call.

Attendance codes are usually a single ID with nothing to split, so this template only gives that ID a clear column name. The scan time and the scanner link are always written in columns A and B, so they need no column of their own. Keep one row per scan rather than one row per person: it gives you an audit trail, and a pivot table still gets you the daily count.

A code like this

STU-4417

Becomes this row

ABCD
scanned_atscannerdevice_idstudent_id
2026-08-23 09:14:02link:Gate AiPhone-a91cSTU-4417

Columns A–C are the tracking prefix. Your mapped columns start at D.

Timesheet / clock in-out

Shift presence, where the link name records the direction.

Nothing in the product alternates direction between scans, so use two scanner links named Clock in and Clock out pointed at the same spreadsheet and give both this mapping. The link name is always written in the scanner column (B), which is what makes each row's direction explicit rather than inferred from scan order. On a link with staff sign-in that column holds the staff member's email instead, so leave staff sign-in off on these two links. Pair the rows and total the hours with formulas in your own sheet; this records presence, not a payroll timesheet.

A code like this

EMP-2043

Becomes this row

ABCDE
scanned_atscannerdevice_idemployee_codedevice
2026-08-23 09:14:02link:Gate AiPhone-a91cEMP-2043mobile

Columns A–C are the tracking prefix. Your mapped columns start at D.

Inventory / SKU count

Stock counts and cycle counts where the barcode is the whole value.

For a stock count the barcode is the entire value, so no splitting is needed. The scan time, the scanner link and the phone's device id are always written in columns A to C, so two people counting different aisles on their own phones can be told apart later, which is the thing most counts get wrong.

A code like this

8801234567890

Becomes this row

ABCDE
scanned_atscannerdevice_idbarcodedevice
2026-08-23 09:14:02link:Gate AiPhone-a91c8801234567890mobile

Columns A–C are the tracking prefix. Your mapped columns start at D.

Warehouse pick / put-away

One label carries the SKU, bin location, quantity and lot, split into columns.

Warehouse labels often pack several fields into one code so a single scan records the whole movement. Splitting them means the sheet reads as a stock ledger straight away: filter by aisle, sum the quantity per SKU, trace a lot. Print your labels with the same delimiter and field order as this template, or change the columns to match the labels you already have.

A code like this

SKU-4471|Aisle B-07|24|LOT-2026-10

Becomes this row

ABCDEFG
scanned_atscannerdevice_idskulocationqtylot
2026-08-23 09:14:02link:Gate AiPhone-a91cSKU-4471Aisle B-0724LOT-2026-10

Columns A–C are the tracking prefix. Your mapped columns start at D.

Event badge check-in

Badges that encode several fields in one code, split into columns.

This is the case column mapping was built for. One printed badge carries the ID, the name and the tier separated by a delimiter, and splitting it means the door list is readable without a lookup formula. The check-in time is always in column A. Check which delimiter your badge printer actually uses before the event.

A code like this

BADGE-001|John Smith|VIP

Becomes this row

ABCDEF
scanned_atscannerdevice_idbadge_idguest_nametier
2026-08-23 09:14:02link:Gate AiPhone-a91cBADGE-001John SmithVIP

Columns A–C are the tracking prefix. Your mapped columns start at D.

Asset / equipment loan

Laptops, tools and AV kit going out and coming back.

A loan log needs to answer who has what, right now. Keep the asset tag raw so it matches your asset register exactly, and use the scan times in column A to work out whether a scan was a checkout or a return. Want a notes column? Type a notes header to the right of asset_tag and write in it by hand; scans never fill that column.

A code like this

ASSET-2291

Becomes this row

ABCD
scanned_atscannerdevice_idasset_tag
2026-08-23 09:14:02link:Gate AiPhone-a91cASSET-2291

Columns A–C are the tracking prefix. Your mapped columns start at D.

Visitor sign-in

Reception and site sign-in, including contractors.

Visitor logs are often read during an evacuation, so the company matters as much as the person. Splitting the pass code from the company keeps both filterable, and a default keeps the column populated when a pass carries only an ID. The sign-in time is always in column A, and the scanner link in column B tells you which entrance, when each entrance has its own link.

A code like this

VIS-8842|Acme Ltd

Becomes this row

ABCDE
scanned_atscannerdevice_idpass_idcompany
2026-08-23 09:14:02link:Gate AiPhone-a91cVIS-8842Acme Ltd

Columns A–C are the tracking prefix. Your mapped columns start at D.

Delivery / parcel scan

Goods received and parcel handover logs.

Tracking numbers are scanned fast and in bulk, so the value stays whole and the scan time in column A does the work. When two people are receiving at once, the device id in column C tells you which phone a scan came from, and the scanner link in column B which van or bay, when each has its own link.

A code like this

TRK-99120054

Becomes this row

ABCDE
scanned_atscannerdevice_idtracking_numberdevice
2026-08-23 09:14:02link:Gate AiPhone-a91cTRK-99120054mobile

Columns A–C are the tracking prefix. Your mapped columns start at D.

The eight column types

Every column you add picks one of these. The first three read the scanned code itself; the rest fill themselves in automatically.

TypeWhat it writesUse it when
Full valueThe entire scanned code, exactly as read.The code is one field. This is the most common choice.
Split by separatorOne piece of the code, cut at a character you choose.The code contains a delimiter such as | or a comma. Pieces are numbered from 0, so the first piece is 0.
Regex extractThe part of the code matching a pattern.The code has no clean delimiter but a predictable shape. Group 0 is the whole match; group 1 is the first set of parentheses.
Scan timestampDate and time of the scan, in your workspace timezone.Rarely: column A already holds it on every mapped row, so this repeats it.
Scannerlink: followed by the scanner link name, or the staff member's email when they scanned signed in (on a link with staff sign-in, or the signed-in scanner).Rarely: column B already holds it on every mapped row, so this repeats it.
Organization nameYour workspace name.Several workspaces write into one shared sheet.
Device typemobile or desktop.Rarely useful on its own; handy when auditing a count.
Scan record IDA unique ID for the scan.You need to match a row back to a support question.

For a worked Regex extract example, split a contact-card badge into name, email and company columns.

Splitting a code, step by step

Pieces are numbered from zero. That is the single most common mistake, so here it is spelled out for the code BADGE-001|John Smith|VIP split on |:

Part number 0

BADGE-001

Part number 1

John Smith

Part number 2

VIP

Do this before you set up any split

  1. Create the scanner link with the default columns and scan one real code.
  2. Look at the qr_value column in your sheet. That is the exact text you are splitting, including any spaces.
  3. Now add your columns, using the separator you actually see there. Guessing the format is what causes empty columns.

If something looks wrong

My headers do not line up with the data

Your own columns start at column D, because of the three tracking columns. Copy the header row from your template above and paste it into cell A1.

The time or the scanner appears twice in each row

Columns A and B already hold the scan time and the scanner on every mapped row. Remove any Scan timestamp or Scanner column you added; the preview in the link editor flags both.

A column is empty on every row

The split or regex did not match. Check the qr_value column of an unmapped scan to see the real code format, and remember that part numbers start at 0. You can also set a default value so the column is never blank.

Everything landed in one column

The separator you chose does not appear in your codes. A code printed with a hyphen will not split on a pipe. Look at one real value and match it exactly.

Old rows still have the old columns

That is intended — existing rows are never rewritten. When you change the mapping, point the link at a fresh tab so one tab holds one shape.

I want the plain six columns back

Edit the link, open the column section and choose Back to defaults. The next scan writes the standard six-column row again.

Set it up on your own Sheet

Column mapping is included on the free plan, up to 20 columns per scanner link. Free tier covers 300 scans, and the people scanning never create an account.

No credit card required