Uploading a travel pass does not create a trip
A travel pass attaches to a trip that already exists. It never creates one. If you upload a pass before the trip is in Logg, the pass is saved, but no trip appears. Create the trip first, or forward the booking confirmation to your import address, and then attach the pass.
What it is
A travel pass is a boarding pass, ticket or QR document you upload so Carreh can read it and keep it to hand. It is a document, not an itinerary entry.
What it does
- Stores the file and reads what it can from it: operator, passenger name, booking reference, travel date, seat, gate, terminal and the barcode.
- Attaches to a trip when you upload it from inside a booking or pick a trip yourself.
- Saves as a standalone pass when there is no trip to attach it to.
- Keeps working when the barcode cannot be decoded. The original file is still there to open.
What it does not do
- It never creates a trip. Uploading ten passes creates zero trips.
- It never creates a booking inside a trip.
- It does not add countries or cities to Atlas.
- It does not tell you that no trip was found. There is no message, which is the reason this article exists.
- It will not match a pass to a trip by guessing from the date or the route. The link is either explicit or absent.
What you need first
A trip in Logg, if you want the pass to sit inside one. There are two ways to get a trip: add it by hand in Logg, or forward the booking confirmation email to your Carreh import address and let the import create it.
How it connects to the rest of Carreh
A pass attached to a trip shows with the bookings of that trip. A pass with no trip opens on Android from More, then Documents, invoices & tools. On iPhone that list returns in the next update, and until then Client Services can find it for you. Trips come from Logg or from an import. Atlas is fed by completed trips only, never by passes.
Who can use it
Everyone. Travel passes are not a Premium feature.
Premium
Not required. Uploading and storing passes is free on every account.
Limits
- One file per upload, up to 4.2 MB.
- PDF and image files on iOS.
- A document that is not a travel document is still stored, filed as an unknown type rather than refused.
Common questions
- I uploaded my boarding pass. Why is there no trip in Logg?
- Because a pass attaches to a trip and never creates one. Add the trip in Logg, or forward the booking confirmation to your import address, then open the trip and attach the pass.
- I uploaded the same ticket several times. Did I make several trips?
- No. Each upload saved another copy of the pass. None of them created a trip. You can delete the extra copies.
- Where did my pass go?
- If it is attached to a trip, with the bookings of that trip. A pass with no trip opens on Android from More, then Documents, invoices & tools. On iPhone that list returns in the next update, and until then Client Services can find it for you.
- My pass is not under Active. Where is it?
- A standalone pass is filed by its travel date as a single day. It shows under Active only on the travel date itself. Before that it is under Upcoming, afterwards it is under Past. A pass with no readable date is filed under Upcoming.
- Does uploading passes fill in my Atlas map?
- No. Atlas counts countries and cities from trips that have completed. Passes are never counted.
Common problems
- Passes uploaded, Logg still empty.
- Expected behaviour. Passes do not create trips. Create the trip first, in Logg or by forwarding the booking email, then attach the pass.
- The pass saved but is not on the trip.
- The trip link is only kept when you own the trip or are a member of it. An unverifiable link is dropped and the pass is still saved, without the link. Open the trip and attach the pass from there.
Edge cases
- A pass uploaded to a friend trip is always saved without a trip link.
- If the barcode will not scan, the pass still saves and you can open the original file.
- Deleting a booking removes the passes attached to that booking. Deleting a trip leaves standalone passes alone.