How to scan a QR code and have it appear automatically in Google Sheets

The short answer: a QR code by itself does not write anywhere. Something has to read the code and then append a row. There are four established ways to do that with Google Sheets, and the right one depends almost entirely on who is holding the phone.

Method 1: a dedicated mobile scanner app

Install an app built for scanning into spreadsheets, link it to your Google account, choose a sheet, and scan. Several exist on both iOS and Android, including Scan to Sheets and Scan-IT to Office. How a browser scanner link compares with the Scan to Sheets app sets out where each one wins.

• Good raw scanning ergonomics, since the app owns the camera.
• Usually the fastest option for one person scanning a lot of items.
• The cost: every person who scans must install the app, and in most of these tools link their own Google account. On shared devices that link can drop and need re-establishing.

Method 2: a Google Form linked to a sheet

Create a form with a field per column, link it to a sheet under Responses, and open the form on a phone. Free, no setup beyond the form, and it genuinely works.

• Completely free and nothing to maintain.
• A form has no camera scanner of its own, so you scan with the phone camera or another app and paste the value in. That is fine for fifty items and painful for five hundred.
• No offline buffer. A submission attempted with no signal fails and is lost rather than queued.
• Self-reported, so for attendance or anything with a consequence attached, anyone with the link can submit for anyone else. Google Forms versus a scanner link goes deeper on when a form is enough.

Method 3: a Google Apps Script web app

Apps Script can host a small web page with a real camera scanner in it, usually by pulling in a JavaScript barcode library, and append rows directly to your sheet. Free, fully yours, and several good public tutorials walk through it.

• You control every field, every validation rule, and the whole layout.
• No third party holds your data or your credentials.
• The trade is maintenance: camera permission edge cases, iOS Safari quirks, in-app browser problems, duplicate suppression, retry behaviour when wifi drops, and Apps Script quotas under concurrent use. None of it is hard alone; together it is a small project, and it usually surfaces on the day you need it to work.

Method 4: a shareable scanner link

A hosted scanner where you configure the destination once and share a URL. This is what QR to Sheets does, so treat this section as interested but specific.

You connect a Google Sheet, create a scanner link, and send the URL to whoever is scanning. They open it in a phone browser, allow the camera once, and scan. Every scan appends a timestamped row. Nobody installs an app or creates an account, which is the whole point when the people scanning are students, temporary staff, or a crew you will not see again next month.

Narrated4:06

What about a USB or Bluetooth barcode scanner?

A hardware scanner acts as a keyboard: click a cell, scan, and the value appears and the cursor moves down. Nothing writes to the sheet except that typing, so the sheet must be open with the right cell selected, but at a fixed desk it is genuinely excellent and people overlook it.

• Very fast and very reliable for high volume at one desk.
• No app, no account and no browser involved.
• Tethered to a computer, so it cannot walk the aisles or work a door.
• One scanner, one station: it does not scale to a team spread across a site, and it records no timestamp unless you add one with a formula or a script.

Comparing all four

A straight recommendation

• Scanning a few dozen items yourself, occasionally: use a Google Form and keep the money.
• One person scanning high volume regularly: a dedicated mobile app is likely the most comfortable.
• One fixed desk, high volume: a USB scanner typing into a cell.
• You want to own the code, or policy forbids third-party services: build the Apps Script version.
• Several people scan, they should not need accounts or installs, and connectivity is unreliable: a scanner link is the fit.

Three things that go wrong whichever method you pick

Overwriting instead of appending

Append one row per scan and derive totals with a formula or a pivot table. A single overwritten quantity column cannot tell you when a discrepancy appeared, who counted a shelf, or whether something was counted twice.

Timestamps in the wrong timezone

Many tools write UTC. If your team works six hours behind UTC, every row is six hours off and every daily report straddles the wrong boundary. Check what timezone your tool writes, and whether you can change it, before you build reports on it; why Google Sheets timestamps show the wrong timezone walks through each cause.

Timestamps stored as text

If a timestamp arrives in a format Google Sheets does not recognise as a date, such as a raw ISO string ending in Z, the column is stored as text, and sorting, date filters and formulas quietly fail on it. Test by sorting the column: if it sorts alphabetically rather than chronologically, it is text. A format like 2026-08-22 10:01:54 is read as a real date and time.

Step by step

1. 1

   Decide who is doing the scanning

   If it is only you, almost any method works and you should pick the free one. If other people scan — staff, students, volunteers, contractors — then whether they need an app or an account becomes the deciding factor.

2. 2

   Prepare the destination sheet

   One column per field, exactly one header row, no merged cells. Format the code column as plain text so long numeric barcodes keep their leading zeros.

3. 3

   Pick a method from the four below

   They differ mainly on who can scan, whether it survives a dropped connection, and how much you maintain yourself.

4. 4

   Test with five real items before you rely on it

   Check the values land in the right columns, that a repeat scan behaves the way you expect, and that the timestamp is in a timezone you can read.

Frequently asked questions