Rail operators
Does Tineo work with Italo?
Yes. Italo has a dedicated route reader in Tineo that pulls the date, departure time and arrival time out of the single combined row Italo uses in its Italian-language confirmations.
- Support level
- Dedicated handling
- Imports as
- Train
- Forward to
[email protected]
Tineo carries Italo-specific code in the import pipeline, pinned by regression tests.
Which Italo emails Tineo reads
- Booking confirmations in Italian
- E-tickets with the journey row
Italo confirmations typically arrive from:
italotreno.it. Forwarded copies from your own address also work, because the
parser matches on content as well as on the sender.
Exactly what gets extracted
These are the fields the import pipeline pulls out of a Italo confirmation. A field only appears on your itinerary if Italo actually printed it in the email.
| Field | What Tineo reads |
|---|---|
| Operator | Italo. |
| Departure and arrival stations | Italian station names. |
| Departure and arrival times | Both read from the same combined row. |
| Journey date | Italian date format, with the year resolved from context. |
| Booking reference | The Italo booking code. |
| Coach and seat | When printed. |
How Italo is handled specifically
- Italo prints the date, departure time and arrival time in one row. Tineo parses all three from that row together, so the arrival cannot be picked up from a different journey.
- Both "Italo" and "italotreno" spellings are recognised, which matters because the sending domain and the brand text differ.
- Italian month names and Italian lodging-style date formats are handled by the locale-aware date parser.
How to get a Italo booking into Tineo
- Start from the original confirmation. Reminders, check-in prompts and loyalty statements usually drop the fields that matter. The booking confirmation is the one to use.
- Forward it unchanged to
[email protected]from the email address on your Tineo account. Leave the subject line alone and do not paste the body into a fresh message. Both habits destroy information the parser depends on. - Open the trip and check the item. Tineo matches the booking to the right trip by date and location, creates a train item, and places it on the timeline and the map.
- Forward changes too. Schedule changes and updated confirmations carry information worth having, and Tineo tells the difference between a new booking and a change.
Honest limits with Italo
No parser reads every layout perfectly. These are the real Italo cases where Tineo will not give you a complete item.
- Verified Italo volume in Tineo is low.
- When the row omits the year, Tineo resolves it from context. Check a journey booked near a year boundary.
If a Italo email does not import
- Forward the Italian original rather than a translation.
- If the year looks wrong on a December or January journey, correct it on the item.
- Check the review queue on the trip. Tineo deliberately holds anything it cannot parse confidently rather than importing a half-filled item you might not notice.
- If the email arrived as a PDF with an empty body, forward the itinerary email as well so there is text to read alongside the attachment.
- Still nothing? Add the train manually on the trip. It takes a minute and the rest of the trip keeps working.
Italo and Tineo: common questions
Does Tineo work with Italo train tickets?
Yes. Italo has a dedicated route reader that parses the date, departure time and arrival time from Italo’s combined journey row in Italian-language confirmations.
Do I need an English Italo confirmation?
No. Tineo parses the Italian original, including Italian month names.
Other rail operators Tineo supports
Try it with your next booking
Forward your next Italo confirmation to
[email protected] and see what Tineo builds. If the
parse is wrong, the item is editable and the review queue shows you
what Tineo was unsure about.