How to build a supplier library that pays off on the second trip

The first time you plan a trip to a destination, you do real research: which rooms actually have the view, which DMC answers emails within a day and which takes a week, which resort's "renovated" wing is the one to book and which one still has the old bathrooms. That research is valuable. The problem is where it usually ends up: scattered across email threads, a notes app, a sticky note on a second monitor. This means the second time you sell that destination, you do the research again.

A supplier library is just a deliberate place to put that knowledge so it survives past the trip it was gathered for. It does not need to be complicated. It needs to be consistent enough that you actually go back to it, and specific enough that what you find there is useful six months later when the details have faded.

Organise by supplier, not by trip

The instinct is to file notes under the client or the trip, because that is the context you were in when you wrote them. Resist it. A note that says "book room 412, ask for late checkout, avoid the pool-view rooms in June" is useless filed under a client name you will not think to search for again. Filed under the hotel, it is there the next time anyone, including a future version of you, needs to book that property.

Each supplier record should hold a small, consistent set of things: contact details and the name of whoever actually replies to emails, the booking process (direct, GDS, a specific portal, a DMC intermediary), payment terms, cancellation policy patterns, and a running list of notes tagged by date, so a note from a booking two years ago does not read as current if the property has since changed.

Capture the details that do not show up in marketing

The generic facts about a hotel are on its website. What is worth writing down is what is not: which room numbers or categories actually deliver what the brochure promises, which ones are close to construction noise or an access road, whether the "infinity pool" photo is taken from an angle that flatters a much smaller pool, what the transfer time from the nearest airport really is once you account for the ferry or the unpaved final stretch, and how responsive the property or DMC actually was when something went wrong on a previous trip.

Client feedback is the single best source for this. When a returning client mentions the room was smaller than expected, or the breakfast was disappointing, or the driver was early and helpful, that goes in the supplier record immediately, while you remember it, not into a general impression you will half-recall next time.

Attach the documents, not just the memory

Rate sheets, group contracts, DMC terms, sample confirmations and any FIT booking instructions are worth keeping attached to the supplier record itself, not buried in an old email thread. When you are quoting a new trip under time pressure, having last season's rate sheet and the DMC's actual terms in front of you is faster than searching your inbox for a subject line you half-remember.

Keep it current, or mark it as aged

The failure mode of any knowledge library is staleness: a note that was accurate two years ago being read as current today. Two habits fix most of this: date every note when you write it, and do a light review pass on any supplier before you sell it again, even if that just means checking whether the rate sheet on file matches what the property is quoting today. If a note is old enough that you would want to verify it anyway, treat it as a prompt to verify, not as the answer.

Start with your top twenty

Building a library for every supplier you have ever touched is a project that never gets finished, which is why it usually never gets started. Start with the twenty suppliers you book most: the properties, DMCs and tour operators behind most of your trips. Build those out properly before worrying about the long tail. That covers most of the value with a manageable amount of work, and the habit of adding to it after every trip is what actually makes it compound.

If you work with other advisors, share it deliberately

In a small team or a host-agency group, a supplier library only compounds if more than one person feeds it. The failure mode here is not a technical one. It is that everyone keeps their own private notes out of habit, and the team ends up with several partial libraries instead of one useful one. Agree on where notes go and make adding one after a trip a normal, expected step, the same way sending a final invoice is, rather than an optional extra that only the most organised person on the team actually does.

Make the second trip faster than the first

The point of all this is not the library itself, it is what happens the next time a client asks about a destination you have already sold. Instead of starting from a search engine, you start from what you already know: the room to request, the DMC to skip, the transfer time that is actually accurate. That is the difference between research and knowledge. Research happens once and evaporates, knowledge gets applied every time after.

WaypointsX keeps a supplier library alongside every trip: notes, rate sheets and documents attached to the supplier record, and the assistant draws on it automatically when it drafts a new itinerary, so what you learned on the last trip to a destination shows up, tagged as library knowledge, on the next one. See how it fits into drafting on the assistant page.