I have a use case where I’m building itinerary documents and have travel related places, accomodation, sightseeing spots etc setup in spreadsheet form and categorised - I’m testing using code interpreter for this, would that be the recommended way for this type of data?
I think this is the good way to go! I have a client who built the samething and it is working really great!
1 Like
Okay, great thanks for the reply. Good to know I’m on the right track here.
Honestly, this sounds like a pretty solid use case for Code Interpreter. If your itinerary data is already structured in spreadsheets — with places, accommodation, sightseeing spots, categories, etc. — then Code Interpreter can clean, filter, sort, group, and even generate formatted outputs based on that data really well. It’s great at pulling patterns from tables and building something more usable out of them.
That said, it does depend on how much logic you need. If your itineraries require dynamic rules (e.g., “avoid long travel times,” “prioritize museums on rainy days,” “paginate into a printable document”), you might still need some manual prompting or post-processing.
But for turning your spreadsheet into customized itineraries quickly? Definitely a recommended and efficient way to do it.