The Manifest
Technology & AI·23 June 2026·10 min read

Itinerary builder tools: what Indian agents should look for

A checklist for choosing itinerary builder software: WhatsApp delivery, GST/TCS pricing, occupancy variants and a defensible inclusions list.

Paris · 08:20

You search "itinerary builder for travel agents" at 11 pm, half-convinced last year's Word template is holding your business back. Ten tabs later you're comparing Travefy, Tourwriter and WeTravel, tools built for a client who opens a link on a laptop and pays by card. None ask, upfront, whether your document survives being forwarded eight times over WhatsApp on someone's three-year-old Redmi.

That gap is the actual decision you're making. An itinerary builder for Indian agents needs to do things these tools weren't designed around: price in rupees with GST and TCS lines in the right place, handle a family booking two twins, a triple and a child-with-bed, and produce an inclusions list that would hold up if a client took you to consumer court. None of that shows up on a features page.

This post is a checklist, not a shopping list. Score any tool against it, including the option of not buying one at all.

Why "itinerary builder" searches in India want something different

Most tools ranking for this search were built for a Western operator whose client opens a web link and pays online. Travefy, Tourwriter, WeTravel, Rezdy and Checkfront all sell some version of that workflow, and none of their public feature lists mention WhatsApp delivery, GST, TCS or Indian occupancy conventions.

Travefy's pitch is a drag-and-drop, branded itinerary builder with custom-domain branding ("everything you send to clients is branded to you") and 200+ supplier integrations (Travefy). Tourwriter starts at $99 a month and works in multiple currencies, but discloses no white-label option (Tourwriter). Rezdy and Checkfront are booking engines, not document builders; Checkfront's features page centers on booking widgets and real-time availability and never mentions an itinerary document (Checkfront).

None of that is a knock on those products, they solve a different problem for a different client. But the four things that decide whether a tool earns its subscription in an Indian agency, WhatsApp-survivable delivery, rupee pricing with the right tax lines, occupancy variants, and a defensible inclusions/exclusions block, weren't the criteria they were built against. Use them as your scoring framework instead.

The WhatsApp test: does the output survive compression?

Send a document as a WhatsApp "document" attachment and it stays intact; send it as a "photo" and WhatsApp compresses it, sometimes badly enough that a client can't read the fine print on transport timings. Before you buy any tool, test what its export looks like on both paths, on a low-end Android, on a slow connection.

WhatsApp raised its in-chat file-upload ceiling from 100MB to 2GB back in May 2022 (Wikipedia, sourced history), so raw file size is rarely the real constraint anymore. The actual constraint is data cost and how many taps it takes a client to open the thing at all. A 40MB branded PDF that needs a data pack to download loses to a screenshot every time.

That's why the itinerary template built to be forwarded, not just opened recommends pairing a full branded PDF with a separate one-page WhatsApp-forwardable summary: day, place, one line each. Most clients only read the preview text without opening attachments, so the first two lines of whatever you send carry more weight than the document's design. Whatever tool you evaluate, ask if it can produce that lightweight second version, not just the polished one.

Can it price in rupees the way Indian quotes actually work?

An itinerary builder that only shows a grand total, or buries tax as a vague "inclusive of all taxes" line, will not survive a client asking why the number moved between quote and invoice. It needs a GST line that matches your actual invoicing (see the 5% or 18% package invoicing rules) and, on any package with an international leg, a TCS line the client understands before they pay.

As of April 2026, TCS on overseas tour packages moved to a flat 2% with no minimum threshold, replacing the earlier tiered structure of 5% up to ₹10 lakh and 20% above it. The obligation applies to any booking bundling at least two of travel, accommodation, or boarding and lodging (the full playbook on the flat 2% TCS). The exact forms and section involved are still being settled in practice, so confirm specifics with your CA rather than trusting a tool's help page.

Occupancy is the other gap. A single "price per person" field breaks the moment a real family books: two adults twin-sharing, one child with an extra bed, one without. If a tool can't hold twin, triple and child-with-bed as separate line items rolling up into one total, you'll end up doing that maths in a side spreadsheet anyway.

Careful: A tool that only supports a flat per-person rate will quietly cost you margin on every mixed-occupancy family booking, because someone will round the child-with-bed rate down "to keep it simple" instead of working out the real room-cost split.

A vague inclusions list isn't a formatting choice, it's a liability. The moment a client disputes what was promised, the itinerary document you sent becomes the primary evidence, and India's National Consumer Helpline accepts grievances through WhatsApp, its app, phone and a web portal, so that chat thread and PDF can end up in front of a consumer forum (National Consumer Helpline, NCH 2.0). What a forum reads back is whatever you actually sent, not whatever you meant.

A defensible block is category-wise, not a paragraph: stays (room category, meal plan), transport (vehicle type, ac or non-ac, exclusions like tolls), meals (which ones, which aren't), and activities (named, with age or fitness caveats where relevant). A tool that builds this as a structured, repeatable block, rather than free text retyped each time, cuts the version-to-version drift that creates the ambiguity. For the arguments that surface when this goes wrong, see what consumer courts weigh in disputes against travel agencies.

Whose logo, whose images: branding and licensing you forget to check

Two questions worth asking in a demo, not after you've signed a year's contract: does the finished document carry your branding or the tool's, and where do its images come from? Travefy is explicit that a paid plan puts your branding, not theirs, on everything you send (Travefy); several others in this category don't disclose their branding policy publicly, so you find out only after you've built a season's worth of itineraries in it.

Images are the part agents skip entirely. Pulling a hotel's marketing photo, or one found on a Google search, into a document you circulate commercially is a licensing risk nobody thinks about, mostly because nobody's been chased for it yet. Default to your own photos, or stock you've actually licensed.

Version control: does a revised itinerary overwrite the one the client already has?

A static PDF forwarded on WhatsApp has one failure mode that costs real money: the itinerary changes, a hotel swap, a flight time shift, and the client is still working off the version sitting in their chat history, because nobody resent it, or they did and now the thread has two files and the client opens the wrong one.

A tool that publishes to a live link, one URL that always shows the current version, solves this cleanly: you edit, the client's saved link updates. A tool that only exports static files pushes that discipline back onto your team, every revision. Before buying, make one change to a sample itinerary in the demo and check what the client-facing link shows afterward. If the answer is "send them a new PDF," you're paying a subscription for something you'll still have to manage manually.

Can you rebuild last year's itinerary in under five minutes?

This is the single feature that decides whether a paid tool earns back its subscription in season. Most agencies aren't writing net-new itineraries every time, they're adapting a Kerala or Goa route they've run a dozen times, with a new date, hotel rate, or group size.

Run this test yourself in the demo: pull up (or build) last year's itinerary for a route you sell often, clone it, and time how long it takes to update the dates, swap one hotel, and reprice for a different pax count. If that takes longer than retyping it in Word, the tool's duplication feature isn't saving you anything, whatever the pitch claimed. Reuse of your own past work, not drafting from scratch, is the everyday case that decides whether the subscription pays for itself.

Scoring the market against the India checklist

None of the tools commonly recommended for "itinerary builder" searches score full marks against an India-specific checklist today, at least on what each discloses publicly:

Tool Built for India-checklist gap
Travefy Branded, drag-and-drop itineraries, 200+ supplier integrations No India pricing, GST/TCS or WhatsApp-delivery features shown publicly
Tourwriter Multi-currency itinerary and quoting, from $99/month No branding/white-label disclosure on the public site
Rezdy Booking, communications and reporting for tour operators Not an itinerary-document builder at all
Checkfront Booking widgets and real-time availability No itinerary builder in its feature set
WeTravel Publicly claims an itinerary-builder feature Could not be independently verified this pass; check manually

Treat that table as a starting point, not a verdict. Feature pages change, and the gaps that matter most, WhatsApp delivery and Indian tax handling, don't show up until you ask a salesperson directly.

When a well-built template still beats any tool

For a one- to three-person agency running a handful of departures a month, a disciplined Word or PDF template, reused with real editing discipline, often beats any paid tool outright. The itinerary template covered earlier applies directly here: the cost isn't the software, it's the habit of updating a master file instead of hunting for "the good one" in old chats.

A paid tool starts earning its subscription once a team is producing enough itineraries that the reuse and version-control problems above cost more staff time each month than the tool does, commonly somewhere past a handful of active quotes running in parallel across more than one person. Below that, discipline matters more than software. Above it, software starts protecting you from the discipline slipping.

Common questions

Is there a good, free itinerary builder for travel agents?

Free tiers typically cap the number of itineraries, strip your branding, or watermark the output, which defeats the purpose for anything client-facing. A well-structured Word or Google Docs template you control outright, reused and revised carefully, often beats a free tier built mainly to convert you to a paid plan.

What should an itinerary builder app do that a PDF can't?

At minimum: a live link that updates when you revise it, rather than a new file each time, and one-click reuse of your own past itineraries. If an app doesn't clearly beat a template on both, it isn't earning its subscription yet.

Which itinerary builder software actually works for Indian agents right now?

None of the commonly recommended tools publicly disclose India-specific handling for WhatsApp delivery, GST/TCS lines, or twin/triple/child-with-bed occupancy, as of August 2026. Score any candidate against those four criteria in a demo rather than assuming a global tool covers them.

The short version

  • Score any itinerary builder against four India-specific tests: WhatsApp-survivable delivery, correct GST/TCS lines, twin/triple/child-with-bed occupancy handling, and a defensible category-wise inclusions/exclusions block.
  • None of the commonly recommended tools (Travefy, Tourwriter, Rezdy, Checkfront) publicly disclose India-specific pricing or WhatsApp handling; verify directly in a demo before assuming.
  • TCS on overseas packages is a flat 2% with no minimum threshold as of April 2026; confirm the exact forms and section with your CA before you build it into any process.
  • Test version control by editing a sample itinerary in the demo: does the client's link update, or do you have to resend a whole new file every time?
  • Test reuse by cloning last year's itinerary for a route you sell often and timing the rebuild; under five minutes is the bar a paid tool needs to clear.
  • Check who owns the branding on the finished document and where its images come from before you sign, not after.
  • For a one- to three-person agency, a disciplined template often beats a paid tool outright; the software starts paying for itself only once reuse and version-control mistakes cost more staff time than the subscription.