Why Your Google Wallet Boarding Pass Has No Gate
Google knows your flight. It runs Google Flights. So when a boarding pass lands in Google Wallet with no gate and no boarding zone, the obvious assumption is that it will fill them in closer to departure. We wanted to know whether that is true, so we ran a controlled test: three passes for the same flight, changing one thing at a time. The answer is clean, and it is not what we expected going in.
The test
We issued three Google Wallet flight passes for the same real route, Paris Orly to Montreal, and added each to a live Android phone.
- Pass A — flight three days out, gate and boarding zone left empty.
- Pass B — same, but for today’s flight, roughly twelve hours before departure. This matters: check-in opens about 24 hours out, and airports often do not assign a gate until a few hours before departure. Testing far in advance proves nothing, because there may be no gate to know yet.
- Pass C — identical to the others, except we supplied a gate and a boarding zone ourselves.
The result
| Pass | What the card showed |
|---|---|
| A & B (fields empty) | Terminal 4 · Seat 12C — no gate, no zone |
| C (fields supplied) | Terminal / Gate 4 / 52 · Zone / Seat 3 / 12C |
Notice that the labels themselves change. Google does not render an empty gate row — the whole row collapses. A field nobody supplies is not blank on your pass, it is simply absent.
Pass B is the important one. That flight was departing the same day and Google was actively tracking it, yet the gate row still never appeared. If Google were in the business of filling in gates, that is precisely where it would have.
What Google does add
Something, and it is genuinely useful. Below the card, pass B showed a status chip reading Scheduled, a scheduled departure time, and the line “Updated at Aug 5, 8:00 PM from Google Flights. Confirm with your airline.”
Tapping that link opens a Google search built entirely from the pass’s own data: carrier, flight number, origin, destination and date. Google is not looking your flight up independently — it is reformatting what the pass already told it, and disclaiming the result.
So the division is clean. The card is the issuer’s. Gate, zone, terminal, seat, boarding time, barcode — all of it comes from whoever created the pass. The block below is Google’s, and it is flight status, not pass content.
Why the boarding zone is different
The gate at least exists in the world — an airport assigns it, screens display it, and in principle a data provider could know it. The boarding zone does not work that way. It is a function of your fare bucket, your status tier and where you are sitting. It lives in the airline’s departure control system and appears in no public flight database.
It is also not in the barcode. Airline barcodes follow the IATA BCBP standard (Resolution 792), which encodes passenger name, booking reference, flight, date, seat and cabin — but not zone, gate or boarding time. That is why scanning a boarding pass into a wallet app yourself produces a pass with almost nothing on it. The scanner is not failing; those fields were never in what it read.
The only place your boarding zone exists is as printed text on the pass. To get it into a wallet pass, something has to read the printed text.
What we cannot claim
Pass B was about twelve hours from departure. Orly frequently assigns gates two to four hours out, so it is possible Google had no gate to show rather than choosing not to show one. We could not fully separate those two.
What the structure suggests is still telling: Google’s data appears in a separate, attributed, explicitly disclaimed block. That is how a platform presents advisory information it does not want merged into an authoritative document.
What this means in practice
- A self-scanned pass will stay sparse. No wallet app can recover fields the barcode never carried.
- Your gate and zone come from whoever built the pass. If the airline’s own app made it, they filled those in. If you scanned it yourself, nobody did.
- Delays still reach you. Google’s status block refreshes on its own, even on a pass that cannot otherwise update. Treat it as a hint, not gospel — Google says as much.
- Check the boards anyway. Any pass, from anyone, is a snapshot. Gates move.